4 ms·
This is the highest and most important thing I want from go. A proper debugger that is not insanely hard to setup ( on any machine! ). Gives a complete stack tr
by ganarajpr 12y ago
This is the highest and most important thing I want from go. A proper debugger that is not insanely hard to setup ( on any machine! ). Gives a complete stack trace and such info. I am not sure how people can live without a debugger in 2014. GDB is not the answer to this - for sure. There are soo many things that can be done ( tooling wise! ) and this one is , I personally think, the first things the golang guys need to do .
- cjslep 12y agoHave you tried debugging using LiteIDE? I've had mixed experiences with it, most of the time I end up using fmt anyway.
- LukeShu 12y agoWhy do you say that GDB is not the answer? In my experience, GDB (and DDD) works great with Go!
- ganarajpr 12y agoYou are probably pretty awesome at setting things up. I am not. I tried GDB, golang and windows as a combination and its an exercise in torture.
- LukeShu 12y agoThat's true, I am great at setting things up... but Go+GDB was zero set up. `go build` then `gdb ${executable_file}`, and nothing else. I suspect that it's Windows being in the mix that gave you trouble?
- lprez 12y agoIn Mac at least you can't just do that, you need to create yourself a certificate and sign GDB. Took me a while too.
- module0000 12y agoJust an FYI, you can use MacPorts to `sudo port install gdb`, and it installs gdb as 'ggdb' without the signing mess. To use with ddd invoke as `ddd --debugger ggdb` and it works like a charm.
- lprez 12y agothank you!