gcore(1) [freebsd man page]
GCORE(1) BSD General Commands Manual GCORE(1) NAME
gcore -- get core images of running process SYNOPSIS
gcore [-f] [-s] [-c core] [executable] pid DESCRIPTION
The gcore utility creates a core image of the specified process, suitable for use with gdb(1). By default, the core is written to the file ``core.<pid>''. The process identifier, pid, must be given on the command line. The following options are available: -c Write the core file to the specified file instead of ``core.<pid>''. -f Dumps all available segments, excluding only malformed and undumpable segments. Unlike the default invocation, this flag dumps map- pings of devices which may invalidate the state of device transactions or trigger other unexpected behavior. As a result, this flag should only be used when the behavior of the application and any devices it has mapped is fully understood and any side effects can be controlled or tolerated. -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 kill(1). FILES
core.<pid> the core image HISTORY
A gcore utility appeared in 4.2BSD. BUGS
Because of the ptrace(2) usage gcore may not work with processes which are actively being investigated with truss(1) or gdb(1). Addition- ally, interruptable sleeps may exit with EINTR. The gcore utility is not compatible with the original 4.2BSD version. BSD
July 14, 2010 BSD
Check Out this Related Man Page
gcore(1) User Commands gcore(1) NAME
gcore - get core images of running processes SYNOPSIS
gcore [-pgF] [-o filename] [-c content] process-id... DESCRIPTION
The gcore utility creates a core image of each specified process. By default, the name of the core image file for the process whose process ID is process-id will be core.process-id. OPTIONS
The following options are supported: -c content Produces core image files with the specified content. The content description uses the same tokens as in coreadm(1M). The -c option does not apply to cores produced due to the -p or -g flags. -F Force. Grabs the target process even if another process has control. -g Produces core image files in the global core file repository with the global content as configured by coreadm(1M). The com- mand will fail if the user does not have permissions to the global core file repository. -o filename Substitutes filename in place of core as the first part of the name of the core image files. filename can contain the same tokens to be expanded as the paths in coreadm(1M). -p Produces a core image file in the process-specific location with the process-specific content for each process as config- ured by coreadm(1M). The command will fail if the user does not have permissions to the per-process core file repository. OPERANDS
The following operand is supported: process-id process ID EXIT STATUS
The following exit values are returned: 0 On success. non-zero On failure, such as non-existent process ID. FILES
core.process-id core images ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWtoo | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ Command Syntax is Evolving. Output Format(s) are Unstable. SEE ALSO
kill(1), coreadm(1M), setrlimit(2), core(4), proc(4), attributes(5) NOTES
gcore is unaffected by the setrlimit(2) system call using the RLIMIT_CORE value. SunOS 5.10 11 Feb 2004 gcore(1)