From: Pedro Alves <pedro@palves.net>
To: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v5 00/14] Fix BZ 25631 - core file memory access problem
Date: Wed, 22 Jul 2020 19:58:59 +0100 [thread overview]
Message-ID: <35982031-7050-c45b-8940-0b770c4d9803@palves.net> (raw)
In-Reply-To: <20200722005832.863276-1-kevinb@redhat.com>
On 7/22/20 1:58 AM, Kevin Buettner via Gdb-patches wrote:
> This series fixes several core file related bugs. The bug which
> started this work can be viewed here:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=25631
>
> Other problems were found either during review or during development.
> I discuss these in my commit log remarks.
>
> This v5 series has only minor changes from v4. Unless noted
> otherwise, these changes all address Pedro's concerns:
>
> o Patch #5, Test ability to access unwritten-to mmap data in core file:
>
> - Add setup_xfail for non-Linux OSes. (I spotted this while testing
> on FreeBSD.)
>
> o Patch #8, Use NT_FILE note section for reading core target memory:
>
> - Formatting fixes.
> - Close bfd after failed bfd_check_format_check.
> - Fix SECNAME leak.
>
> o Patch #11, Adjust coredump-filter.exp to account for NT_FILE note handling:
>
> - Instead of XFAILing test, use Mihails Strasuns's suggestion
> instead.
>
> o Patch #12, Add new command "maint print core-file-backed-mappings":
>
> - Formatting fixes.
> - Don't crash GDB with gdb_assert().
> - Add comments (in both code and commit log) regarding utility
> of this new command.
>
> o Patch #14, New core file tests with mappings over existing program memory:
>
> - Formatting fixes.
> - Add another "maint print core-file-backed-mappings" test requested
> by Pedro in patch #12 review. This one makes sure that we don't
> crash GDB when NOT debugging a core file.
>
> I believe that all patches not listed above have been approved.
> Actually, I think that #5 is still approved too; I doubt that adding
> an XFAIL changes that.
I sent a minor comment to patch #11. Everything else looks great to me.
Thanks for doing all this. Great job.
Pedro Alves
next prev parent reply other threads:[~2020-07-22 18:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 0:58 Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 01/14] Remove hack for GDB which sets the section size to 0 Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 02/14] Adjust corefile.exp test to show regression after bfd hack removal Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 03/14] section_table_xfer_memory: Replace section name with callback predicate Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 04/14] Provide access to non SEC_HAS_CONTENTS core file sections Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 05/14] Test ability to access unwritten-to mmap data in core file Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 06/14] Update binary_get_section_contents to seek using section's file position Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 07/14] Add new gdbarch method, read_core_file_mappings Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 08/14] Use NT_FILE note section for reading core target memory Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 09/14] Add test for accessing read-only mmapped data in a core file Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 10/14] gcore command: Place all file-backed mappings in NT_FILE note Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 11/14] Adjust coredump-filter.exp to account for NT_FILE note handling Kevin Buettner
2020-07-22 18:56 ` Pedro Alves
2020-07-22 0:58 ` [PATCH v5 12/14] Add new command "maint print core-file-backed-mappings" Kevin Buettner
2020-07-23 13:08 ` Tom de Vries
2020-07-23 20:47 ` Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 13/14] Add documentation for " Kevin Buettner
2020-07-22 2:27 ` Eli Zaretskii
2020-07-22 0:58 ` [PATCH v5 14/14] New core file tests with mappings over existing program memory Kevin Buettner
2020-07-22 18:58 ` Pedro Alves [this message]
2020-07-22 20:14 ` [PATCH v5 00/14] Fix BZ 25631 - core file memory access problem Kevin Buettner
2020-07-22 22:40 ` Luis Machado
2020-07-23 3:49 ` Kevin Buettner
2020-07-23 10:37 ` Luis Machado
2020-07-23 21:44 ` Kevin Buettner
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=35982031-7050-c45b-8940-0b770c4d9803@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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