Core dump

related topics
{system, computer, user}
{math, number, function}
{disease, patient, cell}

In computing, a core dump consists of the recorded state of the working memory of a computer program at a specific time, generally when the program has terminated abnormally (crashed).[1] In practice, other key pieces of program state are usually dumped at the same time, including the processor registers, which may include the program counter and stack pointer, memory management information, and other processor and operating system flags and information. The name comes from the days when magnetic core memory was used, before the introduction of semiconductor memory. Core dumps are often used to assist in diagnosing and debugging errors in computer programs.

On many operating systems, a fatal error in a program automatically triggers a core dump; by extension the phrase "to dump core" has come to mean, in many cases, any fatal error, regardless of whether a record of the program memory results.

The term "core dump", "memory dump", or just "dump". has become jargon to indicate any storing of a large amount of raw data for further examination.

Contents

Background

Before the advent of disk operating systems and the ability to record large data files, core dumps were paper printouts of the contents of memory, typically arranged in columns of octal or hexadecimal numbers (a "hex dump"), sometimes accompanied by their interpretations as machine language instructions, text strings, or decimal or floating-point numbers (cf. disassembler). In more recent operating systems, a "core dump" is a file containing the memory image of a particular process, or the memory images of parts of the address space of that process, along with other information such as the values of processor registers. These files can be printed or viewed as text, or analysed with specialised tools such as objdump.

Uses of core dumps

Core dumps can serve as useful debugging aids in several situations. On early standalone or batch-processing systems, core dumps allowed a user to debug a program without monopolizing the (very expensive) computing facility for debugging; a printout could also be more convenient than debugging using switches and lights. On shared computers, whether time-sharing, batch processing, or server systems, core dumps allow off-line debugging of the operating system, so that the system can go back into operation immediately. Core dumps allow a user to save a crash for later or off-site analysis, or comparison with other crashes. For embedded computers, it may be impractical to support debugging on the computer itself, so analysis of a dump may take place on a different computer. Some operating systems such as early versions of Unix did not support attaching debuggers to running processes, so core dumps were necessary to run a debugger on a process's memory contents. Core dumps can be used to capture data freed during dynamic memory allocation and may thus be used to retrieve information from a program that is no longer running. In the absence of an interactive debugger, the core dump may be used by an assiduous programmer to determine the error from direct examination.

Full article ▸

related documents
GW-BASIC
Mutual exclusion
System analysis
Visual DialogScript
Segmentation fault
Nautilus (file manager)
HTTP 404
Abstract Window Toolkit
Application binary interface
Allegro library
QuickBASIC
Pentium FDIV bug
GTK+
LZ77 and LZ78
Megabyte
Modifier key
Source Mage GNU/Linux
Parasitic computing
IBM 1620 Model II
Remote procedure call
Macro virus (computing)
Video coding
Schematic
Microsoft BASIC
Electrical network
Windows Metafile
ActiveX
Simple DirectMedia Layer
Floating point unit
Regression testing