Returning to the case of building of the qtwebengine with the debug option - even 32 gb is not enough for it, and at least 64 gb will be needed. Everything hungs at the linking stage now. And even if the mold linker may still help for linking using gcc12 then the final binary file still cannot be used for debugging since the size of .so file is 4gb, that is extremely large for built-in Haiku debugger. In this case gdb 10.2 could be a salvation and it was even compiled a year ago by cocobean:
But seems it needs Haiku-specific kernel debugging interface, that is probably was not implemented yet. Also rr debugger exists, but it need be ported first. Anyway we need to produce an experimental build on the system with 64-128 Gb of ram and try to get debug output from the compiled binary. @Munchausen has 128Gb machine on demand so if someone could install Haiku on it, compile qtwebengine with the mold linking and check how the executing of the binary will affect the built-in Haiku debugger, it would be great, and I think this is the only thing we can do at the moment for understanding where the qtwebengine falls - is it JIT or css parser stage. The sources with patch are located here: