FS#74941 - [glibc] crtn.o objects contain debuginfo

Attached to Project: Arch Linux
Opened by Luís Ferreira (ljmf00) - Thursday, 02 June 2022, 14:27 GMT
Last edited by freswa (frederik) - Saturday, 29 April 2023, 16:49 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To freswa (frederik)
Morten Linderud (Foxboron)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



The newly compiled glibc objects contains debug info. This cause every binary linked with crtn.o and crt1.o (CRT static objects) to contain debug info, regardless of the debug flag on the compiler. I believe this [1] is the patch causing the current regression. This causes debuggers testsuite, such as LLDB to fail, but the worst is the fact that every single executable gets that debuginfo on its DWARF section making every executable size increase significantly.

Additional info:
* package version(s): glibc 2.35-5

Steps to reproduce:

1. Create a simple C file with an empty main.
2. Compile with e.g. clang without debug info
3. Use dwarfdump to see the debuginfo information


[1]: https://github.com/archlinux/svntogit-packages/commit/643595a970dfdf0eb2d66b4d1500254abc1f94d5
This task depends upon

Closed by  freswa (frederik)
Saturday, 29 April 2023, 16:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed upstream
Comment by freswa (frederik) - Friday, 03 June 2022, 09:14 GMT
This is a bug in our stripping logic to separate the debug symbols. `.o` doesn't get recognized as `.a` lib nor as kernel module, so loop continues. We'll fix this next week.
Comment by freswa (frederik) - Friday, 26 August 2022, 21:49 GMT