Charm++ parallel programming system

["Gunter, David O" <dog AT lanl.gov>]

Has anyone ever used Allinea’s DDT or the Totalview debugger to examine 
memory issues in the charm++ package?

We have a code that hits a memory error 40 iterations into a calculation and 
we cannot figure out what is causing it.  To make matters worse, this is on a 
Cray XC system where we are building things statically.

Each of those debuggers requires one to link codes to instrumented malloc 
libraries before running the code. I build charm++ like this (DDT example):

charm++ gni-crayxc persistent smp -j8 --no-build-shared -L$DDTROOT/lib/64 
-ldmallocthcxx -Wl,--allow-multiple-definition -g -O0

and that seems to build a correct charm++ environment.  However, the code 
that is then built with charm++ will launch but hang at the first call to new 
(malloc), so we cannot even advance to the point where the real bug occurs.

I’m just curious if anyone else as ever done anything like this and if so, 
how?

Thanks,
david
--
David Gunter
HPC-5: Applications Readiness Team