usr/share/man/cat1/gcore.0

GCORE(1)                     BSD Reference Manual                     GCORE(1)

N\bNA\bAM\bME\bE
     g\bgc\bco\bor\bre\be - get core images of running process

S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
     g\bgc\bco\bor\bre\be [-\b-s\bs] [-\b-c\bc _\bc_\bo_\br_\be] _\be_\bx_\be_\bc _\bp_\bi_\bd

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
     G\bGc\bco\bor\bre\be creates a core image of the specified process, suitable for use
     with gdb(1).  By default, the core is written to the file ``_\bc_\bo_\br_\be_\b._\b<_\bp_\bi_\bd_\b>''.
     Both the executable image, _\be_\bx_\be_\bc, and the process identifier, _\bp_\bi_\bd, must be
     given on the command line.

     The options are:

     -\b-c\bc      Write the core file to the specified file instead of
             ``_\bc_\bo_\br_\be_\b._\b<_\bp_\bi_\bd_\b>''.

     -\b-s\bs      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 al-
             ready stopped.  The same effect can be achieved manually with
             kill(1).

F\bFI\bIL\bLE\bES\bS
     core.<pid>         The core image.

H\bHI\bIS\bST\bTO\bOR\bRY\bY
     G\bGc\bco\bor\bre\be appeared in 4.2BSD.

B\bBU\bUG\bGS\bS
     Context switches or paging activity that occur while g\bgc\bco\bor\bre\be is running may
     cause the program to become confused.  For best results, use -s to tem-
     porarily stop the target process.

     G\bGc\bco\bor\bre\be is not compatible with the original 4.2BSD version.  In particular,
     4.4BSD requires the _\be_\bx_\be_\bc argumemt.

4.2 Berkeley Distribution        June 6, 1993                                1