golden hour

/usr/share/vim/vim82/doc

File/Folder	Size	Actions
arabic.txt	11.62 KB
autocmd.txt	70.53 KB
change.txt	76.22 KB
channel.txt	49.13 KB
cmdline.txt	48.19 KB
debug.txt	6.73 KB
debugger.txt	5.32 KB
develop.txt	22.33 KB
diff.txt	16.63 KB
digraph.txt	60.53 KB
editing.txt	72.42 KB
eval.txt	528.52 KB
farsi.txt	523 B
filetype.txt	26.95 KB
fold.txt	23.13 KB
ft_ada.txt	17.82 KB
ft_rust.txt	9.37 KB
ft_sql.txt	29.98 KB
gui.txt	51.5 KB
gui_w32.txt	19 KB
gui_x11.txt	29.21 KB
hangulin.txt	598 B
hebrew.txt	5.53 KB
help.txt	8.69 KB
helphelp.txt	15.36 KB
howto.txt	2.85 KB
if_cscop.txt	18.87 KB
if_lua.txt	16.36 KB
if_mzsch.txt	11.66 KB
if_ole.txt	7.19 KB
if_perl.txt	11.02 KB
if_pyth.txt	37.53 KB
if_ruby.txt	8.32 KB
if_sniff.txt	271 B
if_tcl.txt	22.41 KB
indent.txt	41.29 KB
index.txt	78.75 KB
insert.txt	83.29 KB
intro.txt	38.06 KB
map.txt	69.14 KB
mbyte.txt	58.24 KB
message.txt	30.69 KB
mlang.txt	8 KB
motion.txt	50.14 KB
netbeans.txt	37.09 KB
options.txt	382.14 KB
os_390.txt	4.64 KB
os_amiga.txt	5.34 KB
os_beos.txt	293 B
os_dos.txt	12.09 KB
os_haiku.txt	8.39 KB
os_mac.txt	6.7 KB
os_mint.txt	391 B
os_msdos.txt	523 B
os_os2.txt	299 B
os_qnx.txt	3.98 KB
os_risc.txt	328 B
os_unix.txt	2.54 KB
os_vms.txt	32.13 KB
os_win32.txt	13.04 KB
pattern.txt	58.73 KB
pi_getscript.txt	20.59 KB
pi_gzip.txt	1.26 KB
pi_logipat.txt	4.1 KB
pi_netrw.txt	175.08 KB
pi_paren.txt	2.22 KB
pi_spec.txt	4.03 KB
pi_tar.txt	6.65 KB
pi_vimball.txt	11.58 KB
pi_zip.txt	7.12 KB
popup.txt	38.55 KB
print.txt	30.3 KB
quickfix.txt	80.98 KB
quickref.txt	70.45 KB
quotes.txt	12.45 KB
recover.txt	10.47 KB
remote.txt	8.22 KB
repeat.txt	41.2 KB
rileft.txt	4.82 KB
russian.txt	2.95 KB
scroll.txt	13.46 KB
sign.txt	25.25 KB
spell.txt	62.6 KB
sponsor.txt	7.03 KB
starting.txt	71.87 KB
syntax.txt	220.57 KB
tabpage.txt	16.84 KB
tags	346.5 KB
tagsrch.txt	39.33 KB
term.txt	46.38 KB
terminal.txt	54.79 KB
testing.txt	14.6 KB
textprop.txt	13.09 KB
tips.txt	20.57 KB
todo.txt	302.17 KB
uganda.txt	13.7 KB
undo.txt	16.2 KB
usr_01.txt	6.92 KB
usr_02.txt	23.66 KB
usr_03.txt	23.31 KB
usr_04.txt	18.68 KB
usr_05.txt	26.39 KB
usr_06.txt	9.39 KB
usr_07.txt	15.62 KB
usr_08.txt	18.92 KB
usr_09.txt	11.23 KB
usr_10.txt	28.52 KB
usr_11.txt	12.72 KB
usr_12.txt	13.11 KB
usr_20.txt	13.39 KB
usr_21.txt	18.02 KB
usr_22.txt	14.65 KB
usr_23.txt	12.45 KB
usr_24.txt	20.34 KB
usr_25.txt	18.73 KB
usr_26.txt	8.07 KB
usr_27.txt	17.29 KB
usr_28.txt	15.64 KB
usr_29.txt	19.65 KB
usr_30.txt	22.13 KB
usr_31.txt	10.16 KB
usr_32.txt	5.25 KB
usr_40.txt	22.65 KB
usr_41.txt	95.1 KB
usr_42.txt	13.53 KB
usr_43.txt	7.24 KB
usr_44.txt	28.27 KB
usr_45.txt	17.27 KB
usr_46.txt	6.93 KB
usr_90.txt	16.44 KB
usr_toc.txt	9.28 KB
various.txt	30.37 KB
version4.txt	13.58 KB
version5.txt	301.3 KB
version6.txt	563.42 KB
version7.txt	658.89 KB
version8.txt	1.85 MB
vi_diff.txt	56.08 KB
vim9.txt	55.82 KB
visual.txt	21.28 KB
windows.txt	54.43 KB
workshop.txt	371 B

