Derek Parker explains the internals of the Go runtime and how the Delve debugger works under the hood to debug Go applications.
Speaker : Derek Parker (CoreOS)
Debugging Go can be a difficult task, especially with traditional debuggers such as 'gdb' or 'lldb'. The language has a lot of powerful features which while incredibly useful, can make debugging tough problems tricky. In this talk I will begin by introducing Delve, a Go-specific debugger. Following the introduction I will discuss what makes Go different from other languages, how Delve is different from other debuggers, how it works, and how you can use it to debug your own Go programs.
To explain what makes Go different from other languages, I will take a deep dive into the Go runtime, and other aspects of Go that set it apart and, consequently, can make it difficult to debug. From there I will explain the internals of Delve and how it works under the hood. Finally, I'll talk through how to use Delve to help fix difficult bugs in your own Go code.
This talk will be very beneficial for beginner to expert Go programmers.
Why it's here
1 person recommends this
What people say. Recommended for understanding how Go debuggers work and how Delve compares to traditional debuggers.
g
u/gilescopein r/rust • Recommends
On “A Future for Rust Debugging”
Here’s a talk about the go debugger ‘Delve’ that seems to be written in go and used in all their IDEs:
link to this video
It seems by wrapping lower level debuggers they can switch between lldb, gdb and even rr to enable time travelling debugging.