Be Smug, Debug Why You Should Be a Delve Power User
summary
Shows how Delve debugs web servers, tests, Docker containers and remote processes with concrete commands and configs: use -gcflags "-N -l" when building, run a headless Delve with headless debug server and fixed port 40000, attach via Delve or VS Code using a checked-in launch.json configs. Demonstrates trace vs log points, debug scripts (Starlark), fixing missing sources with substitutePath mapping, and automating Docker startup with VS Code prelaunch tasks so the setup actually works end-to-end.
AI-written summary · about
chapters (16)
- 0:00Introduction to debugging
- 1:23Why use a debugger
- 2:21Core debugging features
- 3:23Advanced breakpoints
- 4:19Delve scripts
- 5:58Debugger setup overview
- 7:21CLI vs GUI debugging
- 8:40Simple local debugging
- 10:20VS Code configuration
- 13:26Debugging Go tests
- 14:43Tracing and logging
- 16:57Debugger architecture
- 18:24Attaching to processes
- 21:57Remote debugging
- 25:49Debugging Docker containers
- 32:48Automation and conclusion
related talks
06mIGNITE: Swiss knife for Go debugging with VSCode
07mDebugging Go Code in VS Code
39mDebug Now! Zap bugs out of PowerShell
01h 00mUnleash the Power of VS Code
43mDebug Like a Scientist!
23mDebug Like a Detective
01h 01mBeyond step-by step debugging in Visual Studio
33mEssential JavaScript debugging tools for the modern detective