Главная
Study mode:
on
1
Intro
2
A DEBUGGER FOR THE GO PROGRAMMING LANGUAGE
3
WHY A NEW DEBUGGER?
4
GDB MUST BE DESTROYED
5
WHY DOES GO CONFUSE EXISTING DEBUGGERS?
6
STACK MANAGEMENT
7
DEFER STATEMENTS
8
THREADS VS GOROUTINES
9
GO SCHEDULER
10
LET'S INTRODUCE THE CAST OF CHARACTERS
11
NON-TRADITIONAL EXECUTION MODEL
12
CONTEXT SWITCHES
13
Channel Operations
14
RUNTIME STACK INSPECTION
15
COMPILER OPTIMIZATIONS
16
Start debugging with Delve
17
Debug standalone packages
18
HISTORY OF DELVE
19
COMMANDS: CONTROL FLOW
20
Single step through program
21
COMMANDS: INFORMATIONAL
Description:
Explore the intricacies of Delve, a debugger specifically tailored for the Go programming language, in this GopherCon 2015 talk by Derek Parker. Dive deep into the unique characteristics of Go that make traditional debuggers unfeasible, such as the runtime scheduler. Learn why a new debugger was necessary for Go and how Delve aims to solve problems with existing debuggers like GDB. Understand Go's non-traditional execution model, including stack management, defer statements, goroutines, and the Go scheduler. Discover how Delve handles context switches, channel operations, and runtime stack inspection. Get insights into compiler optimizations and how they affect debugging. Learn to start debugging with Delve, including how to debug standalone packages. Explore the history of Delve and its various commands for control flow and information gathering, including single-stepping through programs.

Delve Into Go

Gopher Academy
Add to list