09-07-2011
Thread Dump not working
Hello,
I'm running a kill -QUIT on few process IDs (OS: Solaris) but the Thread Dump is empty.
Can you please help me get it back on?
Since I'm quite new to this, I'm not aware of the checks. Please let me know for the info required to debug this issue.
Thanks!
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. Programming
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... (1 Reply)
Discussion started by: kumars
1 Replies
3. UNIX for Advanced & Expert Users
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... (1 Reply)
Discussion started by: rajamohan
1 Replies
4. Programming
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 (4 Replies)
Discussion started by: UsmanUrRehman
4 Replies
5. Shell Programming and Scripting
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 (5 Replies)
Discussion started by: ram5019
5 Replies
6. Linux
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... (2 Replies)
Discussion started by: vishwasungal
2 Replies
gcore(1) General Commands Manual gcore(1)
NAME
gcore - get core images of running processes
SYNOPSIS
filename] process-id...
DESCRIPTION
The command creates a core image of each specified process. By default, the name of the core image file for process-id will be The process
information in the core file can be obtained by using debuggers.
When the command creates a core image of each specified process, the process is temporarily stopped. Further, when the creation of core
image is complete, the process continues to execute.
Options
Creates the core file with name of the file as
If multiple process-id values are specified, filename will be common for all the core image files. See the section.
Operands
process-id The process ID for which a core image file will be created.
RETURN VALUE
Upon completion, exits with one of the following values:
A core file was successfully created.
An error condition was encountered.
In such a case, the creation of a core file is not guaranteed. The error conditions could be because of
o A nonexistent or incorrect process ID was specified.
o An invalid option was specified.
o The current working directory of the process or directory from which was invoked had no write permissions.
o The current working directory of the process was not accessible.
o The file system is full.
EXAMPLES
Example 1
Dump the core image of process 1030 in the file "core.1030".
Example 2
Dump the core image of the process 1030 in the file "test.1030".
Example 3
Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files "core.1030", "core.1031", "core.1032", "core.1033".
Example 4
Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files
FILES
Core image file for process-id. (Both where is invoked and the current working directory of the process.)
AUTHOR
was developed by Chris Bertin (HP).
SEE ALSO
adb(1), gdb(1), kill(1), ttrace(2), a.out(4), core(4).
gcore(1)