This is the mail archive of the
mailing list for the glibc project.
Re: [Bug] Between and glibc causes ld to segfault.
- From: Wolfram Gloger <Wolfram dot Gloger at dent dot med dot uni-muenchen dot de>
- To: cretin at gentoo dot org
- Cc: libc-alpha at sources dot redhat dot com, binutils at sources dot redhat dot com
- Date: Tue, 11 Mar 2003 12:06:02 +0100 ("MET)
- Subject: Re: [Bug] Between and glibc causes ld to segfault.
- References: <email@example.com>
> As I have said before, if you call ld with excessive -l() arguments you
> get the following segfault:
> ( see http://bugs.gentoo.org/show_bug.cgi?id=16577 for examples, also
> works on redhat beta 8.1 )
> #0 new_statement (type=lang_group_statement_enum, size=13, list=0xd)
> at ldlang.c:516
list=0xd looks suspicious; isn't the stack probably already corrupt
at this stage?
> The only valid error causing patch I can see in that lot is the new stack
> stuff in glibc linuxthreads.
Hmm, but since when is 'ld' linked to libpthread? I can't see how
LinuxThreads changes could have anything to do with this.
> Can someone please reply, I am happy to supply any additional info needed,
Have you run the ld command under valgrind?