Re: [OMPI users] invalid write in opal_generic_simple_unpack

2012-03-14 Thread Jeffrey Squyres
On Mar 14, 2012, at 1:06 PM, Patrik Jonsson wrote: > I think I tracked it down, though. The problem was in the boost.mpi > [snip] Yuck! Glad you tracked it down. > I do have a more general question, though: Is there a good way to back > out the location of the request object if I stop deep in t

Re: [OMPI users] invalid write in opal_generic_simple_unpack

2012-03-14 Thread Patrik Jonsson
On Wed, Mar 14, 2012 at 3:43 PM, Jeffrey Squyres wrote: > On Mar 14, 2012, at 9:38 AM, Patrik Jonsson wrote: > >> I'm trying to track down a spurious segmentation fault that I'm >> getting with my MPI application. I tried using valgrind, and after >> suppressing the 25,000 errors in PMPI_Init_thre

Re: [OMPI users] invalid write in opal_generic_simple_unpack

2012-03-14 Thread Jeffrey Squyres
On Mar 14, 2012, at 9:38 AM, Patrik Jonsson wrote: > I'm trying to track down a spurious segmentation fault that I'm > getting with my MPI application. I tried using valgrind, and after > suppressing the 25,000 errors in PMPI_Init_thread and associated > Init/Finalize functions, I haven't looked

[OMPI users] invalid write in opal_generic_simple_unpack

2012-03-14 Thread Patrik Jonsson
Hi, I'm trying to track down a spurious segmentation fault that I'm getting with my MPI application. I tried using valgrind, and after suppressing the 25,000 errors in PMPI_Init_thread and associated Init/Finalize functions, I'm left with an uninitialized write in PMPI_Isend (which I saw is not un