Daniel Hahler <[email protected]> wrote: > Hi Bram, > > how should Valgrind be run (which options)? > > Here is the output from "valgrind --log-file=/tmp/valgrind.log vim" and > reproducing it: http://dpaste.com/22Y96NV > > > Regards, > Daniel.
Hi The valgrind errors you see in Python PyObject_Free are expected. See this for an explanation: http://svn.python.org/view/python/trunk/Misc/README.valgrind?view=markup But the other errors such as this one are real bugs: ==21891== Conditional jump or move depends on uninitialised value(s) ==21891== at 0x522632: lalloc (misc2.c:890) ==21891== by 0x522577: alloc (misc2.c:820) ==21891== by 0x52278F: vim_strnsave (misc2.c:1265) ==21891== by 0x4816CE: find_some_match (eval.c:14349) ==21891== by 0x481C41: f_matchstr (eval.c:14549) ==21891== by 0x478EAB: call_func (eval.c:8626) ==21891== by 0x4788E3: get_func_tv (eval.c:8433) ==21891== by 0x474081: eval7 (eval.c:5210) ==21891== by 0x473931: eval6 (eval.c:4861) ==21891== by 0x473465: eval5 (eval.c:4677) ==21891== by 0x472779: eval4 (eval.c:4370) ==21891== by 0x4725BC: eval3 (eval.c:4282) For uninitialized memory errors, valgrind gives more information when using option --track-origins=yes at the cost of running slower. So far I have not been able to reproduce this bug but it looks like Christian has a patch already! Regards Dominique -- -- 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/d/optout.
