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
Message-ID:	<3D778DFC.5FE31E55@ieee.org>
Date:	Thu, 05 Sep 2002 13:01:48 -0400
From:	"Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
X-Accept-Language:	en,pdf
MIME-Version:	1.0
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: ld problem with latest cvs
References:	<3D7789B3 DOT 6683CC0A AT ieee DOT org> <20020905164805 DOT GE16827 AT redhat DOT com>

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

- Raw text -