pstack(1) [redhat man page]

PSTACK(1)						     Linux Programmer's Manual							 PSTACK(1)

NAME

       pstack - print a stack trace of running processes

SYNOPSIS

       pstack pid [...]

DESCRIPTION

       pstack attaches to the active processes named by the pids on the command line, and prints out an execution stack trace, including a hint at
       what the function arguments are.  If symbols exist in the binary (usually the case unless you have run strip(1)), then  symbolic  addresses
       are printed as well.

       If the process is part of a thread group, then pstack will print out a stack trace for each of the threads in the group.

RESTRICTIONS

       pstack currently works only on Linux, only on an x86 machine running 32 bit ELF binaries (64 bit not supported).  Also, for symbolic infor-
       mation, you need to use a GNU compiler to generate your program, and you can't strip symbols from the binaries.	For thread information	to
       be dumped, you have to use the debug-aware version of libpthread.so.  (To check, run nm(1) on your pthreads library, and make sure that the
       symbol "__pthread_threads_debug" is defined.)

SEE ALSO

       nm(1), ptrace(2)

AUTHORS

       Ross Thompson <ross@whatsis.com>

       Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>

Red Hat Linux							    Feb 25 2002 							 PSTACK(1)

jstack(1)						      General Commands Manual							 jstack(1)

NAME

       jstack - stack trace

SYNOPSIS

       jstack [ option ] pid
       jstack [ option ] executable core
       jstack [ option ] [server-id@]remote-hostname-or-IP

DESCRIPTION

       jstack  prints  Java  stack traces of Java threads for a given Java process or core file or a remote debug server. For each Java frame, the
       full class name, method name, 'bci' (byte code index) and line number, if available, are printed. With the -m option,  jstack  prints  both
       Java  and  native frames of all threads along with the 'pc' (program counter). For each native frame, the closest native symbol to 'pc', if
       available, is printed. C++ mangled names are not demangled. To demangle C++ names, the output of this command may be piped to c++filt.

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

PARAMETERS

       Options are mutually exclusive. Option, if used, should follow immediately after the command name.

       pid	      process  id  for which the stacktrace is to be printed.  The process must be a Java process. To get a list of Java processes
		      running on a machine, jps may be used.

       executable     Java executable from which the core dump was produced.

       core	      core file for which the stack trace is to be printed.

       remote-hostname-or-IP
		      remote debug server's (see jsadebugd) hostname or IP address.

       server-id      optional unique id, if multiple debug servers are running on the same remote host.

OPTIONS

       -m	      prints mixed mode (both Java and native C/C++ frames) stack trace.

       -h	      Prints a help message.

       -help	      Prints a help message.

SEE ALSO

       pstack(1) c++filt(1) jps(1) jsadebugd(1)

KNOWN BUGS

       Mixed mode stack trace, the -m option, does not work with the remote debug server.

								   13 June 2004 							 jstack(1)