10 More Discussions You Might Find Interesting
1. Solaris
Hi guys,
just want to know which core file pattern is best to set for core dumps:
1) per-process file name pattern
or
2) global file name pattern.
I will really appreciate an explanation why the chosen one is better.
Thanks a lot guys. (2 Replies)
Discussion started by: cjashu
2 Replies
2. HP-UX
Hi Guys,
I was wondering if somebody could give me a link to a very good source of information or document about core dump process and How to's about it. I have also googled it and found some articles myself.
Thanks
Messi (1 Reply)
Discussion started by: messi777
1 Replies
3. UNIX for Dummies Questions & Answers
my progrme complaints 'Segmentation fault'.
How to let it print 'Segmentation fault(core dumped)' and generate core dump file?
$ulimit
unlimited (22 Replies)
Discussion started by: vistastar
22 Replies
4. AIX
Hi ,
I want to read core dump file on AIX5.3. While i am trying to use following commands, i am getting only few lines of information.
ux201p3:e46123> dbx capsWrkstnMgr core
Type 'help' for help.
reading symbolic information ...
Segmentation fault in malloc_common.extend_brk at... (1 Reply)
Discussion started by: rps
1 Replies
5. Programming
how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Discussion started by: Manabhanjan
2 Replies
6. AIX
My application gives core dump. When i am debugging with dbx getting instructions below:
pthdb_session.c, 818: 695445 PTHDB_INTERNAL (internal error)
pthreaded.c, 1941: PTHDB_INTERNAL (internal error)
Illegal instruction (illegal opcode) in . at 0x0
warning: Unable to access address 0x0... (1 Reply)
Discussion started by: bapi
1 Replies
7. UNIX for Advanced & Expert Users
Hi All,
i am new to this forum.i want detail of reading the core file and trace the problem because of what the program get crashed.please help me.if any body knows any website or tutoril plese let me know.
sudhir (6 Replies)
Discussion started by: sudhir patnaik
6 Replies
8. Programming
MY friends:
my program under sco unix have a problem?
it create a core dump file on the path when execute program ,
but i can't find the error of the C program ,i don't know how to
see the error about my program use core, please help me
or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 Replies
9. UNIX for Dummies Questions & Answers
I've got a core dump in my weblogic home directory, which i have tried to debug by initiating savecore from /etc/init.d/savecore start
but savecore failed to create the two files, that is vmcore.n and vmunix.n.
savecore is enable on my server to save vmcore and vmunix in /var/crash/hostname
1)... (4 Replies)
Discussion started by: hassan2
4 Replies
10. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
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
programname.core in the working directory; provided the terminated process had write permission in the directory, and provided the abnormal-
ity did not cause a system crash. (In this event, the decision to save the core file is arbitrary, see savecore(8).)
The maximum size of a core file is limited by setrlimit(2). Files which would be larger than the limit are not created.
The name of the file is controlled via the sysctl(8) variable kern.corefile. The contents of this variable describes a filename to store the
core image to. This filename can be absolute, or relative (which will resolve to the current working directory of the program generating
it).
The following format specifiers may be used in the kern.corefile sysctl to insert additional information into the resulting core file name:
%H Machine hostname.
%I An index starting at zero until the sysctl debug.ncores is reached. This can be useful for limiting the number of corefiles
generated by a particular process.
%N process name.
%P processes PID.
%U process UID.
The name defaults to %N.core, yielding the traditional FreeBSD behaviour.
By default, a process that changes user or group credentials whether real or effective will not create a corefile. This behaviour can be
changed to generate a core dump by setting the sysctl(8) variable kern.sugid_coredump to 1.
Corefiles can be compressed by the kernel if the following items are included in the kernel configuration file:
options COMPRESS_USER_CORES
devices gzio
When COMPRESS_USER_CORES is included the following sysctls can control if core files will be compressed:
kern.compress_user_cores_gzlevel Gzip compression level. Defaults to -1.
kern.compress_user_cores Actually compress user cores. Core files will have the suffix .gz appended to them.
EXAMPLES
In order to store all core images in per-user private areas under /var/coredumps, the following sysctl(8) command can be used:
sysctl kern.corefile=/var/coredumps/%U/%N.core
SEE ALSO
gdb(1), kgdb(1), setrlimit(2), sigaction(2), sysctl(8)
HISTORY
A core file format appeared in Version 6 AT&T UNIX.
BSD
November 22, 2012 BSD
Core dump in HP-UX..