From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30761 invoked by alias); 6 Dec 2001 04:01:57 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 30566 invoked from network); 6 Dec 2001 04:00:40 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 6 Dec 2001 04:00:40 -0000 Received: from drow by nevyn.them.org with local (Exim 3.33 #1 (Debian)) id 16Bpiq-0003Et-00; Wed, 05 Dec 2001 23:01:20 -0500 Date: Wed, 05 Dec 2001 20:01:00 -0000 From: Daniel Jacobowitz To: gcc@gcc.gnu.org, Daniel Berlin Subject: Re: DWARF-2 and constructors/destructors Message-ID: <20011205230120.A12341@nevyn.them.org> Mail-Followup-To: gcc@gcc.gnu.org, Daniel Berlin References: <20011205225246.A10961@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011205225246.A10961@nevyn.them.org> User-Agent: Mutt/1.3.23i X-SW-Source: 2001-12/txt/msg00261.txt.bz2 On Wed, Dec 05, 2001 at 10:52:46PM -0500, Daniel Jacobowitz wrote: > Suppose you want to call a (non-virtual) method in C++, from something > with Dwarf-2 info. The only way to get the mangled name from the debug > info is DW_AT_MIPS_linkage_name. This isn't, of course, present for > constructors/destructors, since the entry in the class definition is > for the abstract version. > > Is it reasonable for the debugger to have to mangle this itself? The > constructor arguments can be arbitrarily complex. Should there be > references in the debug information to the base and complete > constructors anywhere? And I see, in a rather memorable rant, Daniel Berlin saying that DW_AT_MIPS_linkage_name is "a hack" (certainly), "not necessary, and we're trying to make it go away anyway." Dan, would you mind enlightening me on how to cope without it without having a full mangler for every supported C++ ABI attached to the Dwarf-2 reader? As far as I'm concerned, GDB has no business ever mangling a single string. Debug info should provide everything that we need. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer