I debuged ex0-dbg in example 1.
Error generates at line 164 of libmesh.C: MPI_Init(&argc, &argv);

Internal Error: invalid error code bffbed80 (Ring Index out of range) in
MPIR_Init_thread:294
Program received signal SIGSEGV, Segmentation fault.
0xb5c5a27b in strlen () from /lib/tls/i686/cmov/libc.so.6

2008/8/4 Shengli Xu <[EMAIL PROTECTED]>

> Ben, Roy, John
>
> cpi.c can be built with mpicxx.
>
> Use ./configure --enable-vtk=no --with-f77=gfortran --with-cc=gcc
> --with-cxx=g++
> make is ok.
> But when run make run_examples:
>
> [EMAIL PROTECTED]:~/code/svn_libmesh$ make run_examples
> make[1]: Entering directory `/home/xsl/code/svn_libmesh/examples'
> make[2]: Entering directory `/home/xsl/code/svn_libmesh/examples/ex0'
> Compiling C++ (in debug mode) ex0.C...
> Linking ex0-dbg...
> /home/xsl/code/svn_libmesh/contrib/tecplot/lib/i686-pc-linux-gnu/tecio.a(tecxxx.o):
> In function `tecini':tecxxx.c:(.text+0x1a7): warning: the use of `mktemp' is
> dangerous, better use `mkstemp'
> ***************************************************************
> * Running Example  ./ex0-dbg
> ***************************************************************
>
> Internal Error: invalid error code bfa07180 (Ring Index out of range) in
> MPIR_Init_thread:294
> p0_11204:  p4_error: interrupt SIGSEGV: 11
> make[2]: *** [run] Error 1
> make[2]: Leaving directory `/home/xsl/code/svn_libmesh/examples/ex0'
> make[1]: *** [run] Error 1
> make[1]: Leaving directory `/home/xsl/code/svn_libmesh/examples'
> make: *** [run_examples] Error 2
>
>
>
>
> 2008/8/3 John Peterson <[EMAIL PROTECTED]>
>
> On Sun, Aug 3, 2008 at 11:46 AM, Shengli Xu <[EMAIL PROTECTED]>
>> wrote:
>> > Roy,
>> >
>> > The example can be linked. But runns error:
>>
>> [snipped]
>>
>> Shengli,
>>
>> This problem has been discussed on the list before.  Search the archives
>> for Pb compilation or check this link:
>>
>>
>> http://sourceforge.net/mailarchive/message.php?msg_id=1AE8B9D6-F61A-4226-9C0B-1E26744372EA%40inria.fr
>>
>> I believe the problem has to do with the way PETSc is compiled.  Here is
>> my comment from that other thread.
>>
>> Note: when I attempted to compile PETSc with Fortran compilers,
>>>
>> none of the resulting executables would actually run.  The runtime
>>>
>> error message was
>>>
>>
>>   0 - <NO ERROR MESSAGE> : Could not convert index 12079072 into a pointer
>>>
>>   The index may be an incorrect argument.
>>>
>>   Possible sources of this problem are a missing "include 'mpif.h'",
>>>
>>   a misspelled MPI object (e.g., MPI_COM_WORLD instead of MPI_COMM_WORLD)
>>>
>>    or a misspelled user variable for an MPI object (e.g.,
>>>
>>   com instead of comm).
>>>
>>   [0]  Aborting program !
>>>
>>   [0] Aborting program!
>>>
>>   p0_84805:  p4_error: : 9039
>>>
>>
>>> And apparently has something to do with the MPI Fortran interface
>>>
>> storing pointers as type INTEGER, which works on 32-bit machines but
>>>
>> not 64.  This website appears to have more info:
>>>
>> http://www.pgroup.com/userforum/viewtopic.php?start=0&t=560
>>>
>>
>>
>>
>>
>> --
>> John
>>
>>
>
>
> --
> Shengli Xu
>



-- 
Shengli Xu
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to