delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
To: | cygwin AT cygwin DOT com |
From: | Ryan Boder <boder AT bitwiserlabs DOT com> |
Subject: | Stacktrace in cygwin gdb after uncaught exception |
Date: | Mon, 18 Sep 2006 18:16:51 +0000 (UTC) |
Lines: | 16 |
Message-ID: | <loom.20060918T200333-337@post.gmane.org> |
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 |
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. Thanks, -- Ryan Boder 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |