4.4BSD/usr/share/man/cat5/core.0

CORE(5)                     BSD Programmer's Manual                    CORE(5)

NNAAMMEE
     ccoorree - memory image file format

SSYYNNOOPPSSIISS
     ##iinncclluuddee <<ssyyss//ppaarraamm..hh>>

DDEESSCCRRIIPPTTIIOONN
     A small number of signals which cause abnormal termination of a process
     also cause a record of the process's in-core state to be written to disk
     for later examination by one of the aviailable debuggers.  (See
     sigaction(2).)  This memory image is written to a file named ccoorree in the
     working directory; provided the terminated process had write permission
     in the directory, and provided the abnormality did not caused a system
     crash.  (In this event, the decision to save the core file is arbitrary,
     see savecore(8).)

     The maximum size of a ccoorree file is limited by setrlimit(2).  Files which
     would be larger than the limit are not created.

     The ccoorree file consists of the _u. area, whose size (in pages) is defined
     by the UPAGES manifest in the <_s_y_s_/_p_a_r_a_m_._h> file.  The _u. area starts
     with a _u_s_e_r structure as given in <_s_y_s_/_u_s_e_r_._h>. The remainder of the ccoorree
     file consists of the data pages followed by the stack pages of the pro-
     cess image.  The amount of data space image in the ccoorree file is given (in
     pages) by the variable _u___d_s_i_z_e in the _u. area.  The amount of stack image
     in the core file is given (in pages) by the variable _u___s_s_i_z_e in the _u.
     area.  The size of a ``page'' is given by the constant NBPG (also from
     <_s_y_s_/_p_a_r_a_m_._h>).

SSEEEE AALLSSOO
     adb(1),  dbx(1),  gdb(1),  kgdb(1),  sigaction(2),  setrlimit(2)

HHIISSTTOORRYY
     A ccoorree file format appeared in Version 6 AT&T UNIX.

4th Berkeley Distribution        June 5, 1993                                1