From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/3] Improve vmcore loading
Date: Mon, 5 Jun 2023 10:11:06 +0100 [thread overview]
Message-ID: <cover.1685956034.git.aburgess@redhat.com> (raw)
This patch started as a proposal to upstream a test from the Fedora
GDB tree (patch #2), however, as I started looking into the test a
little more I realised that there was scope for further improvements
to GDB (patch #3). Patch #1 is a small cleanup/refactor.
This patch is all about loading vmcore files -- that is core files
generated by the Linux kernel. See the commit messages on patches #2
and #3 for more details.
Thanks,
Andrew
---
Andrew Burgess (3):
gdb: split inferior and thread setup when opening a core file
gdb/testsuite: add test for core file with a 0 pid
gdb: handle core files with .reg/0 section names
gdb/corelow.c | 212 +++++++++++++++---
gdb/testsuite/gdb.arch/core-file-pid0.exp | 73 ++++++
.../gdb.arch/core-file-pid0.x86-64.core.bz2 | Bin 0 -> 750 bytes
3 files changed, 252 insertions(+), 33 deletions(-)
create mode 100644 gdb/testsuite/gdb.arch/core-file-pid0.exp
create mode 100644 gdb/testsuite/gdb.arch/core-file-pid0.x86-64.core.bz2
base-commit: e9683acf5e51c2bac8aa68d30d9ac3683dddcc7d
--
2.25.4
next reply other threads:[~2023-06-05 9:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 9:11 Andrew Burgess [this message]
2023-06-05 9:11 ` [PATCH 1/3] gdb: split inferior and thread setup when opening a core file Andrew Burgess
2023-06-10 0:04 ` Kevin Buettner
2023-06-05 9:11 ` [PATCH 2/3] gdb/testsuite: add test for core file with a 0 pid Andrew Burgess
2023-06-10 0:16 ` Kevin Buettner
2023-07-06 14:49 ` Pedro Alves
2023-07-07 9:56 ` Andrew Burgess
2023-07-10 11:10 ` Andrew Burgess
2023-06-05 9:11 ` [PATCH 3/3] gdb: handle core files with .reg/0 section names Andrew Burgess
2023-06-10 0:36 ` Kevin Buettner
2023-07-03 17:03 ` [PATCH 0/3] Improve vmcore loading 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.1685956034.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).