thac0/vim
1
0
Fork 0
forked from aniani/vim
Code Activity

patch 8.0.1505: debugger can't break on a condition

Browse Source 
Problem:    Debugger can't break on a condition. (Charles Campbell)
Solution:   Add ":breakadd expr". (Christian Brabandt, closes #859)
This commit is contained in:
Bram Moolenaar
2018-02-11 19:06:26 +01:00
parent c33ecb2915
commit c6f9f739d3
10 changed files with 460 additions and 261 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
runtime/doc/repeat.txt
View File

@@ -806,6 +806,19 @@ DEFINING BREAKPOINTS
< Note that this only works for commands that are executed when
sourcing the file, not for a function defined in that file.
:breaka[dd] expr {expression}
Sets a breakpoint, that will break whenever the {expression}
evaluates to a different value. Example: >
:breakadd expr g:lnum
< Will break, whenever the global variable lnum changes.
Note if you watch a |script-variable| this will break
when switching scripts, since the script variable is only
valid in the script where it has been defined and if that
script is called from several other scripts, this will stop
whenever that particular variable will become visible or
unaccessible again.
The [lnum] is the line number of the breakpoint. Vim will stop at or after
this line. When omitted line 1 is used.