From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2955 invoked by alias); 20 Jun 2002 16:46:05 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 2922 invoked by uid 71); 20 Jun 2002 16:46:03 -0000 Date: Thu, 20 Jun 2002 10:16:00 -0000 Message-ID: <20020620164603.2919.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: James Cownie Subject: Re: c++/7081: DWARF enhancements for C++ Reply-To: James Cownie X-SW-Source: 2002-06/txt/msg00462.txt.bz2 List-Id: The following reply was made to PR c++/7081; it has been noted by GNATS. From: James Cownie To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/7081: DWARF enhancements for C++ Date: Thu, 20 Jun 2002 17:36:01 +0100 > This one isn't really necessary. The ABI specifies where the vtable > pointer will be, and GDB is quite capable of using that knowledge to > identify the runtime type. I believe even 'whatis' will do this for > you. Whichever debugger you're using must have an understanding of the > binary's ABI to debug C++ anyway... Requiring that the debugger know this from the ABI (rather than being told it by the compiler) is exactly why it takes a long time for debuggers to catch up when the compiler ABI is changed :-( -- Jim James Cownie Etnus, LLC. +44 117 9071438 http://www.etnus.com