4.3BSD-Reno/share/man/cat5/core.0

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



CORE(5)                       1986			  CORE(5)



NNAAMMEE
     core - format of memory image file

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

DDEESSCCRRIIPPTTIIOONN
     The UNIX System writes out a memory image of a terminated
     process when any of various errors occur.	See _s_i_g_v_e_c(2) for
     the list of reasons; the most common are memory violations,
     illegal instructions, bus errors, and user-generated quit
     signals.  The memory image is called `core' and is written
     in the process's working directory (provided it can be; nor-
     mal access controls apply).

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

     The core 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 core file consists first
     of the data pages and then the stack pages of the process
     image.  The amount of data space image in the core 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>).

     In general the debugger _a_d_b(1) is sufficient to deal with
     core images.

SSEEEE AALLSSOO
     adb(1), dbx(1), sigvec(2), setrlimit(2)




















Printed 7/27/90               March				1