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. 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
3. AIX
hi,
i am getting core dump while running my broadcast program.while debbuging with dbx it gives....
Segmentation fault in lzo1z_decompress at 0x10003850 ($t1)
0x10003850 (lzo1z_decompress+0x1d0) 98640000 stb r3,0x0(r4)
(dbx) where
lzo1z_decompress(0x2ff21884, 0x2020,... (1 Reply)
Discussion started by: ajaysahoo
1 Replies
4. UNIX for Advanced & Expert Users
Hello all,
Iam new to unix while executing java program which finely working in windows know iam testing with unix ,but in unix while executing iam getting core dump, my application is in client server environment and it is menu drivrn application on clicking options no problem but after some time... (1 Reply)
Discussion started by: vinp
1 Replies
5. UNIX for Dummies Questions & Answers
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)
Discussion started by: gyanusoni
0 Replies
6. 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
7. 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
8. UNIX for Dummies Questions & Answers
Hi ,
Working on AIX 4.3. An internal error from my apps engine suddenly causes the engine to die. During this time i do notice a core file being dumped in the directory from where I try to re-start my engine.
Q is how does one read this core file, or I should say 'what is this core file'?
thnx (2 Replies)
Discussion started by: buRst
2 Replies
9. UNIX for Dummies Questions & Answers
does any one have read a core dump?
is there any reader for that? or may i know what is the use of that core which takes sometimes memory in GBs?
:) (6 Replies)
Discussion started by: sskb
6 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
SAVECORE(8) BSD System Manager's Manual SAVECORE(8)
NAME
savecore -- save a core dump of the operating system
SYNOPSIS
savecore [-fvz] [-N system] [-Z level] [directory]
savecore -c [-v] [-N system]
savecore -n [-v] [-N system]
DESCRIPTION
When the NetBSD kernel encounters a fatal error, the panic(9) routine arranges for a snapshot of the contents of physical memory to be writ-
ten into a dump area, typically in the swap partition.
Upon a subsequent reboot, savecore is typically run out of rc(8), before swapping is enabled, to copy the kernel and the saved memory image
into directory, and enters a reboot message and information about the core dump into the system log. If a directory is not specified, then
/var/crash is used.
The kernel and core file can then be analyzed using various tools, including crash(8), dmesg(8), fstat(1), gdb(1), iostat(8), netstat(1),
ps(1), and pstat(8), to attempt to deduce the cause of the crash.
Crashes are usually the result of hardware faults or kernel bugs. If a kernel bug is suspected, a full bug report should be filed at
http://www.netbsd.org/, or using send-pr(1), containing as much information as possible about the circumstances of the crash. Since crash
dumps are typically very large and may contain whatever (potentially confidential) information was in memory at the time of the crash, do NOT
include a copy of the crash dump file in the bug report; instead, save it somewhere in the event that a NetBSD developer wants to examine it.
The options are as follows:
-c Only clears the dump without saving it, so that future invocations of savecore will ignore it.
-f Forces a dump to be taken even if the dump doesn't appear correct or there is insufficient disk space.
-n Check whether a dump is present without taking further action. The command exits with zero status if a dump is present, or with
non-zero status otherwise.
-N Use system as the kernel instead of the default (returned by getbootfile(3)). Note that getbootfile(3) uses secure_path(3) to
check that kernel file is ``secure'' and will default to /netbsd if the check fails.
-v Prints out some additional debugging information.
-z Compresses the core dump and kernel (see gzip(1)).
-Z level Set the compression level for -z to level. Defaults to 1 (the fastest compression mode). Refer to gzip(1) for more information
regarding the compression level.
savecore checks the core dump in various ways to make sure that it is current and that it corresponds to the currently running system. If it
passes these checks, it saves the core image in directory/netbsd.#.core and the system in directory/netbsd.# (or in
directory/netbsd.#.core.gz and directory/netbsd.#.gz, respectively, if the -z option is used). 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.
savecore 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.
SEE ALSO
fstat(1), gdb(1), gzip(1), netstat(1), ps(1), send-pr(1), crash(8), dmesg(8), iostat(8), pstat(8), rc(8), syslogd(8), panic(9)
HISTORY
The savecore command appeared in 4.1BSD.
BUGS
The minfree code does not consider the effect of compression.
BSD
September 13, 2011 BSD