Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

core(5) [bsd man page]

CORE(5) 							File Formats Manual							   CORE(5)

core - format of memory image file SYNOPSIS
#include <sys/param.h> DESCRIPTION
The UNIX System writes out a memory image of a terminated process when any of various errors occur. See sigvec(2) for the list of reasons; the most common are memory violations, illegal instructions, bus errors, and user-generated quit signals. The memory image is called `core' and is written in the process's working directory (provided it can be; normal access controls apply). The core file consists of the u. area, whose size (in 64 byte `clicks') is defined by the USIZE manifest in the <sys/param.h> file. The u. area starts with a user structure as given in <sys/user.h>. The rest of the u. area consists of the kernel stack for the terminated process which includes (among other things) the processor registers at the time of the fault; see the system listings for the format of this area. The remainder of the core file consists first of the data pages and then the stack pages of the process image. The amount of data space image in the core file is given (in clicks) by the variable u_dsize in the u. area. If the text segment was not write-only and and shared it is included as the first etext bytes of the data image where etext is taken from the symbol table of the object file which generated the memory image. The amount of stack image in the core file is given (in clicks) by the variable u_ssize in the u. area. In general the debugger adb(1) is sufficient to deal with core images. SEE ALSO
adb(1), sigvec(2), stack(5) 3rd Berkeley Distribution January 26, 1987 CORE(5)

Check Out this Related Man Page

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

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, where pid is the process ID of the process, 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 vari- ous 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 privileged user must do one of the following * Edit /etc/launchd.conf or $HOME/.launchd.conf and add a line specifying the limit limit core unlimited * A privileged user can also enable cores with launchctl limit core unlimited * A privileged user can also enable core files by using ulimit(1) or limit(1) depending upon the shell. SEE ALSO
gdb(1), setrlimit(2), sigaction(2), Mach-O(5), launchd.conf(5), launchd.plist(5), sysctl(8) HISTORY
A core file format appeared in Version 6 AT&T UNIX. BSD
June 26, 2008 BSD
Man Page

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Segmentation fault (core dumped)

Hello To All! Now anfd then I receive a message on my console: Segmentation fault (core dumped) What does it mean? Or more precisely what are the implications? :confused: (1 Reply)
Discussion started by: Ivo
1 Replies

2. Programming

memory fault

When I excute a program . It seems to generate an error : memory fault (core dump ) So how can i (1 Reply)
Discussion started by: iwbasts
1 Replies

3. AIX

occasional core dump

Hi, We have one application (c language) installed on our AIX 5.2. When we enter some large amount of data in one screen and do update, it is dumping core some times without any error (like bus error, segmentation fault). Next we open the application again and enter the same data and do update.... (0 Replies)
Discussion started by: venkatmyname
0 Replies

4. Programming

Memory Fault,Core dumped

I have written a code in UNIX which is complied by using g++. Compling with turbo C didnt yield any errors, but with g++ I am getting Memory fault, core dumped. Could anyone help me out with this? Given below is the code: #include<stdio.h> #include<string.h> #include<stdlib.h>... (2 Replies)
Discussion started by: usshell
2 Replies

5. HP-UX

memory fault(core dump)

i am getting memory fault (core dump) in a C program i want to know which statement execution caused it. i tried following things $ gdb generalised_tapinread_mod HP gdb 5.4.0 for HP Itanium (32 or 64 bit) and target HP-UX 11.2x. Copyright 1986 - 2001 Free Software Foundation, Inc.... (2 Replies)
Discussion started by: junaid.nehvi
2 Replies

6. HP-UX


Hi, I am running a iplanet webserver in a HP-UX box and the iplanet webserver is crashing oftenly. I want to take a core dump. Could you please let me know how can i check whether server core is enabled? if not how can i enable the same? Also let me know to which path it saves the core. ... (7 Replies)
Discussion started by: Krrishv
7 Replies

7. Solaris

segmentation fault core dumped

i am getting segmentation fault (core dumped) i tried following things but couldn't understand what is wrong with my prog and where the problem is.... i have only adb debugger available on solaris.... so plz help bash-3.00$ pstack core core 'core' of 765: ./mod_generalised_tapinread... (4 Replies)
Discussion started by: junaid.nehvi
4 Replies

8. Red Hat

Segmentation fault (core dumped)

Hi All, I am getting "Segmentation fault (core dumped)" error in the runtime. I am new this please can you tell me why is that i am getting this error and I am not sure of my compilation : gcc -c avc_test.c gcc -c md5.c gcc avc_test.o md5.o -shared -o proj ... (1 Reply)
Discussion started by: fido.genial
1 Replies

9. Programming

HELP!!: CPU resource allocation between kernel modules and user mode process

Hi,all: I run my program which consists of one kernel module and one user mode process on a dual core server. The problem here is the kernel module consumes 100% of one core while the user mode process only consumes 10% of the other core, is there any solution that I can assign some computing... (1 Reply)
Discussion started by: neyshule
1 Replies

10. Homework & Coursework Questions

how to delete core file (file created due to apps crashed)

1. The problem statement, all variables and given/known data: When looking for corefiles, include any file with core in its name. (Some UNIX/Linux systems add the PID of the process that created the core to reduce the chances of overwriting an already existing core file that might be needed. The... (6 Replies)
Discussion started by: s3270226
6 Replies