The core dump feature allows offline, postmortem analysis of actors or processes that are killed by exceptions. This is performed in three steps:
Gathering the relevant information from the actor or process to be killed
Dumping the information into a core file on a stable storage medium
Reloading the core file on the host machine for analysis
The core file is generated in the case of a fatal exception, upon request from the debugging server or agent or upon request from any actor or process. The following information is collected in the core file:
The current threads and their characteristics, namely, all hardware and software registers, the scheduling characteristics, and the thread's name and ID
The actor or process name, ID, capability, and type
Dynamic and shared library informations, such as path names and relocation information
Memory regions in use
For details, see the CORE_DUMP(5FEA) man page.