From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21824 invoked by alias); 2 Nov 2007 06:55:02 -0000 Received: (qmail 21753 invoked by uid 48); 2 Nov 2007 06:54:53 -0000 Date: Fri, 02 Nov 2007 06:55:00 -0000 Message-ID: <20071102065453.21752.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/33903] Backtrace info in std::exception In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "djh at emss dot co dot za" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-11/txt/msg00120.txt.bz2 ------- Comment #4 from djh at emss dot co dot za 2007-11-02 06:54 ------- This is a possible solution. Not ideal though, because, then all exceptions will be trigger the breakpoint at __cxa_throw. If however, I put a breakpoint in the catch in question, then I know I will get the exception that I was looking for, and if bakctrace info was part of this exception, then I could find out exactly what happened where. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33903