From: John Baldwin <jhb@freebsd.org>
To: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Cc: Sergio Lopez <slp@redhat.com>
Subject: Re: [PATCH 4/4] Document the new "-a" argument for gcore
Date: Tue, 28 Nov 2017 18:37:00 -0000 [thread overview]
Message-ID: <2426110.pzlzVdcidA@ralph.baldwin.cx> (raw)
In-Reply-To: <834lpe5pk6.fsf@gnu.org>
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).
--
John Baldwin
next prev parent reply other threads:[~2017-11-28 18:37 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 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 [this message]
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 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=2426110.pzlzVdcidA@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=eliz@gnu.org \
--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