Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

environment vars under Test #35

Closed
eduncan911 opened this issue Jun 23, 2016 · 3 comments
Closed

environment vars under Test #35

eduncan911 opened this issue Jun 23, 2016 · 3 comments

Comments

@eduncan911
Copy link

eduncan911 commented Jun 23, 2016

Thank you for the integration with Atom. Though I haven't needed a debugger for Go for years, today is the day I take on a huge unknown codebase and immediately need to debug/follow-through some failing tests.

How would one set environment variables to debug under Test? I need to set a number of CLI environment vars for the integration tests.

I see a textbox under the TEST and DEBUG tabs that says "arguments passed to delve after --". Looking at the delve CLI docs, I didn't see a way to specify environment variables though.

@lloiser
Copy link
Owner

lloiser commented Jun 23, 2016

Unfortunately this is not possible yet...
But you could set them in the your terminal and launch atom from there so atom (and therefore dlv) inherit the same environment variables.

@eduncan911
Copy link
Author

Hey, that kinda worked! (setting env vars and launching Atom). though i can see the breakpoint hit in the Goroutines list (shows the line number it stops on while highlighting the method I put a breakpoint into), it doesn't show any vars and it doesn't allow me to step into.

Is Debugging supposed to allow stepping into? May just be the complexity of the project and packages that it delve is having issues with.

Thanks! Will close.

@lloiser
Copy link
Owner

lloiser commented Jun 23, 2016

it doesn't show any vars and it doesn't allow me to step into

no variables? not able to step into (using the button in the panel or F11)? this sounds like a bug! do you see any errors in the developer tools in atom (alt-ctrl-i on win, alt-cmd-i on mac)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants