Mercurial > vim
view src/testdir/test108.ok @ 12833:db9ffed7e1fc v8.0.1293
patch 8.0.1293: setting a breakpoint in the terminal debugger sometimes fails
commit https://github.com/vim/vim/commit/60e73f2acc890f07056fa1bea8dbe89d26918b3e
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Nov 12 18:02:06 2017 +0100
patch 8.0.1293: setting a breakpoint in the terminal debugger sometimes fails
Problem: Setting a breakpoint in the terminal debugger sometimes fails.
Solution: Interrupt the program if needed. Set the interface to async.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sun, 12 Nov 2017 18:15:04 +0100 |
parents | 8fc60af6dbf5 |
children | a527110d5f56 |
line wrap: on
line source
- show backtrace: 2 function Foo[2] 1 Bar[2] ->0 Bazz line 2: let var3 = "another var" show variables on different levels: 6 2 function Foo[2] ->1 Bar[2] 0 Bazz line 2: let var3 = "another var" 3 ->2 function Foo[2] 1 Bar[2] 0 Bazz line 2: let var3 = "another var" 1 - undefined vars: undefined var3 on former level: Error detected while processing function Foo[2]..Bar[2]..Bazz: line 3: E121: Undefined variable: var3 E15: Invalid expression: var3 here var3 is defined with "another var": another var undefined var2 on former level Error detected while processing function Foo[2]..Bar: line 3: E121: Undefined variable: var2 E15: Invalid expression: var2 here var2 is defined with 10: 10 - backtrace movements: 1 function Foo[2] ->0 Bar line 3: End of function next command cannot go down, we are on bottom frame is zero next command cannot go up, we are on top frame at highest level: 1 ->1 function Foo[2] 0 Bar line 3: End of function fil is not frame or finish, it is file "[No Name]" --No lines in buffer-- - relative backtrace movement 1 function Foo[2] ->0 Bar line 3: End of function ->1 function Foo[2] 0 Bar line 3: End of function - go beyond limits does not crash frame at highest level: 1 ->1 function Foo[2] 0 Bar line 3: End of function frame is zero 1 function Foo[2] ->0 Bar line 3: End of function - final result 19: 19