Christian Brabandt wrote:
> On Di, 14 Feb 2017, Dominique Pellé wrote:
>
> > Hi
> >
> > afl-fuzz found another command that causes access to
> > invalid memory in Vim-8.0.329. It's not a recent regression
> > since bug is present in at least Vim-7.4.52 that comes
> > with ubuntu-14.04.
> >
>
On Mi, 15 Feb 2017, Dominique Pellé wrote:
> Christian Brabandt wrote:
> > On Di, 14 Feb 2017, Dominique Pellé wrote:
> Your patch appears to fix the valgrind error.
> However, it's not correct. If I do...
>
> $ echo "foo bar" | vim -u NONE -c'norm wvapo' -
>
> ... then pressing o multiple
Christian Brabandt wrote:
> Hi Dominique!
>
> On Di, 14 Feb 2017, Dominique Pellé wrote:
>
>> Hi
>>
>> afl-fuzz found another command that causes access to
>> invalid memory in Vim-8.0.329. It's not a recent regression
>> since bug is present in at least Vim-7.4.52 that comes
>> with
Hi Dominique!
On Di, 14 Feb 2017, Dominique Pellé wrote:
> Hi
>
> afl-fuzz found another command that causes access to
> invalid memory in Vim-8.0.329. It's not a recent regression
> since bug is present in at least Vim-7.4.52 that comes
> with ubuntu-14.04.
>
> I have not been able to find a
Hi
afl-fuzz found another command that causes access to
invalid memory in Vim-8.0.329. It's not a recent regression
since bug is present in at least Vim-7.4.52 that comes
with ubuntu-14.04.
I have not been able to find a fix yet.
Step to reproduce:
$ valgrind vim -u NONE -c'norm oxx' -c'norm