CORE(5) CORE(5) NAME core - format of memory image file SYNOPSIS #include DESCRIPTION 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; normal 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 vari‐ able _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. SEE ALSO adb(1), dbx(1), sigvec(2), setrlimit(2) 4th Berkeley Distribution March 9, 1986 CORE(5)