On 2007-08-04, Dominique Pelle <[EMAIL PROTECTED]> wrote: > On 8/4/07, Ali Akcaagac <[EMAIL PROTECTED]> wrote: > > > > On Sat, 2007-08-04 at 17:29 +0200, Dominique Pelle wrote: > > > Valgrind memory checker finds several errors in vim-7.1 (patches 1-50) > > > when built with --enable-multibyte: > > > > Hello, > > > > that's pretty nice that you ran valgrind ontop of vim. I bet everyone > > else could have done so as well. Would you please tell in more detail. > > Maybe the parts within the code that you believe have "errors" ? More or > > less prove us the errors. > > Hi > > I am currently trying to investigate those valgrind errors but it does not > look easy (win_line() has > 2000 lines). So far I have not found how to > fix them, but people who know this code better might have better luck.
I haven't looked at the code referred to by the error messages, but keep in mind that they may not be real errors. All of the messages refer to "uninitialised value(s)". In my experience, correctness-checking programs often report such errors when they cannot determine for certain that the value of a variable has been set when in fact it has, but the mechanism is hidden from the checking program. Regards, Gary --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
