08-10-2011
I usually use gdb bt or dbx where on core, after using file and strings to figure out what it was running. If optimized, expect inlined calls to disappear. I am more into distrusting inputs, good logging, debug messages, error handling, all-cases action and good structure, with an occasional side of truss/tusc/strace. I stopped stepping when I left hardware in the late 80's.
I used to run core dump hunters on my servers, where each core dump was stack traced and analyzed by script, saved compressed in a dir with 8th day purge, removed and reported by email. Many prod mysteries are core dumps. Some are not fixable, but you get to know their signatures.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi folks,
I'm hoping someone would be charitable enough to give me a quick explanation of adb usage for analyzing core files...or point me in the right direction. A search here revealed scant results and web searches are providing me with ambiguous information.
Running Solaris.
Thanks,... (1 Reply)
Discussion started by: kristy
1 Replies
2. UNIX for Advanced & Expert Users
Hello,
I'm new to the group and this is my first post. I'm hoping someone can help me out. I have a core dump that I need to analyze from a Unix box and I've never done this sort of thing before. I was told to run a pmap and pstack on the core file which provided two different output files. ... (3 Replies)
Discussion started by: kimblebee
3 Replies
3. Solaris
Hello everyone,
I have a 12-thread application running on Solaris 9.
When I use the pstack command after a typical core dump, it prints the stack output of all 12 threads/lwps. This is the standard procedure as it is described in the Solaris MAN pages.
Is there a way to filter out the... (1 Reply)
Discussion started by: gregb32
1 Replies
4. Shell Programming and Scripting
Hello,
I have a text file containin 4 lines which are repeated along the file, ie
the file looks like this:
16:20:12.060769 blablabla 40
16:20:12.093199 blablabla 640
16:20:12.209003 blablabla 640
16:20:12.273179 blablabla 216
16:20:27.217444 blablabla 40
16:20:27.235410 blablabla 640... (2 Replies)
Discussion started by: Celine19
2 Replies
5. Red Hat
Can someone tell me the Linux equivalent for pstack and pfiles and ptree which are Solaris commands. (1 Reply)
Discussion started by: bdsffl
1 Replies
6. Solaris
How can we analyze a core file and determine why it was generated on a solaris system?
I know file core filename will tell us what program generated the file. But, what to do next to get more details?
Thanks, (5 Replies)
Discussion started by: Pouchie1
5 Replies
7. Shell Programming and Scripting
Hi All,
Given a list of date and time, how can i split them in intervals of 1 hour. The input file is listed as below f.e.:
16-OCT-2009 09:11:47 10.65.4.24.
.
. (1 Reply)
Discussion started by: x-plicit78
1 Replies
8. UNIX for Advanced & Expert Users
Dear All,
I am new to this forum. This is my first.
I am facing customer issue. Customer has got core file while running the server.
He had sent core file and details from pstack, pmap and pldd commands.
I have to debug this application, please help me to fix this issue.
I am using sparc... (1 Reply)
Discussion started by: KiranBangalore
1 Replies
9. Solaris
Dear All,
I am new to this forum. This is my first.
I am facing customer issue. Customer has got core file while running the server.
He had sent core file and details from pstack, pmap and pldd commands.
I have to debug this application, please help me to fix this issue.
I am using sparc 10... (4 Replies)
Discussion started by: KiranBangalore
4 Replies
10. Ubuntu
Hi All
I would like to use the tool "pstack" to get a sample of the stack trace for a process.
As far as I understood It seems widely available in all Linux systems, but it is not in Ubuntu 10.10.
I tried using apt-get as per some posts in few forum, but it cannot be found in the APT... (9 Replies)
Discussion started by: manustone
9 Replies
SAVECORE(8) System Manager's Manual SAVECORE(8)
NAME
savecore - save a core dump of the operating system
SYNOPSIS
savecore dirname [ system ]
DESCRIPTION
Savecore is meant to be called at the end of the /etc/rc file. Its function is to save the core dump of the system (if one was made) and
to write a reboot message in the shutdown log.
It saves the core image in the file dirname/core.n and its corresponding namelist in dirname/unix.n. The second argument is the namelist
for the system which made the core image; the current system is always assumed to be /unix. The trailing ".n" in the pathnames is replaced
by a number which grows every time savecore is run in that directory.
Before savecore writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the file sys-
tem which contains dirname than the number obtained from the minfree file, the core dump is not done. If the minfree file does not exist,
savecore always writes out the core file (assuming that a core dump was taken).
Savecore also writes a reboot message in the shut down log. If the system crashed as a result of a panic, savecore records the panic
string in the shut down log too.
If savecore detects that the system time is wrong because of a crash (the time in the core image is after the current time), it will reset
the system time to its best estimate of the time, which is the time in the core image plus the elapsed time since the reboot. It announces
the time that it set when this occurs.
FILES
/usr/adm/shutdownlogshutdown log
/unix current UNIX
BUGS
The method used to determine whether a dump is present, and to prevent the same core image from being saved multiple times, is not elegant.
This information should be passed to init by the system; however, this is difficult because the system may have to be rebooted a second
time if the root filesystem is patched.
3rd Berkeley Distribution SAVECORE(8)