Use 2nd debugger - https://github.com/mailgun/godebug about go-debug

[lloiser]

I don't think that this solves the problem entirely because getting the sources only isn't enough. You also have to build them using make (see https://github.com/derekparker/delve/tree/master/Documentation/installation)

Although I already use https://github.com/joefitzgerald/go-config to find the dlv so this shouldn't be any problem anymore.

[joefitzgerald]

Ahh yeah, good call. I wonder if it would be worth also giving people an option of using godebug since it is go gettable? I know the feature sets don't match 1:1. but there is some shared functionality.

[lloiser]

Great idea, I will give it a try as soon as I have some free time to play with it a bit.

[lloiser]

Update: have to fork it as it seems pretty "dead" (last commit in September 2015...) and is not really easy to integrate yet...

[joefitzgerald]

/cc @jeremyschlatter - is godebug still being actively maintained?

[pkieltyka]

personally, -1 on https://github.com/mailgun/godebug .. its a nice idea, but I've never found it useful for any serious debugging.

[pkieltyka]

If the issue is getting this plugin to just plug-and-play, you could look at how IntelliJ pulls it off. Their go ide plugin supports delve right out of the box. I think they just package a pre-compiled binary with a cert for the system.

Otherwise, just link clearly to Delve install instructions until the Delve guys solve this issue

[batatababa]

Agreed on godebug not being good for serious debugging. I've been using it and it's better than nothing and quick to get going. It won't run if you have vendored dependencies which is a big deal.

[joefitzgerald]

Closing this, it appears godebug isn't actively maintained anymore. @jeremyschlatter, feel free to correct me if I am wrong.