core(4CC)

NAME | DESCRIPTION | ATTRIBUTES | SEE ALSO

NAME

core- core image file

DESCRIPTION

The operating system writes out a core image of a process when it is terminated, due to the receipt of a certain signal. A core dump can be triggered by a pdump or system call on the specified process, or by a crash of the process itself.

Note: The CORE_DUMP feature must be active.

The core image is called core_processName and is written to the directory indicated by the COREDIR configuration environment variable (/tmp by default). The configuration environment variable is positioned using the sysSetEnv() and sysGetEnv() API calls.

The core file contains all the process information relevant to debugging, including the contents of hardware registers, process status, and process data (all memory regions).

The core file is generated as an ELF file, containing ELF program and file headers. The e_type field in the file header has type ET_CORE. The program header contains an entry for every segment that was part of the process address space, including shared library segments. The contents of the writable segments are also part of the core image.

The program header of an ELF core file also contains one entry for one NOTE segment.

The NOTE segment format is defined in <chorus/dump.h>.

All other segments are page-aligned, so that they may be mapped if necessary.

The size of the core file created by a process may be controlled by the user through the iom.maxcoresize tunable. If the core file generated would exceed the maximum size specified by iom.maxcoresize, the dump process is aborted and no core file is generated.

Core file generation may be triggered by the process itself or by another process through the pdump(2K) system call.

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Interface Stability	Evolving

SEE ALSO

pdump(1M), pdump(2K),

ChorusOS 5.0  Last Revised December 2001

NAME | DESCRIPTION | ATTRIBUTES | SEE ALSO