From 788901248bb224fef5c42a9c4651169a9a26bd57 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Tue, 26 Aug 2008 04:34:37 +0000 Subject: [PATCH] Make the page more helpful to non-programmers by referencing the documentation of the shell's 'ulimit' command in the discussion of RLIMIT_CORE and RLIMIT_FSIZE. Note that a core dump file can be used in a debugger. --- man5/core.5 | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/man5/core.5 b/man5/core.5 index d56a06f9e..55ed64cdb 100644 --- a/man5/core.5 +++ b/man5/core.5 @@ -20,7 +20,7 @@ .\" Formatted or processed versions of this manual, if unaccompanied by .\" the source, must acknowledge the copyright and authors of this work. .\" -.TH CORE 5 2008-06-15 "Linux" "Linux Programmer's Manual" +.TH CORE 5 2008-08-26 "Linux" "Linux Programmer's Manual" .SH NAME core \- core dump file .SH DESCRIPTION @@ -29,6 +29,9 @@ and produce a .IR "core dump file" , a disk file containing an image of the process's memory at the time of termination. +This image can be used in a debugger (e.g., +.BR gdb (1)) +to inspect the state of the program at the time that it terminated. A list of the signals which cause a process to dump core can be found in .BR signal (7). @@ -65,11 +68,18 @@ or the user has reached their quota for the file system. The directory in which the core dump file is to be created does not exist. .IP * +The .B RLIMIT_CORE -or +(core file size) or .B RLIMIT_FSIZE -resource limits for a process are set to zero (see -.BR getrlimit (2)). +(file size) resource limits for the process are set to zero; see +.BR getrlimit (2) +and the documentation of the shell's +.I ulimit +command +.RI ( limit +in +.BR csh (1)). .IP * The binary being executed by the process does not have read permission enabled.