From: Daniel Jacobowitz <drow@mvista.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: Benjamin Kosnik <bkoz@redhat.com>,
Eli Zaretskii <eliz@is.elta.co.il>,
jason@redhat.com, libstdc++@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: c++ debugging hosed
Date: Mon, 26 Nov 2001 16:53:00 -0000 [thread overview]
Message-ID: <20011126195405.A29713@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0111261942360.20651-100000@www.cgsoftware.com>
On Mon, Nov 26, 2001 at 07:43:39PM -0500, Daniel Berlin wrote:
>
>
> On Mon, 26 Nov 2001, Daniel Jacobowitz wrote:
> > Could you clarify what symptom this fix you're discussing is supposed
> > to solve?
> Not being able to print subobjects, etc.
OK, I'm just printing objects right now :)
> > I thought it was the one I was working on, but
> > baseclass_offset actually does nothing ABI specific at all.
> This would be incorrect for virtual base classes
> Look at it again.
> Also notice we call find_rt_base_offset for the HP ABI.
> The reason is that baseclass offsets are *always* abi specific.
(it's find_rt_vbase_offset)
OK, this isn't in baseclass_offset. I assume you mean
search_struct_method or find_method_list.
I'll get back to this in a few days when I fix my current bug.
--
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: Daniel Berlin <dan@cgsoftware.com>
Cc: Benjamin Kosnik <bkoz@redhat.com>,
Eli Zaretskii <eliz@is.elta.co.il>,
jason@redhat.com, libstdc++@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: c++ debugging hosed
Date: Thu, 15 Nov 2001 09:57:00 -0000 [thread overview]
Message-ID: <20011126195405.A29713@nevyn.them.org> (raw)
Message-ID: <20011115095700.Oaf1Bbz8K-lwD3u8w8JI1xLvTlznJKj0X1Re_6SUeWI@z> (raw)
In-Reply-To: <Pine.LNX.4.33.0111261942360.20651-100000@www.cgsoftware.com>
On Mon, Nov 26, 2001 at 07:43:39PM -0500, Daniel Berlin wrote:
>
>
> On Mon, 26 Nov 2001, Daniel Jacobowitz wrote:
> > Could you clarify what symptom this fix you're discussing is supposed
> > to solve?
> Not being able to print subobjects, etc.
OK, I'm just printing objects right now :)
> > I thought it was the one I was working on, but
> > baseclass_offset actually does nothing ABI specific at all.
> This would be incorrect for virtual base classes
> Look at it again.
> Also notice we call find_rt_base_offset for the HP ABI.
> The reason is that baseclass offsets are *always* abi specific.
(it's find_rt_vbase_offset)
OK, this isn't in baseclass_offset. I assume you mean
search_struct_method or find_method_list.
I'll get back to this in a few days when I fix my current bug.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-11-26 16:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200110291812.f9TICtQ10130@constant.com>
2001-11-03 1:50 ` Jason Merrill
2001-11-03 7:59 ` Benjamin Kosnik
2001-11-03 10:52 ` Benjamin Kosnik
2001-11-12 8:27 ` Eli Zaretskii
2001-11-12 11:29 ` Daniel Berlin
2001-11-13 10:06 ` Benjamin Kosnik
2001-11-13 10:07 ` Daniel Berlin
2001-11-13 13:18 ` Benjamin Kosnik
2001-11-25 22:56 ` Benjamin Kosnik
2001-11-26 15:38 ` Daniel Jacobowitz
2001-11-14 20:13 ` Daniel Jacobowitz
2001-11-15 8:55 ` Daniel Berlin
2001-11-15 13:10 ` Daniel Jacobowitz
2001-11-26 17:19 ` Daniel Jacobowitz
2001-11-26 16:53 ` Daniel Berlin
2001-11-26 16:43 ` Daniel Berlin
2001-11-15 8:48 ` Daniel Berlin
2001-11-26 16:53 ` Daniel Jacobowitz [this message]
2001-11-15 9:57 ` Daniel Jacobowitz
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=20011126195405.A29713@nevyn.them.org \
--to=drow@mvista.com \
--cc=bkoz@redhat.com \
--cc=dan@cgsoftware.com \
--cc=eliz@is.elta.co.il \
--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