From: "H. J. Lu" <hjl@lucon.org>
To: Andreas Schwab <schwab@suse.de>
Cc: dj@redhat.com, binutils@sourceware.org
Subject: Re: Increment
Date: Mon, 12 Jun 2006 19:13:00 -0000 [thread overview]
Message-ID: <20060612190517.GA12535@lucon.org> (raw)
In-Reply-To: <je7j3mzq77.fsf@sykes.suse.de>
On Mon, Jun 12, 2006 at 11:19:24AM +0200, Andreas Schwab wrote:
> Alan Modra <amodra@bigpond.net.au> writes:
>
> > On Fri, Jun 09, 2006 at 03:36:59PM +0200, Andreas Schwab wrote:
> >> Alan Modra <amodra@bigpond.net.au> writes:
> >> > * hash.c (bfd_hash_lookup): Correct stray line.
> >>
> >> The linker is now crashing very often with an assertion failure in
> >> _bfd_elf_strtab_delref. Apparently the hash resizing was never properly
> >> tested, since with the misplaced increment it was unlikely to ever
> >> trigger. In fact, disabling it will fix the crashes.
> >
> > How do you get these crashes?
>
> Just by linking any moderately big binary.
Will building gcc on x86, x86-64 and ia64 trigger this?
H.J.
next prev parent reply other threads:[~2006-06-12 19:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 16:33 Increment Ian Lance Taylor
2006-06-06 4:30 ` Increment Alan Modra
2006-06-06 10:52 ` Increment Alan Modra
2006-06-07 1:40 ` Increment Thiemo Seufer
2006-06-07 5:02 ` Increment Alan Modra
2006-06-09 13:42 ` Increment Andreas Schwab
2006-06-12 4:32 ` Increment Alan Modra
2006-06-12 10:50 ` Increment Andreas Schwab
2006-06-12 18:53 ` Increment DJ Delorie
2006-06-12 19:13 ` H. J. Lu [this message]
2006-06-12 23:55 ` Increment Andreas Schwab
2006-06-13 1:11 ` Increment Alan Modra
2006-06-13 10:52 ` Increment Andreas Schwab
2006-06-13 8:53 ` Increment H. J. Lu
2006-06-13 13:49 ` Increment Andreas Schwab
2006-06-13 14:49 ` Increment Alan Modra
2006-06-13 14:52 ` Increment Alan Modra
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=20060612190517.GA12535@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sourceware.org \
--cc=dj@redhat.com \
--cc=schwab@suse.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).