Query: core
OS: opendarwin
Section: 5
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
CORE(5) BSD File Formats Manual CORE(5)NAMEcore -- memory image file formatSYNOPSIS#include <sys/param.h>DESCRIPTIONA small number of signals which cause abnormal termination of a process also cause a record of the process's in-core state to be written to disk for later examination by one of the available debuggers. (See sigaction(2).) This memory image is written to a file named by default core.pid in the /cores directory; provided the terminated process had write permission in the directory, and the directory existed. The maximum size of a core file is limited by setrlimit(2). Files which would be larger than the limit are not created. The core file consists of the ~ Mach-O(5) header as described in the <mach-o/loader.h> file. The remainder of the core file consists of various sections described in the Mach-O(5) header.NOTECore dumps are disabled by default under Darwin/Mac OS X. To re-enable core dumps, a privlaged user must edit /etc/hostconfig to contain the line: COREDUMPS=-YES-SEE ALSOgdb(1), setrlimit(2), sigaction(2), Mach-O(5), sysctl(8)HISTORYA core file format appeared in Version 6 AT&T UNIX.BSDMarch 18, 2002 BSD
Related Man Pages |
---|
gcore(1) - mojave |
core(5) - bsd |
gcore(1) - minix |
gcore(1) - osx |
gcore(1) - v7 |
Similar Topics in the Unix Linux Community |
---|
Decoding of Core Dump |
Query: Analysing the Core file |
CORE in HP-UX |
Unable to catch the output after core dump and bus error |
12-Core MacPro (2013) kernel_task over 1200% |