You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While #2958 discusses a bigger refactoring work, we want to clear all breakpoints/logpoints before disconnecting.
Related: #1961
We were told Goland explicitly issues the ClearBreakpoints command before exiting, which I think is a good default behavior.
For users who really want to keep the debug target running with breakpoints set, if any, we can consider this as a launch attribute optionally, but IMO that's unusual case.
Ah, should have added my update here, not at #2958 (comment).
But basically last time we had a vscode-go/delve group chat about this, I was sort of pushing for clearing (because it would make the async logic covered in #2958 soooo much simpler), but the consensus was that we need to give users the flexibility both ways with an option to do either (keep or clear). Time to revisit that decision? :)
Spin-off from #2958 (comment)
Original feature request: golang/vscode-go#2368
While #2958 discusses a bigger refactoring work, we want to clear all breakpoints/logpoints before disconnecting.
Related: #1961
We were told Goland explicitly issues the
ClearBreakpoints
command before exiting, which I think is a good default behavior.For users who really want to keep the debug target running with breakpoints set, if any, we can consider this as a launch attribute optionally, but IMO that's unusual case.
cc @suzmue @polinasok
The text was updated successfully, but these errors were encountered: