From: Eli Zaretskii <eliz@gnu.org>
To: "Alexandra Hájková" <ahajkova@khirnov.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add "error_message+" feature to qSupported
Date: Sat, 27 Apr 2024 13:03:24 +0300 [thread overview]
Message-ID: <865xw3w2ab.fsf@gnu.org> (raw)
In-Reply-To: <20240427085226.2087243-1-ahajkova@khirnov.net> (message from Alexandra =?utf-8?B?SMOhamtvdsOh?= on Sat, 27 Apr 2024 10:52:26 +0200)
> From: Alexandra Hájková <ahajkova@khirnov.net>
> Cc: ahajkova@redhat.com
> Date: Sat, 27 Apr 2024 10:52:26 +0200
>
> From: Alexandra Hájková <ahajkova@redhat.com>
>
> Check if the gdbserver GDB is communicating with supports
> responding with the error message in an E.message format to GDB's
> packets.
>
> Add a new 'error_message' feature to the qSupported packet. When GDB
> and gdbserver support this feature then gdbserver is able to send
> errors in the E.message format for the qRcmd and m packets.
>
> Update qRcmd packet and m packets documentation as qRcmd newly
> accepts errors in a E.message format.
> Previously these two packets didn't support E.message style errors.
> ---
> gdb/doc/gdb.texinfo | 27 ++++++++++++++++++++++
> gdb/remote.c | 56 +++++++++++++++++++++++++++++++++++++++++++--
> gdbserver/server.cc | 6 +++++
> gdbserver/server.h | 5 ++++
> 4 files changed, 92 insertions(+), 2 deletions(-)
Thanks.
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 92731c510b2..c589c05db58 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -42888,6 +42888,11 @@ Reply:
> Memory contents; each byte is transmitted as a two-digit hexadecimal number.
> The reply may contain fewer addressable memory units than requested if the
> server was able to read only part of the region of memory.
> +@item E @var{NN}
> +@var{NN} is errno
> +@item E.errtext
> +Alternatively, an error can be sent as a string. This reply is only valid
Two spaces between sentences, please (here and elsewhere in the
patch).
> +if the 'accept-error-message' feature (@pxref{accept-error-message}) is enabled.
^^^^^^^^^^^^^^^^^^^^^^
This should be @code{accept-error-message} instead of the quotes.
> +Alternatively, an error can be sent as a string. This reply is only valid
> +if the 'accept-error-message' feature (@pxref{accept-error-message}) is enabled.
^^^^^^^^^^^^^^^^^^^^^^
Likewise.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2024-04-27 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-27 8:52 Alexandra Hájková
2024-04-27 10:03 ` Eli Zaretskii [this message]
2024-04-29 14:17 ` Tom Tromey
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=865xw3w2ab.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ahajkova@khirnov.net \
--cc=gdb-patches@sourceware.org \
/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).