diff options
| author | Bram Moolenaar <Bram@vim.org> | 2010-07-14 13:58:07 +0200 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2010-07-14 13:58:07 +0200 |
| commit | 164fca39bdacc36b7d9f2d1b28ab5abe03ce4004 (patch) | |
| tree | 0280e2098fc47966b5bb419f63d3c655a75d1e25 /runtime/doc/debug.txt | |
| parent | 7abcaab78da25f07190a114a84a9000f91cf044f (diff) | |
Add clipboard support in Mac console. (Bjorn Winckler)
Diffstat (limited to 'runtime/doc/debug.txt')
| -rw-r--r-- | runtime/doc/debug.txt | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/runtime/doc/debug.txt b/runtime/doc/debug.txt index 55939022bf..eb5a30593d 100644 --- a/runtime/doc/debug.txt +++ b/runtime/doc/debug.txt @@ -39,7 +39,7 @@ This also applies when using the MingW tools. ============================================================================== -2. Locating memory leaks *debug-leaks* +2. Locating memory leaks *debug-leaks* *valgrind* If you suspect Vim is leaking memory and you are using Linux, the valgrind tool is very useful to pinpoint memory leaks. @@ -47,14 +47,18 @@ tool is very useful to pinpoint memory leaks. First of all, build Vim with EXITFREE defined. Search for this in MAKEFILE and uncomment the line. -Use this command to start Vim: *valgrind* +Use this command to start Vim: > - valgrind --log-file=valgrind.log ./vim + valgrind --log-file=valgrind.log --leak-check=full ./vim Note: Vim will run much slower. If your .vimrc is big or you have several plugins you need to be patient for startup, or run with the "-u NONE" argument. +There are often a few leaks from libraries, such as getpwuid() and +XtVaAppCreateShell(). Those are unavoidable. The number of bytes should be +very small a Kbyte or less. + ============================================================================== 3. Windows Bug Reporting *debug-win32* |