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

2013-02-13 Thread Andreas Schwab
k...@freefriends.org (Karl Berry) writes: However, I can't see what it's complaining about. That line in tag.c is while ((p = input + strlen (input)) endp) /* go forward to null */ and I fail to see anything uninitialized about it. Any ideas, anyone? There is no garantee that input is

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

2013-02-13 Thread Sergey Poznyakoff
Andreas Schwab sch...@linux-m68k.org ha escrit: There is no garantee that input is zero-terminated. Fixed that too. Thanks a lot! Regards, Sergey

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

2013-02-13 Thread Norbert Preining
Hi Segey, On Mi, 13 Feb 2013, Sergey Poznyakoff wrote: Sergey, if you have a chance to try to track it down Sure, I've fixed it. Great, thanks. Norbert PREINING, Norbert

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

2013-02-12 Thread Karl Berry
$ echo $LINES $COLUMNS 64 208 Start info with the make info file from make-doc 3.81-5.1: $ info make Enter these keystrokes: i p TAB TAB Result: segfault. I can reproduce this, even without all the special compiler flags (-g only).

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

2013-02-12 Thread 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