-
Notifications
You must be signed in to change notification settings - Fork 645
Process starts but does not completely attach #2783
Comments
Please share the debug configuration you are using. |
This was caused by using --ldflags "-s" in the build args. I am running someone else's code and was told to include this directive. The program does not compile without several others. From searching around on delve and running the program outside vscode, I've learned what this flag does and why it would cause debugging to fail. The issue with vscode is that everything looks fine. Breakpoints look fine. The debug starts up. Logs flow to output. The debugger console even accepts input, although nothing works. I would change this issue to a feature request to indicate that symbols are not properly loaded. In Visual Studio we get the empty red ring rather than the solid dot if the symbols cannot be matched up. Whether it is that or some other indication that things are not right is fine. Just something to point people in the right direction. While I'm at it. I'd like to be able to use the delve command line directives and see the goroutines. Thank you, |
Sorry for the delay on this issue. To summarize your comment:
@ramya-rao-a, @hyangah, @quoctruong: (1) seems reasonable enough to me (and hopefully is trivial to implement?), but I'm not sure what (2) would entail. |
I copied (1) to golang/vscode-go#182, as we are moving to a new repository (#3247). If you would like to discuss (2) more in-depth, please file a feature request in our new repo: https://github.com/golang/vscode-go. |
My process starts, but does not seem to attach. Breakpoints are not hit and all debugger console commands return "not available". Logs follow
The text was updated successfully, but these errors were encountered: