From: Daniel Berlin <dan@cgsoftware.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: <libstdc++@gcc.gnu.org>, <gdb@sources.redhat.com>
Subject: Re: [dmj+@andrew.cmu.edu: Re: C++ debugging progress]
Date: Wed, 21 Nov 2001 15:21:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0111281555310.19994-100000@www.cgsoftware.com> (raw)
In-Reply-To: <20011128151908.A1036@nevyn.them.org>
On Wed, 28 Nov 2001, Daniel Jacobowitz wrote:
> 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!
The small problem may be that we may not be able to handle it in gdb,
depending on how complex it is.
--Dan
WARNING: multiple messages have this Message-ID
From: Daniel Berlin <dan@cgsoftware.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: <libstdc++@gcc.gnu.org>, <gdb@sources.redhat.com>
Subject: Re: [dmj+@andrew.cmu.edu: Re: C++ debugging progress]
Date: Wed, 28 Nov 2001 12:56:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0111281555310.19994-100000@www.cgsoftware.com> (raw)
Message-ID: <20011128125600.113p_6NYFP1Q_6ai8sYOqrXcgbV18gcYfyntKNdLEZo@z> (raw)
In-Reply-To: <20011128151908.A1036@nevyn.them.org>
On Wed, 28 Nov 2001, Daniel Jacobowitz wrote:
> 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!
The small problem may be that we may not be able to handle it in gdb,
depending on how complex it is.
--Dan
next prev parent reply other threads:[~2001-11-28 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 12:18 Daniel Jacobowitz
2001-11-21 13:26 ` Daniel Jacobowitz
2001-11-21 15:21 ` Daniel Berlin [this message]
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=Pine.LNX.4.33.0111281555310.19994-100000@www.cgsoftware.com \
--to=dan@cgsoftware.com \
--cc=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