From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2178 invoked by alias); 12 Jun 2003 18:16:05 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 2131 invoked from network); 12 Jun 2003 18:16:04 -0000 Received: from unknown (HELO smtp7.Stanford.EDU) (171.67.16.34) by sources.redhat.com with SMTP; 12 Jun 2003 18:16:04 -0000 Received: (from root@localhost) by smtp7.Stanford.EDU (8.12.9/8.12.9) id h5CIG3eS028363 for gdb@sources.redhat.com; Thu, 12 Jun 2003 11:16:03 -0700 (PDT) Received: from jackfruit.Stanford.EDU (jackfruit.Stanford.EDU [171.64.38.136]) by smtp7.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h5CIFw3J028318; Thu, 12 Jun 2003 11:15:58 -0700 (PDT) Received: (from carlton@localhost) by jackfruit.Stanford.EDU (8.11.6/8.11.6) id h5CIFwp12685; Thu, 12 Jun 2003 11:15:58 -0700 X-Authentication-Warning: jackfruit.Stanford.EDU: carlton set sender to carlton@math.stanford.edu using -f To: Daniel Jacobowitz Cc: gdb , Elena Zannoni , Jim Blandy Subject: Re: DW_AT_containing_type References: <20030612180714.GA19092@nevyn.them.org> From: David Carlton Date: Thu, 12 Jun 2003 18:16:00 -0000 In-Reply-To: <20030612180714.GA19092@nevyn.them.org> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-06/txt/msg00215.txt.bz2 On Thu, 12 Jun 2003 14:07:14 -0400, Daniel Jacobowitz said: > On Thu, Jun 12, 2003 at 10:56:50AM -0700, David Carlton wrote: >> What's with GDB's and GCC's use of DW_AT_containing type? As far as I >> can tell, it's only supposed to be used within >> DW_TAG_ptr_to_member_type, but GCC generates it and GDB uses it in >> many other contexts. > We are misusing it. See the GCC source for a comment explaining > this GNU extension. We use it to indicate which base type contains > the vtable pointer for the derived class; there are a number of > other ways to do it, and at one point we should switch to another > way. Ah, thanks for the explanation. David Carlton carlton@math.stanford.edu