C/C++ DevTools Support (DWARF)
Extension Actions
CRX ID
pdcpmagijalfljmkmjngeonclgbbannb
Status
- Extension status: Unlisted
- Live on Store
Description from extension meta
DevTools Plugin for debugging C/C++ WebAssembly applications (using DWARF debug information). BETA version, use at your own risk.
Image from store
Description from store
Note: This is a BETA version of the extension and not the final product. Use it at your own risk. Please report any bug to https://bugs.chromium.org/p/chromium/issues/entry?template=DevTools+issue
This extension serves as an adapter between a WebAssembly app running in the browser and Chrome DevTools.
It enables developers to debug C++ applications, that are exported to WebAssembly in Chrome DevTools 89+ directly. Please not that this extension is only compatible with the latest Chrome Canary and Dev version.
Please make sure that your WebAssembly export is providing valid DWARF information.
Latest reviews
- Joachim Fosse
- I don't doubt for a second that this extension is extremely usefull, IF it works. The c/c++ files simpy fail to load: Could not load content for https://chrome.dev/devtools-memory-inspector/demo-cpp.cc (HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE). Seems like a known issue. Alle the official Google docs detailing the setup of wasm+dwarf debugging using this extension are seemingly also quite outdated. Pls fix 🙏 EDIT: Seems like the main issue is with googles example documentation. When debugging official emscriptem demos everything works as expected.
- Joe Eagar
- Absolutely terrible
- x86me
- This and memory inspector saved me a bunch of time on debugging wasm compiled c++. Thanks guys.
- Tomáš Mark
- Cool!
- Dario Lencina
- Broken
- Kristupas Stumbrys
- Worked, until Chrome version 133
- Dmitry Sabanin
- A life saver.
- Craig Macomber
- I used this with the chromium snap. The snap confinement prevented it from loading the source files so I had to force the snap into `--devmode` with `snap refresh --devmode --beta chromium && snap refresh --devmode --stable chromium` to work around that. That's a bit of a security issue since it disabled both updates and confinement, so use with caution! Once done, I was able to do source level debugging (break points, single stepping, viewing variables etc) of Rust code just fine, even on stable chromium.
- Francisco Javier Trujillo Mata
- Still is not able to demangle Swift symbols :(
- Gérald Guyomard
- A must have for debugging wasm/C++ code. Sometimes breakpoints stop to work and a full reboot of my machine fixes this.
- Борис Щец
- it worked perfectly about a year ago, but now it really does work like 5% of the time. I think it has something to do with rebuilding the project it tries to debug, maybe some cache misalignment
- Harutyun Tagushyan
- Randomly loading or not loading debug info. Sometimes other extensions causes the issue.
- Adam Leggett
- Only works at seemingly random times.
- Alexey Andreev
- Buggy and does not support even simple cases. Irresponsive development team that does not care of product quality at all
- Andre Kohn
- Indispensable for debugging more complex projects.
- Jasper Hugunin
- Works as advertised, helped me track down a bug.