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 system panic). I simply find using a debugger less efficient on "live" programs where I can afford to run the program multiple times.
On Thu, Feb 2, 2023 at 6:51 PM Pat Farrell <pat22...@gmail.com> 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 level debugger. > > Any recommendations? > I guess I could use an IDE if that it popular, I'm kinda old > school and just use vim > > Thanks > Pat > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/5f9a909c-ef29-4669-b1bd-b2dd941f03f2n%40googlegroups.com > <https://groups.google.com/d/msgid/golang-nuts/5f9a909c-ef29-4669-b1bd-b2dd941f03f2n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Kurtis Rader Caretaker of the exceptional canines Junior and Hank -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CABx2%3DD8%2ByVrE%2B0%2BF%3Du16yGu30dbOqd47fRgOsEdJaaKXFLm55A%40mail.gmail.com.
