Re: [bug] another use of free memory in quickfix code

2016-03-22 Fir de Conversatie h_east
Hi Yegappan, 2016-3-23(Wed) 14:02:53 UTC+9 yega...@gmail.com: > Hi, > > On Mon, Mar 21, 2016 at 2:45 AM, Dominique Pellé > wrote: > > Hi > > > > afl-fuzz found another crash with use of freed memory in vim-7.4.1627 > > (and older) in quickfix code. This is a different

Re: [bug] another use of free memory in quickfix code

2016-03-22 Fir de Conversatie Yegappan Lakshmanan
Hi, On Mon, Mar 21, 2016 at 2:45 AM, Dominique Pellé wrote: > Hi > > afl-fuzz found another crash with use of freed memory in vim-7.4.1627 > (and older) in quickfix code. This is a different bug that the one fixed > recently in Vim-7.4.1592: > The attached patch fixes

Patch 7.4.1639

2016-03-22 Fir de Conversatie Bram Moolenaar
Patch 7.4.1639 Problem:Invoking garbage collection may cause a double free. Solution: Don't free the dict in a partial when recursive is FALSE. Files: src/eval.c *** ../vim-7.4.1638/src/eval.c 2016-03-22 21:00:06.052953785 +0100 --- src/eval.c 2016-03-22 22:22:09.045823705 +0100

Re: [patch] Possible memory leak with partial

2016-03-22 Fir de Conversatie Bram Moolenaar
Thinca wrote: > Thank you for the patch! > > I found a SEGV pattern with this patch. > > " test.vim > let obj = {} > function! obj.func() abort > endfunction > let obj.func = obj.func > unlet obj > call garbagecollect() > > > vim -u test.vim -i NONE -N That's actually an existing problem,

Re: [patch] Possible memory leak with partial

