Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: Abhay Kandpal <abhay@linux.ibm.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Andrew Burgess <aburgess@redhat.com>,
	"eliz@gnu.org" <eliz@gnu.org>,
	"cel@linux.ibm.com" <cel@linux.ibm.com>,
	Abhay Kandpal <Abhay.k@ibm.com>
Subject: Re: [PATCH v3 2/2] gdb: add stat64 and fstat64 to the F-packet file-i/o protocol
Date: Wed, 28 Oct 2026 14:19:34 +0000	[thread overview]
Message-ID: <e28a81df76b4fa567497ff3deda096b65b4fa0a2.camel@de.ibm.com> (raw)
In-Reply-To: <a6591a5e-ec76-4b91-bc2e-da9a9bc99e4e@linux.ibm.com>

Abhay Kandpal <abhay@linux.ibm.com> wrote:

 
>There is a second mismatch as well. For a regular file, the fstat
>handler never sets fst_dev, so the host's real st_dev is passed
>through rather than the documented 0. Today only stat matches
>the documentation:
>
>stat, file:        documented 0, sends 0
>fstat, console:    documented 1, sends 0
>fstat, file:       documented 0, sends the host's st_dev

Ah, right.  That's even more confusing.

>My preference would be to fix the code to match the documentation,
>since the 2015 change looks accidental. I'd do that as a separate
>patch, so it doesn't depend on the stat64 series.

This makes sense to me, yes.

Thanks,
Ulrich


 

      reply	other threads:[~2026-10-28 14:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  9:21 [PATCH v3 0/2] Widen the stat fields in the remote protocol Abhay Kandpal
2026-10-14  9:21 ` [PATCH v3 1/2] gdbserver: widen the stat fields returned by the vFile packets Abhay Kandpal
2026-10-27 17:27   ` Ulrich Weigand
2026-10-27 22:16   ` Andrew Burgess
2026-10-14  9:21 ` [PATCH v3 2/2] gdb: add stat64 and fstat64 to the F-packet file-i/o protocol Abhay Kandpal
2026-10-14 11:47   ` Eli Zaretskii
2026-10-27 17:47   ` Ulrich Weigand
2026-10-28 10:42     ` Abhay Kandpal
2026-10-28 14:19       ` Ulrich Weigand [this message]

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=e28a81df76b4fa567497ff3deda096b65b4fa0a2.camel@de.ibm.com \
    --to=ulrich.weigand@de.ibm.com \
    --cc=Abhay.k@ibm.com \
    --cc=abhay@linux.ibm.com \
    --cc=aburgess@redhat.com \
    --cc=cel@linux.ibm.com \
    --cc=eliz@gnu.org \
    --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