On 09/07/10 00:26, Dimitar DIMITROV wrote:
valgrind --leak-check=full --show-reachable=yes gvim

1. cc, then a,a,a,a,a,a,a,a,a,a,a,
2. /\(\(\s*\w\+\s*\)\+,\)\{1,20}
3. :h\{
4. Close gvim

==3987== LEAK SUMMARY:
==3987== definitely lost: 12,986 bytes in 47 blocks.
==3987== indirectly lost: 28,332 bytes in 1,403 blocks.
==3987== possibly lost: 349,216 bytes in 498 blocks.
==3987== still reachable: 3,245,978 bytes in 47,532 blocks.
==3987== suppressed: 0 bytes in 0 blocks.

VIM - Vi IMproved 7.1 (2007 May 12, compiled Oct 17 2008 18:04:59)
Included patches: 1-314
[...]

On 09/07/10 00:29, Dimitar DIMITROV wrote:
> 1. <f1>
> 2. 3yy`]
> 3. 5yy`]
>
> ==4008== LEAK SUMMARY:
> ==4008== definitely lost: 37,350 bytes in 116 blocks.
> ==4008== indirectly lost: 28,332 bytes in 1,403 blocks.
> ==4008== possibly lost: 319,554 bytes in 469 blocks.
> ==4008== still reachable: 2,425,077 bytes in 30,351 blocks.
> ==4008== suppressed: 0 bytes in 0 blocks.
>
> VIM - Vi IMproved 7.1 (2007 May 12, compiled Oct 17 2008 18:04:59)
> Included patches: 1-314
[...]

7.1, even 7.1.314, is not the latest version. Among the 445 patches already published for the _next_ version (7.2), more than a few were leak fixes, see http://ftp.vim.org/pub/vim/patches/7.2/README

If you want to usefully contribute memory leak reports, please use the latest version, either the latest stable version (currently 7.2.445) or the bleeding-edge development version (7.3a, available only over Mercurial, not as a bz2 archive).

See:
http://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial (7.2 or 7.3a)
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm (compiling)

On Debian, you should be able to use apt-get to get the "dependencies" of the vim-x11 package (or of whatever it is called on that distro).


Best regards,
Tony.
--
For every credibility gap, there is a gullibility fill.
                -- R. Clopton

--
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

Raspunde prin e-mail lui