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)
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)
Hi All
I am new for this forum. I have a core file by using gdb and bt cmd I got the function name but I want to the exact cause of the core dump because of I can not reproduse the binary so if any one know the cmd plz plz plz let me know. (0 Replies)
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)
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)
my progrme complaints 'Segmentation fault'.
How to let it print 'Segmentation fault(core dumped)' and generate core dump file?
$ulimit
unlimited (22 Replies)
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)
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
LEARN ABOUT FREEBSD
savecore
SAVECORE(8) BSD System Manager's Manual SAVECORE(8)NAME
savecore -- save a core dump of the operating system
SYNOPSIS
savecore -c [-v] [device ...]
savecore -C [-v] [device ...]
savecore [-fkvz] [-m maxdumps] [directory [device ...]]
DESCRIPTION
The savecore utility copies a core dump into directory, or the current working directory if no directory argument is given, and enters a
reboot message and information about the core dump into the system log.
The options are as follows:
-C Check to see if a dump exists, and display a brief message to indicate the status. An exit status of 0 indicates that a dump is
there, 1 indicates that none exists. This option is compatible only with the [-v] option.
-c Clear the dump, so that future invocations of savecore will ignore it.
-f Force a dump to be taken even if either the dump was cleared or if the dump header information is inconsistent.
-k Do not clear the dump after saving it.
-m maxdumps Maximum number of dumps to store. Once the number of stored dumps is equal to maxdumps the counter will restart from 0.
-v Print out some additional debugging information. Specify twice for more information.
-z Compress the core dump and kernel (see gzip(1)).
The savecore utility looks for dumps on each device specified by the device argument(s), or on each device in /etc/fstab marked as ``dump''
or ``swap''. The savecore utility checks the core dump in various ways to make sure that it is complete. If it passes these checks, it
saves the core image in directory/vmcore.# and information about the core in directory/info.#. For kernel textdumps generated with the
textdump(4) facility, output will be stored in the tar(5) format and named directory/textdump.tar.#. The ``#'' is the number from the first
line of the file directory/bounds, and it is incremented and stored back into the file each time savecore successfully runs.
The savecore utility also checks the available disk space before attempting to make the copies. If there is insufficient disk space in the
file system containing directory, or if the file directory/minfree exists and the number of free kilobytes (for non-superusers) in the file
system after the copies were made would be less than the number in the first line of this file, the copies are not attempted.
If savecore successfully copies the kernel and the core dump, the core dump is cleared so that future invocations of savecore will ignore it.
The savecore utility is meant to be called near the end of the initialization file /etc/rc (see rc(8)).
SEE ALSO gzip(1), getbootfile(3), textdump(4), tar(5), dumpon(8), syslogd(8)HISTORY
The savecore utility appeared in 4.1BSD.
Support for kernel textdumps appeared in FreeBSD 7.1.
BUGS
The minfree code does not consider the effect of compression or sparse files.
BSD December 17, 2012 BSD