Dimitar wrote: > 1. valgrind --leak-check=full --show-reachable=yes ./vim -u NONE -U NONE > > 2. ZQ > > ==14191== LEAK SUMMARY: > ==14191== definitely lost: 36 bytes in 1 blocks. > ==14191== indirectly lost: 120 bytes in 10 blocks. > ==14191== possibly lost: 0 bytes in 0 blocks. > ==14191== still reachable: 40,689 bytes in 261 blocks. > ==14191== suppressed: 0 bytes in 0 blocks. > > VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Jul 13 2010 20:27:14) > Included patches: 1-446 [...]
Please check where the leaks are. At least some of them will be in libraries. Those can't be avoided. And you need to compile Vim with EXITFREE defined, otherwise it won't clean up. -- A real patriot is the fellow who gets a parking ticket and rejoices that the system works. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- 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
