[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-readline] unfreed memory allocated within rl_initialize
|
From: |
Chet Ramey |
|
Subject: |
Re: [Bug-readline] unfreed memory allocated within rl_initialize |
|
Date: |
Thu, 27 Nov 2014 13:17:56 -0500 |
|
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 |
On 11/27/14 6:58 AM, Andreas Grapentin wrote:
> Hello,
>
> I am currently trying to verify that an application of mine does not
> leak memory, and I noticed that the readline library does not free some
> allocations below the rl_initialize function.
This is not unexpected; there are data structures like keymaps that
readline allocates once the first time it is called and expects to
persist through all calls to readline() by a particular application.
What does a memory allocation profiler like valgrind say about where
the blocks were allocated and whether or not the library retains
pointers to those blocks?
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU address@hidden http://cnswww.cns.cwru.edu/~chet/