This is the mail archive of the
mailing list for the glibc project.
Re: ld segfaults with long link lines
- From: Stefan Jones <cretin at gentoo dot org>
- To: binutils <binutils at sources dot redhat dot com>
- Cc: libc-alpha <libc-alpha at sources dot redhat dot com>
- Date: 09 Mar 2003 18:47:43 +0000
- Subject: Re: ld segfaults with long link lines
- Organization: Gentoo Linux
- References: <1047134738.1665.11.camel@localhost>
After extensive testing of about 10 system I have narrowed down the
problem (not by much) to the glibc-2.3.1 to glibc-2.3.2 upgrade.
This affects gentoo and redhat phoebe 3.
Using gcc-3.2.2 with redhat patches (or without) and rpm gcc-3.2.1-7
binutils-220.127.116.11.18 from source and rpm binutils-18.104.22.168.18-6
And the package sparking the problem:
with glibc-2.3.1 from source ld works fine.
glibc-2.3.2 from source and glibc-2.3.1-46 from redhat phoebe 3 causes
ld to segfault as described before.
redhat phoebe 3 and my gentoo systems both produce the same gdb stack
trace on segfault.
Any more information needed?
Hope this helps.
On Sat, 2003-03-08 at 14:45, Stefan Jones wrote:
> Hello all,
> I have come across this problem with binutils-22.214.171.124.18 on
> If you call ld with a very long link command it crashes.
> This may be a silly case but see
> for it in action.
> Any ideas?
Stefan Jones <cretin at gentoo dot org>