Upgrading to mpich2-1.4 seems to have fixed this problem. <div><br></div><div>Thanks,</div><div>Edgar<br><br><div class="gmail_quote">On Tue, Aug 16, 2011 at 9:54 AM, Edgar Solomonik <span dir="ltr"><<a href="mailto:solomon@eecs.berkeley.edu">solomon@eecs.berkeley.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello,<div><br></div><div>After upgrading my system from Ubuntu 10.10 to 11.04 I am experiencing difficulties running mpi with valgrind. The upgrade seemed to have deleted libcr-dev, which I reinstalled.</div>
<div><br></div>
<div>However, even after building clean versions of mpich2-1.3.1 and valgrind 3.6.1, I still get the following error, when running mpirun -np 4 valgrind ./app</div><div><br></div><div><div>cr_libinit.c:183 cri_init: sigaction() failed: Invalid argument</div>
</div><div><br></div><div>I am not sure if I have a bad libcr. Or perhaps a later version of mpich2 is using check point restart as well as valgrind and cri_init is not re-entrant.</div><div><br></div><div>Any help with this problem would be appreciated. Including any different approach for doing memory corruption/leak debugging when running an app with mpich2-1.3.1.</div>
<div><br></div><div>Thanks,</div><div>Edgar</div>
</blockquote></div><br></div>