From: Daniel Jacobowitz <drow@mvista.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: Jason Merrill <jason@redhat.com>,
libstdc++@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: C++ debugging progress
Date: Wed, 21 Nov 2001 12:33:00 -0000 [thread overview]
Message-ID: <20011128135013.A28361@nevyn.them.org> (raw)
Message-ID: <20011121123300.wX3OEH4N-Nhll1W4TOdC7_zAoAXanQnSwngIbtmszFI@z> (raw)
In-Reply-To: <Pine.LNX.4.33.0111281335250.12685-100000@www.cgsoftware.com>
On Wed, Nov 28, 2001 at 01:36:28PM -0500, Daniel Berlin wrote:
> > 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.
You owe me some money.
Both 22e and 2df are marked as inheriting from Base, which is <56> (I
included 22e in the original message). They contain:
<2><23f>: Abbrev Number: 22 (DW_TAG_inheritance)
DW_AT_type : <56>
DW_AT_data_member_location: 2 byte block: 23 8 (DW_OP_plus_uconst: 8; )
DW_AT_virtuality : 1 (virtual)
DW_AT_accessibility: 1 (public)
That tells me where xxx would be, inside the <56> at offset +8, if my
object was of type 2df or 22e. It isn't, it's of type 115.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-11-28 18:49 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
2001-11-28 10:36 ` Daniel Berlin
2001-11-28 10:49 ` Daniel Jacobowitz [this message]
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=20011128135013.A28361@nevyn.them.org \
--to=drow@mvista.com \
--cc=dan@cgsoftware.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