Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <007101c5d078$a71a2a90$1600a8c0@toyon.corp>
From: "Peter J. Stieber" <developer AT toyon DOT com>
To: <cygwin AT cygwin DOT com>
References: <045001c5cd2c$657579e0$1600a8c0 AT toyon DOT corp> <diccd2$s2d$1 AT sea DOT gmane DOT org> <056901c5cd3e$3986d010$1600a8c0 AT toyon DOT corp> <434A5ADB DOT 2080602 AT byu DOT net> <20051010151806 DOT GC14608 AT trixie DOT casa DOT cgf DOT cx> <20051010153309 DOT GD14608 AT trixie DOT casa DOT cgf DOT cx> <036201c5d04a$7f485010$1600a8c0 AT toyon DOT corp> <434EF021 DOT 8C23A29 AT dessent DOT net> <20051014022412 DOT GC4476 AT trixie DOT casa DOT cgf DOT cx>
Subject: Re: 1.5.18: ld command generates stackdump
Date: Thu, 13 Oct 2005 21:35:06 -0700
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=original
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

PS = Pete Stieber
PS>>> Do I also need to build a debug version of the cygwin DLL?

BD = Brian Dessent
BD>>It would help, since otherwise backtraces will only have raw
BD>> addresses. Note that the cygwin configure script[*] has a
BD>> --enable-debugging switch, but this is for enabling lots of
BD>> runtime consistency checks and extra verbosity -- it is not
BD>> meant for enabling debug symbols, which you
BD>>should get by default.

CF> Is this dying in the cygwin DLL?  I suspect that it isn't.
CF> The stackdump file would show if it is, as would using
CF> CYGWIN error_start setting that I mentioned previously.
CF>
CF> I don't think there's any reason to build a debugging
CF> version of cygwin unless the problem points to the
CF> cygwin DLL.

Keeping in mind that I am having problems building binutils (mentioned 
in a recent reply to Brian's post), here is the back trace from a 
stripped version of ld using the technique you suggested.

Attaching to program `/bin/ld.exe', process 3248

[Switching to thread 3248.0x850]
(gdb) bt
#0  0x7c901231 in ntdll!DbgUiConnectToDbg ()
   from /cygdrive/c/WINDOWS/system32/ntdll.dll
#1  0x7c9507a8 in ntdll!KiIntSystemCall ()
   from /cygdrive/c/WINDOWS/system32/ntdll.dll
#2  0x00000005 in ?? ()
#3  0x00000004 in ?? ()
#4  0x00000001 in ?? ()
#5  0x1941ffd0 in ?? ()
#6  0x3531283a in ?? ()
#7  0xffffffff in ?? ()
#8  0x7c90ee18 in strchr () from /cygdrive/c/WINDOWS/system32/ntdll.dll
#9  0x7c9507c8 in ntdll!KiIntSystemCall ()
   from /cygdrive/c/WINDOWS/system32/ntdll.dll
#10 0x00000000 in ?? () from
(gdb)

This is probably useless, but just wanted to indicate I'm not ignoring 
your advice. It is greatly appreciated.

Thanks for the help Christopher,
Pete 



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/