I wonder if the author had tried using Delve (https://github.com/derekparker/delve) to see if that is any better/more featured for the problems he was having.
Someone tweeted about it shortly after my post when live, Delve does look interesting and a lot more compatible with go in general, but there is significant appeal around being able to use a general debugging tool with go. It's the classic balance of solving a generic problem fairly well vs solving a simple problem very well.
I'll certainly be watching delve closely and using it myself! I am sure I'd have better luck having specific go issues resolved with the delve team since it's a focussed project.
Check out Derek Parker's talk from GopherCon 2015. He provides specific reasons gdb has difficulties with debugging Go programs, and why a tool which specifically understands how Go functions is needed. https://www.youtube.com/watch?v=InG72scKPd4
4 comments
[ 3.0 ms ] story [ 23.4 ms ] threadI'll certainly be watching delve closely and using it myself! I am sure I'd have better luck having specific go issues resolved with the delve team since it's a focussed project.