Package: gcc-2.95 Version: 2.95.4-0.010629 Severity: critical While packaging a new binutils, I noticed that 'strip -g' called twice failed to strip binaries that were generated by gcc-2.95, and in fact, produced binaries that no longer worked (as well as causing strip to segfault). This only appears to affect object files, NOT linked binaries, so stripping archives won't work properly. When comparing assembly output, it appears that the stabs info isn't correctly generated. Using gcc-3.0 to compile the same file (with the -gstabs option) produced a correct object file that could be stripped repeatedly without problems. Also, using DWARF2 output from gcc-2.95 as well as gcc-3.0 both worked fine. I emailed upstream for binutils to verify this and HJ Lu confirmed that the stabs info doesn't look correct and that binutils was actually correct. This appears to only affect Alpha and is holding back a binutils upload.
This bug is meant as a tracking mechanism for me while I try to fix this problem, but if someone wants to ask upstream, I can provide asm output and a very simple testcase. Binutils that uncovered the problem: 2.11.90.0.24. 2.11.90.0.7 appears to work fine, but I could reproduce the same problem if I used a certain file and passed it certain flags. All gcc-2.95.4 versions that I have (dating back to April) showed this problem. C