Print a stack trace of running processes
Go to file
Thomas Preud'homme a8f2e34c5f Make struct used by PTRACE_GETREGS arch-dependant
Structure used by ptrace in PTRACE_GETREGS mode is unfortunetely
arch-dependant. Although pt_regs seems portable, it's only designed to
represent the way registers are stored on the stack during system call.
The right struct to use is defined in sys/user.h and is
user_regs_struct on x86-{32,64} and user_regs on armel.
2011-10-05 17:38:17 +02:00
man1 Initial commit (pstack v1.2) 2011-08-18 17:18:25 +02:00
.gitattributes Don't include .*ignore files in archives 2011-10-03 22:51:02 +02:00
.gitignore Add .gitignore file 2011-10-02 22:22:28 +02:00
COPYING Initial commit (pstack v1.2) 2011-08-18 17:18:25 +02:00
Makefile Compile with -g -O2 by default 2011-10-05 17:38:17 +02:00
README Initial commit (pstack v1.2) 2011-08-18 17:18:25 +02:00
VERSION New release: pstack 1.3 2011-10-02 22:22:28 +02:00
changelog New release: pstack 1.3 2011-10-02 22:22:28 +02:00
pstack.c Make struct used by PTRACE_GETREGS arch-dependant 2011-10-05 17:38:17 +02:00

README

pstack - print stack trace of running processes

pstack dumps a stack trace for a process, given the pid of that
process.  If the process named is part of a thread group, then all the threads
inthe group are traced.  See the man page for more information.

This program was inspired by the 'pstack' program available on Solaris.

SUPPORTED PLATFORMS:
	This program runs on 32 bit x86 machines, using ELF binaries
generated from GNU compilers.  If threads are being used, it depends
on a debuggable version of the pthreads library to find the threads in
the thread group.  If anyone wants to port this to other
architectures, please let me know about questions you may have, or
achievements you have made.  I'd like to incorporate such changes into
my version of the code.

FEATURES:
	symbolic address dumping
  thread group support

BUILD:
   make

INSTALL:
	 make install

UNINSTALL:
   make uninstall

NOTE: you must be root to [un]install.  pstack will run fine from any
directory, install just puts the binary and man page in 'normal'
places (/usr/local/...)

USAGE:
	pstack pid [...]

See the man page for more details.