X-Spam-Check-By: sourceware.org Date: Mon, 18 Sep 2006 15:24:44 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Stacktrace in cygwin gdb after uncaught exception Message-ID: <20060918192444.GB29609@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 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/