Re: [BProc] Valgrind and BProc (again)

[Greg W. <gw...@la...>]

On Jun 20, 2005, at 9:50 AM, Julian Seward wrote:

>
>
>> OpenMPI developers who have a very similar problem.
>> [...]
>> The basic problem is the need to get two (or more)
>> executables onto a node in such a way as they know about each other,
>>
>
> Yes.  Just to be clear, what we need to get onto the nodes is:
>
> * executable to be debugged
> * valgrind stage 1 executable, which is really a loader for
> * valgrind stage 2 executable
>
> * a bunch of .so's.  These we dlopen, so am not sure if the standard
>   BProc library mechanism takes care of it or not.
>
> * a bunch of pre-supplied text files ("suppressions")
>   which tell V to hide errors from standard libraries.  Identity of
>   these files are known at the time V is built/installed.
>
> * possibly extra such files as supplied by the application's
>   developers.  Their identity is not known until V starts up.
>
> I wasn't aware of the no-exec-on-nodes restriction, although that
> isn't a big deal for us -- V uses its own user-space exec
> implementation.

To clarify, you can exec an executable that is local to the node. In  
bproc 3 and earlier you could give exec a full path name and it would  
automatically load it from the front end if it wasn't found on the  
node. This no longer works in bproc 4.

Greg