pstack(1) [debian 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 the LinuxThreads libpthread.so library.  (To check, run nm(1) on your pthreads
       library, and make sure that the symbol "__pthread_threads_debug" is defined.)  Threads are not supported with the newer NPTL  libpthread.so
       library.

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)

pstack(1)						      General Commands Manual							 pstack(1)

NAME

       pstack - print a stack trace for each LWP in each process and core file

SYNOPSIS


DESCRIPTION

       prints a stack trace (hex+symbolic) for each LWP (Lightweight Process) in each process and core file.

       Given  the  pid of a running process or the full path of a core file, prints the stack trace for each LWP thread in the process.  To obtain
       symbol information, searches load modules (executable and shared libraries) in the current directory, and You can  specify  the	executable
       path  with the pid/corepath, separated by a colon character.  If cannot find a load module, symbol information for frames in that module is
       not displayed.

       works by attaching to the running process and reading its registers, memory, and stack.	 Mismatch  between  executable	and  corefile  may
       result in unpredictable behavior.

   Options
       supports the following option:

	      Prints the usage menu.

   Operand
       supports the following operand:
	      pid identifies a running process, with an optional execpath, the full executable path.

		     corepath is the full path name of the specified executable.

RETURN VALUES

       returns the following values:

	      Successful completion.
	      Failure.
		      An error has occurred.

SEE ALSO

       ldd(1), pldd(1).

Itanium(R)-based Systems Only														 pstack(1)