Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=562226 Jerry James <loganjerry@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |loganjerry@xxxxxxxxx --- Comment #1 from Jerry James <loganjerry@xxxxxxxxx> 2010-02-24 17:35:29 EST --- Hi Alexander, The C code is being compiled to object files that contain valid DWARF-2 debug information. The problem is with the assembler sources. They are being processed with m4, which is adding explicit stabs information to the files, even though as would normally produce DWARF-2 debug information as well. Search for ".stabs" in lisp-kernel/m4macros.m4. One (untested) workaround is to strip only these files, prior to linking the executable: imports.o x86-asmutils64.o x86-spentry64.o x86-spjump64.o x86-subprims64.o That way you'd still get debug information for the C sources. Long term, we should get upstream to stop inserting .stab sections into the output, or at least to insert correct .stab sections into the output if they really can't be bothered to move up to DWARF. I wonder if passing -g to as and removing all the .stab junk from m4macros.m4 would work.... Incidentally, I figured out which files are the culprits like this, should it prove useful: for f in *.o; do readelf -S $f | grep -F stab > /dev/null if [ $? = 0 ]; then echo $f; fi done -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review