No More Printf: Interactive Debugging Wasm for web and server
summary
Claim: interactive step‑through debugging for WebAssembly components actually works end to end. Concrete setup shows lldb for native WebAssembly modules and a SpiderMonkey‑based runtime with componentized JS plus a VS Code debugger extension to hit breakpoints hit inside components, use an outgoing socket connection for the debugger, and step through JavaScript without DWARF or turned‑off optimizations. The demo builds with Wasmtime or a Node shim, connects back to VS Code, and runs in production builds with no debug symbols needed.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:09Debugging with Rust and VS Code
- 6:10JavaScript in Wasm differences
- 10:28Debugging with Starling Monkey
- 15:30Live demo: JavaScript debugging
- 19:37Universal debugging across runtimes
- 21:27Future steps
- 22:33Next goals
related talks
09mDebugging WebAssembly with modern tools
13mWebAssembly Debugging Demystified
26mNavigating Strategies for Debugging WASM
10mLightning Talk: Implementing Wasm Debugging with .net in vscode
46mWebAssembly (Digging a bit deeper)
41mDemystifying WebAssembly, Through the Eyes of A Beginner
31mThe CPU in your browser: WebAssembly demystified
31mZero Install Embedded CC++ Development Running GDB in the Browser with WebAssembly
