On Thursday, July 26 2018, GSR wrote:

> Patch for possible update of man page.

The patch is reversed.

> And a note: the suggested compression trick doesn't work (seek
> errors). Maybe there is other way, maybe not possible. The other
> example, about using securely created destination, works.

I personally would like to see the gdb.texinfo file updated using the
upstream version.  No need to carry an extra patch for this scenario.

> --- gcore.1   2018-07-26 04:50:01.066541238 +0200
> +++ gcore.1-old       2018-07-11 17:49:59.000000000 +0200
> @@ -1,26 +1,20 @@
> -.TH gcore "1" "Jul 2018" "gdb 8.1" "GNU Tools"
> +.TH gcore "1" "May 2007" "gdb 6.8" "GNU Tools"
>  .SH NAME
> -gcore \- Generate core files for running processes
> +gcore \- Generate a core file for a running process
>  .SH SYNOPSIS
>  .B gcore
> -[-a] [-o \fIfilename\fR] \fIpid[s]\fR
> +[-o \fIfilename\fR] \fIpid\fR
>  .SH DESCRIPTION
>  .\" Add any additional description here
>  .PP
> -gcore generates a core file for the process(es) specified by process IDs,
> -\fIpid[s]\fR. By default, each core file is written to core.\fIpid\fR, in the
> +gcore generates a core file for the process specified by its process ID,
> +\fIpid\fR. By default, the core file is written to core.\fIpid\fR, in the
>  current directory.
>  .TP
> -\fB\-a\fR
> -(Linux only) ignore /proc/PID/coredump_filter and also dump memory mappings
> -marked with the 'VM_DONTDUMP' flag. See info node Core File Generation for
> -longer explanation.
> -.TP
>  \fB\-o\fR \fIfilename\fR
> -write core file to \fIfilename\fR if one PID, or \fIfilename.pid\fR if
> -multiple PIDs, instead of default core.\fIpid\fR
> +write core file to \fIfilename\fR instead of core.\fIpid\fR
>  .SH COPYING
> -Copyright \(co 2003, 2005, 2007, 2008, 2018 Free Software Foundation, Inc.
> +Copyright \(co 2003, 2005, 2007, 2008 Free Software Foundation, Inc.
>  .PP
>  Permission is granted to make and distribute verbatim copies of this manual
>  provided the copyright notice and this permission notice are preserved on
>

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Attachment: signature.asc
Description: PGP signature

Reply via email to