This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Stacktrace in cygwin gdb after uncaught exception
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 18 Sep 2006 15:24:44 -0400
- Subject: Re: Stacktrace in cygwin gdb after uncaught exception
- References: <loom.20060918T200333-337@post.gmane.org>
- Reply-to: cygwin at cygwin dot com
On Mon, Sep 18, 2006 at 06:16:51PM +0000, Ryan Boder wrote:
>In Linux, if I am using gdb on a program and it throws an exception that is not
>caught, I can then get a stack trace with the bt command.
>
>In Cygwin, the program just exists and I see the following line:
>
>Program exited with code 0400.
>
>Is it possible to get a stacktrace in gdb for an uncaught exception in Cygwin? I
>am aware of dumper, but I am looking for a way to do it all in a single gdb
>session so I can see the strack trace when I debug in eclipse CDT.
gdb does not just exit with an uncaught exception. It responds to a SIGSEGV
the same way as linux.
cgf
--
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/