[Bug] Between and glibc causes ld to segfault.

Wolfram Gloger Wolfram.Gloger@dent.med.uni-muenchen.de
Tue Mar 11 11:06:00 GMT 2003


Hi,

> 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?

Regards,
Wolfram.



More information about the Binutils mailing list