split-debuginfo="unpacked" results in executables that still have debug info? about rust

[bjorn3]

DWARF split debuginfo splits the debuginfo into two parts. A part that is independent of the actual addresses at which each function ends up. This is what ends up in a separate file. And a part which glues the separate file together with the actual addresses of each function after linking. This part ends up in the final executable.

There is another way to do split debuginfo which is slower to link but does end up with all debuginfo in a separate file. This one is currently not supported by rustc. Adding support for this has been accepted, but not yet implemented: rust-lang/compiler-team#721 You can still do it manually by disabling split debuginfo and then using objcopy twice. One with --only-keep-debug to extract the debuginfo into a separate file and once with --strip-debug to remove the debuginfo from the executable.

[vlovich]

Thanks for the fast explanation! Not sure if you kept this open because you wanted it around as tracking for the implementation but feel free to close it otherwise as I consider my question answered.

[bjorn3]

#105991 is probably a better issue for tracking this.