Hi Christian,
I like how the debugging solution turned out so far with the simple Genode components which automatically download the debug packages in the background and dynamically create symbolic links to the symbol files of the monitored components for GDB by watching and evaluating the Sculpt runtime configuration.
I wholeheartedly agree! All the individual steps where so carefully planned and executed. It was wonderful watching how these foundations happened to also inspire Goa's recent debugging support, leveraging the downloadable symbols and the monitor component [1] to great effect.
[1] https://genodians.org/jschlatow/2024-07-31-goa-gdb
Now, what's admittedly left is to move our regular work flows more and more towards this powerful tooling.
So, for 2025 I'm planning to continue working on the Qt6 Falkon and Morph browsers and then it will probably be time for another Genode tool chain update. Apart from that I'm also interested in the topic of building Genode and Genode components natively on Genode, which Norman mentioned, and would help working on that.
That sounds like a solid plan!
I'm extremely grateful for your steady hand in the tool-chain topic.
Regarding your last point, I definitely plan to (re-)attend the problem of tracing of short-lived activities, which somewhat fizzled out last time we looked at it. Once this instrument is in place, chances will be good that we can jointly uncover the bottlenecks in the libc/vfs.
Cheers Norman