2016-03-22 Fir de Conversatie Bram Moolenaar
Ken Takata wrote; > The last assert_false() in the following script fails after 7.4.1577: > (This is reported by Thinca.) > > let obj = {} > function! obj.func() abort > endfunction > let funcnumber = matchstr(string(obj.func), '^function(''\zs.\{-}\ze''') > call assert_true(exists('*{' .

Patch 7.4.1638

2016-03-22 Fir de Conversatie Bram Moolenaar
Patch 7.4.1638 Problem:When binding a function to a dict the reference count is wrong. Solution: Decrement dict reference count, only reference the function when actually making a copy. (Ken Takata) Files: src/eval.c, src/testdir/test_partial.vim ***

Re: Patch 7.4.1610

2016-03-22 Fir de Conversatie Bram Moolenaar
Ken Takata wrote: > 2016/3/20 Sun 4:51:58 UTC+9 Bram Moolenaar wrote: > > Patch 7.4.1610 > > Problem:Compiler warnings for non-virtual destructor. > > Solution: Mark the classe final. (Ken Takata) > > Files: src/Make_cyg_ming.mak, src/gui_dwrite.cpp, src/if_ole.cpp > > I'm a little

Patch 7.4.1637

2016-03-22 Fir de Conversatie Bram Moolenaar
Patch 7.4.1637 Problem:Can't build with older MinGW compiler. Solution: Change option from c++11 to gnu++11. (Ken Takata) Files: src/Make_cyg_ming.mak *** ../vim-7.4.1636/src/Make_cyg_ming.mak 2016-03-19 20:51:30.707550109 +0100 --- src/Make_cyg_ming.mak 2016-03-22

Re: Arrow characters shouldn't be wide

2016-03-22 Fir de Conversatie Bram Moolenaar
Matteo Cavalleri wrote: > Hi, I don't know if the latest changes regarding emoji and wide > characters are related to this, but I'm currently experiencing some > redraw issues when syntastic puts a glyph on the sign column. Please > see this screenshot: > > http://imgur.com/uKQR4Od > > as you

Patch 7.4.1636

2016-03-22 Fir de Conversatie Bram Moolenaar
Patch 7.4.1636 Problem:When 'F' is in 'shortmess' the prompt for the encryption key isn't displayed. (Toothpik) Solution: Reset msg_silent. Files: src/ex_getln.c *** ../vim-7.4.1635/src/ex_getln.c 2016-03-19 22:50:38.419595003 +0100 --- src/ex_getln.c 2016-03-22

Re: [vim] netrw silently closing buffers on its own (#231)

2016-03-22 Fir de Conversatie Jake Bell
Updating to the latest netrw fixes the issue. Thanks! On Tuesday, March 22, 2016 at 9:34:13 AM UTC-5, K.Takata wrote: > DrChip's reply doesn't seem to be redirected here (vim/vim#231). > > https://groups.google.com/d/msg/vim_dev/1TKfXBi0pEc/SJVAUud1GgAJ > > > > Before you go to the trouble of

Re: [patch] Possible memory leak with partial

2016-03-22 Fir de Conversatie thinca
Thank you for the patch! I found a SEGV pattern with this patch. " test.vim let obj = {} function! obj.func() abort endfunction let obj.func = obj.func unlet obj call garbagecollect() vim -u test.vim -i NONE -N #0 0x74afd6e7 in raise () from /lib64/libc.so.6 #1 0x74afeaba

Re: Patch 7.4.1610

2016-03-22 Fir de Conversatie Ken Takata
Hi Bram, 2016/3/20 Sun 4:51:58 UTC+9 Bram Moolenaar wrote: > Patch 7.4.1610 > Problem:Compiler warnings for non-virtual destructor. > Solution: Mark the classe final. (Ken Takata) > Files: src/Make_cyg_ming.mak, src/gui_dwrite.cpp, src/if_ole.cpp I'm a little bit surprised at this

warnings and a hang

2016-03-22 Fir de Conversatie Charles Campbell
Hello: I use ./configure --with-features=huge --enable-gui=gtk2 --enable-perlinterp --enable-pythoninterp --enable-rubyinterp --enable-cscope for configuring. When I attempt to compile: (using gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)) if_perl.xs|53 warning| expected

[patch] Possible memory leak with partial

2016-03-22 Fir de Conversatie Ken Takata
Hi, The last assert_false() in the following script fails after 7.4.1577: (This is reported by Thinca.) let obj = {} function! obj.func() abort endfunction let funcnumber = matchstr(string(obj.func), '^function(''\zs.\{-}\ze''') call assert_true(exists('*{' . funcnumber . '}')) unlet obj call

Re: [vim] netrw silently closing buffers on its own (#231)

2016-03-22 Fir de Conversatie Charles E Campbell
Jake Bell wrote: > > Also experiencing this issue, as noted in macvim-dev/macvim#255 > . It appears to have > /started/ happening for me some time between patch 7.4.1362 and the > current HEAD. > > I'll try to do a |git bisect| in the next few days

Re: Patch 7.4.1630

2016-03-22 Fir de Conversatie Bram Moolenaar
Elimar Riesebieter wrote: > * Bram Moolenaar [2016-03-21 22:16 +0100]: > > > > > Patch 7.4.1630 > > Problem:Unicode table for double width is outdated. > > Solution: Update to the latest Unicode standard. > > Files: src/mbyte.c > > Now my setup runs without

Re: Patch 7.4.1630

2016-03-22 Fir de Conversatie Elimar Riesebieter
* Bram Moolenaar [2016-03-21 22:16 +0100]: > > Patch 7.4.1630 > Problem:Unicode table for double width is outdated. > Solution: Update to the latest Unicode standard. > Files: src/mbyte.c Now my setup runs without setting noemoji. Thanks! Elimar -- Learned

Re: Arrow characters shouldn't be wide

2016-03-22 Fir de Conversatie Matteo Cavalleri
Hi, I don't know if the latest changes regarding emoji and wide characters are related to this, but I'm currently experiencing some redraw issues when syntastic puts a glyph on the sign column. Please see this screenshot: http://imgur.com/uKQR4Od as you can see the "f" of function is drawn in