From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Sergio Lopez <slp@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4] Document the new "-a" argument for gcore
Date: Tue, 28 Nov 2017 15:54:00 -0000 [thread overview]
Message-ID: <87a7z6o0us.fsf@redhat.com> (raw)
In-Reply-To: <20171128132148.31802-5-slp@redhat.com> (Sergio Lopez's message of "Tue, 28 Nov 2017 14:21:48 +0100")
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
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2017-11-28 15:54 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 1/4] Implement 'set honor-dontdump-flag' command 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 2/4] Document new " 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 3/4] Add "-a" argument to gcore.in Sergio Lopez
2017-11-28 15:57 ` 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 [this message]
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=87a7z6o0us.fsf@redhat.com \
--to=sergiodj@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