From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30928 invoked by alias); 29 Oct 2006 22:15:54 -0000 Received: (qmail 30919 invoked by uid 22791); 29 Oct 2006 22:15:54 -0000 X-Spam-Check-By: sourceware.org Received: from pivsbh1.ms.com (HELO pivsbh1.ms.com) (199.89.64.101) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 29 Oct 2006 22:15:51 +0000 Received: from pivsbh1.ms.com (localhost [127.0.0.1]) by localhost.ms.com (Postfix) with ESMTP id 76C7010D7 for ; Sun, 29 Oct 2006 17:15:49 -0500 (EST) Received: from ny37im02.ms.com (unknown [144.14.31.41]) by pivsbh1.ms.com (internal Postfix) with ESMTP id 5385C1DB0 for ; Sun, 29 Oct 2006 17:15:49 -0500 (EST) Received: from PAWEXOB02.msad.ms.com (pawexob02 [205.228.46.101]) by ny37im02.ms.com (Sendmail MTA Hub) with ESMTP id k9TMFn728457 for ; Sun, 29 Oct 2006 17:15:49 -0500 (EST) Received: from PIWEXBH02.msad.ms.com ([205.228.46.225]) by PAWEXOB02.msad.ms.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 29 Oct 2006 17:15:48 -0500 Received: from NYWEXMB81.msad.ms.com ([144.203.227.8]) by PIWEXBH02.msad.ms.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 29 Oct 2006 17:15:48 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Finding the type of an exception Date: Sun, 29 Oct 2006 22:15:00 -0000 Message-ID: <1F8E762E1B3F814F9630D0D32A1C65F808DA323E@NYWEXMB81.msad.ms.com> In-Reply-To: <20061029211751.GA19301@sdf.lonestar.org> From: "Kulkarni, Mayuresh \(IT\)" To: X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00285.txt.bz2 Hello, I am looking at a core generated by a C++ process because a throw spec was violated by a function. The concerned frame in the stack trace is : #5 0xf65c2485 in __cxa_call_unexpected (exc_obj_in=3D0xb58cbb4) at /sw/gcc/src/libstdc++-v3/libsupc++/eh_personality.cc:485 At this point in the process (after std::unexpected() has been called and we end up in the above function), is it still somehow possible to deduce the type of the exception from the exc_obj_in void * argument? Say by trying to interpret the above void * argument as a std::exception (from other reasons, I am pretty sure that this was a std::exception) and then doing what typeid does to get at the type_info ? I am not knowledgeable about the gcc unwinding internals and am not sure if the above will work, even in principle.=20 Thanks a lot. Mayuresh. -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does= not intend to waive confidentiality or privilege. Use of this email is pro= hibited when received in error.