[BProc] Valgrind and BProc (again)

[Julian S. <ju...@va...>]

Valgrind is a GPL'd tool suite for doing memory debugging and profiling
on x86-linux and amd64-linux.  We are looking into the issue of making
Valgrind work well on BProc and hence on MPI.

I'd like to re-ask Ceri's question: has anyone used or tried to use 
Valgrind over BProc?  If so, what did you have to do to make it work?

Thanks,

J

> From: Cerion Armour-Brown <cerion@op...>
> Subject: valgrind & bproc   
> Date: 2005-05-30 01:40 
>   Hi,
> I"m a developer working on Valgrind, and I"m trying to work out the best way 
> to use valgrind with bproc.
>
> Does anyone already do this?  (Directly with bproc - not via mpi).
> If so, I"d really appreciate some details on how you"ve set this up.
> 
> I understand that using valgrind with mpirun is fairly straightforward 
>(though 
> I haven"t set up mpi yet to try it out).  From what I"ve read, it seems 
> valgrind must be accessible from the nodes (nfs, or whatever), but the 
> program to run is migrated from the master, yes?
> 
> Using bpsh, I don"t see how I can avoid needing both valgrind, and the 
>program 
> to run, accessible from the nodes, since running
> $ bpsh -a valgrind foo
> will migrate valgrind, then, on the nodes, valgrind will look for foo.
> Valgrind is unlike gdb in that you cannot "attach" it once the program has 
> started.  So the trick used for gdb (bpsh -a foo, find foo"s pid, attach 
>gdb) 
> won"t work.
> 
> Any pointers much appreciated,
> Cerion