From: Michael Snyder <msnyder@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jim Blandy <jimb@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] gdb extension for Harvard architectures
Date: Tue, 02 Oct 2001 15:09:00 -0000 [thread overview]
Message-ID: <3BBA3B03.B864ABE0@cygnus.com> (raw)
In-Reply-To: <3BBA2DC9.5060500@cygnus.com>
Andrew Cagney wrote:
>
> > Andrew Cagney <ac131313@cygnus.com> writes:
> >
> >> Would it be better if the cast operator, by default, preserved the
> >> address space of the pointer being cast?
> >
> >
> > That would get a bit hairy. If I've got a value of the type:
> >
> > (@code int * @code * @code * @code)
> >
> > --- that is, "a pointer in code space to a pointer in code space to a
> > pointer in code space to an int in code space" --- and cast it to
> >
> > (int **)
> >
> > (note that I've dropped a layer of pointers here), how far down do we
> > go? Does that become a `@code int * @code * @code'? Or just a `int
> > * @code *'? It's a bit weird.
>
> You don't.
>
> > I kind of think that casts should just work the normal way. People
> > working on machines with separate address spaces have to think a
> > little harder --- I don't think we can really conceal that.
>
> Remember we're talking about poerations that potentially cast a code
> pointer to a data or I/O pointer so this can't be described as normal.
> It is definitly way outside the bounds of the C language spec.
>
> Any way, consider the intent of someone entering a sequence like:
>
> (gdb) x/w foo
> 0x0
> (gdb) x/i foo
> nop
Andrew, right now the "x" command has no knowledge about
separate code and data spaces, so both "x/w foo" and "x/i foo"
will refer to the same address. Whether that address comes
from code or data space depends entirely on the data type of foo.
If foo is a data-like object (eg. an int or an int pointer)
it will come from data space. If foo is a function, it will come
from code space. The purpose of the @code and @data modifiers
is to override this default.
> (gdb) print/x *(int*)foo
> 0xdeadbeef
An (int *) is by default a data pointer.
A function pointer is by default a code pointer.
> vs
> (gdb) print/x *(int*)foo
> 0x0
>
> and where should this go:
>
> (gdb) set *(int*)foo = 0xdeadbeef
This will go to data space. Any "normal" data type will default to data
space (as it already does). The @code and @data modifiers are for when
you want to alter the default behavior.
> This mysterious address switching strikes me as wierd.
You are right -- it's wierd. ;-)
next prev parent reply other threads:[~2001-10-02 15:09 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 13:07 Michael Snyder
2001-09-28 13:50 ` Andrew Cagney
2001-10-03 10:41 ` Michael Snyder
2001-10-03 11:06 ` Daniel Jacobowitz
2001-10-03 11:12 ` Michael Snyder
2001-10-03 11:19 ` Andrew Cagney
2001-10-03 11:49 ` Michael Snyder
2001-10-03 14:38 ` Andrew Cagney
2001-10-03 14:14 ` Jim Blandy
2001-10-03 14:31 ` Andrew Cagney
2001-10-03 16:14 ` Jim Blandy
2001-10-04 11:44 ` Michael Snyder
2001-10-04 16:28 ` Jim Blandy
2001-09-28 17:15 ` Andrew Cagney
2001-09-28 17:44 ` Andrew Cagney
2001-10-02 12:59 ` Jim Blandy
2001-10-02 14:13 ` Andrew Cagney
2001-10-02 15:09 ` Michael Snyder [this message]
2001-10-02 16:58 ` Andrew Cagney
2001-10-03 10:10 ` Jim Blandy
2001-10-03 12:22 ` Andrew Cagney
2001-10-03 15:08 ` Jim Blandy
2001-10-10 0:56 ` Andrew Cagney
2001-10-09 23:34 ` Andrew Cagney
2001-10-10 10:53 ` Jim Blandy
2001-10-10 11:17 ` Andrew Cagney
2001-10-10 12:15 ` Jim Blandy
2001-10-10 12:31 ` Andrew Cagney
2001-10-10 0:16 ` Andrew Cagney
2001-10-03 11:11 ` Michael Snyder
2001-10-04 12:08 ` Michael Snyder
2001-10-04 13:13 ` Andrew Cagney
2001-10-08 10:36 ` Michael Snyder
2001-10-10 1:25 ` Andrew Cagney
2001-11-05 11:34 ` Michael Snyder
2001-10-02 16:14 ` Jim Blandy
2001-10-02 17:16 ` Andrew Cagney
2001-10-02 17:31 ` Michael Snyder
2001-10-02 19:09 ` Andrew Cagney
2001-10-03 12:41 ` Jim Blandy
2001-10-03 12:52 ` Andrew Cagney
2001-10-03 16:13 ` Jim Blandy
2001-10-03 16:51 ` Frank Ch. Eigler
2001-10-03 10:55 ` Michael Snyder
2001-10-03 11:06 ` Andrew Cagney
2001-10-03 11:51 ` Michael Snyder
2001-10-03 12:17 ` Andrew Cagney
2001-10-03 16:54 ` Michael Snyder
2001-10-03 14:33 ` Jim Blandy
2001-10-03 14:44 ` Andrew Cagney
2001-10-03 16:17 ` Jim Blandy
2001-10-04 13:16 ` Andrew Cagney
2001-10-10 0:45 ` Andrew Cagney
2001-10-10 10:56 ` Jim Blandy
2001-10-03 14:48 ` Andrew Cagney
2001-10-04 11:49 ` Michael Snyder
2001-10-03 10:49 ` Michael Snyder
2001-09-29 2:29 ` Eli Zaretskii
2001-10-02 19:27 ` Andrew Cagney
2001-10-03 14:04 ` 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=3BBA3B03.B864ABE0@cygnus.com \
--to=msnyder@cygnus.com \
--cc=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