[Bug binutils/4208] 'final link failed: Bad value' when building Linux MIPS kernels.
--- Additional Comments From pkoning at equallogic dot com 2007-03-20 14:02 --- I ran into this issue with GCC 4.1.2, so I'm not sure about it not happening with newer compilers. A warning doesn't help, because it's as bad as an error when you build with "warnings are errors" as many do. Either this pattern is legal, in which case ld should accept it without any muttering, or it is illegal, in which case gcc has a bug that should be fixed. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4208 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/23881] New: pdp11 binutils fails if too much debug data
https://sourceware.org/bugzilla/show_bug.cgi?id=23881 Bug ID: 23881 Summary: pdp11 binutils fails if too much debug data Product: binutils Version: 2.31 Status: UNCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: pkoning at equallogic dot com Target Milestone: --- Created attachment 11390 --> https://sourceware.org/bugzilla/attachment.cgi?id=11390&action=edit test file full of .stabs data For pdp11, the linker is happy to generate outputs with many kB of debug data, but beyond a certain point such files are not readable in nm or objdump. To reproduce, assemble the two attached files and link as: pdp11-aout-ld testdbg.o testdbg.o testdbg.o testdbg.o maindbg.o Then objdump fails this way: pdp11-aout-objdump -t a.out a.out: file format a.out-pdp11 /usr/local/pdp11-aout/bin/pdp11-aout-objdump: failed to read symbol table from: a.out /usr/local/pdp11-aout/bin/pdp11-aout-objdump: error message was: file in wrong format If I link testdbg.o just once or twice, objdump works fine. -- 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
[Bug binutils/23881] pdp11 binutils fails if too much debug data
https://sourceware.org/bugzilla/show_bug.cgi?id=23881 --- Comment #1 from Paul Koning --- Created attachment 11391 --> https://sourceware.org/bugzilla/attachment.cgi?id=11391&action=edit main program to link with testdbg.S -- 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
[Bug binutils/23931] New: objdump -r often fails on pdp11 files
https://sourceware.org/bugzilla/show_bug.cgi?id=23931 Bug ID: 23931 Summary: objdump -r often fails on pdp11 files Product: binutils Version: 2.31 Status: UNCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: pkoning at equallogic dot com Target Milestone: --- Created attachment 11417 --> https://sourceware.org/bugzilla/attachment.cgi?id=11417&action=edit crt0.o for pdp11 Function dump_relocs_in_section in objdump.c checks that the relic count is valid by comparing the size of the reloc data against the file size. That check is incorrect because "relsize" is the decoded (canonical) reloc data size, not the size of the reloc data encoded in the file. In the case of pdp11, sizeof (arelent) is 8, while the size in the file is 2 bytes per entry, so the check can easily fail. The attached file shows the issue. If I comment out the check at objdump.c:3465, it works. -- 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
[Bug binutils/23931] objdump -r often fails on pdp11 files
https://sourceware.org/bugzilla/show_bug.cgi?id=23931 --- Comment #3 from Paul Koning --- Great. I agree fixing the check is best. I looked at the code but it wasn't clear to me how to do that, so I did the disable as a crude test. -- 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
[Bug ld/24144] Gnu ld for PDP-11 is creating corrupt output. NULL inserted in data section.
https://sourceware.org/bugzilla/show_bug.cgi?id=24144 Paul Koning changed: What|Removed |Added CC||pkoning at equallogic dot com -- 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
[Bug ld/24144] Gnu ld for PDP-11 is creating corrupt output. NULL inserted in data section.
https://sourceware.org/bugzilla/show_bug.cgi?id=24144 --- Comment #2 from Paul Koning --- GCC sets the max alignment to 2 bytes for pdp11, since alignment larger than that is not useful on that machine. It may make sense for binutils to apply the same limit. -- 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
[Bug ld/24144] Gnu ld for PDP-11 is creating corrupt output. NULL inserted in data section.
https://sourceware.org/bugzilla/show_bug.cgi?id=24144 --- Comment #4 from Paul Koning --- Created attachment 11638 --> https://sourceware.org/bugzilla/attachment.cgi?id=11638&action=edit Test case object files and script I ran into this issue some time ago while debugging pdp11-gcc test case failures. Here is one. I extracted the needed object files from the libc library it uses, included the linker script, and a shell script to build it showing the failure. In this one, the bug corrupts a message supposed to be printed by exit(). In exit.S you can see that status 0 results in message "exit: ok\n". If you objdump lib_a-exit.o, you will see that message. Now link the program using linkbug.sh. In the objdump of executable "bug", the message shows up in the objdump .data output for address 1610. It shows that "exit" is now "e\000it", i.e., the string is truncated by the spurious zero byte at the second character. It appears the issue is not directly related to alignment > 2, because the link script in this example only has ALIGNED(2) in it. I suspect the reason it seemed that way in the original is that changing alignment moves where the stray 0 lands, and probably for alignment 2 in his example it ended up in some spot where it does no damage. -- 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
[Bug ld/24144] Gnu ld for PDP-11 is creating corrupt output. NULL inserted in data section.
https://sourceware.org/bugzilla/show_bug.cgi?id=24144 --- Comment #9 from Paul Koning --- Thanks, that cures my test case and in fact makes 14 fewer failures in the gcc test suite. -- 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
