Re: [bug] vim-7.4.2305 crashes in bugIsChanged with NULL buf pointer

2016-09-03 Fir de Conversatie Bram Moolenaar
Dominique Pellé wrote: > I see that patch 7.4.2309 fixed it. Thanks. > > However, I see another case found by afl-fuzz > that still crashes in Vim-7.4.2311 with a > similar stack: > > $ cat crash2.vim > tabedit > autocmd BufUnload tabnext > f x > e y Thanks. It's hard to think of all corner

Re: [bug] vim-7.4.2305 crashes in bugIsChanged with NULL buf pointer

2016-09-02 Fir de Conversatie Dominique Pellé
Bram Moolenaar wrote: > Dominique Pellé wrote: > >> The attached script causes vim-7.4.2305 to crash: >> >> $ cat crash.vim >> new >> tabedit >> tabfirst >> au BufUnload tabnext >> q >> >> $ vim -u NONE -S crash.vim >> Vim: Caught deadly signal SEGV >> Vim: Finished. >> Segmentation fault (core

Re: [bug] vim-7.4.2305 crashes in bugIsChanged with NULL buf pointer

2016-09-02 Fir de Conversatie Bram Moolenaar
Dominique Pellé wrote: > The attached script causes vim-7.4.2305 to crash: > > $ cat crash.vim > new > tabedit > tabfirst > au BufUnload tabnext > q > > $ vim -u NONE -S crash.vim > Vim: Caught deadly signal SEGV > Vim: Finished. > Segmentation fault (core dumped) > > 3518│ int > 3519│

[bug] vim-7.4.2305 crashes in bugIsChanged with NULL buf pointer

2016-09-02 Fir de Conversatie Dominique Pellé
Hi The attached script causes vim-7.4.2305 to crash: $ cat crash.vim new tabedit tabfirst au BufUnload tabnext q $ vim -u NONE -S crash.vim Vim: Caught deadly signal SEGV Vim: Finished. Segmentation fault (core dumped) 3518│ int 3519│ bufIsChanged(buf_T *buf) 3520│ { 3521│ return