Re: [Bug-readline] Readline fuzz testing

[Chet Ramey]

On 7/11/17 3:53 AM, Ben Wong wrote:
> I'm not sure where to find it on the web page, but you can page
> through the most recent changes using `git log -p` and find some
> patches that look like they might be relevant (e.g., char
> mb[MB_LEN_MAX] -> char mb[MB_LEN_MAX+1]:

The change logs are in the bash devel git tree; the original fuzzing
reports came in against bash (and I do readline development as part
of bash anyway).

> I can confirm that when I compile readline using the devel branch from
> Savannah, it fixes some, but not all, of the bugs I found. In
> particular, examples A & C seem to work, but if you try dataset B in
> my examples, it still triggers a memory allocation problem (heap usage
> after free).

I can't reproduce this on Mac OS X, using clang and asan (though it does
turn my Terminal window an attractive shade of royal blue for the
duration of its run).

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/