This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: remote protocol extension for memory access width
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: remote protocol extension for memory access width
- From: jtc at redback dot com (J.T. Conklin)
- Date: 01 Feb 2001 15:13:46 -0800
- Cc: gdb at sourceware dot cygnus dot com
- References: <5md7dbkr6i.fsf@jtc.redback.com> <3A75E55D.696C4303@cygnus.com>
- Reply-To: jtc at redback dot com
>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
>> Rather than add new commands, my thought is to add attribute support
>> like:
>> mAA..AA,LLLL[,attr=val[,attr=val[,...]]]
>> MAA..AA,LLLL[,attr=val[,attr=val[,...]]]:DDDD...
Andrew> How do you expect to detect the presence or lack of support
Andrew> for this in a remote target?
You don't. But if the user doesn't specify an attribute, it won't
be added to the command packages... Ok, I admit that's not a very
satisfactory answer.
So another set of (this time extensible) commands seem to be needed.
Other than attribute support, what other deficiencies are there in the
memory read/write commands which need to be addressed? As "everyone"
knows, I'm not a big fan of the so called "binary download" command.
Perhaps we could fix it along the way.
--jtc
--
J.T. Conklin
RedBack Networks