Mercurial > vim

comparison runtime/doc/debug.txt @ 16606:7e733046db1d v8.1.1306

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.1.1306: Borland support is outdated and doesn't work commit https://github.com/vim/vim/commit/eae1b91fea74842000fc055afc74fe2e7934c6ee Author: Bram Moolenaar <Bram@vim.org> Date: Thu May 9 15:12:55 2019 +0200 patch 8.1.1306: Borland support is outdated and doesn't work Problem: Borland support is outdated and doesn't work. Solution: Remove Borland support, there are other (free) compilers available. (Thomas Dziedzic, Ken Takata, closes #4364)
author Bram Moolenaar <Bram@vim.org>
date Thu, 09 May 2019 15:15:07 +0200
parents 09f560dde6be
children 1eaf34420bb3
comparison
equal deleted inserted replaced
16605:50115650f6c7 16606:7e733046db1d
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 80
81 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.
82 82
83 For other compilers, you should always use the corresponding debugger: TD for 83 For other compilers, you should always use the corresponding debugger: gdb
84 a Vim executable compiled with the Borland compiler; gdb (see above 84 (see above |debug-gcc|) for the Cygwin and MinGW compilers.
85 |debug-gcc|) for the Cygwin and MinGW compilers.
86 85
87 86
88 *debug-vs2005* 87 *debug-vs2005*
89 3.2 Debugging Vim crashes with Visual Studio 2005/Visual C++ 2005 Express ~ 88 3.2 Debugging Vim crashes with Visual Studio 2005/Visual C++ 2005 Express ~
90 89