Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

When breakpoints that set inside init()s is hit, the IDE does not show which line the program is running to. And the callstack of the current go routine is empty. #2038

Closed
szmcdull opened this issue Oct 23, 2018 · 5 comments
Closed

When breakpoints that set inside init()s is hit, the IDE does not show which line the program is running to. And the callstack of the current go routine is empty. #2038

szmcdull opened this issue Oct 23, 2018 · 5 comments

Comments

@szmcdull
Copy link

Steps to Reproduce:

Sample code:
image

  1. Set a breakpoint inside init()
  2. Start Debugging
@szmcdull
Copy link
Author

Using the dlv command line debugger, I can successfully set a line breakpoint inside init() and debug just like normal.

@ramya-rao-a
Copy link
Contributor

This should be fixed with #2029

Can you try our latest beta-version

@szmcdull
Copy link
Author

szmcdull commented Nov 2, 2018

Great! After installing the beta-version, it works again. But 'Check for Updates' of Visual Code says server returned 502. Don't know if it is related to the beta-version?

@ramya-rao-a
Copy link
Contributor

The 502 error is not related to the Go extension. The update server for VS Code was down yesterday for some time. It should be up now.

@ramya-rao-a ramya-rao-a mentioned this issue Nov 5, 2018
Closed
@ramya-rao-a
Copy link
Contributor

The fix for this is now out in the latest update to the Go extension as well (0.7.0)

@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 17, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@szmcdull @ramya-rao-a