MUTRACE Mutex Tracer
GIT:
git://git.0pointer.de/mutrace.git
GITWEB:
http://git.0pointer.de/?p=mutrace.git
INSTALLATION:
sudo apt-get install shtool autotools-dev binutils-dev
aclocal
libtoolize
autoheader
autoconf
automake --add-missing --foreign
./configure
make
sudo make install
HINTS FOR INSTALLATION:
If many dependencies are missing when running ./configure, I recommend installing auto-apt. It will monitor ./configure and install packages on the fly!
sudo apt-get install auto-apt
sudo auto-apt update
sudo auto-apt updatedb && sudo auto-apt update-local
sudo auto-apt run ./configure
In case of missing header files when running make, a useful tool is apt-file:
sudo apt-get install apt-file
sudo apt-file update
apt-file search <missing-file>
After installing the package you might need to rerun ./configure before running make.
TROUBLESHOOTING INSTALLATION:
In case of this error:
backtrace-symbols.c:53:23: fatal error: libiberty.h: No such file or directory
#include <libiberty.h>
you might need to change this line to:
#include <libiberty/libiberty.h>
In case of huge amount of error that start with:
/usr/include/libiberty/libiberty.h:110:38: error: expected declaration specifiers before 'ATTRIBUTE_RETURNS_NONNULL'
extern char *basename (const char *) ATTRIBUTE_RETURNS_NONNULL ATTRIBUTE_NONNULL(1);
you probably have 2 files ansidecl.h which differ.
E.g. those:
/usr/include/ansidecl.h
/usr/include/libiberty/ansidecl.h
You should use the latter. To do this, rename the former and link to the later instead:
sudo mv /usr/include/ansidecl.h /usr/include/ansidecl.h.tmp
sudo ln -s /usr/include/libiberty/ansidecl.h /usr/include/ansidecl.h
make
When the compilation is successful, revert it by running:
sudo rm /usr/include/ansidecl.h
sudo mv /usr/include/ansidecl.h.tmp /usr/include/ansidecl.h
USAGE:
LD_PRELOAD=/usr/local/lib/libmutrace.so <your program>
NOTES:
For a terse overview what mutrace can do for you, please read
the announcement blog story:
http://0pointer.de/blog/projects/mutrace.html
The tarball includes two profilers:
mutrace profiles lock contention for you. Just use it as
prefix for your usual command line and it will profile
mutexes used in all child processes. Example:
mutrace gedit
matrace traces memory allocation operations in realtime
threads for you. It is of no use in applications that do not
make use of realtime scheduling. Example:
matrace myrealtimetool
Both tools understand a --debug-info switch in which case the
backtraces generated will include debugging information such as
line numbers and source file names. This is not enabled by
default since generating those traces is not always safe in
situations where locks are taken or memory allocated as we do
it here. YMMV.
mutrace cannot be used to profile glibc-internal mutexes.
LICENSE:
LGPLv3+
Exception:
backtrace-symbols.c is GPLv2+. Which probably means that using
the --debug-info switch for mutrace and matrace might not be
legally safe for non-GPL-compatible applications. However,
since that module is independantly built into a seperate .so
it should still be safe using the profilers without this
switch on such software.
AUTHORS:
Lennart Poettering
REQUIREMENTS:
Recent gcc, glibc, Linux