On Apr 22, 2011, at 9:02 AM, Roy Stogner wrote: > In particular we can see failed assertions (and probably crashes or > corruption) in multithreaded code that relys on the mesh-provided > point_locator() incorrectly: MeshFunction, PeriodicBoundaries, > ExactSolution/ExactErrorEstimator, and RBEIMSystem are likely > affected.
Thank god! We've known for a while now (like over a year) that PeriodicBoundaries didn't work with threading... but never had time to fully investigate! This could be it! > I'd like to change point_locator() to return an AutoPtr instead, an > API-incompatible change. The alternative would be to just deprecate > the existing function and create a new one with a different name. Any > preferences? Just change it. I'm sure there aren't _too_ many people using PointLocator... and we can easily change the few places we use it. Derek ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
