From: Yao Qi <qiyaoltc@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Small improvements to the remote protocol manual
Date: Thu, 15 Sep 2016 16:09:00 -0000 [thread overview]
Message-ID: <CAH=s-PPSPruEcS7xuXyrB6259WBG39prLFJrWCMopePj4vqE3w@mail.gmail.com> (raw)
In-Reply-To: <87eg4mrsvg.fsf@tromey.com>
On Wed, Sep 14, 2016 at 11:58 PM, Tom Tromey <tom@tromey.com> wrote:
> Also, I forgot to note here that I didn't understand the documentation
> for the "A" packet; but when I looked at the code I couldn't find it in
> either gdb or gdbserver. So, I wonder if it ought to be deleted.
>
The "A" packet was added in 1999 as a "reserved" packet,
+@item set program arguments @strong{(reserved)} @emph{(optional)}
+@tab @code{A}@var{arglen}@code{,}@var{argnum}@code{,}@var{arg}@code{,...}
but the "reserved" marker is removed in
b8ff78cefa335846b4303f303847a4d69e652795 (2005),
- Remove "(reserved)" markers on 'A' and 'I' packets; it's unclear
what this ever meant.
Nowadays, we still can't pass arguments in remote debugging. If "A" still
meets our needs, we can use it in the future to pass arguments.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-09-15 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 2:19 Tom Tromey
2016-09-14 22:58 ` Tom Tromey
2016-09-15 16:09 ` Yao Qi [this message]
2016-09-15 16:14 ` Tom Tromey
2016-12-02 11:58 ` Pedro Alves
2016-09-27 16:44 ` Tom Tromey
2016-09-27 17:46 ` Eli Zaretskii
2016-09-27 19:39 ` Tom Tromey
2016-09-27 19:47 ` Eli Zaretskii
2016-09-28 18:42 ` Tom Tromey
2016-12-02 11:59 ` Pedro Alves
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='CAH=s-PPSPruEcS7xuXyrB6259WBG39prLFJrWCMopePj4vqE3w@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).