Re: Bug#700354: info: segfault on tab completion on large terminals

[Sergey Poznyakoff]

Hi,

> Sergey, if you have a chance to try to track it down

Sure, I've fixed it.

> P.S. Independent of all these settings and input, valgrind reports:
> 
> ==5435== Conditional jump or move depends on uninitialised value(s)
> ==5435==    at 0x4006A97: strlen (mc_replace_strmem.c:275)

That looks rather a valgrind quirk.  All values are definitely
initialized.  From the formal point of view, endp may point to
uninitialized memory, but the C standard explicitly allows that.

Regards,
Sergey