Menu
▾
▴
Re: [Libmesh-users] crash in example 10
|
From: Michael P. <pov...@in...> - 2005-06-24 11:05:30
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#cccccc">
Dear all,<br>
we menage to solve the problem by using GNU Fortran instead of Intel v.
8.0.<br>
Thank you for help,<br>
Michael.<br>
<br>
KIRK, BENJAMIN (JSC-EG) (NASA) wrote:<br>
<blockquote type="cite"
cite="mid...@js...">
<title>Message</title>
<div><span> I'm back at work and now have access to my petsc-2.3.0
build... </span></div>
<div><span> </span> </div>
<div><span> Here is how I configured petsc: </span></div>
<div><span> </span> </div>
<div><span> ./config/configure.py </span><span> --with-cc=gcc
--with-cxx=g++ --with-fc=g77
--with-blas-lapack-dir=/software/ia32/intel/mkl-7.0
--with-mpi-dir=/software/ia32/mpi/mpich-1.2.6-gcc --with-debugging=0
--with-shared=1 --useThreads=0 </span></div>
<div><span> </span> </div>
<div><span> (Note that --useThreads=0 is automatically set on RH9
machines by the PETSc configuration script due to a known issue.
Perhaps you are suffering from this issue? Maybe you need
--useThreads=0 on your platform as well? BTW, what platform are you
on?) </span></div>
<div><span> </span> </div>
<div><span> Beyond that, I have tested libMesh-0.5.0/PETSc-2.3.0 with
gcc-4.0.0 and gcc-3.4.3 on a Fedora Core 3 machine, and ex10 runs with
no issue. </span></div>
<div><span> </span> </div>
<div><span> Is both PETSc and libMesh built with the same compiler?
Are there any special flags you are passing ./configure for libmesh? </span></div>
<div><span> </span> </div>
<div><span> In any case, I would suspect something is amiss with
PETSc. The library is primarily developed under gcc, and portability
is maintained by testing with a number of compilers. I seriously doubt
this is a compiler issue, but rather too many libraries not *quite*
working together. </span></div>
<div><span> </span> </div>
<div><span> Looking forward to solving this problem... </span></div>
<div><span> </span> </div>
<div><span> -Ben </span></div>
<div><span> </span> </div>
<div><span> </span> </div>
<blockquote>
<div lang="en-us"> -----Original Message-----<br>
<b>From:</b> <a class="moz-txt-link-abbreviated" href="mailto:lib...@li...">lib...@li...</a>
[<a class="moz-txt-link-freetext" href="mailto:lib...@li...">mailto:lib...@li...</a>] <b>On Behalf Of </b>Michael
Povolotskyi<br>
<b>Sent:</b> Friday, June 17, 2005 4:49 AM<br>
<b>To:</b> John Peterson<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:Lib...@li...">Lib...@li...</a><br>
<b>Subject:</b> Re: [Libmesh-users] crash in example 10<br>
<br>
</div>
Hi John,<br>
so far we didn't make any progress.<br>
<br>
I'd like to know how do you configure PETSc?<br>
Which fortran compiler and libraries are used?<br>
<br>
Michael.<br>
<br>
<br>
John Peterson wrote:<br>
<blockquote cite="mid...@ar..."
type="cite">
<pre>Hi Michael,
> Hi John,<br>
> we found that there are two "ways" to make it work:<br>
> 1) subsititute dynamic_cast by static_cast:<br>
I imagine this is only working by chance, since as far as I
know static_cast<> is equivalent to the old C-style cast, and
does not take into account class hierarchies like dynamic_cast.
I was also under the impression that dynamic_cast returned a NULL
pointer upon failure (thus the reason for checking rhs_elem
against NULL and returning false upon failure) In case the
cast *is* failing and *is not* returning a NULL pointer, then that
could definitely cause the code to crash...
Does anything happen if you change the if-test to the following?
// If we cannot cast to an Elem*, rhs must be a Node
if (rhs_elem == static_cast<const Elem*>(NULL))
return false;
> 2) disable PETSc :)
Well that is just plain weird, I have never seen something like
that before!
> Do you think that it may be related to the version of PETSc or to the
> C++ compiler version?<br>
I doubt it's related to PETSc since we have successfully run the
examples in 2.3.0 before. The only thing I haven't tried seems to be
GCC-3.4.3, which is apparently a bug-fix for 3.4.2...
If you are feeling adventurous, you might try building
libmesh (and petsc) with GCC-4.0.0 as well and seeing if the segfault
just goes away.
-John
P.S. One other thing I might be concerned with is what happens with
dynamic_cast in the presence of multiple inheritance. An Elem is
multiply inherited from DofObject and ReferenceCountedObject, but I've
never heard bug reports about something like that. In any case, what
happens if you make the destructor for ReferenceCountedObject virtual?
Probably nothing, but I did read somewhere that any class which is
inherited from should have a virtual dtor.
</pre>
</blockquote>
<br>
<br>
<pre>--
------------------------------------------------------------
Michael Povolotskyi, Ph.D.
University of Rome "Tor Vergata"
Department of Electronic Engineering
Viale Politecnico, 1 - 00133 Rome - Italy
Phone + 39 06 72597367
Fax + 39 06 2020519
<a href="http://www.optolab.uniroma2.it/pages/moshe/moshe.html">http://www.optolab.uniroma2.it/pages/moshe/moshe.html</a>
-------------------------------------------------------------
</pre>
------------------------------------------------------- SF.Net email is
sponsored by: Discover Easy Linux Migration Strategies from IBM. Find
simple to follow Roadmaps, straightforward articles, informative
Webcasts and more! Get everything you need to get up to speed, fast.
<a class="moz-txt-link-freetext" href="http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click">http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click</a>
_______________________________________________ Libmesh-users mailing
list <a class="moz-txt-link-abbreviated" href="mailto:Lib...@li...">Lib...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/libmesh-users">https://lists.sourceforge.net/lists/listinfo/libmesh-users</a></blockquote>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="250">--
------------------------------------------------------------
Michael Povolotskyi, Ph.D.
University of Rome "Tor Vergata"
Department of Electronic Engineering
Viale Politecnico, 1 - 00133 Rome - Italy
Phone + 39 06 72597367
Fax + 39 06 2020519
<a class="moz-txt-link-freetext" href="http://www.optolab.uniroma2.it/pages/moshe/moshe.html">http://www.optolab.uniroma2.it/pages/moshe/moshe.html</a>
-------------------------------------------------------------
</pre>
</body>
</html>
|