Re: [BProc] Valgrind and BProc (again)

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

> > The intention is that the carried-around tree is small, as is indeed
> > V's install tree is (5.7 M).

That's -O -g; if we knock off the debug info it's about 2M.


> What about 'program'?
> Are you imagining this to be in valgrind's install tree?
> Else this would still have to be separately migrated, or on nfs, no?

Good point.  Uh, this is more complex than I thought.  

* 'program' does indeed need to be migrated too

* How will .../bin/valgrind know to start 'program' ?

* Very often, users want to supply their own suppressions
  files for Valgrind (--supp=filename on the command line)
  and that needs to be shunted across too

* How does all this work when starting stuff with mpirun
  rather than bpsh ?

* What if the valgrinded program on the nodes decides to
  start a child process which it wants valgrinded?

Hum.

J