4 ms·
You can debug the original code by providing a map file (compiler generated) that allows you to let the WebAssembly runtime know how to map WASM bytecode to the
by speps 3y ago
You can debug the original code by providing a map file (compiler generated) that allows you to let the WebAssembly runtime know how to map WASM bytecode to the source code. It works really well.
- flohofwoe 3y agoThe old source-maps-approach never worked all too well. Emscripten can generate DWARF debug info for a while now, and there are extensions for Chrome and VSCode which make use of this DWARF debug information and allow for a much better debugging experience. E.g. see here: https://developer.chrome.com/blog/wasm-debugging-2020 https://developer.chrome.com/blog/wasm-debugging-2020 ...and here...: https://marketplace.visualstudio.com/items?itemName=ms-vscode.wasm-dwarf-debugging https://marketplace.visualstudio.com/items?itemName=ms-vscod...