From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14196 invoked by alias); 2 Nov 2007 06:28:08 -0000 Received: (qmail 14148 invoked by uid 48); 2 Nov 2007 06:27:58 -0000 Date: Fri, 02 Nov 2007 06:28:00 -0000 Message-ID: <20071102062758.14147.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: "pinskia at gcc dot gnu dot org" 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/msg00118.txt.bz2 ------- Comment #3 from pinskia at gcc dot gnu dot org 2007-11-02 06:27 ------- (In reply to comment #2) > I am using debugger. After the exception is thrown, the program asserts. So I > get a backtrace to the system fatal call, having no idea where the exception > was thrown. Since GCC follows the IA64 C++ ABI, you can have a breakpoint at __cxa_throw (the function which is called for throwing the exception). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33903