From: Ian Lance Taylor <iant@google.com>
To: Daniel Drake <dsd@laptop.org>
Cc: gcc@gcc.gnu.org
Subject: Re: ld build-id crash on ARM linking gcc
Date: Sat, 24 Sep 2011 21:32:00 -0000 [thread overview]
Message-ID: <mcrvcshloj0.fsf@coign.corp.google.com> (raw)
In-Reply-To: <CAMLZHHQ=4z89Hvu_86RvT7jTbQALXRcuGz0sH730H-2vygmemA@mail.gmail.com> (Daniel Drake's message of "Sat, 24 Sep 2011 13:26:29 +0100")
Daniel Drake <dsd@laptop.org> writes:
> We have found a ld segfault that occurs early in the gcc compile
> process - the first time it tries to link cc1. This is testing on
> armv5tel.
Issues with the GNU binutils should normall go to
binutils@sourceware.org. See http://sourceware.org/binutils/ .
I don't know what might have fixed this. I didn't see anything
immediately obvious in the diff. If the backtrace can be trusted, the
problem is that the length passed to sha1_process_bytes is far too
large, but I don't know why.
Ian
next prev parent reply other threads:[~2011-09-24 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 12:26 Daniel Drake
2011-09-24 12:46 ` Daniel Drake
2011-09-24 21:32 ` Ian Lance Taylor [this message]
2011-09-24 22:47 ` Daniel Drake
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=mcrvcshloj0.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=dsd@laptop.org \
--cc=gcc@gcc.gnu.org \
/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).