| | |
*debug.txt* For Vim version 7.2. Last change: 2006 May 01 | | |
VIM REFERENCE MANUAL by Bram Moolenaar | | |
Debugging Vim *debug-vim* | | |
This is for debugging Vim itself, when it doesn't work properly.
For debugging Vim scripts, functions, etc. see |debug-scripts| | | |
1. Location of a crash, using gcc and gdb |debug-gcc|
2. Windows Bug Reporting |debug-win32| | | |
============================================================================== | | |
1. Location of a crash, using gcc and gdb *debug-gcc* | | |
When Vim crashes in one of the test files, and you are using gcc for
compilation, here is what you can do to find out exactly where Vim crashes.
This also applies when using the MingW tools. | | |
1. Compile Vim with the "-g" option (there is a line in the Makefile for this,
which you can uncomment). | | |
2. Execute these commands (replace "11" with the test that fails): >
cd testdir
gdb ../vim
run -u unix.vim -U NONE -s dotest.in test11.in | | |
3. Check where Vim crashes, gdb should give a message for this. | | |
4. Get a stack trace from gdb with this command: >
where
< You can check out different places in the stack trace with: >
frame 3
< Replace "3" with one of the numbers in the stack trace. | | |
============================================================================== | | |
2. Windows Bug Reporting *debug-win32* | | |
If the Windows version of Vim crashes in a reproducible manner, you can take
some steps to provide a useful bug report. | | |
| | |
You must obtain the debugger symbols (PDB) file for your executable: gvim.pdb
for gvim.exe, or vim.pdb for vim.exe. The PDB should be available from the
same place that you obtained the executable. Be sure to use the PDB that
matches the EXE (same date). | | |
If you built the executable yourself with the Microsoft Visual C++ compiler,
then the PDB was built with the EXE. | | |
Alternatively, if you have the source files, you can import Make_ivc.mak into
Visual Studio as a workspace. Then select a debug configuration, build and
you can do all kinds of debugging (set breakpoints, watch variables, etc.). | | |
