|
|
DataMuseum.dkPresents historical artifacts from the history of: ICL Comet 32 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about ICL Comet 32 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 1138 (0x472)
Types: TextFile
Notes: UNIX file
Names: »core.5«
└─⟦26887b7e0⟧ Bits:30009717 Comet 32 harddisk image
└─⟦28c352965⟧ »/a« UNIX Filesystem
└─⟦this⟧ »usr/man/man5/core.5«
.ig @(#)core.5 2.1 7/1/84 @(#)Copyright (C) 1983 by National Semiconductor Corp. .. .TH CORE 5 .SH NAME core \- format of memory image file .SH DESCRIPTION UNIX writes out a memory image of a terminated process when any of various errors occur. See .IR signal (2) for the list of reasons; the most common are memory violations, illegal instructions, bus errors, and user-generated quit signals. The memory image is called `core' and is written in the process's working directory (provided it can be; normal access controls apply). .PP The maximum size of a .I core file is limited by .IR vlimit (2) . Files which would be larger than the limit are not created. .PP The core file consists of the \fIu.\fR area, which currently consists of 4 pages, beginning with a \fIuser\fR structure as given in /usr/include/sys/user.h. The kernel stack grows from the end of this 4 page region. The remainder of the core file consists first of the text pages and then the data pages and the stack pages of the process image. .PP In general the debugger .IR ddt (1) is sufficient to deal with core images. .SH "SEE ALSO" ddt(1), signal(2), vlimit(2)