Can you get a stack trace? Does this happen on a different machine? Should we turn off signal handling when running in valgrind? On Apr 17, 2013 6:42 AM, "Dominik Szczerba" <dominik at itis.ethz.ch> wrote:
> I have been successfully using valgrind for a long long time with petsc > but now suddenly it refuses to work. E.g. calling up a properly functioning > program causes a crash: > > mpiexec -n 2 valgrind --tool=memcheck -q --num-callers=20 MySolver > > cr_libinit.c:183 cri_init: sigaction() failed: Invalid argument > cr_libinit.c:183 cri_init: sigaction() failed: Invalid argument > > > ===================================================================================== > = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES > = EXIT CODE: 134 > = CLEANING UP REMAINING PROCESSES > = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES > > ===================================================================================== > APPLICATION TERMINATED WITH THE EXIT STRING: Aborted (signal 6) > > Same problem if I run without mpiexec at all, just on one proc. > > Google found just one and only related page on valgrind pages but I was > not able to conclude much. Did anyone else experience the same problem? > > Thanks, > Dominik > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20130417/5aeeadd9/attachment.html>
