@@ -705,11 +705,11 @@ Put focus on the gdb window and type: >
705
705
Vim will start running in the program window. Put focus there and type: >
706
706
:help gui
707
707
Gdb will run into the ex_help breakpoint. The source window now shows the
708
- ex_cmds.c file. A ">> " marker will appear where the breakpoint was set. The
709
- line where the debugger stopped is highlighted. You can now step through the
710
- program. Let's use the mouse: click on the "Next" button in the window
711
- toolbar. You will see the highlighting move as the debugger executes a line
712
- of source code.
708
+ ex_cmds.c file. A red "1 " marker will appear in the signcolumn where the
709
+ breakpoint was set. The line where the debugger stopped is highlighted. You
710
+ can now step through the program. Let's use the mouse: click on the "Next"
711
+ button in the window toolbar. You will see the highlighting move as the
712
+ debugger executes a line of source code.
713
713
714
714
Click "Next" a few times until the for loop is highlighted. Put the cursor on
715
715
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 created for the source code. This also
788
788
happens if the buffer in the source code window has been modified and can't be
789
789
abandoned.
790
790
791
+ Gdb gives each breakpoint a number. In Vim the number shows up in the sign
792
+ column, with a red background. You can use these gdb commands:
793
+ - info break list breakpoints
794
+ - delete N delete breakpoint N
795
+ You can also use the `:Clear ` command if the cursor is in the line with the
796
+ breakpoint, or use the "Clear breakpoint" right-click menu entry.
797
+
791
798
792
799
Inspecting variables ~
793
800
*termdebug-variables* *:Evaluate*
@@ -831,6 +838,13 @@ There is another, hidden, buffer, which is used for Vim to communicate with
831
838
gdb. The buffer name is "gdb communication". Do not delete this buffer, it
832
839
will break the debugger.
833
840
841
+ Gdb has some weird behavior, the plugin does its best to work around that.
842
+ For example, after typing "continue" in the gdb window a CTRL-C can be used to
843
+ interrupt the running program. But after using the MI command
844
+ "-exec-continue" pressing CTRL-C does not interrupt. Therefore you will see
845
+ "continue" being used for the `:Continue ` command, instead of using the
846
+ communication channel.
847
+
834
848
835
849
Customizing ~
836
850
0 commit comments