You are not logged in.
Oolite (opensource remake of Elite) devs & users are discussing how to improve debugging options in https://github.com/OoliteProject/oolite/issues/586
One of the options mentioned is using -gsplit-dwarf to create .dwo files which will then be combined into .dwp files.
gcc, llvm/clang, gdb, lldb and debuginfo.d appear to support both dbg & dwp formats.
What do you see as pro & cons of these methods ?
Could archlinux packages be build with -gsplit-dwarf or would that require changes in pacman/makepkg ?
Last edited by Lone_Wolf (2026-05-02 11:27:26)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
What do you see as pro & cons of these methods ?
Cloud effort
Offline
It's not clear why format of debug symbols is chosen by upstream. I think build system should be able to generate any format that compiler support, so user or downstream can configure it with compiler options while compiling or building a package.
Offline
Upstream provides binary flatpaks & appimages for download and felt the need to add debug symbols to them.
Since the compiling for those binaries is done by upstream they needed to set something .
The option chosen was -ggdb3 as both -gn & -gsplit-dwarf didn't work for all usecases.
Marking as solved.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline