X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Ryan Boder Subject: Re: Stacktrace in cygwin gdb after uncaught exception Date: Fri, 22 Sep 2006 20:05:43 +0000 (UTC) Lines: 29 Message-ID: References: <20060918192444.GB29609@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.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/