CORE(5) BSD Programmer's Manual CORE(5)
c
\bco
\bor
\bre
\be - memory image file format
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
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 c
\bco
\bor
\bre
\be 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,
The maximum size of a c
\bco
\bor
\bre
\be file is limited by setrlimit(2). Files which
would be larger than the limit are not created.
The c
\bco
\bor
\bre
\be file consists of the _
\bu. area, whose size (in pages) is defined
by the UPAGES manifest in the <_
\bs_
\by_
\bs_
\b/_
\bp_
\ba_
\br_
\ba_
\bm_
\b._
\bh> file. The _
\bu. area starts
with a _
\bu_
\bs_
\be_
\br structure as given in <_
\bs_
\by_
\bs_
\b/_
\bu_
\bs_
\be_
\br_
\b._
\bh>. The remainder of the c
\bco
\bor
\bre
\be
file consists of the data pages followed by the stack pages of the pro-
cess image. The amount of data space image in the c
\bco
\bor
\bre
\be file is given (in
pages) by the variable _
\bu_
\b__
\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_
\b__
\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_
\b/_
\bp_
\ba_
\br_
\ba_
\bm_
\b._
\bh>).
S
\bSE
\bEE
\bE A
\bAL
\bLS
\bSO
\bO
adb(1), dbx(1), gdb(1), kgdb(1), sigaction(2), setrlimit(2)
H
\bHI
\bIS
\bST
\bTO
\bOR
\bRY
\bY
A c
\bco
\bor
\bre
\be file format appeared in Version 6 AT&T UNIX.
4th Berkeley Distribution June 5, 1993 1