From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/8] Extension for looking up debug info by build-id
Date: Wed, 5 Jun 2024 14:15:07 +0100 [thread overview]
Message-ID: <cover.1717592683.git.aburgess@redhat.com> (raw)
Patches #1 and #2 are bug fixes.
Patch #3 is a minor improvement.
Patch #4 is a conversion to the new(ish) debug scheme.
Patches #5, #6, & #7 add target_ops::fileio_stat() function.
Patch #8 adds an extension to how GDB looks for files based on
build-id.
---
Andrew Burgess (8):
gdb/fileio: fix errno for packets where an attachment is expected
gdb: avoid duplicate search in build_id_to_bfd_suffix
gdb: warn of slow remote file reading only after a successful open
gdb: convert separate-debug-file to new(ish) debug scheme
gdb: add target_fileio_stat, but no implementations yet
gdb: add GDB side target_ops::fileio_stat implementation
gdbserver: add gdbserver support for vFile::stat packet
gdb: check for multiple matching build-id files
gdb/NEWS | 5 +
gdb/build-id.c | 205 +++++++++++++-----
gdb/doc/gdb.texinfo | 11 +
gdb/inf-child.c | 15 ++
gdb/inf-child.h | 2 +
gdb/remote.c | 122 ++++++++---
gdb/symfile.c | 45 ++--
gdb/symfile.h | 19 ++
gdb/target.c | 31 +++
gdb/target.h | 16 ++
gdb/testsuite/gdb.base/build-id-seqno.c | 22 ++
gdb/testsuite/gdb.base/build-id-seqno.exp | 133 ++++++++++++
gdb/testsuite/gdb.server/build-id-seqno.c | 22 ++
gdb/testsuite/gdb.server/build-id-seqno.exp | 198 +++++++++++++++++
gdb/testsuite/gdb.server/remote-read-msgs.c | 22 ++
gdb/testsuite/gdb.server/remote-read-msgs.exp | 119 ++++++++++
gdbserver/hostio.cc | 38 ++++
17 files changed, 912 insertions(+), 113 deletions(-)
create mode 100644 gdb/testsuite/gdb.base/build-id-seqno.c
create mode 100644 gdb/testsuite/gdb.base/build-id-seqno.exp
create mode 100644 gdb/testsuite/gdb.server/build-id-seqno.c
create mode 100644 gdb/testsuite/gdb.server/build-id-seqno.exp
create mode 100644 gdb/testsuite/gdb.server/remote-read-msgs.c
create mode 100644 gdb/testsuite/gdb.server/remote-read-msgs.exp
base-commit: 2db414c36b4f030782c2c8a24c916c3033261af0
--
2.25.4
next reply other threads:[~2024-06-05 13:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 13:15 Andrew Burgess [this message]
2024-06-05 13:15 ` [PATCH 1/8] gdb/fileio: fix errno for packets where an attachment is expected Andrew Burgess
2024-06-06 16:49 ` Tom Tromey
2024-06-11 19:52 ` Andrew Burgess
2024-06-05 13:15 ` [PATCH 2/8] gdb: avoid duplicate search in build_id_to_bfd_suffix Andrew Burgess
2024-06-06 16:49 ` Tom Tromey
2024-06-11 19:52 ` Andrew Burgess
2024-06-05 13:15 ` [PATCH 3/8] gdb: warn of slow remote file reading only after a successful open Andrew Burgess
2024-06-06 16:58 ` Tom Tromey
2024-06-11 19:52 ` Andrew Burgess
2024-06-05 13:15 ` [PATCH 4/8] gdb: convert separate-debug-file to new(ish) debug scheme Andrew Burgess
2024-06-06 16:54 ` Tom Tromey
2024-06-11 19:52 ` Andrew Burgess
2024-06-05 13:15 ` [PATCH 5/8] gdb: add target_fileio_stat, but no implementations yet Andrew Burgess
2024-06-05 13:15 ` [PATCH 6/8] gdb: add GDB side target_ops::fileio_stat implementation Andrew Burgess
2024-06-05 14:21 ` Eli Zaretskii
2024-06-05 13:15 ` [PATCH 7/8] gdbserver: add gdbserver support for vFile::stat packet Andrew Burgess
2024-06-05 13:15 ` [PATCH 8/8] gdb: check for multiple matching build-id files Andrew Burgess
2024-06-13 10:29 ` [PATCH 0/8] Extension for looking up debug info by build-id Andrew Burgess
2024-06-13 10:29 ` [PATCHv2 1/4] gdb: add target_fileio_stat, but no implementations yet Andrew Burgess
2024-06-13 10:29 ` [PATCHv2 2/4] gdb: add GDB side target_ops::fileio_stat implementation Andrew Burgess
2024-06-13 10:29 ` [PATCHv2 3/4] gdbserver: add gdbserver support for vFile::stat packet Andrew Burgess
2024-06-13 10:29 ` [PATCHv2 4/4] gdb: check for multiple matching build-id files 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=cover.1717592683.git.aburgess@redhat.com \
--to=aburgess@redhat.com \
--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).