robotux
/
pstack
1
0
Fork 0
Code Issues Pull Requests Releases Activity
Print a stack trace of running processes
8 Commits 1 Branch 1 Tag 100 KiB
C 84.9%
Roff 8.7%
Makefile 6.4%
Go to file
Thomas Preud'homme 0125e45595 Port pstack to amd64 architecture 
This patch is an effort to port pstack to other architectures. So far
only amd64 is supported and there is probably still some issues in the
architecture independant code (endianness, integer range, per
architecture frame browsing, …).
 		2011-09-10 23:46:17 +02:00
man1 Initial commit (pstack v1.2) 2011-08-18 17:18:25 +02:00
.cvsignore Initial commit (pstack v1.2) 2011-08-18 17:18:25 +02:00
COPYING Initial commit (pstack v1.2) 2011-08-18 17:18:25 +02:00
Makefile Remove pstack unconditionally in clean target. 2011-09-10 23:45:38 +02:00
README Initial commit (pstack v1.2) 2011-08-18 17:18:25 +02:00
VERSION Initial commit (pstack v1.2) 2011-08-18 17:18:25 +02:00
pstack.c Port pstack to amd64 architecture 2011-09-10 23:46:17 +02:00
pstack.spec Initial commit (pstack v1.2) 2011-08-18 17:18:25 +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.