nokotan / cdp-gdb-bridge

Debugger of WebAssembly on Chrome

WebAssembly on Chrome Debugger

WebAssembly Debugger for Google Chrome, node.js

CLI

Install

npm i cdp-gdb-bridge

Usage

# Launch Chrome & Debugging Proxy
> cdp-gdb-bridge

# And then, open the debugged url in launched chrome.
Page navigated.
http://localhost:8080/index.wasm
Start Loading http://localhost:8080/index.wasm...

# Now you can use debug commands like gdb
> b Main.cpp:10

Supported Commands

Syntax
r (url)	Jump to url
b (FileName):(LineNumber)	Set Breakpoint
d (breakpoint ID	Delete Breakpoint
n	Step-Over
s	Step-In
u	Step-Out
c	Continue
l	Show Source File around Current Frame
il	Show Local Variables Name
ig	Show Global Variables Name
p (VariableName)	Evaluate Variable

VSCode Extension

Implemented Features

• BreakPoints
• Variable Value Inspection

Support Status

	Windows	macOS	Linux	Support Version
node.js	✅	✅	✅	v16.0+, no workers debugging support
Chrome	✅	✅	✅	v64+
FireFox	❌	❌	❌
Safari	-	❌	-
Edge	❌	-	-

cdp-gdb-bridge's Issues

Configuration to specify the Chrome profile

Would be nice if ew can specify in the vscode launch.json a setting to set the Chrome profile to load when launching the wasm-chrome debugger mode. It seems Chrome Laucher library already have a setting for that purpose:

// (optional) Chrome profile path to use, if set to `false` then the default profile will be used.
// By default, a fresh Chrome profile will be created
userDataDir: string | boolean;