mirror of https://github.com/mkerrisk/man-pages
Minor wording changes
This commit is contained in:
parent
5ddfb8c744
commit
d216b211c3
11
man5/core.5
11
man5/core.5
|
@ -134,9 +134,16 @@ shares its memory with another process by being created with the
|
||||||
flag of
|
flag of
|
||||||
.BR clone (2))
|
.BR clone (2))
|
||||||
dumps core, then the process ID is always appended to the core filename,
|
dumps core, then the process ID is always appended to the core filename,
|
||||||
unless the PID was otherwise included as a consequence of a
|
unless the process ID was already included elsewhere in the
|
||||||
%p specification in
|
filename via a %p specification in
|
||||||
.IR /proc/sys/kernel/core_pattern .
|
.IR /proc/sys/kernel/core_pattern .
|
||||||
|
.\" This made sense for LinuxThreads, where each thread had a unique
|
||||||
|
.\" PID, but doesn't seem to have any use with NPTL, where all the
|
||||||
|
.\" threads in a process share the same PID (as POSIX.1 requires).
|
||||||
|
.\" Probably the behaviour is maintained so that applications using
|
||||||
|
.\" LinuxThreads continue appending the PID (the kernel has no easy
|
||||||
|
.\" way of telling which threading implementation the userspace
|
||||||
|
.\" application is using). -- mtk, April 2006
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
.BR gdb (1),
|
.BR gdb (1),
|
||||||
.BR getrlimit (2),
|
.BR getrlimit (2),
|
||||||
|
|
Loading…
Reference in New Issue