On Sat, Aug 04, 2007 at 17:29:37 +0200, Dominique Pelle wrote: > > Hi, > > Valgrind memory checker finds several errors in vim-7.1 (patches 1-50) > when built with --enable-multibyte: > > $ ./configure --enable-multibyte > $ make CFLAGS="-O0 -g" > $ cd src/testdir > $ valgrind ../vim -u unix.vim -U NONE --noplugin -s dotest.in > test45.in 2> valgrind-test45.txt
Could you specify/make available the contents of files unix.vim, dotest.in and test45.in? Also platform details can be useful. Being able to reproduce is quite helpful in figuring out what's going on (the messages you included are a good start, but leave you quite blind if you try to look into it in detail). Also, is there a crash (e.g. when compiled with optimizations) or incorrect result? Without that it's hard to tell whether the accesses to uninitialized memory actually (can) result in an incorrect behavior. That's because valgrind operates on rather low level and cannot see if the uninitialized values really influence the program flow or if a higher level logic of the program prevents them to spread further. In short: We need a human to have a look at the code ;-) Regards, Peter --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
