[petsc-dev] Memory Logging Problem

[Jed Brown]

Lisandro Dalcin <dalcinl at gmail.com> writes:

> On 13 March 2016 at 04:21, Matthew Knepley <knepley at gmail.com> wrote:
>> You can fix the SEGV by moving the library unloading to after the malloc
>> dump. However,
>> it then records that the memory from loading the library is still unfreed.
>
> Or let's do it the Python way and never ever dlclose() dynamic libraries :-)

If I understand correctly, this would be no different from calling
dlclose after dealing with the malloc_dump.  And I think it's the right
solution because otherwise we have to copy __func__ instead of just
referencing it.  What is the "memory from loading the library"?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20160315/4975b0a7/attachment.sig>