A crash dump is a snapshot captured when a program or operating system stops unexpectedly. Depending on the dump type and settings, it can contain register values, stack traces, memory pages and information about loaded modules that help engineers reconstruct a failure.
Developers examine dumps to understand problems that are hard to reproduce, such as corrupted memory, a failing driver or a race condition. Full-memory dumps are usually more informative than minimal dumps but may also be larger and slower to collect.
Because a dump can include whatever was held in memory at the time, it may accidentally contain access tokens, passwords, cryptographic key material or personal data. A dump copied from a restricted production system into a less protected debugging environment can therefore become a security exposure.
Limit who may collect and read crash dumps, use secure storage and retention policies, and redact or minimize sensitive material where practical. Treat dumps as potentially confidential evidence, especially when investigating a security incident.