https://github.com/glycerine/vprint shows you how to get
source file and line numbers (and timestamps) automatically
in your PMD print statements.
For examples, I use vv() or VV() for unconditional prints, and pp() or PP()
for condition prints that only print if Verbose is true. Debuggers ar
On Thursday, February 2, 2023 at 10:49:40 PM UTC-5 Ian Lance Taylor wrote:
Have you tried Delve? https://github.com/go-delve/delve
Thanks I will check into it.
One point about go and PMD, because the compile time is so fast, using PMD
is not nearly as painful as it
would be in other languages tha
On Thu, Feb 2, 2023 at 6:51 PM Pat Farrell wrote:
>
> I've been using PMD to debug my go code since I started.
> (PMD => Poor Man's Debugger, i.e fmt.Printf statements)
> and it was OK for my initial simple stuff. But as I am writing
> more complex code, I think its time to find a nice source leve
FWIW, I still use the Poor Man's Debugger most of the time to understand
the behavior of running programs where I can afford to iterate while trying
to understand a problem. Having said that I do regularly use an actual
debugger to examine core dumps (both user space and from a Unix operating
syste
I've been using PMD to debug my go code since I started.
(PMD => Poor Man's Debugger, i.e fmt.Printf statements)
and it was OK for my initial simple stuff. But as I am writing
more complex code, I think its time to find a nice source level debugger.
Any recommendations?
I guess I could use an IDE
