Mercurial > vim
diff runtime/doc/terminal.txt @ 14126:1ce45478cbf1
patch 8.1.0080: can't see the breakpoint number in the terminal debugger
commit https://github.com/vim/vim/commit/de1a83147a28d3db8f9fca415ffc8fa04218eac2
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Jun 19 16:59:54 2018 +0200
patch 8.1.0080: can't see the breakpoint number in the terminal debugger
Problem: Can't see the breakpoint number in the terminal debugger.
Solution: Use the breakpoint number for the sign. (Christian Brabandt)
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Tue, 19 Jun 2018 17:00:07 +0200 |
parents | 583bf95b6c84 |
children | 4543777545a3 |
line wrap: on
line diff
--- a/runtime/doc/terminal.txt +++ b/runtime/doc/terminal.txt @@ -705,11 +705,11 @@ Put focus on the gdb window and type: > Vim will start running in the program window. Put focus there and type: > :help gui Gdb will run into the ex_help breakpoint. The source window now shows the -ex_cmds.c file. A ">>" marker will appear where the breakpoint was set. The -line where the debugger stopped is highlighted. You can now step through the -program. Let's use the mouse: click on the "Next" button in the window -toolbar. You will see the highlighting move as the debugger executes a line -of source code. +ex_cmds.c file. A red "1 " marker will appear in the signcolumn where the +breakpoint was set. The line where the debugger stopped is highlighted. You +can now step through the program. Let's use the mouse: click on the "Next" +button in the window toolbar. You will see the highlighting move as the +debugger executes a line of source code. Click "Next" a few times until the for loop is highlighted. Put the cursor on the end of "eap->arg", then click "Eval" in the toolbar. You will see this @@ -788,6 +788,13 @@ source code, a new window will be create happens if the buffer in the source code window has been modified and can't be abandoned. +Gdb gives each breakpoint a number. In Vim the number shows up in the sign +column, with a red background. You can use these gdb commands: +- info break list breakpoints +- delete N delete breakpoint N +You can also use the `:Clear` command if the cursor is in the line with the +breakpoint, or use the "Clear breakpoint" right-click menu entry. + Inspecting variables ~ *termdebug-variables* *:Evaluate* @@ -831,6 +838,13 @@ There is another, hidden, buffer, which gdb. The buffer name is "gdb communication". Do not delete this buffer, it will break the debugger. +Gdb has some weird behavior, the plugin does its best to work around that. +For example, after typing "continue" in the gdb window a CTRL-C can be used to +interrupt the running program. But after using the MI command +"-exec-continue" pressing CTRL-C does not interrupt. Therefore you will see +"continue" being used for the `:Continue` command, instead of using the +communication channel. + Customizing ~