From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10660 invoked by alias); 3 Dec 2001 22:58:25 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 10462 invoked from network); 3 Dec 2001 22:58:19 -0000 Received: from unknown (HELO localhost.localdomain) (62.30.164.150) by sources.redhat.com with SMTP; 3 Dec 2001 22:58:19 -0000 Received: (from jason@localhost) by localhost.localdomain (8.11.6/8.11.6) id fB3MthZ14734; Mon, 3 Dec 2001 22:55:43 GMT X-Authentication-Warning: localhost.localdomain: jason set sender to jason@redhat.com using -f To: gdb-patches@sources.redhat.com Cc: gcc@gcc.gnu.org Subject: Re: [RFA/stabs reader] Fix v3 duplicate constructors problem References: <20011203154836.A28821@nevyn.them.org> <20011203172931.A2512@nevyn.them.org> From: Jason Merrill In-Reply-To: <20011203172931.A2512@nevyn.them.org> (Daniel Jacobowitz's message of "Mon, 3 Dec 2001 17:29:31 -0500") Date: Mon, 03 Dec 2001 14:58:00 -0000 Message-ID: User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.1 (i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2001-12/txt/msg00070.txt.bz2 >>>>> "Daniel" == Daniel Jacobowitz writes: >> What does GDB actually use the member function information for? What >> impact would this change have, other than the output of ptype? > Right now, the big thing is probably member function calls. If the > constructor is called from GDB, we want to get the complete object > constructor. I'm not 100% sure this is even possible, though. You can't call a constructor directly in C++; no reason to allow it from GDB. Destructors are a different matter, though; an explicit call should go to the non-deleting, in-charge version. > I hadn't considered setting breakpoints on all of them. That's very > difficult; suppose I look at an assembly listing for a constructor and > tell it to break on a particular line. How can I figure out source > line information for every constructor? With Dwarf, all clones/inlines point to the abstract version; the internal representation could keep track of all instances of a particular abstract function. > Perhaps it is best to continue emitting them and ignore them until we > support them in GDB. Seems reasonable. Jason