On Tuesday, May 21, 2013 9:27:34 AM UTC-5, Bram Moolenaar wrote: > Dominique Pelle wrote: > > > > > Attached patch fixes a memory leak in regexp_nfa.c > > > detected by valgrind: > > > > > > ==3055== 128 bytes in 4 blocks are definitely lost in loss record 76 of 110 > > > ==3055== at 0x4C2B3F8: malloc (in > > > /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) > > > ==3055== by 0x50E98C: lalloc (misc2.c:929) > > > ==3055== by 0x572226: post2nfa (regexp_nfa.c:2161) > > > ==3055== by 0x57697F: nfa_regcomp (regexp_nfa.c:3682) > > > ==3055== by 0x576CF7: vim_regcomp (regexp.c:7827) > > [...] > > > > > > > > I can reproduce it with Vim-7.3.988 using... > > > vim -N -c ':syntax on' vim/src/spell.c > > > ... and then exiting immediately with ":q!" > > > > Thanks! Please keep an eye out for more leaks. The more problems I > > find in the NFA code the less I trust it... >
Maybe you could ask the Coverity folks to run a new analysis on this code. I know in tested and proven code it finds mostly stuff you don't care about, but in new code it may be more useful. I'm not sure how they handle their open-source scan project. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
