From: Pedro Alves <palves@redhat.com>
To: Sergio Lopez <slp@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 0/5] Enable the user to dump all memory regions
Date: Mon, 04 Dec 2017 14:37:00 -0000 [thread overview]
Message-ID: <42ab4f25-13ef-76d4-adf1-3412a406c96d@redhat.com> (raw)
In-Reply-To: <20171204081716.5414-1-slp@redhat.com>
On 12/04/2017 08:17 AM, Sergio Lopez wrote:
> GDB versions prior to df8411da087dc05481926f4c4a82deabc5bc3859
> unconditionally included all memory regions in the core dump.
>
> After that change, while is still possible to ask GDB to ignore
> /proc/PID/coredump_filter using the 'set use-coredump-filter' command,
> there's no way to request it to dump regions marked with the VM_DONTDUMP
> flag ("dd" in /proc/PID/smaps").
>
> This patch series implement the new 'set dump-excluded-mappings' command
> for GDB, and the "-a" argument for gcore, allowing the user to mimic the
> behavior of previous GDB versions.
>
> ---
>
> Changes since v2:
> - 1/5: Removed an empty line between command and definition of variable.
> - 5/5: Added a test case for 'set dump-excluded-mappings'.
Thanks!
This is OK.
Pedro Alves
next prev parent reply other threads:[~2017-12-04 14:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 8:18 Sergio Lopez
2017-12-04 8:18 ` [PATCH v3 3/5] Implement "-a" command line option for gcore Sergio Lopez
2017-12-04 8:18 ` [PATCH v3 2/5] Document new {set,show} dump-excluded-mappings commands Sergio Lopez
2017-12-04 15:19 ` Eli Zaretskii
2017-12-04 8:18 ` [PATCH v3 1/5] Implement 'set dump-excluded-mappings' command Sergio Lopez
2017-12-04 8:26 ` [PATCH v3 4/5] Document the new "-a" command line option for gcore Sergio Lopez
2017-12-04 15:25 ` Eli Zaretskii
2017-12-04 17:10 ` Sergio Durigan Junior
2017-12-04 8:27 ` [PATCH v3 5/5] Extend gdb.core/coredump-filter.exp to test dump-excluded-mappings Sergio Lopez
2017-12-04 14:37 ` Pedro Alves [this message]
2017-12-04 17:09 ` [PATCH v3 0/5] Enable the user to dump all memory regions Sergio Durigan Junior
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=42ab4f25-13ef-76d4-adf1-3412a406c96d@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=slp@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).