[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-readline] Memory leak in readline using alternate interface

From: Chet Ramey
Subject: Re: [Bug-readline] Memory leak in readline using alternate interface
Date: Thu, 02 May 2013 09:01:59 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5

On 5/2/13 3:29 AM, Dido Sevilla wrote:
> While attempting to make use of the readline alternate interface, I found
> what looks like a memory leak in Readline 6.2-8 (Ubuntu 12.04) when run
> under valgrind. I don't know if this is because I am using
> rl_callback_read_char() and friends improperly or if this really is a
> problem with readline. I hope it is the former, and if so I would
> appreciate the correct usage of the interface, on which documentation seems
> to be very scant. I have attached a C program that illustrates my usage of
> readline's interface, and while it works correctly as far as the interface
> is concerned, whenever I attempt to use Ctrl-R to do a reverse isearch
> valgrind notices the following memory leak report after I quit. The memory
> leak does not appear if I do not attempt to search the history.

Thanks for the report.  This was fixed last year and is in the bash and
readline development git trees on savannah.  In fact, the whole
rl_message() implementation has changed pretty significantly since


``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/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]