-
Notifications
You must be signed in to change notification settings - Fork 797
debug golang cannot close with button unless kill it(__debug_bin) with cmd #1536
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@enjoycx Could you please include additional details in your report to help us diagnose the issue: such as your launch.json configuration, anything that got logged into the Debug Console (you can get additional information there with In general there could be circumstances where the debugger might get unresponsive, so the stop operation from the editor could timeout before the debugger/adapter shut things down gracefully and acknowledge the request. We try to catch such cases and forcefully kill delve. In the legacy adapter vs dlv-dap adapter it is done with different signals. The legacy adapter would leave the debuggee running when killed from the extension while the dlv-dap adapter should be able to shut things down correctly. So please do let us know which one you are using. And also if delve itself is still running when you close the debug session. |
the project remote run in docker launch.json
** first logs:**
second start logs:
|
@enjoycx Thank you for additional information. Looks like I provided the wrong flag earlier to enable all the logging. It should be "debugger", not "debug" - Is this easily reproduced? Does this happen often? Is dlv still running when the session is over? |
The first log is the log printed by the shutdown program, and the second one is the log printed by the startup program. Because it was not closed when it was closed, it couldn't get up the second time I guess it's the reason why I run in docker remotely, or the reason why many breakpoints in my program haven't been deleted I can't turn it off almost every time now. I need to use CMD kill |
@enjoycx It sounds like your experience is rather frustrating. And I am sorry about that. I sincerely do want to help, but sadly from your description, I do not fully understand what exactly you do and where things go wrong. Ideally, we look for a simple reproducible local test case to debug and diagnose problems. When that is not possible, a list of the exact steps that you follow in addition to the log would be quite helpful as well. I am not sure what you mean by "shutdown program" and "start-up program". It looks to me that you first launch a debug session that launches your http server on port 2619. Then you end the session and start a new one, which tries to start up the same http server on the same port 2619. Except the port is still in use, so the target and the session terminate. Is that correct? Additional information that would help:
|
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
No description provided.
The text was updated successfully, but these errors were encountered: