4.4BSD/usr/src/usr.bin/gcore/gcore.1

Compare this file to the similar file:
Show the results in this format:

.\" Copyright (c) 1983, 1990, 1992, 1993
.\"	The Regents of the University of California.  All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in the
.\"    documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\"    must display the following acknowledgement:
.\"	This product includes software developed by the University of
.\"	California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\"    may be used to endorse or promote products derived from this software
.\"    without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\"	@(#)gcore.1	8.1 (Berkeley) 6/6/93
.\"
.Dd "June 6, 1993"
.Dt GCORE 1
.Os BSD 4.2
.Sh NAME
.Nm gcore
.Nd get core images of running process
.Sh SYNOPSIS
.Nm gcore
.Op Fl s
.Op Fl c Ar core
.Ar exec pid
.Sh DESCRIPTION
.Nm Gcore
creates a core image of the specified process,
suitable for use with
.Xr gdb  1 .
By default, the core is written to the file
.Dq Pa core.<pid> .
Both the executable image,
.Ar exec ,
and the process identifier,
.Ar pid ,
must be given on the command line.
.Pp
The options are:
.Bl -tag -width indent
.It Fl c
Write the core file to the specified file instead of
.Dq Pa core.<pid> .
.It Fl s
Stop the process while gathering the core image, and resume it
when done.  This guarantees that the resulting core dump will
be in a consistent state.  The process is resumed even if it was
already stopped.
The same effect can be achieved manually with 
.Xr kill 1 .
.El
.Sh FILES
.Bl -tag -width /var/log/messages -compact
.It Pa core.<pid>
The core image.
.EL
.Dp
.Sh HISTORY
.Nm Gcore
appeared in 4.2BSD.
.Sh BUGS
Context switches or paging activity that occur while
.Nm gcore
is running may cause the program to become confused.
For best results, use -s to temporarily stop the target process.
.Pp
.Nm Gcore
is not compatible with the original 4.2BSD version.
In particular, 4.4BSD requires the 
.Ar exec
argumemt.