.\" Copyright (c) 2006, 2008 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
+.\" %%%LICENSE_START(VERBATIM)
.\" Permission is granted to make and distribute verbatim copies of this
.\" manual provided the copyright notice and this permission notice are
.\" preserved on all copies.
.\"
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
+.\" %%%LICENSE_END
.\"
-.TH CORE 5 2010-02-27 "Linux" "Linux Programmer's Manual"
+.TH CORE 5 2014-05-28 "Linux" "Linux Programmer's Manual"
.SH NAME
core \- core dump file
.SH DESCRIPTION
not produced:
.IP * 3
The process does not have permission to write the core file.
-(By default the core file is called
-.IR core ,
+(By default, the core file is called
+.IR core
+or
+.IR core.pid ,
+where
+.I pid
+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 will fail if the directory in which
core dump already exists, but there is more than one hard link to that
file.
.IP *
-The file system where the core dump file would be created is full;
+The filesystem where the core dump file would be created is full;
or has run out of inodes; or is mounted read-only;
-or the user has reached their quota for the file system.
+or the user has reached their quota for the filesystem.
.IP *
The directory in which the core dump file is to be created does
not exist.
.\" and PR_SET_DUMPABLE to this page?
file in
.BR proc (5).)
+.IP *
+(Since Linux 3.7)
+.\" commit 046d662f481830e652ac34cd112249adde16452a
+The kernel was configured without the
+.BR CONFIG_COREDUMP
+option.
+.PP
+In addition,
+a core dump may exclude part of the address space of the process if the
+.BR madvise (2)
+.B MADV_DONTDUMP
+flag was employed.
.SS Naming of core dump files
By default, a core dump file is named
.IR core ,
%%
a single % character
.TP
-%p
-PID of dumped process
+%c
+core file size soft resource limit of crashing process (since Linux 2.6.24)
.TP
-%u
-(numeric) real UID of dumped process
+%d
+.\" Added in git commit 12a2b4b2241e318b4f6df31228e4272d2c2968a1
+dump mode\(emsame as value returned by
+.BR prctl (2)
+.B PR_GET_DUMPABLE
+(since Linux 3.7)
+.TP
+%e
+executable filename (without path prefix)
+.TP
+%E
+pathname of executable,
+with slashes (\(aq/\(aq) replaced by exclamation marks (\(aq!\(aq)
+(since Linux 3.0).
.TP
%g
(numeric) real GID of dumped process
.TP
+%h
+hostname (same as \fInodename\fP returned by \fBuname\fP(2))
+.TP
+%p
+PID of dumped process,
+as seen in the PID namespace in which the process resides
+.TP
+%P
+.\" Added in git commit 65aafb1e7484b7434a0c1d4c593191ebe5776a2f
+PID of dumped process, as seen in the initial PID namespace
+(since Linux 3.12)
+.TP
%s
number of signal causing dump
.TP
time of dump, expressed as seconds since the
Epoch, 1970-01-01 00:00:00 +0000 (UTC)
.TP
-%h
-hostname (same as \fInodename\fP returned by \fBuname\fP(2))
-.TP
-%e
-executable filename (without path prefix)
-.TP
-%c
-core file size soft resource limit of crashing process (since Linux 2.6.24)
+%u
+(numeric) real UID of dumped process
.PD
.RE
.PP
If this file contains a nonzero value, then the core dump file includes
the process ID in a name of the form
.IR core.PID .
+
+Since Linux 3.6,
+.\" 9520628e8ceb69fa9a4aee6b57f22675d9e1b709
+if
+.I /proc/sys/fs/suid_dumpable
+is set to 2 ("suidsafe"), the pattern must be either an absolute pathname
+(starting with a leading \(aq/\(aq character) or a pipe, as defined below.
.SS Piping core dumps to a program
Since kernel 2.6.19, Linux supports an alternate syntax for the
.I /proc/sys/kernel/core_pattern
.IR root .
.IP *
Command-line arguments can be supplied to the
-program (since kernel 2.6.24),
+program (since Linux 2.6.24),
delimited by white space (up to a total line length of 128 bytes).
.IP *
The command-line arguments can include any of
.fi
.in
.PP
-This file is only provided if the kernel was built with the
+This file is provided only if the kernel was built with the
.B CONFIG_ELF_CORE
configuration option.
.SH NOTES
.I gcore
command can be used to obtain a core dump of a running process.
-If a multithreaded process (or, more precisely, a process that
+In Linux versions up to and including 2.6.27,
+.\" Changed with commit 6409324b385f3f63a03645b4422e3be67348d922
+if a multithreaded process (or, more precisely, a process that
shares its memory with another process by being created with the
.B CLONE_VM
flag of
unless the process ID was already included elsewhere in the
filename via a %p specification in
.IR /proc/sys/kernel/core_pattern .
-(This is primarily useful when employing the LinuxThreads implementation,
+(This is primarily useful when employing the obsolete
+LinuxThreads implementation,
where each thread of a process has a different PID.)
.\" Always including the PID in the name of the core file made
.\" sense for LinuxThreads, where each thread had a unique PID,
.\" threads in a process share the same PID (as POSIX.1 requires).
.\" Probably the behavior is maintained so that applications using
.\" LinuxThreads continue appending the PID (the kernel has no easy
-.\" way of telling which threading implementation the userspace
+.\" way of telling which threading implementation the user-space
.\" application is using). -- mtk, April 2006
.SH EXAMPLE
The program below can be used to demonstrate the use of the
.RB "$" " cc \-o core_pattern_pipe_test core_pattern_pipe_test.c"
.RB "$" " su"
Password:
-.RB "#" " echo \(aq|$PWD/core_pattern_pipe_test %p \
-UID=%u GID=%g sig=%s\(aq > \e"
+.RB "#" " echo \(dq|$PWD/core_pattern_pipe_test %p \
+UID=%u GID=%g sig=%s\(dq > \e"
.B " /proc/sys/kernel/core_pattern"
.RB "#" " exit"
.RB "$" " sleep 100"
.BR proc (5),
.BR pthreads (7),
.BR signal (7)
+.SH COLOPHON
+This page is part of release 3.68 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
OSDN Git Service
