Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Lopez <slp@redhat.com>
To: gdb-patches@sourceware.org
Cc: Sergio Lopez <slp@redhat.com>
Subject: [PATCH 0/4] Enable the user to dump all memory regions
Date: Tue, 28 Nov 2017 13:22:00 -0000	[thread overview]
Message-ID: <20171128132148.31802-1-slp@redhat.com> (raw)

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 honor-dontdump-flag' command
for GDB, and the "-a" argument for gcore, allowing the user to mimic the
behavior of previous GDB versions.

Sergio Lopez (4):
  Implement 'set honor-dontdump-flag' command
  Document new 'set honor-dontdump-flag' command
  Add "-a" argument to gcore.in
  Document the new "-a" argument for gcore

 gdb/ChangeLog       | 10 ++++++++++
 gdb/doc/ChangeLog   |  9 +++++++++
 gdb/doc/gdb.texinfo | 18 +++++++++++++++++-
 gdb/gcore.in        | 25 +++++++++++++++++++++++--
 gdb/linux-tdep.c    | 19 ++++++++++++++++++-
 5 files changed, 77 insertions(+), 4 deletions(-)

-- 
2.14.3


             reply	other threads:[~2017-11-28 13:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 13:22 Sergio Lopez [this message]
2017-11-28 13:22 ` [PATCH 3/4] Add "-a" argument to gcore.in Sergio Lopez
2017-11-28 15:57   ` Sergio Durigan Junior
2017-11-28 13:22 ` [PATCH 2/4] Document new 'set honor-dontdump-flag' command Sergio Lopez
2017-11-28 15:51   ` Sergio Durigan Junior
2017-11-28 16:32   ` Pedro Alves
2017-11-28 16:39   ` Eli Zaretskii
2017-11-28 13:22 ` [PATCH 1/4] Implement " Sergio Lopez
2017-11-28 15:06   ` Sergio Lopez
2017-11-28 15:42   ` Sergio Durigan Junior
2017-11-28 16:21     ` Pedro Alves
2017-11-28 16:36       ` Sergio Durigan Junior
2017-11-29 10:59     ` Sergio Lopez
2017-11-29 19:39       ` Sergio Durigan Junior
2017-11-29 20:02         ` Sergio Lopez
2017-11-29 20:22           ` Sergio Durigan Junior
2017-11-28 13:22 ` [PATCH 4/4] Document the new "-a" argument for gcore Sergio Lopez
2017-11-28 15:54   ` Sergio Durigan Junior
2017-11-28 16:35   ` Eli Zaretskii
2017-11-28 18:37     ` John Baldwin
2017-11-28 16:08 ` [PATCH 0/4] 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=20171128132148.31802-1-slp@redhat.com \
    --to=slp@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