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:	Fri, 22 Sep 2006 20:05:43 +0000 (UTC)
Lines:	29
Message-ID:	<loom.20060922T215957-734@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> <loom DOT 20060920T223347-967 AT post DOT gmane DOT 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

> Yes, try the 'catch throw' command in gdb -- that should break on the  
> throw itself, and will give a useful stack trace (in my quick  
> testing) ;)

Thanks, but that's not exactly what I'm looking for. I only want gdb to break
when  the exception is not caught. Using the 'catch throw' command breaks 
any time an exception is thrown.

If you debug the following program, 'catch throw' will cause gdb to break on the
throw -1 line when I only want it to break on the throw -2 line.

int main() {

  try {
    throw -1;
  } catch (...) {}

  throw -2;

  return 0;
}

The default behavior of gdb on Fedora Linux Linux is to break on the throw -2
line. Is this impossible on cygwin or something?

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

- Raw text -