Possibly something not getting properly inlined and creating multiple symbols?

Can you try the libmesh.automake branch?

-Ben

On Apr 17, 2012, at 10:47 AM, "John Peterson" <jwpeter...@gmail.com> wrote:

> Hi,
> 
> We're hitting the following error (in libmesh_cast_ptr) under Xcode 4.3 on 
> Lion.
> 
> Failed to convert N7libMesh13NumericVectorIdEE pointer to
> PKN7libMesh11PetscVectorIdEE
> The N7libMesh13NumericVectorIdEE appears to be a N7libMesh11PetscVectorIdEE
> 
> The full backtrace for this error is below, it arises from a call to
> PetscVector::operator= in our local code, all the libmesh examples
> seem to run fine however.
> 
> I'm wondering if anyone can elaborate on the difference between the
> two types listed?
> 
> PKN7libMesh11PetscVectorIdEE
> N7libMesh11PetscVectorIdEE
> 
> The only difference is the "PK", does this mean anything to anyone?
> 
> The same code works fine on OSX Lion with an older Xcode.
> 
> -- 
> John
> 
> 
> 
> 
> 
> 
> [0] /Users/moose/projects/trunk/libmesh/include/base/libmesh_common.h,
> line 356, compiled Apr 16 2012 at 14:55:52
> terminate called throwing an exception
> Program received signal SIGABRT, Aborted.
> 0x00007fff8b3a782a in __kill ()
> (gdb) bt
> #0  0x00007fff8b3a782a in __kill ()
> #1  0x00007fff873f9a9c in abort ()
> #2  0x00007fff8e7c47bc in abort_message ()
> #3  0x00007fff8e7c1fcf in default_terminate ()
> #4  0x00007fff8e7c2001 in safe_handler_caller ()
> #5  0x00007fff8e7c205c in std::terminate ()
> #6  0x00007fff8e7c3152 in __cxa_throw ()
> #7  0x0000000101109461 in
> libMesh::libmesh_cast_ptr<libMesh::PetscVector<double> const*,
> libMesh::NumericVector<double> const> (oldvar=0xec60)
>   at libmesh_common.h:356
> #8  0x0000000101102568 in libMesh::PetscVector<double>::operator=
> (this=0x1021304d0, v_in=@0xec60) at petsc_vector.C:582
> #9  0x0000000101105ffb in libMesh::PetscVector<double>::localize
> (this=0x102130420, v_local_in=@0x6, send_list=@0x100aaf6d0) at
> petsc_vector.C:784
> #10 0x000000010089cb33 in
> SystemTempl<libMesh::TransientSystem<libMesh::NonlinearImplicitSystem>
>> ::update ()
>   at /Users/moose/projects/trunk/moose/include/base/SystemBase.h:1574
> #11 0x000000010089cb33 in FEProblem::init2 (this=0x102845600) at
> FEProblem.C:1574
> #12 0x000000010089d26e in FEProblem::init (this=0x102845600) at 
> FEProblem.C:1565
> #13 0x000000010082d6be in ActionWarehouse::executeAllActions
> (this=0xec60) at ActionWarehouse.C:241
> #14 0x00000001009874f3 in Parser::execute (this=0x7fff5fbff708) at 
> Parser.C:636
> #15 0x0000000100045bce in main (argc=6, argv=0x0) at main.C:33
> 
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second 
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Libmesh-devel mailing list
> Libmesh-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libmesh-devel

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to