PS: What I *usually* do however is just debug a native build of my code in VSCode, Xcode or Visual Studio, having a debugger right under your 'fingertips' during development is still much more convenient than debugging in the browser IMHO - now if VSCode could somehow remote-connect to the Chrome debugger also for WASM code that would be the icing on the cake, but I couldn't get this to work for plain Javascript ;)
On Thursday, 25 August 2022 at 14:14:09 UTC+2 Floh wrote: > It should definitely work on Vanilla Chrome, but setting everything up can > be a bit finicky: > > - install the Debugging extension: > https://chrome.google.com/webstore/detail/cc%20%20-devtools-support-dwa/pdcpmagijalfljmkmjngeonclgbbannb > - in the Dev Tools settings, search for 'WebAssembly Debugging' and check > that box > - compile your code with '-O0 -g' (no optimization, and debug info enabled' > - IMPORTANT: in the Chrome debugger, there's a 'Filesystem' tab on the > left side which is very easy to miss. Here you need to navigate to your > project directory and allow Chrome to access that area of your filesystem. > > (I think/hope these are all steps) > > When you load your application you should see something like this on the > Dev Tools console: > > [C/C++ DevTools Support (DWARF)] Loading debug symbols for > http://localhost:8080/cube-sapp.wasm... > [C/C++ DevTools Support (DWARF)] Loaded debug symbols for > http://localhost:8080/cube-sapp.wasm, found 91 source file(s) > > ...and if everything works it should look roughly like this in the > debugger: > > [image: Screenshot 2022-08-25 at 14.08.17.png] > On Wednesday, 24 August 2022 at 01:56:12 UTC+2 [email protected] wrote: > >> It seems I missed something about the plugin that was important, which is >> that it seems to be designed to run only on the Canary builds of Chrome. I >> went to get the Canary build but it says right on the front page "Linux is >> not supported." Anyone aware of any other way to debug emscripten besides >> Chrome Canary? Anything like the Chrome plugin for Firefox or other >> browsers? The plugin still works on the production version of Chrome except >> for the fact that you can't see the identities of your variables which is a >> pretty critical failing at this point. I can at least stop using printf >> statements just to determine if a certain function or section of code is >> running though. >> >> >> On Fri, Aug 19, 2022 at 11:00 AM 'Sam Clegg' via emscripten-discuss < >> [email protected]> wrote: >> > >> > Indeed, source-map only give you line level debugging (i.e. not >> variables or parameter values), but work in all browsers. >> > >> > Full dwarf debugging (-g) requires the chrome extension. I thought >> that you must have that already installed since I'm not sure how you would >> even set a breakpoint without that working. >> > >> > On Thu, Aug 18, 2022 at 11:36 PM Sebastian Theophil <[email protected]> >> wrote: >> >> >> >> IIRC for source level breakpoints you need to enable the experimental >> support for dwarf debugging in chrome >> >> >> >> https://developer.chrome.com/blog/wasm-debugging-2020/ >> >> >> >> Von meinem iPhone gesendet >> >> >> >> Am 19.08.2022 um 06:28 schrieb Gregory Propf <[email protected]>: >> >> >> >> >> >> I also tried it with "emcc debugtest.cpp -gsource-map >> --source-map-base=http://localhost:6931/ -o debugtest.js" >> >> In this case the breakpoints actually are being honored but the >> variables are all just identified as $var1, $var2, etc... I've seen this >> before when trying to debug ClojureScript and eventually abandoned the >> effort because it wasn't that useful, particularly with complex data >> structures where I really needed the names of the structure members. >> >> >> >> On Thu, Aug 18, 2022 at 5:02 PM 'Sam Clegg' via emscripten-discuss < >> [email protected]> wrote: >> >>> >> >>> Can you make it work with a simple hello world program compiled >> without optimizations? If not it sounds like maybe a bug in either >> toolchain or in the debugger plugin. >> >>> >> >>> If you can't set a breakpoint in a simple hello world program can you >> open a bug, and please include the full command line and full program you >> are using. >> >>> >> >>> cheers, >> >>> sam >> >>> >> >>> On Thu, Aug 18, 2022 at 3:52 PM Gregory Propf <[email protected]> >> wrote: >> >>>> >> >>>> Hello everyone, first post here and a simple (but aggravating) >> problem - No matter what combination of -g flags or other command line >> tricks I use I cannot seem to get Chrome to allow me to step through my C++ >> code. I can add the CPP files and even set breakpoints but the program does >> not stop for them. I'm doing this on Ubuntu 22.04 with the latest version >> of Chrome. >> >>>> >> >>>> -- >> >>>> You received this message because you are subscribed to the Google >> Groups "emscripten-discuss" group. >> >>>> To unsubscribe from this group and stop receiving emails from it, >> send an email to [email protected]. >> >>>> To view this discussion on the web visit >> https://groups.google.com/d/msgid/emscripten-discuss/02e05a34-f383-4e39-b051-ff7bdb3ae1c9n%40googlegroups.com >> . >> >>> >> >>> -- >> >>> You received this message because you are subscribed to the Google >> Groups "emscripten-discuss" group. >> >>> To unsubscribe from this group and stop receiving emails from it, >> send an email to [email protected]. >> >>> To view this discussion on the web visit >> https://groups.google.com/d/msgid/emscripten-discuss/CAL_va2_eNCJj_9qnzJfJrYpwkzzLQrVzd-kOnXT2GGB45Mi5Xg%40mail.gmail.com >> . >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups "emscripten-discuss" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> an email to [email protected]. >> >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/emscripten-discuss/CAKdUWHO3ahfPE-31Sj22WiRRuMuyy9E9UNvN93D%2B0dVmz-vkuQ%40mail.gmail.com >> . >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups "emscripten-discuss" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> an email to [email protected]. >> >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/emscripten-discuss/7AE81AD1-3532-47B4-B401-16164233AB25%40gmail.com >> . >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "emscripten-discuss" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/emscripten-discuss/CAL_va2_UC4m_re92Ar%3DxzsbGtG21sauEa-72CgvNKwK1Xv5cRw%40mail.gmail.com >> . >> > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/039eae52-b0c4-4eac-ac98-4e0c226b489fn%40googlegroups.com.
