[unix-history] / usr / share / man / cat5 / core.0



CORE(5)                       1986			  CORE(5)


N\bNA\bAM\bME\bE
     core - format of memory image file

S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
     #\b#i\bin\bnc\bcl\blu\bud\bde\be <\b<s\bsy\bys\bs/\b/p\bpa\bar\bra\bam\bm.\b.h\bh>\b>

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
     The UNIX System writes out a memory image of a terminated
     process when any of various errors occur.	See _\bs_\bi_\bg_\bv_\be_\bc(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 _\bc_\bo_\br_\be file is limited by _\bs_\be_\bt_\br_\bl_\bi_\bm_\bi_\bt(2).
     Files which would be larger than the limit are not created.

     The core file consists of the _\bu. area, whose size (in pages)
     is defined by the UPAGES manifest in the <_\bs_\by_\bs/_\bp_\ba_\br_\ba_\bm._\bh> file.
     The _\bu. area starts with a _\bu_\bs_\be_\br structure as given in
     <_\bs_\by_\bs/_\bu_\bs_\be_\br._\bh>.  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 _\bu__\bd_\bs_\bi_\bz_\be in the _\bu. area.
     The amount of stack image in the core file is given (in
     pages) by the variable _\bu__\bs_\bs_\bi_\bz_\be in the _\bu. area.  The size of
     a ``page'' is given by the constant NBPG (also from
     <_\bs_\by_\bs/_\bp_\ba_\br_\ba_\bm._\bh>).

     In general the debugger _\ba_\bd_\bb(1) is sufficient to deal with
     core images.

S\bSE\bEE\bE A\bAL\bLS\bSO\bO
     adb(1), dbx(1), sigvec(2), setrlimit(2)


Printed 7/27/90               March				1
Commit	Line	Data
3922de1d C	1
	2
	3
	4	CORE(5) 1986 CORE(5)
	5
	6
	7
	8	N\bNA\bAM\bME\bE
	9	core - format of memory image file
	10
	11	S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
	12	#\b#i\bin\bnc\bcl\blu\bud\bde\be <\b<s\bsy\bys\bs/\b/p\bpa\bar\bra\bam\bm.\b.h\bh>\b>
	13
	14	D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
	15	The UNIX System writes out a memory image of a terminated
	16	process when any of various errors occur. See _\bs_\bi_\bg_\bv_\be_\bc(2) for
	17	the list of reasons; the most common are memory violations,
	18	illegal instructions, bus errors, and user-generated quit
	19	signals. The memory image is called `core' and is written
	20	in the process's working directory (provided it can be; nor-
	21	mal access controls apply).
	22
	23	The maximum size of a _\bc_\bo_\br_\be file is limited by _\bs_\be_\bt_\br_\bl_\bi_\bm_\bi_\bt(2).
	24	Files which would be larger than the limit are not created.
	25
	26	The core file consists of the _\bu. area, whose size (in pages)
	27	is defined by the UPAGES manifest in the <_\bs_\by_\bs/_\bp_\ba_\br_\ba_\bm._\bh> file.
	28	The _\bu. area starts with a _\bu_\bs_\be_\br structure as given in
	29	<_\bs_\by_\bs/_\bu_\bs_\be_\br._\bh>. The remainder of the core file consists first
	30	of the data pages and then the stack pages of the process
	31	image. The amount of data space image in the core file is
	32	given (in pages) by the variable _\bu__\bd_\bs_\bi_\bz_\be in the _\bu. area.
	33	The amount of stack image in the core file is given (in
	34	pages) by the variable _\bu__\bs_\bs_\bi_\bz_\be in the _\bu. area. The size of
	35	a ``page'' is given by the constant NBPG (also from
	36	<_\bs_\by_\bs/_\bp_\ba_\br_\ba_\bm._\bh>).
	37
	38	In general the debugger _\ba_\bd_\bb(1) is sufficient to deal with
	39	core images.
	40
	41	S\bSE\bEE\bE A\bAL\bLS\bSO\bO
	42	adb(1), dbx(1), sigvec(2), setrlimit(2)
	43
	44
	45
	46
	47
	48
	49
	50
	51
	52
	53
	54
	55
	56
	57
	58
	59
	60
	61
	62
	63	Printed 7/27/90 March 1
	64
65
66