Re: [RFC/RFA] gdb extension for Harvard architectures

[Michael Snyder <msnyder@cygnus.com>]

Andrew Cagney wrote:
> 
> > Without change.  My contention is that the user is almost never going to
> >> want to do what you just described.  Why make what the user is going to
> >> want to do hard?
> >
> >
> > This whole change was prompted by a user's request to be able
> > to do just that.  Well, actually, he wanted to be able to do
> >
> >         set *(@code short *) myfunction = 0xabcd
> 
> I think everyone is in agreement that not being able to frob an
> instruction location is a ``breakage''.  Can I guess they entered:
> 
>         set *(short *) myfunc = 0xabcd
> 
> I would.  And as I'm doing now, I would also be asking why I have to
> explicitly specify @code, when the cast operator already knows that my
> pointer is designating code space.

Your intuition is counter to what GCC actually implements.
Your hypothetical user might have the same intuition as you, 
but if he's using GCC, then his intuition may actually be
the source of the bug he's trying to debug.  GCC evaluates
the expression:

	x = *(int *) &main;

by taking a value from data space.  I think GDB should be 
able to cut and paste the expression from the source code
and give the same result that the compiler gives.