core - format of core image file
The IRIX system writes out a core image of a terminated process when any
of various errors occur. See signal(2) for the list of reasons; the most
common are memory violations, illegal instructions, bus errors, and
user-generated quit signals. The core image is called core and is
written in the process's working directory (provided it can be; normal
access controls apply). A process with an effective user ID different
from the real user ID does not produce a core image.
The format of the core image is defined by <core.out.h>. It consists of
a header, maps, descriptors, and section data.
The header data includes the process name (as in ps(1)), the signal that
caused the core dump, the descriptor array, and the corefile location of
the map array.
Each descriptor defines the length of useful process data. One
descriptor defines the general-purpose registers at the time of the core
dump for example. The data is present in the core image at the file
location given in the descriptor only if the IVALID flag is set in the
Each map defines the virtual address and length of a section of the
process at the time of the core dump. The data is present in the core
image at the file location given in the descriptor only if the VDUMPED
flag is set in the map. The process's stack and data sections are
normally written in the core image. The process's text is not normally
written in the core image.
Core image format designed by Silicon Graphics, Inc.
dbx(1), ps(1), setuid(2), signal(2).
PPPPaaaaggggeeee 1111 [ Back ]