Qt, Linux and everything: Debugging Qt WebAssembly

Posted by speckx 10 hours ago

Counter59Comment15OpenOriginal

Comments

Comment by N_Lens 6 hours ago

What's interesting here is that you can now debug WebAssembly applications with full C++ source-level debugging directly in Chrome, complete with breakpoints, variable inspection, and step-through debugging, just like a native desktop app.

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

> directly in Chrome

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

I feel like this article is severely flawed.

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

I think you are disconnected from the pain of debugging in the past. The fact that it all works so seamlessly together now is a bit fascinating and astounding.

Comment by nottorp 23 minutes ago

Well anyone who worked on native apps has had seamlessly working debuggers for ages :)

Comment by irishcoffee 6 hours ago

I am not at all disconnected, but I understand why you might say that.

Comment by em3rgent0rdr 9 hours ago

Very useful. It would be great for the browser become the cross-platform application target. I've been eagerly waiting for Qt WebAssembly to mature.

Comment by bionsystem 8 hours ago

> It would be great for the browser become the cross-platform application target.

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

Maybe not the browser per se, but a WASI runtime

Comment by baudaux 7 hours ago

Or both the browser and wasi. As I am doing with exaequOS

Comment by mkoubaa 5 hours ago

I think this kind of thing could be really useful for a project I'm building.

Comment by baudaux 25 minutes ago

What is your project ?

Comment by oblio 8 hours ago

Is anyone using Qt for developing Mac apps these days? How is the integration after the recent Mac UI refresh?

Comment by torarnv 7 hours ago

Qt for macOS maintainer here.

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!

See also https://www.qt.io/blog/qt-on-macos-26-tahoe

Comment by rubymamis 7 hours ago

Yes! I'm developing my note-taking app[1] for macOS and now working on a mobile version.

[1] https://get-notes.com