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
{{ message }}
This repository was archived by the owner on Jul 15, 2023. It is now read-only.
When a debug session panics, Delve will show a code listing with a cursor at the panic with a "Command failed: XXX" message. You can then issue commands to get a backtrace, etc.
In VSC, a cryptic message "Failed to continue - XXX" is shown in the Debug Console and nothing else. It would be great if instead:
Move the editor to the relevant source line that panicked.
Show the call stack in the debugger pane. If that's too hard, at the very least please show the panic details in the Debug Console, including stack trace.
Instead of "Failed to continue", use a more descriptive "Debugger stopped after program failure: XXX". (The first time I encountered this I thought it was a debugger issue, rather than my code.)