delve

IMO: very much still half broken. Calling functions is still experimental[1] and in my experience has yet to work even once, there's no display formatting options (afaik) so you are often looking at a chunk of bytes instead of something useful (after diving several times more layers deep than other debuggers require), and you pretty often can't view memory that's in scope at another call stack location without going to that location. All of which gives you a pretty crippled experience, especially as it makes conditional breakpoints extremely limited in use. That said, it's mostly just half, before it was like 3/4 or worse. It has improved in stability (I haven't had it randomly disconnect at all since late Go 1.9 days, but I haven't pressed it hard at all either) and GoLand's integration works well and is mostly fast. It just can't do

I think the closet Go equivalent of 'byebug' would be delve[0]. It's got more of a learning curve than a REPL, but very powerful. Editor plugins for Go also tend to have good convenience support for delve, making using it less painful. For example, vim-go[1]. [0]: https://github.com/derekparker/delve/blob/master/Documentati... [1]: https://github.com/fatih/vim-go/blob/master/doc/vim-go.txt#L...

Huh? https://github.com/derekparker/delve integrates nicely with many editors, including [1] and [2] and allows you to do exactly that. 1 - https://www.jetbrains.com/go 2 - https://github.com/Microsoft/vscode-go

The debug story in Go is fairly decent these days for Linux, using Delve (the main "debugging" thing): https://github.com/derekparker/delve Apparently Delve supports Win and OSX/macOS too, though I've not tried it on those in years. On BSD though... there's no debugging story. :(

Delve only works on Linux, OSX, and Windows. Not at all on *BSD. ∙ Delve works "ok-ish" on Linux. Sometimes breakpoints don't fire (for me), but generally it's mostly usable. ∙ Windows and OSX both have issues with (at least) cgo code. ∙ The lack of BSD support is just because no-one's contributed the native bits yet: https://github.com/derekparker/delve/tree/master/pkg/proc/native So, it'll probably get done at some point in the future. As an example of the problems, a basic search on the Jetbrains issue tracker for Gogland (which includes Delve) shows many, many, many bugs filed. https://youtrack.jetbrains.com/issues/GO?q=debugger eg breakpoints not firing, variables being shown outside their scope, variable names being incorrect, debugging session just hanging (etc) That being said, the problems are getting looked at and fixe

Delve and the VSC integration is great. Just note that it's historically been quite buggy and unstable. Worse, for a long time it wasn't practically possible to use Delve on macOS due to changes introduced in 10.12 [1] [2]. It should be better now, though. [1] https://github.com/derekparker/delve/issues/645 [2] https://github.com/aaronhackney/delve_on_mac/blob/master/REA...

there is a debugger for Go https://github.com/derekparker/delve you can step through things and print stuff out

Nothing is better than Gogland or their (JetBrans') plugin for IDEA. You can also try https://github.com/derekparker/delve

Have you tried out Delve? https://github.com/derekparker/delve I've only used it for simple cases, so I don't know if it helps with your criticisms, but it was designed for Go. I mention this because it seems like many gophers aren't aware of Delve.

> debugging is way harder. Hope you like printf. You have other options: https://github.com/derekparker/delve

Precompiled binaries for OS X are coming: https://github.com/derekparker/delve/issues/494

0. It does dynamic linking on most stdlibs (libc, etc) 1. What do you mean self-hosted runtime? Anyways, golang will likely never be a good candidate for kernel development, but in theory you could do it (go supports assembly) 2. Generics would be nice. Who knows, maybe they'll be in 2.0? Go wasn't developed in llvm, because they wanted to build something very fast, and they were planning on writing the compiler in golang from the start (so that it could be part of the libs). Also having your own scheduler kind of breaks debugging, you can build go programs with gccgo, but gdb doesn't work because it has no concept of what a "go routine" is. Delve (https://github.com/derekparker/delve) will eventually fill the hole of the missing debugger, imo. Edit: Formatting

>so is debugging Have you used delve? https://github.com/derekparker/delve

Delve is an open source debugger for go. And many editors can work with delve such as Visual Studio Code. There is an animated gif of the debugger on the vscode-go page. https://github.com/derekparker/delve https://github.com/Microsoft/vscode-go