Evaluates to a non-zero value if status was returned for a child process that stopped due to the receipt of a signal that was not caught (see [xref to <signal.h>]).

<h2>Core File</h2>
A file of unspecified format that may be generated when a process terminates
abnormally.

<h2>Core Image</h2>
An unspecified object of unspecified format that may be generated when
a process terminates abnormally.

CLD_KILLED Child has terminated abnormally and did not create a core file.
CLD_DUMPED Child has terminated abnormally and created a core file.

CLD_KILLED Child has terminated abnormally with no additional actions.
CLD_DUMPED Child has terminated abnormally and additional actions may have
                been taken.

While the example using _SC_VERSION in the APPLICATION USAGE section does
not provide the greatest degree of imaginable utility to the application
developer or user, it is arguably better than a core file or some other
equally obscure result.

While the example using _SC_VERSION in the APPLICATION USAGE section does
not provide the greatest degree of imaginable utility to the application
developer or user, it is arguably better than the production of a core
image or some other equally obscure result.

RLIMIT_CORE

This is the maximum size of a core file, in bytes,
that may be created by a process. A limit of 0 shall prevent
the creation of a core file. If this limit is exceeded,
the writing of a core file shall terminate at this size.

RLIMIT_CORE

This is the maximum size of a file containing a core image,
in bytes, that may be created by a process. A limit of 0 shall
prevent the creation of such a file. If this limit is exceeded,
the writing of a file containing a core image shall terminate
at this size. NOTE the production of such a file may be one of the
implementation defined actions for abnormal termination.

Implementations that support core file creation or other
implementation-defined actions ...

Implementations that support implementation-defined actions, such as the
creation of a file containing a core image, ...

Clean up core files every weekday morning at 3:15 am:

Remove files named core every weekday morning at 3:15 am:

The results from SIGQUIT are partially unspecified because, on systems
that create core files upon receipt of SIGQUIT, the core
from make would conflict with a core file from the command that
was running when the SIGQUIT arrived.

The results from SIGQUIT are partially unspecified because, on systems
that create a file named core upon receipt of SIGQUIT, the core file
from make would conflict with a core file from the command that
was running when the SIGQUIT arrived.

SZ (l) The size in blocks of the core image of the process.

SZ (l) The size in pages of the total memory requirements of the process, including text, data, stack, mapped memory and other resources.

WCOREDUMP

WCOREDUMP True if WIFSIGNALED is true and creation of a core image was attempted.
NOTE: The use of the word "attempted"
here means that the process terminated abnormally
with actions (see "SIG_DFL" in [xref to 2.4.3 Signal Actions]).
A core image might or might not have been
produced. Some implementations do not set this bit if
a core image was not produced, but this is not a requirement.

True if child is currently stopped.

True if child stopped due to uncaught signal.

Evaluates to a non-zero value if status was returned for a child process that is currently stopped.

Evaluates to a non-zero value if status was returned for a child process that stopped due to the receipt of a signal that was not caught (see [xref to <signal.h>]).

WCOREDUMP(stat_val)

If the value of WIFSIGNALED(stat_val) is non-zero, this macro evaluates to a non-zero value if the creation of a core image of the terminated child was attempted.