core(5) [v7 man page]

CORE(5) 							File Formats Manual							   CORE(5)

NAME

       core - format of core image file

DESCRIPTION

       UNIX  writes  out  a  core image of a terminated process when any of various errors occur.  See signal(2) for the list of reasons; the most
       common are memory violations, illegal instructions, bus errors, and user-generated quit signals.  The core image is called  `core'  and	is
       written in the process's working directory (provided it can be; normal access controls apply).

       The  first  1024  bytes of the core image are a copy of the system's per-user data for the process, including the registers as they were at
       the time of the fault; see the system listings for the format of this area.  The remainder represents the actual  contents  of  the  user's
       core  area  when  the  core  image  was written.  If the text segment is write-protected and shared, it is not dumped; otherwise the entire
       address space is dumped.

       In general the debugger adb(1) is sufficient to deal with core images.

SEE ALSO

       adb(1), signal(2)

																	   CORE(5)

GCORE(1)						      General Commands Manual							  GCORE(1)

NAME

       gcore - get core image of running process

SYNOPSIS

       gcore [-s][-c core] pid

DESCRIPTION

       gcore  creates  a  core	image  of  each specified process, suitable for use with adb(1).  By default the core image is written to the file
       <pid>.core.

       The options are:

       -c     Write the core file to the specified file instead of <pid>.core.

       -s     Stop the process while creating the core image and resume it when done.  This makes sure that the core dump will be in a	consistent
	      state.   The  process is resumed even if it was already stopped.	Of course, you can obtain the same result by manually stopping the
	      process with kill(1).

       The core image name was changed from core.<pid> to <pid>.core to prevent matching names like core.h and core.c when using programs such	as
       find(1).

FILES

       <process-id>.core   The core image.

BUGS

       If gcore encounters an error while creating the core image and the -s option was used the process will remain stopped.

       Swapped out processes and system processes (the swapper) may not be gcore'd.

4.2 Berkeley Distribution					  April 15, 1994							  GCORE(1)