Hmm, to be honest, I've never debugged a program using MPI, so I'm not completely sure what I need. For a seg. fault. what would you suspect I need? The model runs on one processor without problems right now.<div>
<br></div><div>For your latter comment, I suspect you're right. Right now I'm working on building MPICH and the models I need to run with GNU compilers.<br><br></div><div>Thanks.</div><div><br><div class="gmail_quote">
On Tue, Aug 30, 2011 at 12:09 PM, Dave Goodell <span dir="ltr"><<a href="mailto:goodell@mcs.anl.gov">goodell@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Do you just need debugging symbols or do you also need support for locating MPI processes and viewing MPI message queues with the Totalview debugger? Your configure options are asking for the additional MPI message queue debugging. If you simply need to be able to see debugging symbols in your debugger then you can configure instead with "--enable-g=dbg" or "CFLAGS=-g".<br>
<br>
Otherwise if you do need support for the special MPI debugging hooks then you'll need to build MPICH2 with gcc or some compiler that is capable of building shared libraries.<br>
<br>
-Dave<br>
<div><div></div><div class="h5"><br>
On Aug 30, 2011, at 10:27 AM CDT, Matthew Russell wrote:<br>
<br>
> Hi,<br>
><br>
> I'm having problems building MPICH2 with debugging symbols. I'm using OS X Lion on an 86x64 box using PGI 10.9 as my compiler.<br>
><br>
> As far as I can tell, the issue is that the builder wants me to use the flag -fpic to produce position independent code, but PGI doesn't support the -fpic flag for OS X on a 64 bit machine.<br>
><br>
> My problem is with ./src/mpi/debugger/dll_mpich2.c, specifically, here is the line the fails while i'm make'ing it.<br>
><br>
> /opt/pgi/osx86-64/10.9/bin/pgcc -fPIC -DHAVE_CONFIG_H -I. -I. -I../../include -I../../../src/include -O2 -Msignextend -V -g -DNDEBUG -DpgiFortran -I/Users/matt/software/mpich2/mpich2-1.4/src/mpl/include -I/Users/matt/software/mpich2/mpich2-1.4/src/mpl/include -I/Users/matt/software/mpich2/mpich2-1.4/src/openpa/src -I/Users/matt/software/mpich2/mpich2-1.4/src/openpa/src -I/Users/matt/software/mpich2/mpich2-1.4/src/mpid/ch3/include -I/Users/matt/software/mpich2/mpich2-1.4/src/mpid/ch3/include -I/Users/matt/software/mpich2/mpich2-1.4/src/mpid/common/datatype -I/Users/matt/software/mpich2/mpich2-1.4/src/mpid/common/datatype -I/Users/matt/software/mpich2/mpich2-1.4/src/mpid/common/locks -I/Users/matt/software/mpich2/mpich2-1.4/src/mpid/common/locks -I/Users/matt/software/mpich2/mpich2-1.4/src/mpid/ch3/channels/nemesis/include -I/Users/matt/software/mpich2/mpich2-1.4/src/mpid/ch3/channels/nemesis/include -I/Users/matt/software/mpich2/mpich2-1.4/src/mpid/ch3/channels/nemesis/n<br>
emesis/include -I/Users/matt/software/mpich2/mpich2-1.4/src/mpid/ch3/channels/nemesis/nemesis/include -I/Users/matt/software/mpich2/mpich2-1.4/src/mpid/ch3/channels/nemesis/nemesis/utils/monitor -I/Users/matt/software/mpich2/mpich2-1.4/src/mpid/ch3/channels/nemesis/nemesis/utils/monitor -I/Users/matt/software/mpich2/mpich2-1.4/src/util/wrappers -I/Users/matt/software/mpich2/mpich2-1.4/src/util/wrappers -g -c ./dll_mpich2.c -o _sdll_mpich2.o<br>
> pgcc-Error-Unknown switch: -fPIC<br>
><br>
> pgcc 10.9-0 64-bit target on Apple OS/X -tp nehalem-64<br>
> Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.<br>
> Copyright 2000-2010, STMicroelectronics, Inc. All Rights Reserved.<br>
> make[2]: *** [dll_mpich2.lo] Error 1<br>
> make[1]: *** [all-postamble] Error 2<br>
> make: *** [all-redirect] Error 2<br>
><br>
> My configuration options were:<br>
><br>
> ./configure --prefix=/usr/local/mpich2_pg-dbg --enable-f77 --enable-debuginfo --enable-error-messages=all --enable-g=all --enable-fast=none<br>
><br>
><br>
> Does any one know how I can get around this? I need the debug info, since the program I'm trying to run with MPICH (CMAQ) seg. faults. right away, and I don't know how else to debug it.<br>
><br>
> Note, with my installation (without debugging symbols), I can run all the sample programs on multiple processors, etc.<br>
><br>
> Thanks,<br>
</div></div>> _______________________________________________<br>
> mpich-discuss mailing list<br>
> <a href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a><br>
> <a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br>
<br>
_______________________________________________<br>
mpich-discuss mailing list<br>
<a href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a><br>
<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br>
</blockquote></div><br></div>