Hi Rob, I'm currently writing some documentation on how to Debug Docker binaries; given the fact that it's a large project gdb doesn't seem adequate for a newbie looking to contribute to the Docker project. Most Gophers I've talked to have recommended delve as the debugger to go with such cases. Just looking for other options.
Thanks, Nyah On Tue, Nov 15, 2016 at 4:02 PM, Rob Pike <r...@golang.org> wrote: > Debugging is always hard, debuggers help, and better debuggers help more. > I have had good luck with delve, myself. Perhaps if you explained the > problem you're having there would be suggestions to make your task easier. > > -rob > > > On Mon, Nov 14, 2016 at 11:55 PM, Nyah Check <check.n...@gmail.com> wrote: > >> Hi Gophers, >> >> I know this post is old and there's a lot online with different sometimes >> contrasting opinions on how to debug go programs. My question given the >> complexities involved in multi-threading in Go does the go team have any >> plans on creating a standard debugger. I'm currently looking at delve and >> gdb(although inadequate). What's the best way of debugging go programs so >> far. I know some may say use intelligently placed fmt.Printf() statements. >> Just looking for more ideas. >> >> Thanks, >> Nyah >> >> -- >> 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. >> For more options, visit https://groups.google.com/d/optout. >> > > -- "The heaviest penalty for declining to rule is to be ruled by someone inferior to yourself." --*Plato* -- 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. For more options, visit https://groups.google.com/d/optout.
