It's great to hear that people are interested in mpiP!
Currently, I am configuring mpiP on x86_64 with gcc 3.4.4 with -O2 and
When running some simple tests, I'm having good luck using both mpiP
stack walking and libunwind when compiling with gcc and -O2. However,
it looks to me like compiling the mpiP library or an application with
-O3 will cause stack walking with the mpiP-implemented stack walking
code to segfault. If I configure mpiP to use libunwind and compile my
application with -O3, some libunwind calls fail and some MPI call sites
are not recorded. It looks to me like building and running with -O3
with the Intel compiler (v9.1) is successful.
At this point the work-around for gcc appears to be building with -O2.
Hopefully we can get this sorted out by the next mpiP release.
The issue that George points out with the failed address lookup could be
due either to not compiling with -g or with the version of binutils he
is using. I've successfully used binutils versions 2.15.92 and 2.16.1,
but have run into some issues with binutils-2.17.
We don't hear all that much from mpiP users, so if you run into annoying
issues with mpiP that you'd like sorted out or just have general
questions or comments about the tool, please let us know at