On Wed, Apr 15, 2009 at 6:41 AM, Nicholas Nethercote
wrote:
>
> It's almost certainly caused by heap corruption due to the errors
> Valgrind reports about your program. If you fix those, this crash
> will almost certainly go away.
I just clarified the abort/crash message, making this possibility
Hi graham
Are you sure that all libraries needed by valgrind are accessible
on all your nodes? If it is Open MPIy wrote:
> On Wed, Apr 15, 2009 at 6:31 AM, Graham Mark wrote:
>>
>> I'm trying to track down the cause of a seg fault in my MPI program.
>> Here's what happens with valgrind.
>>
>> % m
On Wed, Apr 15, 2009 at 6:31 AM, Graham Mark wrote:
>
> I'm trying to track down the cause of a seg fault in my MPI program.
> Here's what happens with valgrind.
>
> % mpirun -n 27 ../../valgrind-3.4.1/bin/valgrind --kernel-
> variant=bproc mc3_op
> ERROR: ld.so: object '/usr/projects/dark/gam/val
I'm trying to track down the cause of a seg fault in my MPI program.
Here's what happens with valgrind.
% mpirun -n 27 ../../valgrind-3.4.1/bin/valgrind --kernel-
variant=bproc mc3_op
ERROR: ld.so: object '/usr/projects/dark/gam/valgrind/amd64-linux/
libmpiwrap.so' from LD_PRELOAD cannot be p
