Mercurial > vim

comparison runtime/doc/debug.txt @ 16580:09f560dde6be v8.1.1293

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.1.1293: MSVC files are no longer useful commit https://github.com/vim/vim/commit/fda9784dc9596e1e36f840bbf1935a4c4b502bd9 Author: Bram Moolenaar <Bram@vim.org> Date: Tue May 7 22:25:27 2019 +0200 patch 8.1.1293: MSVC files are no longer useful Problem: MSVC files are no longer useful for debugging. Newer Visual Studio versions cannot read them. Solution: Delete the files. (Ken Takata, closes #4357)
author Bram Moolenaar <Bram@vim.org>
date Tue, 07 May 2019 22:30:05 +0200
parents 2f7e67dd088c
children 7e733046db1d
comparison
equal deleted inserted replaced
16579:083130237591 16580:09f560dde6be
75 same place that you obtained the executable. Be sure to use the PDB that 75 same place that you obtained the executable. Be sure to use the PDB that
76 matches the EXE (same date). 76 matches the EXE (same date).
77 77
78 If you built the executable yourself with the Microsoft Visual C++ compiler, 78 If you built the executable yourself with the Microsoft Visual C++ compiler,
79 then the PDB was built with the EXE. 79 then the PDB was built with the EXE.
80
81 Alternatively, if you have the source files, you can import Make_ivc.mak into
82 Visual Studio as a workspace. Then select a debug configuration, build and
83 you can do all kinds of debugging (set breakpoints, watch variables, etc.).
84 80
85 If you have Visual Studio, use that instead of the VC Toolkit and WinDbg. 81 If you have Visual Studio, use that instead of the VC Toolkit and WinDbg.
86 82
87 For other compilers, you should always use the corresponding debugger: TD for 83 For other compilers, you should always use the corresponding debugger: TD for
88 a Vim executable compiled with the Borland compiler; gdb (see above 84 a Vim executable compiled with the Borland compiler; gdb (see above