From b665474b29435f39ef9377408f8849ea642a7ec9 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Mon, 8 Jun 2020 18:06:10 +0200 Subject: [PATCH] core.5: wfix Reported-by: Jonny Grant Signed-off-by: Michael Kerrisk --- man5/core.5 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/man5/core.5 b/man5/core.5 index e9b01fd03..456366ea6 100644 --- a/man5/core.5 +++ b/man5/core.5 @@ -29,7 +29,7 @@ core \- core dump file The default action of certain signals is to cause a process to terminate and produce a .IR "core dump file" , -a disk file containing an image of the process's memory at +a 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)) @@ -58,7 +58,7 @@ is the ID of the process that dumped core, and is created in the current working directory. See below for details on naming.) Writing the core file fails if the directory in which -it is to be created is nonwritable, +it is to be created is not writable, or if a file with the same name exists and is not writable or is not a regular file @@ -287,7 +287,7 @@ in earlier kernels, meaning that the core dump handler needs to use mechanisms to find the executable name. .PP -Instead of being written to a disk file, the core dump is given as +Instead of being written to a file, the core dump is given as standard input to the program. Note the following points: .IP * 3