Warn users when debugging optimized binaries #1446
JadenSimon
started this conversation in
Discussions
Replies: 1 comment 2 replies
-
|
Sorry that I didn't see this earlier. Good idea. Not sure what is the best way to reflect this in the UI though. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
No worries. Glad to see it's being considered! |
Beta Was this translation helpful? Give feedback.
-
|
This feature is now available in the latest dlv (built at master). You can see it when using the dlv-dap mode. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Delve allows users to debug optimized binaries, however, when using the Delve client it will warn you that the function is optimized after hitting a breakpoint. This means the user is not confused when local variables are not what they expect (i.e. missing or invalid). The Go extension's DA makes no attempt at alerting the user that they might be debugging an optimized binary, causing a lot of confusion when debugging does not work as expected. This is especially true when remote debugging, as it may be up to an external process to do the compilation.
Beta Was this translation helpful? Give feedback.
All reactions