From: Daniel Jacobowitz <drow@mvista.com>
To: libstdc++@gcc.gnu.org, gdb@sources.redhat.com
Subject: [dmj+@andrew.cmu.edu: Re: C++ debugging progress]
Date: Wed, 28 Nov 2001 12:18:00 -0000 [thread overview]
Message-ID: <20011128151908.A1036@nevyn.them.org> (raw)
Feh. Meant to send this to the lists.
----- Forwarded message from Daniel Jacobowitz <dmj+@andrew.cmu.edu> -----
Date: Wed, 28 Nov 2001 15:18:19 -0500
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Subject: Re: C++ debugging progress
To: Jason Merrill <jason@redhat.com>
On Wed, Nov 28, 2001 at 07:40:37PM +0000, Jason Merrill wrote:
> >>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
>
> > On Wed, Nov 28, 2001 at 09:31:07AM +0000, Jason Merrill wrote:
>
> >> 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.
>
> > <1><22e>: Abbrev Number: 15 (DW_TAG_structure_type)
> > DW_AT_sibling : <2df>
> > DW_AT_name : Left
> > DW_AT_byte_size : 12
> > DW_AT_decl_file : 1
> > DW_AT_decl_line : 2
> > DW_AT_containing_type: <22e>
> > <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)
>
> Yep. Since Base is a virtual base of Left, the DW_AT_data_member_location
> here should be a complex expression telling the debugger to go through the
> vtable. I'll get on it.
Thanks!
> I'll also change the stabs output to give the offset within the vtable
> rather than the offset of the base in a complete object; gdb will still
> need to be clever enough to know what to do with it.
<delete lots of incoherent rambling>
OK, if I'm reading this at all correctly, the offset in the baseclass
definition is assumed to be 0 for a virtual baseclass, and ignored; it
is assumed that there will be a $vb later. So that offset slot is a
perfect place to put the information I need. Just let me know if it is
relative to the start of the vtable or to the vtable pointer. That'll
be enough information to do a much better job.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
----- End forwarded message -----
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@mvista.com>
To: libstdc++@gcc.gnu.org, gdb@sources.redhat.com
Subject: [dmj+@andrew.cmu.edu: Re: C++ debugging progress]
Date: Wed, 21 Nov 2001 13:26:00 -0000 [thread overview]
Message-ID: <20011128151908.A1036@nevyn.them.org> (raw)
Message-ID: <20011121132600.e1atJdS2f5g-qEHnISCG7-LzwdgPtpFSR9suzq2r5R0@z> (raw)
Feh. Meant to send this to the lists.
----- Forwarded message from Daniel Jacobowitz <dmj+@andrew.cmu.edu> -----
Date: Wed, 28 Nov 2001 15:18:19 -0500
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Subject: Re: C++ debugging progress
To: Jason Merrill <jason@redhat.com>
On Wed, Nov 28, 2001 at 07:40:37PM +0000, Jason Merrill wrote:
> >>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
>
> > On Wed, Nov 28, 2001 at 09:31:07AM +0000, Jason Merrill wrote:
>
> >> 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.
>
> > <1><22e>: Abbrev Number: 15 (DW_TAG_structure_type)
> > DW_AT_sibling : <2df>
> > DW_AT_name : Left
> > DW_AT_byte_size : 12
> > DW_AT_decl_file : 1
> > DW_AT_decl_line : 2
> > DW_AT_containing_type: <22e>
> > <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)
>
> Yep. Since Base is a virtual base of Left, the DW_AT_data_member_location
> here should be a complex expression telling the debugger to go through the
> vtable. I'll get on it.
Thanks!
> I'll also change the stabs output to give the offset within the vtable
> rather than the offset of the base in a complete object; gdb will still
> need to be clever enough to know what to do with it.
<delete lots of incoherent rambling>
OK, if I'm reading this at all correctly, the offset in the baseclass
definition is assumed to be 0 for a virtual baseclass, and ignored; it
is assumed that there will be a $vb later. So that offset slot is a
perfect place to put the information I need. Just let me know if it is
relative to the start of the vtable or to the vtable pointer. That'll
be enough information to do a much better job.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
----- End forwarded message -----
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2001-11-28 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 12:18 Daniel Jacobowitz [this message]
2001-11-21 13:26 ` Daniel Jacobowitz
2001-11-21 15:21 ` Daniel Berlin
2001-11-28 12:56 ` Daniel Berlin
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=20011128151908.A1036@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.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