Mercurial > vim

comparison runtime/doc/debug.txt @ 2309:543ea69d037f vim73

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Add clipboard support in Mac console. (Bjorn Winckler)
author Bram Moolenaar <bram@vim.org>
date Wed, 14 Jul 2010 13:58:07 +0200
parents 7c8c7c95a865
children 12b829477c60
comparison
equal deleted inserted replaced
2308:cb025511f6b6 2309:543ea69d037f
37 frame 3 37 frame 3
38 < Replace "3" with one of the numbers in the stack trace. 38 < Replace "3" with one of the numbers in the stack trace.
39 39
40 ============================================================================== 40 ==============================================================================
41 41
42 2. Locating memory leaks *debug-leaks* 42 2. Locating memory leaks *debug-leaks* *valgrind*
43 43
44 If you suspect Vim is leaking memory and you are using Linux, the valgrind 44 If you suspect Vim is leaking memory and you are using Linux, the valgrind
45 tool is very useful to pinpoint memory leaks. 45 tool is very useful to pinpoint memory leaks.
46 46
47 First of all, build Vim with EXITFREE defined. Search for this in MAKEFILE 47 First of all, build Vim with EXITFREE defined. Search for this in MAKEFILE
48 and uncomment the line. 48 and uncomment the line.
49 49
50 Use this command to start Vim: *valgrind* 50 Use this command to start Vim:
51 > 51 >
52 valgrind --log-file=valgrind.log ./vim 52 valgrind --log-file=valgrind.log --leak-check=full ./vim
53 53
54 Note: Vim will run much slower. If your .vimrc is big or you have several 54 Note: Vim will run much slower. If your .vimrc is big or you have several
55 plugins you need to be patient for startup, or run with the "-u NONE" 55 plugins you need to be patient for startup, or run with the "-u NONE"
56 argument. 56 argument.
57
58 There are often a few leaks from libraries, such as getpwuid() and
59 XtVaAppCreateShell(). Those are unavoidable. The number of bytes should be
60 very small a Kbyte or less.
57 61
58 ============================================================================== 62 ==============================================================================
59 63
60 3. Windows Bug Reporting *debug-win32* 64 3. Windows Bug Reporting *debug-win32*
61 65