Edit: debug.txt

*debug.txt*     For Vim version 8.2.  Last change: 2019 May 07

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* *gdb*

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 src/Makefile for
   this, which you can uncomment).  Also make sure "strip" is disabled (do not
   install it, or use the line "STRIP = /bin/true").

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. 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.

First of all, build Vim with EXITFREE defined.  Search for this in MAKEFILE
and uncomment the line.

Use this command to start 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 "--clean"
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*

If the Windows version of Vim crashes in a reproducible manner, you can take
some steps to provide a useful bug report.

3.1 GENERIC ~

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.

If you have Visual Studio, use that instead of the VC Toolkit and WinDbg.

For other compilers, you should always use the corresponding debugger: gdb
(see above |debug-gcc|) for the Cygwin and MinGW compilers.

*debug-vs2005*
3.2 Debugging Vim crashes with Visual Studio 2005/Visual C++ 2005 Express ~

First launch vim.exe or gvim.exe and then launch Visual Studio.  (If you don't
have Visual Studio, follow the instructions at |get-ms-debuggers| to obtain a
free copy of Visual C++ 2005 Express Edition.)

On the Tools menu, click Attach to Process.  Choose the Vim process.

In Vim, reproduce the crash.  A dialog will appear in Visual Studio, telling
you about the unhandled exception in the Vim process.  Click Break to break
into the process.

Visual Studio will pop up another dialog, telling you that no symbols are
loaded and that the source code cannot be displayed.  Click OK.

Several windows will open.  Right-click in the Call Stack window.  Choose Load
Symbols.  The Find Symbols dialog will open, looking for (g)vim.pdb.  Navigate
to the directory where you have the PDB file and click Open.

At this point, you should have a full call stack with vim function names and
line numbers.  Double-click one of the lines and the Find Source dialog will
appear.  Navigate to the directory where the Vim source is (if you have it.)

If you don't know how to debug this any further, follow the instructions
at ":help bug-reports".  Paste the call stack into the bug report.

If you have a non-free version of Visual Studio, you can save a minidump via
the Debug menu and send it with the bug report.  A minidump is a small file
(<100KB), which contains information about the state of your process.
Visual C++ 2005 Express Edition cannot save minidumps and it cannot be
installed as a just-in-time debugger. Use WinDbg, |debug-windbg|, if you
need to save minidumps or you want a just-in-time (postmortem) debugger.

*debug-windbg*
3.3 Debugging Vim crashes with WinDbg ~

See |get-ms-debuggers| to obtain a copy of WinDbg.

As with the Visual Studio IDE, you can attach WinDbg to a running Vim process.
You can also have your system automatically invoke WinDbg as a postmortem
debugger. To set WinDbg as your postmortem debugger, run "windbg -I".

To attach WinDbg to a running Vim process, launch WinDbg. On the File menu,
choose Attach to a Process. Select the Vim process and click OK.

At this point, choose Symbol File Path on the File menu, and add the folder
containing your Vim PDB to the sympath. If you have Vim source available,
use Source File Path on the File menu. You can now open source files in WinDbg
and set breakpoints, if you like. Reproduce your crash. WinDbg should open the
source file at the point of the crash. Using the View menu, you can examine
the call stack, local variables, watch windows, and so on.

If WinDbg is your postmortem debugger, you do not need to attach WinDbg to
your Vim process. Simply reproduce the crash and WinDbg will launch
automatically. As above, set the Symbol File Path and the Source File Path.

To save a minidump, type the following at the WinDbg command line: >
        .dump vim.dmp
<
							*debug-minidump*
3.4 Opening a Minidump ~

If you have a minidump file, you can open it in Visual Studio or in WinDbg.

In Visual Studio 2005: on the File menu, choose Open, then Project/Solution.
Navigate to the .dmp file and open it. Now press F5 to invoke the debugger.
Follow the instructions in |debug-vs2005| to set the Symbol File Path.

In WinDbg: choose Open Crash Dump on the File menu. Follow the instructions in
|debug-windbg| to set the Symbol File Path.

*get-ms-debuggers*
3.5 Obtaining Microsoft Debugging Tools ~

The Debugging Tools for Windows (including WinDbg) can be downloaded from
    http://www.microsoft.com/whdc/devtools/debugging/default.mspx
This includes the WinDbg debugger.

Visual C++ 2005 Express Edition can be downloaded for free from:
    http://msdn.microsoft.com/vstudio/express/visualC/default.aspx

=========================================================================
 vim:tw=78:ts=8:noet:ft=help:norl: