# core file

Contains the memory snapshot of a process at error time

The following errors cause core dump

* Memory address violations,
* illegal instructions,
* bus errors,
* user generated quit signals

Core dump contents

<table><thead><tr><th>Name</th><th width="249.33333333333331">Description</th></tr></thead><tbody><tr><td>Core header</td><td>Basic information about core dump, and contains offsets that locate the remaining core dump info.</td></tr><tr><td>ldinfo</td><td>Loader information</td></tr><tr><td>mstsave</td><td>Kernel thread state information. The faulting thread mstsave structure is saved in the core header</td></tr><tr><td>Default user stack</td><td>A copy of the user stack at the time of the core dump</td></tr><tr><td>Default data area</td><td>(Optional) Contains the user data section</td></tr><tr><td>Memory mapped regions</td><td>(Optional) Contains the anonymously mapped regions</td></tr><tr><td>vm_info</td><td>(Optional) Contains offset and size information for memory mapped regions</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://i.janardhanpulivarthi.com/season-2/core-file.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.