This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC/RFA] gdb extension for Harvard architectures
- To: Michael Snyder <msnyder at cygnus dot com>
- Subject: Re: [RFC/RFA] gdb extension for Harvard architectures
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Wed, 03 Oct 2001 15:16:45 -0400
- Cc: gdb-patches at sources dot redhat dot com
- References: <3BB4D843.A92818B9@cygnus.com> <3BB512A9.6050801@cygnus.com> <3BB5195F.6050603@cygnus.com> <3BBB50C0.BD01BF20@cygnus.com> <3BBB5391.4010001@cygnus.com> <3BBB5E0A.14435A06@cygnus.com>
> 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.
Andrew