:( that's all I see. Do you mean running with -on_error_attach_debugger? On Mon, Apr 9, 2012 at 7:29 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
> Always send the whole error message. If this is all you see, then > something is misbehaving and you'll have to catch the message in a debugger. > > > On Mon, Apr 9, 2012 at 20:10, Mohammad Mirzadeh <mirzadeh at gmail.com>wrote: > >> Hi, >> >> I have this strange behavior that sometimes when I run the code on >> certain number of processors and for a certain problem size, I get a >> message like: >> >> "key # not found!" >> >> where # is just some number (like 9087 but changes every time I run it). >> Is there something wrong with my MPI? is this even an MPI message or >> something else? Sorry my question is this broad, but I have no clue where >> this message is popping from! PETSc does not produce any error message when >> this happens and the code is valgrind clean. >> >> I'd appreciate any input. >> Thanks >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20120409/29abaee5/attachment.htm>
