On 11/27/14 1:25 PM, Andreas Grapentin wrote:
> valgrind will probably claim that these blocks are still reachable at
> program exit, but that is beside the point. I am not claiming that
> readline leaks memory, I claim that the unfreed allocations at exit
> produce noise that makes it harder to find real memory leaks.
I think it's easy enough to tell the difference between memory that
valgrind reports as leaked and blocks it reports as still reachable.
I've used valgrind pretty extensively and I've never had that trouble.
> IMO, it would be nice to have a rl_finalize() function, that explicitly
> releases the resources held by the library.
If someone wants to take a shot at writing one, I'd be happy to look
at it.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU [email protected] http://cnswww.cns.cwru.edu/~chet/
_______________________________________________
Bug-readline mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-readline
