Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Improve vmcore loading
Date: Mon, 03 Jul 2023 18:03:55 +0100	[thread overview]
Message-ID: <873525lyf8.fsf@redhat.com> (raw)
In-Reply-To: <cover.1685956034.git.aburgess@redhat.com>

Andrew Burgess <aburgess@redhat.com> writes:

> 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.

I've gone ahead and pushed this series.

Thanks,
Andrew


      parent reply	other threads:[~2023-07-03 17:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05  9:11 Andrew Burgess via Gdb-patches
2023-06-05  9:11 ` [PATCH 1/3] gdb: split inferior and thread setup when opening a core file Andrew Burgess via Gdb-patches
2023-06-10  0:04   ` Kevin Buettner via Gdb-patches
2023-06-05  9:11 ` [PATCH 2/3] gdb/testsuite: add test for core file with a 0 pid Andrew Burgess via Gdb-patches
2023-06-10  0:16   ` Kevin Buettner via Gdb-patches
2023-07-06 14:49   ` Pedro Alves
2023-07-07  9:56     ` Andrew Burgess via Gdb-patches
2023-07-10 11:10   ` Andrew Burgess via Gdb-patches
2023-06-05  9:11 ` [PATCH 3/3] gdb: handle core files with .reg/0 section names Andrew Burgess via Gdb-patches
2023-06-10  0:36   ` Kevin Buettner via Gdb-patches
2023-07-03 17:03 ` Andrew Burgess via Gdb-patches [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=873525lyf8.fsf@redhat.com \
    --to=gdb-patches@sourceware.org \
    --cc=aburgess@redhat.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