4.4BSD/usr/share/man/cat1/gcore.0

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

GCORE(1)                     BSD Reference Manual                     GCORE(1)

NNAAMMEE
     ggccoorree - get core images of running process

SSYYNNOOPPSSIISS
     ggccoorree [--ss] [--cc _c_o_r_e] _e_x_e_c _p_i_d

DDEESSCCRRIIPPTTIIOONN
     GGccoorree creates a core image of the specified process, suitable for use
     with gdb(1).  By default, the core is written to the file ``_c_o_r_e_._<_p_i_d_>''.
     Both the executable image, _e_x_e_c, and the process identifier, _p_i_d, must be
     given on the command line.

     The options are:

     --cc      Write the core file to the specified file instead of
             ``_c_o_r_e_._<_p_i_d_>''.

     --ss      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).

FFIILLEESS
     core.<pid>         The core image.

HHIISSTTOORRYY
     GGccoorree appeared in 4.2BSD.

BBUUGGSS
     Context switches or paging activity that occur while ggccoorree is running may
     cause the program to become confused.  For best results, use -s to tem-
     porarily stop the target process.

     GGccoorree is not compatible with the original 4.2BSD version.  In particular,
     4.4BSD requires the _e_x_e_c argumemt.

4.2 Berkeley Distribution        June 6, 1993                                1