robotux
/
pstack
1
0
Fork 0
Code Issues Pull Requests Releases Activity
Print a stack trace of running processes
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1 Commit
1 Branch
1 Tag
100 KiB
 
 
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '35824dbd12'
${ noResults }
Go to file
Thomas Preud'homme 35824dbd12
Initial commit (pstack v1.2) 		12 years ago
man1 Initial commit (pstack v1.2) 12 years ago
.cvsignore Initial commit (pstack v1.2) 12 years ago
COPYING Initial commit (pstack v1.2) 12 years ago
Makefile Initial commit (pstack v1.2) 12 years ago
README Initial commit (pstack v1.2) 12 years ago
VERSION Initial commit (pstack v1.2) 12 years ago
pstack.c Initial commit (pstack v1.2) 12 years ago
pstack.spec Initial commit (pstack v1.2) 12 years ago

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.