On May 14, 2009, at 10:11 AM, Valmor de Almeida wrote:
> This sounds like memory badness is occurring somewhere in your
> application which eventually corrupts things to make them stop
working
> (e.g., writing beyond the end of arrays, etc.). Have you run your
app
> through a memory-checking debugger, perchance?
>
I have the compiler flag for array bounds checking turned on. Is this
sufficient?
Probably not; there are many different kinds of memory corruption.
I have not used a debugger for this purpose. Would gdb do it with mpi?
Try valgrind.
--
Jeff Squyres
Cisco Systems
