Hum … thanks, the error was somewhere else in my code, in a part not necessarily linked with libMesh or smart pointers, but using the point_locator avoids a memory leak.
Just one thing, if I understood correctly the point_locator() method is deprecated. So, it’ll be removed in a future version of libMesh, no? Thiago > On 11 Feb 2016, at 17:48, John Peterson <jwpeter...@gmail.com> wrote: > > > > On Thu, Feb 11, 2016 at 7:44 AM, Thiago Milanetto Schlittler > <thiago...@gmail.com <mailto:thiago...@gmail.com>> wrote: > Hello! > > Sorry for the delay, I was away for some days. > > The initializer is due to an error - I tried to use a common pointer > instead of the UniquePtr, and forgot to remove it. Unfortunately, removing it > doesn’t fix the problem. > > No, I didn’t configure libMesh with --enable-unique-ptr. I exchanged the > libMesh::UniquePtr<...> for a (deprecated) libMesh::AutoPtr<…>, just to test, > but I still got the same error as before. I’ll recompile libMesh with this > option, to see if it solves the problem. For what is worth, I’m using the > 1.0.0pre version. > > A better overall approach might be to just use the PointLocator provided by > the Mesh. You can get a reference to it in the constructor of your class by > calling: > > alpha_mesh.point_locator() > > Then you don't have to deal with any kind of smart pointers. > > -- > John ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
