http://sourceware.org/bugzilla/show_bug.cgi?id=13449
Nick Clifton <nickc at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #3 from Nick Clifton <nickc at redhat dot com> 2011-12-01 17:51:03
UTC ---
Hi Alexander,
Thanks for the binaries - they really help.
If you compare a hex dump of the .ARM.exidx sections in the two binaries, you
will see that the broken binary does not contain garbage, just two erroneous
set bits:
% readelf -x17 exc
Hex dump of section '.ARM.exidx':
0x00008758 70feffff 01000000 e0feff7f d0ffff7f p...............
0x00008768 54ffffff ad08b180 90ffffff b0b0b080 T...............
0x00008778 8cffff7f 01000000 ........
% readelf -x17 exc.broken
Hex dump of section '.ARM.exidx':
0x0000874c 70feffff 01000000 e0feffff d0ffffff p...............
0x0000875c 54ffffff ad08b180 90ffffff b0b0b080 T...............
0x0000876c 8cffff7f 01000000 ........
(It would be very interesting to compare the exc.o files for the broken and
working builds to see if these bits are the same there. Ie I am wondering if
the linker might be the problem rather than the assembler - and the valgrind
detection of an uninitialised write might just be a red herring).
I am still investigating, but in the meantime would you mind trying out the
small patch that I am about to upload and let me know if it makes any
difference ?
Cheers
Nick
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
