From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: Tom Tromey <tom@tromey.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: RE: [RFC PATCH] gdb, rsp: clarify a 0-length memory access
Date: Thu, 28 Mar 2024 09:56:09 +0000 [thread overview]
Message-ID: <DM4PR11MB7303819115A24F8D7062D0FAC43B2@DM4PR11MB7303.namprd11.prod.outlook.com> (raw)
In-Reply-To: <86v85f1qfs.fsf@gnu.org>
Hi Tom,
On Thursday, March 21, 2024 5:49 PM, Eli Zaretskii wrote:
> > From: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
> > Date: Thu, 21 Mar 2024 14:30:18 +0100
> >
> > Currently GDB uses a 0-length write access to probe for the 'X' packet
> > support. However, it is not clear from the document what a 0-length
> > read or write attempt should do. Clarify the document that it is
> > an error. Also update gdbserver's implementation to return an error.
> >
> > Note that for probing, returning an error is fine. It successfully
> > shows that the packet is supported.
> >
> > Regression-tested on X86-64 Linux using the default (unix) and
> > native-extended-gdbserver board files.
> > ---
> > gdb/doc/gdb.texinfo | 9 +++++++++
> > gdbserver/target.cc | 9 ++++++---
> > 2 files changed, 15 insertions(+), 3 deletions(-)
>
> Thanks, the documentation part is okay.
>
> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Would the code parts be ok? This is based on the discussion we had stemming
from the 'x' packet.
Thanks
-Baris
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2024-03-28 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 13:30 Tankut Baris Aktemur
2024-03-21 16:48 ` Eli Zaretskii
2024-03-28 9:56 ` Aktemur, Tankut Baris [this message]
2024-03-28 14:13 ` Andrew Burgess
2024-03-28 15:31 ` Aktemur, Tankut Baris
2024-04-05 13:10 ` Andrew Burgess
2024-04-09 6:39 ` Aktemur, Tankut Baris
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=DM4PR11MB7303819115A24F8D7062D0FAC43B2@DM4PR11MB7303.namprd11.prod.outlook.com \
--to=tankut.baris.aktemur@intel.com \
--cc=eliz@gnu.org \
--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