From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
Fabian Kilger <kilger@sec.in.tum.de>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2][PR GDB/32956] gdb: implement linux namespace support for fileio_stat
Date: Wed, 11 Jun 2025 11:45:57 -0600 [thread overview]
Message-ID: <87v7p2masq.fsf@tromey.com> (raw)
In-Reply-To: <87tt4mgwsd.fsf@redhat.com> (Andrew Burgess's message of "Wed, 11 Jun 2025 15:47:30 +0100")
>>>>> "Andrew" == Andrew Burgess <aburgess@redhat.com> writes:
Andrew> - The vFile:stat packet was only added in GDB 16
... I didn't realize that.
Andrew> If you feel strongly though then we can for sure just leave the
Andrew> vFile:stat packet implemented as 'lstat' and document it as such.
Given the above it seems fine to go ahead
Tom
next prev parent reply other threads:[~2025-06-11 18:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 15:01 [PATCH 0/2][PR GDB/32956] gdb: fix GDB failing to find build-id debug files in linux mount namespaces Fabian Kilger
2025-05-11 15:01 ` [PATCH 1/2][PR GDB/32956] gdb: implement linux namespace support for fileio_stat Fabian Kilger
2025-05-23 18:14 ` Andrew Burgess
2025-05-24 20:25 ` Fabian Kilger
2025-06-11 9:43 ` Andrew Burgess
2025-05-24 10:46 ` Andrew Burgess
2025-05-24 19:43 ` Fabian Kilger
2025-05-24 20:43 ` Fabian Kilger
2025-06-11 9:47 ` Andrew Burgess
2025-06-11 9:58 ` Andrew Burgess
2025-06-11 13:29 ` Tom Tromey
2025-06-11 14:47 ` Andrew Burgess
2025-06-11 17:45 ` Tom Tromey [this message]
2025-06-11 15:06 ` Fabian Kilger
2025-05-11 15:01 ` [PATCH 2/2][PR GDB/32956] gdb: query inferior's filesystem for build-id debug files Fabian Kilger
2025-05-23 18:20 ` Andrew Burgess
2025-05-24 19:54 ` Fabian Kilger
2025-06-10 9:10 ` Andrew Burgess
2025-06-11 8:11 ` Fabian Kilger
2025-06-11 9:35 ` Andrew Burgess
2025-06-11 14:00 ` Simon Marchi
2025-05-30 19:50 ` [PATCH 0/2][PR GDB/32956] gdb: fix GDB failing to find build-id debug files in linux mount namespaces Tom Tromey
2025-06-10 17:02 ` Andrew Burgess
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=87v7p2masq.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kilger@sec.in.tum.de \
/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