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 2/4] Document new 'set honor-dontdump-flag' command
Date: Tue, 28 Nov 2017 13:22:00 -0000	[thread overview]
Message-ID: <20171128132148.31802-3-slp@redhat.com> (raw)
In-Reply-To: <20171128132148.31802-1-slp@redhat.com>

2017-11-28  Sergio Lopez  <slp@redhat.com>

        * gdb.texinfo (gcore): Mention new command 'set
        honor-dontdump-flag'.
        (set honor-dontdump-flag): Document new command.
---
 gdb/doc/ChangeLog   |  6 ++++++
 gdb/doc/gdb.texinfo | 14 +++++++++++++-
 2 files changed, 19 insertions(+), 1 deletion(-)

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 2a1eb76d15..cdde49a887 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,9 @@
+2017-11-28  Sergio Lopez  <slp@redhat.com>
+
+	* gdb.texinfo (gcore): Mention new command 'set
+	honor-dontdump-flag'.
+	(set honor-dontdump-flag): Document new command.
+
 2017-11-26  Dominik Czarnota  <dominik.b.czarnota@gmail.com>
 
 	PR gdb/21945
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 675f6e7bc8..472a0fe8cc 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -11543,7 +11543,9 @@ this writing, @sc{gnu}/Linux, FreeBSD, Solaris, and S390).
 
 On @sc{gnu}/Linux, this command can take into account the value of the
 file @file{/proc/@var{pid}/coredump_filter} when generating the core
-dump (@pxref{set use-coredump-filter}).
+dump (@pxref{set use-coredump-filter}), and will honor the VM_DONTDUMP
+flag for sections where is present in the file
+@file{/proc/@var{pid}/smaps} (@pxref{set honor-dontdump-flag}).
 
 @kindex set use-coredump-filter
 @anchor{set use-coredump-filter}
@@ -11573,6 +11575,16 @@ value is currently @code{0x33}, which means that bits @code{0}
 (anonymous private mappings), @code{1} (anonymous shared mappings),
 @code{4} (ELF headers) and @code{5} (private huge pages) are active.
 This will cause these memory mappings to be dumped automatically.
+
+@kindex set honor-dontdump-flag
+@anchor{set honor-dontdump-flag}
+@item set honor-dontdump-flag on
+@itemx set honor-dontdump-flag off
+If @code{on} is specified, GDB will not dump memory regions marked
+with the VM_DONTDUMP flag. This flag is represented in
+@file{/proc/@var{pid}/smaps} with the acronym @code{dd}.
+
+The default value is @code{on}.
 @end table
 
 @node Character Sets
-- 
2.14.3


  parent 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 [PATCH 0/4] Enable the user to dump all memory regions Sergio Lopez
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 ` Sergio Lopez [this message]
2017-11-28 15:51   ` [PATCH 2/4] Document new 'set honor-dontdump-flag' command 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-3-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