On May 28, 2013, at 2:36 PM, Derek Gaston <fried...@gmail.com> wrote:
> Ben - are you saying I need to apply that patch? Has that patch been removed > - I thought that was still in there right now…. What is in there right now is // Construct singletons who may be at risk of the // "static initialization order fiasco" Singleton::setup(); // Make sure the construction worked libmesh_assert(remote_elem); You could try commenting-out the Singleton::setup() call and restore just the construction of the remote_elem (I think) because that is all that is actually required at the moment. But if there is something weird with linking going on, that may just shift the error. Bigger than MOOSE+libMesh, huh? Scary! -Ben ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
