Re: [OMPI users] Segfault when using valgrind

2009-07-09 Thread Justin Luitjens
I was able to get rid of the segfaults/invalid reads by disabling the shared memory path. They still reported an error with uninitialized memory in the same spot which I believe is due to the struct being padded for alignment. I added a supression and was able to get past this part just fine.

Re: [OMPI users] Segfault when using valgrind

2009-07-09 Thread Jeff Squyres
On Jul 7, 2009, at 11:47 AM, Justin wrote: (Sorry if this is posted twice, I sent the same email yesterday but it never appeared on the list). Sorry for the delay in replying. FWIW, I got your original message as well. Hi, I am attempting to debug a memory corruption in an mpi program

[OMPI users] Segfault when using valgrind

2009-07-07 Thread Justin
(Sorry if this is posted twice, I sent the same email yesterday but it never appeared on the list). Hi, I am attempting to debug a memory corruption in an mpi program using valgrind. However, when I run with valgrind I get semi-random segfaults and valgrind messages with the openmpi

[OMPI users] Segfault when using valgrind

2009-07-06 Thread Justin Luitjens
Hi, I am attempting to debug a memory corruption in an mpi program using valgrind. Howver, when I run with valgrind I get semi-random segfaults and valgrind messages with the openmpi library. Here is an example of such a seg fault: ==6153== ==6153== Invalid read of size 8 ==6153==at