service/dap: supports noDebug launch requests (#2400)
If the launch requests has noDebug attribute set, run the built binary directly. The launch request handler will block until the binary terminates, so the editor won't send additional requests like breakpoint setting etc. Still disconnect or restart requests can flow in though and they should trigger killing of the target process if it's still running. In order to run the binary using os/exec on windows, the target binary has to have .exe as its extension. So, add .exe to the default output name if it is on windows. I am not sure though yet we want to modify the user-specified output or not yet. Considering how go commands behave (not automatically append .exe for 'go build -o') I think respecting what user specified is right, but the failure (file not exist) may be mysterious.
Showing
想要评论请 注册 或 登录