Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@cgsoftware.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Jason Merrill <jason@redhat.com>, <libstdc++@gcc.gnu.org>,
	<gdb@sources.redhat.com>
Subject: Re: C++ debugging progress
Date: Wed, 28 Nov 2001 10:36:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0111281335250.12685-100000@www.cgsoftware.com> (raw)
Message-ID: <20011128103600.ZALXZPQhZnxVLA6q2QrPZczYgvjZ7bTl_4t0bnl3y5I@z> (raw)
In-Reply-To: <20011128124118.A23447@nevyn.them.org>

On Wed, 28 Nov 2001, Daniel Jacobowitz wrote:

> On Wed, Nov 28, 2001 at 09:31:07AM +0000, Jason Merrill wrote:
> > >>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
> >
> > > I'll not be posting the patches for another day or two.  The way I do it now
> > > is grossly inefficient; I look through RTTI at every lookup instead of once
> > > per type.  It also depends on presence of RTTI.  There's not much I can do
> > > about that - or rather, I could, but AFAICT it would require walking the
> > > inheritance graph in the proper order and I don't have the machinery to do
> > > that easily.  I'm not heartbroken that we need RTTI for debugging though.
> >
> > So you're using the inheritance information in the RTTI rather than the debug
> > info?  That seems unfortunate.  I'm not sure why you would need to worry
> > about ordering; the debug info should tell you exactly where things are.
> > If it doesn't, it should probably be fixed.
>
> In that case, the debug info absolutely needs to be fixed.
>
> (I'm looking at stabs here.  I haven't tried to see what Dwarf2 emits
> yet.  I don't have my head wrapped around Dwarf2.  Yeah, I know, I
> should be using it.)
>
> Consider this:
>
> struct Base { int xxx; };
> struct Left : public virtual Base { int yyy; };
> struct Right : public virtual Base { int zzz; };
> struct Bottom : public Left, public Right { int bbb; };
>
> int main() { struct Bottom bzz; return 1; }
>
> The question, of course, is:  Where's bzz.xxx?
>
> Dwarf2 first:
>  <1><115>: Abbrev Number: 15 (DW_TAG_structure_type)
>      DW_AT_sibling     : <1c2>
>      DW_AT_name        : Bottom
>      DW_AT_byte_size   : 24
>      DW_AT_decl_file   : 1
>      DW_AT_decl_line   : 4
>      DW_AT_containing_type: <22e>
>  <2><128>: Abbrev Number: 16 (DW_TAG_inheritance)
>      DW_AT_type        : <22e>
>      DW_AT_data_member_location: 2 byte block: 23 0 (DW_OP_plus_uconst: 0; )
>      DW_AT_accessibility: 1     (public)
>  <2><131>: Abbrev Number: 16 (DW_TAG_inheritance)
>      DW_AT_type        : <2df>
>      DW_AT_data_member_location: 2 byte block: 23 8 (DW_OP_plus_uconst: 8; )
>      DW_AT_accessibility: 1     (public)
>  <2><13a>: Abbrev Number: 3 (DW_TAG_member)
>      DW_AT_name        : bbb
>      DW_AT_decl_file   : 1
>      DW_AT_decl_line   : 4
>      DW_AT_type        : <cd>
>      DW_AT_data_member_location: 2 byte block: 23 10 (DW_OP_plus_uconst: 16; )
>
> Do you see it?  I don't, and I'm pretty sure it's not there.

Umm, look at type 2df and 22e.
I'm going to bet money xxx is there.



  parent reply	other threads:[~2001-11-28 10:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-27 23:03 Daniel Jacobowitz
2001-11-18 21:43 ` Daniel Jacobowitz
2001-11-19  9:04 ` Benjamin Kosnik
2001-11-27 23:36   ` Benjamin Kosnik
2001-11-19 11:16 ` Daniel Berlin
2001-11-21 13:37   ` Dan Mosedale
2001-11-28 12:25     ` Dan Mosedale
2001-11-27 23:43   ` Daniel Berlin
2001-11-19 13:41 ` Jason Merrill
2001-11-28  1:31   ` Jason Merrill
2001-11-28  9:41   ` Daniel Jacobowitz
2001-11-21  4:12     ` Daniel Jacobowitz
2001-11-21  5:06     ` Daniel Berlin [this message]
2001-11-28 10:36       ` Daniel Berlin
2001-11-28 10:49       ` Daniel Jacobowitz
2001-11-21 12:33         ` Daniel Jacobowitz
2001-11-28 11:41     ` Jason Merrill
2001-11-21 13:21       ` Jason Merrill
2001-11-21 13:42       ` Daniel Jacobowitz
2001-11-28 12:32         ` Daniel Jacobowitz
2001-11-21 16:38       ` Jason Merrill
2001-11-22  0:13         ` Daniel Jacobowitz
2001-11-24 22:52           ` Jason Merrill
2001-11-29  9:44             ` Jason Merrill
2001-11-29 12:28             ` Daniel Jacobowitz
2001-11-25  8:34               ` Daniel Jacobowitz
2001-11-25  9:01               ` Kevin Buettner
2001-11-25 10:30                 ` Jason Merrill
2001-11-29 19:12                   ` Jason Merrill
2001-11-29 13:11                 ` Kevin Buettner
2001-11-29 12:50               ` Benjamin Kosnik
2001-11-25  8:40                 ` Benjamin Kosnik
2001-11-28 13:31           ` Daniel Jacobowitz
2001-11-28 13:03         ` Jason Merrill
     [not found]       ` <20011128151819.A31514@nevyn.them.org>
2001-11-21 22:26         ` Jason Merrill
2001-11-28 13:14           ` Jason Merrill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.33.0111281335250.12685-100000@www.cgsoftware.com \
    --to=dan@cgsoftware.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=jason@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox