xref: /freebsd/usr.bin/gcore/gcore.1 (revision 7f3dea244c40159a41ab22da77a434d7c5b5e85a)
1.\" Copyright (c) 1983, 1990, 1992, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by the University of
15.\"	California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"    without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\"	@(#)gcore.1	8.2 (Berkeley) 4/18/94
33.\"	$Id$
34.\"
35.Dd April 18, 1994
36.Dt GCORE 1
37.Os BSD 4.2
38.Sh NAME
39.Nm gcore
40.Nd get core images of running process
41.Sh SYNOPSIS
42.Nm
43.Op Fl s
44.Op Fl c Ar core
45.Op Ar exec
46.Ar pid
47.Sh DESCRIPTION
48.Nm Gcore
49creates a core image of the specified process,
50suitable for use with
51.Xr gdb  1 .
52By default, the core is written to the file
53.Dq Pa core.<pid> .
54The process identifier,
55.Ar pid ,
56must be given on the command line. If no executable image is
57specified,
58.Nm
59will use
60.Dq Pa /proc/<pid>/file .
61.Pp
62The options are:
63.Bl -tag -width indent
64.It Fl c
65Write the core file to the specified file instead of
66.Dq Pa core.<pid> .
67.It Fl s
68Stop the process while gathering the core image, and resume it
69when done.  This guarantees that the resulting core dump will
70be in a consistent state.  The process is resumed even if it was
71already stopped.
72The same effect can be achieved manually with
73.Xr kill 1 .
74.El
75.Sh FILES
76.Bl -tag -width /var/log/messages -compact
77.It Pa core.<pid>
78The core image.
79.It Pa /proc/<pid>/file
80The executable image.
81.EL
82.Dp
83.Sh HISTORY
84.Nm Gcore
85appeared in
86.Bx 4.2 .
87.Sh BUGS
88Context switches or paging activity that occur while
89.Nm
90is running may cause the program to become confused.
91For best results, use
92.Fl s
93to temporarily stop the target process.
94.Pp
95.Nm Gcore
96is not compatible with the original
97.Bx 4.2
98version.
99