From: Andrew Cagney <cagney@gnu.org>
To: Robert Picco <Robert.Picco@hp.com>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: new gdb remote packet type
Date: Fri, 24 Sep 2004 20:07:00 -0000 [thread overview]
Message-ID: <41547DD5.5020100@gnu.org> (raw)
In-Reply-To: <410E623C.3020107@hp.com>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
[draining my backlog]
> Andrew Cagney wrote:
>
>>
>> To get this in, there's some additional leg work:
>>
>> - copyright assignment?
>>
>> - documentation (see gdb/doc/gdb.texinfo near the end)
>>
>> - a corresponding gdbserver patch
>>
>> - not to forget, ChangeLogs :-)
>>
>> Andrew
I cleaned up the ChangeLog and commited the remote.c change (adding a
nod to Fernando Nasser who wrote a part of the original code).
Eli, How's the attached slightly revised doco tweak?
Andrew
> FSF has a copyright assignment on file for me. The other items you mentioned are contained in the patch below with the exception of gdbserver patch. There wasn't any feedback on 'P' packet support not being in gdbserver. So I'm assuming that not adding 'p' packet support is o.k.
>
> thanks,
>
> Bob
>
> diff -ruN gdb-6.1.1-orig/gdb/ChangeLog gdb-6.1.1/gdb/ChangeLog
> --- gdb-6.1.1-orig/gdb/ChangeLog 2004-06-14 18:39:49.000000000 -0400
> +++ gdb-6.1.1/gdb/ChangeLog 2004-08-02 10:33:03.993382712 -0400
> @@ -1,3 +1,9 @@
> +2004-06-28 Robert Picco <Robert.Picco@hp.com>
> + * Add new 'p' packet to gdb/remote.c. The 'p' is for fetching
> + the value of a single register. It complements the 'P' which
> + writes a single register. Should the remote gdbserver support
> + the 'p', then 'g' packets aren't used.
> +
> 2004-06-14 GDB Administrator <gdbadmin@sourceware.org>
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1135 bytes --]
2004-09-24 Andrew Cagney <cagney@gnu.org>
Robert Picco <Robert.Picco@hp.com>
* gdb.texinfo (Packets): Document the "p" packet.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.214
diff -p -u -r1.214 gdb.texinfo
--- gdb.texinfo 20 Sep 2004 22:26:21 -0000 1.214
+++ gdb.texinfo 24 Sep 2004 20:04:27 -0000
@@ -19963,17 +19963,20 @@ Reserved for future use.
@item @code{O} --- reserved
-Reserved for future use.
-
-@item @code{p}@var{n@dots{}} --- read reg @strong{(reserved)}
+@item @code{p}@var{hex number of register} --- read register packet
@cindex @code{p} packet
-@xref{write register packet}.
+@xref{read registers packet}, for a description of how the returned
+register value is encoded.
Reply:
@table @samp
-@item @var{r@dots{}.}
-The hex encoded value of the register in target byte order.
+@item @var{XX@dots{}}
+the register's value
+@item E@var{NN}
+for an error
+@item
+Indicating an unrecognized @var{query}.
@end table
@item @code{P}@var{n@dots{}}@code{=}@var{r@dots{}} --- write register
next prev parent reply other threads:[~2004-09-24 20:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 0:45 Robert Picco
2004-04-16 18:33 ` Andrew Cagney
2004-04-22 15:45 ` Robert Picco
2004-04-22 16:09 ` Andrew Cagney
2004-04-29 15:31 ` Robert Picco
2004-04-30 17:31 ` Andrew Cagney
2004-05-04 17:56 ` Robert Picco
2004-05-05 19:10 ` Andrew Cagney
2004-05-06 19:41 ` Robert Picco
2004-05-11 17:31 ` Robert Picco
2004-05-12 18:20 ` Andrew Cagney
2004-05-12 18:31 ` Daniel Jacobowitz
2004-05-12 18:59 ` Robert Picco
2004-05-12 20:55 ` Daniel Jacobowitz
2004-05-12 22:16 ` Robert Picco
[not found] ` <40A279AF.30603@gnu.org>
2004-05-12 20:53 ` Daniel Jacobowitz
2004-08-02 15:51 ` Robert Picco
2004-09-24 20:07 ` Andrew Cagney [this message]
2004-09-25 16:33 ` Eli Zaretskii
2004-09-27 19:21 ` Andrew Cagney
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=41547DD5.5020100@gnu.org \
--to=cagney@gnu.org \
--cc=Robert.Picco@hp.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.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