From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: addresses and pointers may be different sizes while printing
Date: Thu, 05 Jul 2001 13:22:00 -0000 [thread overview]
Message-ID: <3B44CC74.8070603@cygnus.com> (raw)
In-Reply-To: <npwv5nmh6x.fsf@zwingli.cygnus.com>
> Andrew Cagney <ac131313@cygnus.com> writes:
>
>> Would you have an example illustrating the actual affect of this change?
>
>
> Sure. First, read the section ``Pointers Are Not Always Addresses''
> in doc/gdbint.texinfo. It actually uses the D10V as its running
> example.
gdb.texinfo? Do we need a gdb.base/harvard.exp?
> This patch only affects architectures where code addresses and
> pointers are different sizes, like the D10V. Without my larger D10V
> patch ("RFA: Remove D10V-specific code from arch-independent
> modules"), GDB represents all code pointers as 32 bit values, so this
> patch has no effect there, either.
I can imagine that. I was kind of assuming you're examples would be
pre/post all changes.
> (gdb) print main
> $1 = {int ()} 0x101405c <main>
> (gdb) print/x &main
> $2 = 0x405c
> (gdb)
then
> (gdb) print main
> $1 = {int ()} 0x101405c <main>
> (gdb) print/x &main
> $2 = 0x101405c
> (gdb)
to be 110% sure, all of:
(gdb) print main
(gdb) print &main
(gdb) print/x main
(gdb) print/x &main
end up displaying the same hex (CORE_ADDR) value?
Andrew
next prev parent reply other threads:[~2001-07-05 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 15:35 Jim Blandy
[not found] ` <3B43F682.1040502@cygnus.com>
2001-07-05 10:13 ` Jim Blandy
2001-07-05 13:22 ` Andrew Cagney [this message]
2001-07-05 16:33 ` Jim Blandy
2001-07-05 23:14 ` Andrew Cagney
2001-07-06 14:51 ` Jim Blandy
2001-07-10 13:32 ` Andrew Cagney
2001-07-09 19:49 David Taylor
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=3B44CC74.8070603@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@cygnus.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