I use mostly Printf-based debugging, and still find delve useful at times.
Primarily when I'm not sure exactly where in my code a bug arises, so I'll
set a couple breakpoints, step through some code, and sometimes find I need
to add some debug output in the problem area. If delve had more outp
This is not meant to be snide or flippant. Go actually made me learn Printf
based debugging, and I am a much better debugger for it.
Add fmt.Printf() to your code. Or use a shortcut function like PP(), which
will automatically show where it was called from to. I use
a file like vprint.go in all
On Thursday, 8 March 2018 12:32:42 UTC-4, Parthasarathi Kundu wrote:
>
> Hi,
> How can I debug the unit tests in go ? Normal executible I debug with gdb
> or delve.
> I am running from command prompt go test -v ./test/... -run Test_Connect.
>
> Any thing better with ide ?
>
> Thanks
>
>
I use delv
