Debugging Go from the Command Line

Presentation: So there you are all ssh'd into a remote machine running a misbehaving Go binary that you need to fix. How do you start to figure out what's wrong? There's no graphic UI much less an IDE. Sure wish you'd taken some time to look at Delve, don't you?

Well, let's just get all proactive and take that look before you need it. This talk will first cover what makes Delve so much more suitable for debugging Go than other command line debuggers. It then covers the basics of using Delve to attach to a running process and how to look around. Finally, there will be a brief introduction on how to produce and evaluate a core dump on Linux for a Go application that panics.

You probably should have looked at tmux, too, but that won't get covered tonight.

Presenter: Charles Sharp is a Principal Software Engineer at Object Computing, Inc.(OCI), a leading software engineering firm providing consulting for software architecture, design, and implementation. He's been not-so-happily debugging various languages with Unix and Linux command line debuggers for over thirty-five years. Sooner or later he's going to quit fixing other people's code.

We'll start the pizza around 6 then intros around 6:20 - 6:30. A few minutes of something interesting in the Go world, then the presentation. We typically wrap up around 8 but the room will be open for a while so feel free to hang around a bit and visit.