Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Date:	Sat, 7 Sep 2002 22:21:05 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: ld problem with latest cvs
Message-ID:	<20020908022105.GA28656@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
References:	<3D7789B3 DOT 6683CC0A AT ieee DOT org> <20020905164805 DOT GE16827 AT redhat DOT com> <3D778DFC DOT 5FE31E55 AT ieee DOT org>
Mime-Version:	1.0
In-Reply-To:	<3D778DFC.5FE31E55@ieee.org>
User-Agent:	Mutt/1.4i

On Thu, Sep 05, 2002 at 01:01:48PM -0400, Pierre A. Humblet wrote:
>Christopher Faylor wrote:
>
>> Run the build and get a meaningful stack trace from gdb.
>> 
>
>Sorry, I didn't seem to have --enable-debugging
>
>Does this help?
>
>gdb -nw /bin/ld.exe
>(gdb) dll cygwin1
>(gdb) x 0x610975ab
>0x610975ab <fflush+59>: Cannot access memory at address 0x610975ab
>(gdb) x 0x610a1aa8
>0x610a1aa8 <_fwalk+56>: Cannot access memory at address 0x610a1aa8
>(gdb) x 0x610A1EA3
>0x610a1ea3 <_cleanup_r+23>:     Cannot access memory at address 0x610a1ea3
>(gdb) x 0x61097291
>0x61097291 <exit+145>:  Cannot access memory at address 0x61097291

It helps a little.  I think you need to do a make clean and rebuild.
Recent newlib changes to the FILE structure seem to require that.

cgf

- Raw text -