From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: static cast from base class to derived class
Date: Wed, 21 Aug 2002 05:25:00 -0000 [thread overview]
Message-ID: <20020821122557.GA19505@nevyn.them.org> (raw)
In-Reply-To: <200208210600.g7L60qD29529@zenia.red-bean.com>
On Wed, Aug 21, 2002 at 01:00:52AM -0500, Jim Blandy wrote:
>
> Once when my grandfather was a boy, he was riding his bicycle along a
> gravel path, and going pretty fast, when he hit a stone, went flying
> over the handlebars, and landed on his face. The gravel was ground so
> deeply into his face that, even in his forties, he'd still
> occasionally encounter, while shaving, bits of rock that had finally
> worked their way out to the surface.
>
> Here's a patch for a bit of 1998 HP Merge gravel that has finally
> found its way to the surface.
>
> I didn't see any regressions with this patch using either STABS or
> Dwarf 2. I'll put together a regression test for the original bug
> tomorrow.
>
> 2002-08-20 Jim Blandy <jimb@redhat.com>
>
> * valops.c (value_cast): Simplify and correct logic for doing a
> static cast from a pointer to a base class to a pointer to a
> derived class.
>
> Index: gdb/valops.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/valops.c,v
> retrieving revision 1.67
> diff -c -r1.67 valops.c
> *** gdb/valops.c 19 Aug 2002 23:19:53 -0000 1.67
> --- gdb/valops.c 21 Aug 2002 02:42:21 -0000
> ***************
> *** 361,378 ****
> value_zero (t1, not_lval), 0, t1, 1);
> if (v)
> {
> ! struct value *v2 = value_ind (arg2);
> ! VALUE_ADDRESS (v2) -= VALUE_ADDRESS (v)
> ! + VALUE_OFFSET (v);
> !
> ! /* JYG: adjust the new pointer value and
> ! embedded offset. */
> ! v2->aligner.contents[0] -= VALUE_EMBEDDED_OFFSET (v);
> ! VALUE_EMBEDDED_OFFSET (v2) = 0;
> !
> ! v2 = value_addr (v2);
> ! VALUE_TYPE (v2) = type;
> ! return v2;
> }
> }
> }
> --- 361,371 ----
> value_zero (t1, not_lval), 0, t1, 1);
> if (v)
> {
> ! CORE_ADDR addr2 = value_as_address (arg2);
> ! addr2 -= (VALUE_ADDRESS (v)
> ! + VALUE_OFFSET (v)
> ! + VALUE_EMBEDDED_OFFSET (v));
> ! return value_from_pointer (type, addr2);
> }
> }
> }
I've got a question... what does VALUE_ADDRESS mean in this context?
If it means what it normally means (ought to mean?), then taking an
address, subtracting an address, and using it as a pointer doesn't make
a lot of sense.
Answering my own question - it's dereferencing a pointer to a struct at
0. So we'll actually get an address relative to zero, which makes
everything work out. This looks good to me.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-08-21 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 23:11 Jim Blandy
2002-08-21 5:25 ` Daniel Jacobowitz [this message]
2002-08-21 10:22 ` Jim Blandy
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=20020821122557.GA19505@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
/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