X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Ryan Boder <boder AT bitwiserlabs DOT com>
Subject:	Re: Stacktrace in cygwin gdb after uncaught exception
Date:	Wed, 20 Sep 2006 20:38:43 +0000 (UTC)
Lines:	21
Message-ID:	<loom.20060920T223347-967@post.gmane.org>
References:	<loom DOT 20060918T200333-337 AT post DOT gmane DOT org> <20060918192444 DOT GB29609 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes
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

Christopher Faylor <cgf-no-personal-reply-please <at> cygwin.com> writes:
> gdb does not just exit with an uncaught exception.  It responds to a SIGSEGV
> the same way as linux.

Can cygwin gdb print a stack trace that would direct me to the throw -1 line
when debugging the following program? 

int main() {

  throw -1;

  return 0;
}

When I do it, the program just exits returning a non-zero error code.

Thanks,
--
Ryan
http://bitwiserlabs.com



--
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/

- Raw text -