*** UNIX MANUAL PAGE BROWSER ***

A Nergahak database for man pages research.

Navigation

Directory Browser

1Browse 4.4BSD4.4BSD
1Browse Digital UNIXDigital UNIX 4.0e
1Browse FreeBSDFreeBSD 14.3
1Browse MINIXMINIX 3.4.0rc6-d5e4fc0
1Browse NetBSDNetBSD 10.1
1Browse OpenBSDOpenBSD 7.7
1Browse UNIX v7Version 7 UNIX
1Browse UNIX v10Version 10 UNIX

Manual Page Search

Manual Page Result

0 Command: core | Section: 5 | Source: UNIX v7 | File: core.5
CORE(5) File Formats Manual CORE(5) NAME core - format of core image file DESCRIPTION UNIX writes out a core image of a terminated process when any of vari- ous errors occur. See signal(2) for the list of reasons; the most com- mon are memory violations, illegal instructions, bus errors, and user- generated quit signals. The core image is called `core' and is written in the process's working directory (provided it can be; normal access controls apply). The first 4096 bytes of the core image are a copy of the system's per- user data, and the next 4096, a copy of the kernel stack for the process, including the registers as they were at the time of the fault; see the system listings for the format of this area. The remainder represents the actual contents of the user's core area when the core image was written. If the text segment is write-protected and shared, it is not dumped; otherwise the entire address space is dumped. In general the debugger adb(1) is sufficient to deal with core images. SEE ALSO adb(1), signal(2) CORE(5)

Navigation Options