Thread Dump not working Post: 302553363

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

help, what is the difference between core dump and panic dump?

2. Programming

Thread prog (core dump)

Could any one please suggest me how to solve this...... when I compiled the program and tried to execute it as follows, it works fine under different inputs like: ./main -r 300 -w 3 -s 100 ./main -r 600 -w 3 -s 1000 ./main -r 10 -w 3 -s 100 But it fails when I tired to give the input as...

3. UNIX for Advanced & Expert Users

How to know whether my perodic thread is working fine

Dear All, I am using xenomai-2.4 along with linux kernel 2.6 In my application having following threads. 8ms perodic thread (RT TASK) 1ms perodic thread(RT TASK) 16ms perodic thread(RT TASK) 256ms perodic thread(RT TASK) 22 - pthread are condition based it may execute or else in...

4. Programming

Thread Not Working

Hy, In my current knowledge, i write the code for multiply 3x3 matrix to it self . . . Problem is that pthread_create function is not working. Here is my code :wall::wall::wall::wall: Please help me to this problem ! Thanks

5. Shell Programming and Scripting

Thread Dump

I used take thread dump when our application gets out of memory issue. can any one help on check thread dump result. where it will save tool to read thread dump.:wall: date; kill -3 process_id; sleep 300; kill -3 process_id; sleep 300; kill -3 process_id;date

6. Linux

Thread specific data from linux core dump

How do i get pointer to thread's local storage or thread specific data while analyzing core dump for linux ? i use pthread_setspecific to store some data in the pthread's local stoare. my multi threaded program on linux crashed, and i want to see what is stored in current running thread's...

LEARN ABOUT MOJAVE

kill.d

kill.d(1m)							   USER COMMANDS							kill.d(1m)

NAME

       kill.d - snoop process signals as they occur. Uses DTrace.

SYNOPSIS

       kill.d

DESCRIPTION

       kill.d is a simple DTrace program to print details of process signals as they are sent, such as the PID source and destination, signal num-
       ber and result.

       This program can be used to determine which process is sending signals to which other process.

       Since this uses DTrace, only users with root privileges can run this command.

EXAMPLES

       Default output, print process signals as they are sent.
	      # kill.d

FIELDS

       FROM   source PID

       COMMAND
	      source command name

       TO     destination PID

       SIG    destination signal ("9" for a kill -9)

       RESULT result of signal (-1 is for failure)

DOCUMENTATION

       See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver-
       bose descriptions explaining the output.

EXIT

       kill.d will run forever until Ctrl-C is hit.

AUTHOR

       Brendan Gregg [Sydney, Australia]

SEE ALSO

       dtrace(1M), truss(1)

version 0.90							   May 14, 2005 							kill.d(1m)