This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: ld segfault on incrementally linked object
- To: amodra at one dot net dot au
- Subject: Re: ld segfault on incrementally linked object
- From: "Ryan Bedwell (ra9407)" <ra9407 at email dot sps dot mot dot com>
- Date: Fri, 11 May 2001 08:18:55 -0500
- CC: binutils at sources dot redhat dot com
- Organization: Motorola - SPS - IES - MSD
- References: <3AFB5970.BFDE62F1@email.sps.mot.com> <20010511152325.E10306@squeak.one.net.au>
- Reply-To: ryan dot bedwell at motorola dot com
Alan,
Attached is a tarball with the requested object files and a makefile.
The makefile assumes that powerpc-eabi-ld is in the path. The two
object files come from Michael J. Haertel's malloc library
implementation.
Here are the configure options which I used in building binutils:
./configure --prefix=$(HOME) --target=powerpc-eabi
Ryan
amodra@one.net.au wrote:
>
> On Thu, May 10, 2001 at 10:16:00PM -0500, Ryan Bedwell (ra9407) wrote:
> > I'm seeing a bit of strange behavior: I'm getting ld segfaults, and I've
> > narrowed it down to unresolved symbols in an object file which was
> > created by incrementally linking several other object files. However,
> > if I specify the source object files rather than the incrementally
> > linked file, it correctly reports the unresolved symbols and exits.
>
> I'll take a look if you send me
> a) The configure options you used when building binutils,
> b) a set of (preferably small) object files that exhibit the problem,
> c) a script or makefile to produce the incrementally linked intermediate
> and final ld segfault.
>
> --
> Alan Modra
ld_segfault.tar.gz