WebAssembly Debugging Demystified
summary
Explains how to get line-level stacks out of wasm: DWARF debug file format and Source Maps enable original filenames and line numbers, browser DevTools then set breakpoints and show scopes, the webassembly binary toolkit decompiles and interprets binaries to find logic bugs, a demo edits the text-format and reassembles it to fix a Fibonacci bug, memory leaks get diagnosed with Memory Inspector in Chrome and heap dumps, and production symbolication uses wasm-split and Sentry to upload debug files.
AI-written summary · about
chapters (9)
- 0:00WebAssembly debugging intro
- 1:46DWARF and Source Maps
- 3:56Browser DevTools for WASM
- 4:17Advanced WABT debugging
- 6:45Memory leaks in WASM
- 8:08Release binary prep
- 9:12Debug data with Build IDs
- 10:55Production exception monitoring
- 11:17Q&A on non-browser WASM
related talks
09mDebugging WebAssembly with modern tools
46mWebAssembly (Digging a bit deeper)
26mNavigating Strategies for Debugging WASM
24mNo More Printf: Interactive Debugging Wasm for web and server
32mWebAssembly Demystified
37mDecoding the hype behind WebAssembly: Looking under the hood
25mBehind the Scenes: Debugging Kotlin/Wasm
52mWebAssembly: Taking Your C++ and Going Places
