<br><br><div class="gmail_quote">On Wed, Jul 1, 2009 at 10:35 AM, Rob Latham <span dir="ltr"><<a href="mailto:robl@mcs.anl.gov">robl@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Tue, Jun 30, 2009 at 08:31:10PM -0400, Shawn Kim wrote:<br>
> Hi,<br>
><br>
> I installed PVFS-2.8.1 and MPICH2-1.1 correctly (I believe).<br>
><br>
> MPICH2 configuration options:<br>
><br>
> $ ./configure --enable-romio --enable-threads=multiple --enable-debuginfo<br>
> --enable-g=dbg --prefix=$MYHOME/mpich2-install/<br>
> --with-pvfs2=$MYHOME/pvfs-2.8.1 --with-file-system=ufs+nfs+pvfs2 |& tee<br>
> c.txt<br>
><br>
> I could compile mpich2-1.1 with the above option successfully, but whenever<br>
> I try to run a sample program, errors occured.<br>
><br>
> $mpirun -n 2 mpi-io-test<br>
> rank 1 in job 3 aum10.cse.psu.edu_41952 caused collective abort of all<br>
> ranks<br>
> exit status of rank 1: killed by signal 9<br>
> rank 0 in job 3 aum10.cse.psu.edu_41952 caused collective abort of all<br>
> ranks<br>
> exit status of rank 0: killed by signal 4<br>
><br>
> Is there anybody who know this error?<br>
<br>
</div>I know of no reason why pvfs-2.8.1 and mpich2-1.1 should fail to work.<br>
Did you get a core file from those signals? Can you post a stack<br>
trace?<br>
<div class="im"></div></blockquote><div><br>I am afraid not. Because of urgency I installed mpich2-1.0.8p1 and pvfs-2.8.1 and both work fine. Also both configure options are fine. I suspect that valgrind has a issue.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br>
> In addition, I couldn't compile with the following option. I mean I could<br>
> finish "./configure" successfully, but when make, error happened. The only<br>
> difference is "--enable-g=all" instead of "--enable-debuginfo --enable-g=dbg<br>
> "<br>
><br>
> $ ./configure --prefix=$MYHOME/mpich2-install/<br>
> --with-pvfs2=$MYHOME/pvfs-2.8.1 --enable-romio --enable-threads=multiple<br>
> --with-file-system=nfs+ufs+pvfs2 --enable-g=all |& tee c.txt**<br>
><br>
> Error message:<br>
> $ make<br>
> ~~~~<br>
><br>
> ../../../../../lib/libmpich.a(trmem.o)(.text+0x24c): In function<br>
> `MPIU_trvalid_unsafe':<br>
><br>
> /home/mdl/seokim/mpich2-1.1+pvfs-2.8.1/mpich2-1.1/src/util/mem/trmem.c:523:<br>
> undefined reference to `VALGRIND_MAKE_MEM_NOACCESS'<br>
<br>
</div>I'll let the other MPICH2 folks weigh in on that one. Typically those<br>
trmem warnings kick in when you call malloc/calloc/realloc/free<br>
directly instead of through the memory management wrappers.<br>
<br>
==rob<br>
<font color="#888888"><br>
--<br>
Rob Latham<br>
Mathematics and Computer Science Division<br>
Argonne National Lab, IL USA<br>
</font></blockquote></div><br>