[4/4] Document the new "-a" argument for gcore
Commit Message
2017-11-28 Sergio Lopez <slp@redhat.com>
* gdb.texinfo (gcore man): Document new "-a" argument.
---
gdb/doc/ChangeLog | 3 +++
gdb/doc/gdb.texinfo | 4 ++++
2 files changed, 7 insertions(+)
Comments
On Tuesday, November 28 2017, Sergio Lopez wrote:
> 2017-11-28 Sergio Lopez <slp@redhat.com>
> * gdb.texinfo (gcore man): Document new "-a" argument.
> ---
> gdb/doc/ChangeLog | 3 +++
> gdb/doc/gdb.texinfo | 4 ++++
> 2 files changed, 7 insertions(+)
>
> diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
> index cdde49a887..491acb0a9a 100644
> --- a/gdb/doc/ChangeLog
> +++ b/gdb/doc/ChangeLog
> @@ -1,3 +1,6 @@
> +2017-11-28 Sergio Lopez <slp@redhat.com>
> + * gdb.texinfo (gcore man): Document new "-a" argument.
> +
> 2017-11-28 Sergio Lopez <slp@redhat.com>
>
> * gdb.texinfo (gcore): Mention new command 'set
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 472a0fe8cc..c0146c66dc 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -42962,6 +42962,10 @@ running without any change.
>
> @c man begin OPTIONS gcore
> @table @env
> +@item -a
> +Instruct GDB to unconditionally dump all sections (except IO), ignoring the
> +value of @file{/proc/@var{pid}/coredump_filter} and the VM_DONTDUMP flag.
@code{} around 'VM_DONTDUMP'.
> +
> @item -o @var{filename}
> The optional argument
> @var{filename} specifies the file name where to put the core dump.
> --
> 2.14.3
> From: Sergio Lopez <slp@redhat.com>
> Cc: Sergio Lopez <slp@redhat.com>
> Date: Tue, 28 Nov 2017 14:21:48 +0100
>
> +@item -a
> +Instruct GDB to unconditionally dump all sections (except IO), ignoring the
^^^
"@value{GDBN}"
> +value of @file{/proc/@var{pid}/coredump_filter} and the VM_DONTDUMP flag.
Is this Linux-specific? Because AFAIK 'gcore' isn't, and so we need
to document that this switch and the details you've put into its
description are specific to Linux.
Also, VM_DONTDUMP should be in @code.
Thanks.
On Tuesday, November 28, 2017 06:35:37 PM Eli Zaretskii wrote:
> > From: Sergio Lopez <slp@redhat.com>
> > Cc: Sergio Lopez <slp@redhat.com>
> > Date: Tue, 28 Nov 2017 14:21:48 +0100
> >
> > +@item -a
> > +Instruct GDB to unconditionally dump all sections (except IO), ignoring the
> ^^^
> "@value{GDBN}"
>
> > +value of @file{/proc/@var{pid}/coredump_filter} and the VM_DONTDUMP flag.
>
> Is this Linux-specific? Because AFAIK 'gcore' isn't, and so we need
> to document that this switch and the details you've put into its
> description are specific to Linux.
>
> Also, VM_DONTDUMP should be in @code.
It is OS-specific. FreeBSD has a similar notion (it excludes memory regions
marked with a KVME_FLAG_NOCOREDUMP in fbsd_find_memory_regions in fbsd-nat.c
that are created by passing MAP_NOCORE to mmap()). I could make FreeBSD's
native target honor the same flag name once this is pushed in, though
FreeBSD's kernel always honors the NOCOREDUMP flag (there is no way to force
a kernel-generated coredump to include those regions).
@@ -1,3 +1,6 @@
+2017-11-28 Sergio Lopez <slp@redhat.com>
+ * gdb.texinfo (gcore man): Document new "-a" argument.
+
2017-11-28 Sergio Lopez <slp@redhat.com>
* gdb.texinfo (gcore): Mention new command 'set
@@ -42962,6 +42962,10 @@ running without any change.
@c man begin OPTIONS gcore
@table @env
+@item -a
+Instruct GDB to unconditionally dump all sections (except IO), ignoring the
+value of @file{/proc/@var{pid}/coredump_filter} and the VM_DONTDUMP flag.
+
@item -o @var{filename}
The optional argument
@var{filename} specifies the file name where to put the core dump.