From: "H. J. Lu" <hjl@lucon.org>
To: Fabian Wenzel <wenzel@tu-harburg.de>
Cc: binutils@sources.redhat.com
Subject: Re: libbfd crashes when linking in elf_i386_relocate_section
Date: Fri, 25 Jun 2004 14:48:00 -0000 [thread overview]
Message-ID: <20040625144836.GA28920@lucon.org> (raw)
In-Reply-To: <40DC29C3.9080603@tu-harburg.de>
On Fri, Jun 25, 2004 at 03:33:55PM +0200, Fabian Wenzel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all!
>
> A month ago I already posted this error to gnu.utils.bug, but apparently
> the list is not working currently (I wrote a follow-up today, but it did
> not appear in the newsgroup).
>
> The problem is that the linker crashes when linking an own application with
>
> /usr/bin/ld: BFD 2.14.90.0.7 20031029 Debian GNU/Linux internal error,
> aborting at ../../bfd/elf32-i386.c line 2247 in elf_i386_relocate_section
>
> I already tried binutils 2.15 which I built from the original tarball,
> but the error remained.
>
> This problem suddently appeared; I did not make any changes to the code
> which was building correctly for years. I did some debugging and found
> out that the linker crashes as soon as two of three "critical" objects
> are linked together.
>
> The abort() is called in the following lines:
>
> if (off >= (bfd_vma) -2)
> ~ abort ();
>
> I added some tracing code and figured out that it is indeed caused by
> one of the "critical" object files with section *UND*.
>
> If there is more that I can do in order to locate the problem, it would
> be great if you could let me know. I am a little lost and don't know if
> I am trying to figure things out in the right direction.
Please open a bugzilla bug report and provide a small testcase.
H.J.
prev parent reply other threads:[~2004-06-25 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 13:34 Fabian Wenzel
2004-06-25 14:48 ` H. J. Lu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040625144836.GA28920@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=wenzel@tu-harburg.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).