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

jsadebugd

jsadebugd(1)						      General Commands Manual						      jsadebugd(1)

NAME

       jsadebugd - serviceability agent debug daemon

SYNOPSIS

       jsadebugd [pid] [server-id]
       jsadebugd executable core [server-id]

DESCRIPTION

       jsadebugd  attaches to a Java process or core file and acts as a debug server. Remote clients such as jstack, jmap, and jinfo can attach to
       the server using Java Remote Method Invocation (RMI). Before starting jsadebugd, rmiregistry must be started with:

	      rmiregistry -J-Xbootclasspath/p:$JAVA_HOME/lib/sajdi.jar

       where $JAVA_HOME is the J2SE SDK installation directory.  If rmiregistry was not started, jsadebugd will start an rmiregistry in a standard
       (1099) port internally. Debug server may be stopped by sending SIGINT (pressing Ctrl-C) to it.

       NOTE - This utility is unsupported and may or may not be available in future versions of the J2SE SDK.  jinfo is not currently available on
       Windows platforms or on the Linux Itanium platform.

PARAMETERS

       pid	      process id of the process to which the debug server should attach. The process must be a Java process. To get a list of Java
		      processes  running  on  a  machine,  jps	may be used.  At most one instance of the debug server may be attached to a single
		      process.

       executable     Java executable from which the core dump was produced.

       core	      core file to which the debug server should attach.

       server-id      optional unique id, needed if multiple debug servers are started on the same machine. This ID must be used by remote clients
		      to identify the particular debug server to attach. Within a single machine, this ID must be unique.

SEE ALSO

       jinfo(1) jmap(1) jps(1) jstack(1) rmiregistry(1)

								   13 June 2004 						      jsadebugd(1)