coredump_write(9) [netbsd man page]

COREDUMP_WRITE(9)					   BSD Kernel Developer's Manual					 COREDUMP_WRITE(9)

NAME

     coredump_write -- common coredump write routine

SYNOPSIS

     #include <sys/signalvar.h>

     int
     coredump_write(void *iocookie, enum uio_seg segflg, const void *data, size_t len);

DESCRIPTION

     coredump_write() is used by both machine-dependent and machine-independent components to write information to a coredump.	iocookie is an
     opaque pointer that was supplied to the caller of coredump_write().  segflg indicates where the data is located, system space or user space.
     data points to the information to be written to the coredump.  len is the amount of data to be written.

     coredump_write() returns 0 on success and an appropriate error code on failure.

CODE REFERENCES

     Process core dumps are initiated within the file sys/kern/kern_sig.c.  Process core dumps for ELF NetBSD binaries are performed within the
     files sys/kern/core_elf32.c or sys/kern/core_elf64.c.  Process core dumps for other NetBSD binaries are performed within the file
     sys/kern/core_netbsd.c.

SEE ALSO

     cpu_coredump(9)

BSD
								 December 24, 2005							       BSD

CORE(5) 						      BSD File Formats Manual							   CORE(5)

NAME

     core -- memory image file format

SYNOPSIS

     #include <sys/param.h>

DESCRIPTION

     A small number of signals which cause abnormal termination of a process also cause a record of the process's in-core state to be written to
     disk for later examination by one of the available debuggers.  (See sigaction(2).)  This memory image is written to a file named by default
     core.pid in the /cores directory; provided the terminated process had write permission in the directory, and the directory existed.

     The maximum size of a core file is limited by setrlimit(2).  Files which would be larger than the limit are not created.

     The core file consists of the ~ Mach-O(5) header as  described in the <mach-o/loader.h> file.  The remainder of the core file consists of
     various sections described in the Mach-O(5) header.

NOTE

     Core dumps are disabled by default under Darwin/Mac OS X.	To re-enable core dumps, a privlaged user must edit /etc/hostconfig to contain the
     line:

     COREDUMPS=-YES-

SEE ALSO

     gdb(1), setrlimit(2), sigaction(2), Mach-O(5), sysctl(8)

HISTORY

     A core file format appeared in Version 6 AT&T UNIX.

BSD
								  March 18, 2002							       BSD