Qt, Linux and everything: Debugging Qt WebAssembly
Posted by speckx 10 hours ago
Comments
Comment by N_Lens 6 hours ago
What makes this particularly interesting is the technology stack: Emscripten embeds DWARF debugging symbols (the same format used for native Linux binaries) directly into WebAssembly binaries. A Chrome browser extension then reads these embedded symbols and reconstructs the original C++ source code view in the DevTools, mapping the compiled WebAssembly back to your Qt C++ source with full directory paths intact.
All of this would have seemed impossible not long ago.
Comment by nottorp 22 minutes ago
So it doesn't work in any other browser? More incentive for those web 4.0 or 5.0, i lost count, "experts" to only support Chrome?
Comment by irishcoffee 7 hours ago
Debugging wasm qt apps is not hard at all. Yes, as the article says, you need to build the code in debug mode, this isn’t unusual.
If you use qtcreator, it’s, and I hate this word, trivial. Most of the work comes from setting up the qt kit in qtcreator… which takes about 5 minutes.
Breakpoints just work. Debugging just works. Everything… works.
Comment by N_Lens 6 hours ago
Comment by nottorp 23 minutes ago
Comment by irishcoffee 6 hours ago
Comment by em3rgent0rdr 9 hours ago
Comment by bionsystem 8 hours ago
This is the kind of thing that I feel is very nice and terrible at the same time. Yes it is convenient but it is also such a complex piece of software, it's sad that it is required to run gui apps. Ok, it may not be required yet per say, but I have mixed feelings about this direction.
Comment by mkoubaa 8 hours ago
Comment by oblio 8 hours ago
Comment by torarnv 7 hours ago
We've tweaked our styles to take the new design metrics into account, and fixed or worked around issues where we've seen them. We don't integrate with NSGlassEffectView and friends yet. If you find any issues in recently released version of Qt 6.10, 6.8 or 6.5, please report them upstream, thanks!
Comment by rubymamis 7 hours ago