On Thu, Feb 11, 2016 at 10:46 AM, Thiago Milanetto Schlittler <
[email protected]> wrote:
> 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 under
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
On Thu, Feb 11, 2016 at 7:44 AM, Thiago Milanetto Schlittler <
[email protected]> 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,
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
On Thu, Feb 4, 2016 at 3:54 AM, Thiago Milanetto Schlittler <
[email protected]> wrote:
> Hello!
>
>I’m using a PointLocatorTree to determinate the values of a parameter
> over a mesh, and it’s causing a segmentation fault at the end of the
> program. I’m using it inside a class with the cod
Hello!
I’m using a PointLocatorTree to determinate the values of a parameter over a
mesh, and it’s causing a segmentation fault at the end of the program. I’m
using it inside a class with the code below:
class weight_parameter_function
{
protected:
// Members
libMesh::UniqueP
