X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1/dVK8Sq717g/IOZsZxqMHv
Date:	Thu, 14 Mar 2013 10:48:39 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: gdb bt gives many question marks
Message-ID:	<20130314144839.GD7550@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<603c2ab2 DOT 23bed DOT 13d67af2820 DOT Coremail DOT hgw00 AT 126 DOT com> <CAJH9Tsd+4ztE=OknKcUj=7CVefi3sSHiw6bvxPivuSFjgZ1Udg AT mail DOT gmail DOT com> <5141D1F5 DOT 9000207 AT cs DOT utoronto DOT ca>
MIME-Version:	1.0
In-Reply-To:	<5141D1F5.9000207@cs.utoronto.ca>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Thu, Mar 14, 2013 at 09:34:45AM -0400, Ryan Johnson wrote:
>On 14/03/2013 3:37 AM, Ken Huang wrote:
>> Hi all,
>>
>> I have a problem when using gdb to debug my program in cygwin, the 'bt' command
>> gives me many '??'.
>>
>> So I write a quite easy program named abort.c which just aborts. after
>> compiled with
>> "gcc -g abort.c -o abort" and run with " gdb abort", it aborts as
>> expected. At this time
>> I type "bt" in gdb to see the backtrace info, but it only gives the following:
><standard useless windows stack frames that have nothing to do with the 
>actual cygwin program under debug>
>
>My experience is that you're SOL once Windows has started its exception 
>handling. I dont' know if it's an alternate stack, a debug info problem, 
>or what; but the only reliable way I know to debug aborts is to `b 
>__abort' so that gdb gets there before of Windows (I think it's two 
>underscores, but it could be one or three).

The changes mentioned here should help:
http://cygwin.com/ml/cygwin/2013-03/msg00176.html

But you'll need a snapshot.

(And now that I've had a few days to mull over the change I can see that
I probably need to do more work on the stack frame)

cgf

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

- Raw text -