[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/23534] ld.bfd: internal error from ldlang.c:6635
From: |
amodra at gmail dot com |
Subject: |
[Bug ld/23534] ld.bfd: internal error from ldlang.c:6635 |
Date: |
Mon, 10 Sep 2018 04:46:18 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=23534
--- Comment #4 from Alan Modra <amodra at gmail dot com> ---
One of you who can manage to reproduce this bug will need to spend a little
time using gdb to find out what is going on. If I had a reproducible test
case, I'd
a) Run the failing link with "-save-temps -v -Wl,-v" added to the command line.
b) Run the ld invocation so found to check that the error still occurs.
c) Run that under gdb, putting a breakpoint on the assertion.
d) Find the address of entry->the_bfd->link.next when the assertion triggers.
e) Put a watchpoint on writes to that address, and run it again.
This should reveal the wild write to memory that destroys the linked list.
Once that is known it should be easy to fix.
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug ld/23534] ld.bfd: internal error from ldlang.c:6635, m4ntdjzdi2 at wylie dot me.uk, 2018/09/09
- [Bug ld/23534] ld.bfd: internal error from ldlang.c:6635,
amodra at gmail dot com <=
- [Bug ld/23534] ld.bfd: internal error from ldlang.c:6635, dirkjan at ochtman dot nl, 2018/09/10
- [Bug ld/23534] ld.bfd: internal error from ldlang.c:6635, m4ntdjzdi2 at wylie dot me.uk, 2018/09/10
- [Bug ld/23534] ld.bfd: internal error from ldlang.c:6635, slyfox at inbox dot ru, 2018/09/10
- [Bug ld/23534] ld.bfd: internal error from ldlang.c:6635, amodra at gmail dot com, 2018/09/10
- [Bug ld/23534] ld.bfd: internal error from ldlang.c:6635, slyfox at inbox dot ru, 2018/09/11