09-16-2011
to: DGPickett
Hi DGPickett,
can you please send me your core dump analysis scripts that you mentioned(which runs continuously and analyzes core files and send report)
Thanks and Regards
Madhu
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
SKILL(1) Linux User's Manual SKILL(1)
,
NAME
skill, snice - report process status
SYNOPSIS
skill [signal to send] [options] process selection criteria
snice [new priority] [options] process selection criteria
DESCRIPTION
The default signal for skill is TERM. Use -l or -L to list available signals. Particularly useful signals include HUP, INT, KILL, STOP,
CONT, and 0. Alternate signals may be specified in three ways: -9 -SIGKILL -KILL.
The default priority for snice is +4. (snice +4 ...) Priority numbers range from +20 (slowest) to -20 (fastest). Negative priority num-
bers are restricted to administrative users.
GENERAL OPTIONS
-f fast mode This is not currently useful.
-i interactive use You will be asked to approve each
action.
-v verbose output Display information about selected
processes.
-w warnings enabled This is not currently useful.
-n no action This only displays the process ID.
PROCESS SELECTION OPTIONS
Selection criteria can be: terminal, user, pid, command. The options below may be used to ensure correct interpretation.
-t The next argument is a terminal (tty or pty).
-u The next argument is a username.
-p The next argument is a process ID number.
-c The next argument is a command name.
SIGNALS
The signals listed below are available for use with skill. When known, numbers and default behavior are shown.
Name Num Action Description
() ()
ALRM 14 exit
HUP 1 exit
INT 2 exit
KILL 9 exit this signal may not be blocked
PIPE 13 exit
POLL exit
PROF exit
TERM 15 exit
USR1 exit
USR2 exit
VTALRM exit
STKFLT exit i386, m68k, arm and ppc hardware only
UNUSED exit i386, m68k, arm and ppc hardware only
TSTP stop context-dependent behavior may appear random
TTIN stop context-dependent behavior may appear random
TTOU stop context-dependent behavior may appear random
STOP stop this signal may not be blocked
CONT restart continue if stopped, otherwise ignore
PWR ignore may exit on some systems
WINCH ignore
CHLD ignore
URG ignore
ABRT 6 core
FPE 8 core
ILL 4 core
QUIT 3 core
SEGV 11 core
TRAP 5 core
SYS core may not be implemented
EMT core may not be implemented
BUS core core dump may fail
XCPU core core dump may fail
XFSZ core core dump may fail
EXAMPLES
Command Description
snice netscape crack +7 Slow down netscape and crack
skill -KILL -v pts/* Kill users on new-style PTY devices
skill -STOP torvalds davem tytso Stop 3 users
snice -17 root bash Give priority to root's shell
SEE ALSO
top(1) kill(1) renice(1) nice(1)
STANDARDS
No standards apply.
AUTHOR
Albert Cahalan <acahalan@cs.uml.edu> wrote skill and snice in 1999 as a replacement for a non-free version. Michael K. Johnson <john-
sonm@redhat.com> is the current maintainer of the procps collection.
Please send bug reports to <procps-list@redhat.com>
()