> When Delve compiles your program for you it passes `-gcflags="-N -l"`,
> which will produce a binary that's more suited for debugging. If you need
> to use `dlv exec` over `dlv debug`, you can build your binary using that
> flag and you should have a better experience.
>
Thanks for the tip :-)
>
> But I found it hard to debug a Go program not started by delve itself.
>
When Delve compiles your program for you it passes `-gcflags="-N -l"`,
which will produce a binary that's more suited for debugging. If you need
to use `dlv exec` over `dlv debug`, you can build your binary using that
I use vi and command line a lot as well, but for some tasks like debugging,
a good IDE is of great help. All you have to do is to click at the left
margin of your source code to create a breakpoint and press F5 to reach
there. It is almost too easy.
As far as I know, VSCode is not able to use d
After I installed 1.8 I deleted my GOPATH environment variable, but VSCode
didn't like that, so I created GOPATH variable again, this time pointing to
%USERPROFILE%\go
While I were at it, I extended my PATH variable to include the bin from
GOPATH
%USERPROFILE%\go\bin
Don't forget to drop dlv.
Hi JuciE,
> Nyah, there are several IDEs capable of controlling Delve under the hood
>> to debug Go programs. It works nicely.
>> If you are used to Visual Studio you will feel in home with VSCode. Even
>> shortcuts for debugging are the same.
>>
>>
I can't say much about IDEs since I don't reall
I tried delve with VSCode, and had a problem with GOPATH. For some reason
the debugger saw a GOPATH that was different from the one set in the
environment or VSCode settings.
Anyone have any input on this?
On Wednesday, March 1, 2017 at 6:18:43 PM UTC-5, JuciÊ Andrade wrote:
>
> Nyah, there are
Nyah, there are several IDEs capable of controlling Delve under the hood to
debug Go programs. It works nicely.
If you are used to Visual Studio you will feel in home with VSCode. Even
shortcuts for debugging are the same.
On Wednesday, March 1, 2017 at 4:32:09 PM UTC-3, Nyah Check wrote:
>
>
>
>
> Great! Hope it continues to work for you. We're constantly working to
> improve the debugging experience for Go, so feel free to reach out via our
> mailing list or Github if you run into any issues or have any ideas for
> improvement.
>
>
Will do
--
You received this message because you are
