changeset 30707:b005d7886185 v9.0.0688

patch 9.0.0688: debugger does not display the whole command Commit: https://github.com/vim/vim/commit/33b55b562b90e5cc0091fa39d87cd60956c73f57 Author: Bram Moolenaar <Bram@vim.org> Date: Fri Oct 7 18:51:23 2022 +0100 patch 9.0.0688: debugger does not display the whole command Problem: Debugger does not display the whole command. Solution: Set ea.cmd before checking for a breakpoint.
author Bram Moolenaar <Bram@vim.org>
date Fri, 07 Oct 2022 20:00:04 +0200
parents ad50301e2d22
children 4936e1df9199
files src/ex_docmd.c src/testdir/test_debugger.vim src/version.c
diffstat 3 files changed, 7 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- a/src/ex_docmd.c
+++ b/src/ex_docmd.c
@@ -1889,7 +1889,11 @@ do_one_cmd(
 	}
     }
 # endif
-
+#endif
+
+    ea.cmd = cmd;
+
+#ifdef FEAT_EVAL
     // May go to debug mode.  If this happens and the ">quit" debug command is
     // used, throw an interrupt exception and skip the next command.
     dbg_check_breakpoint(&ea);
@@ -1935,7 +1939,6 @@ do_one_cmd(
 #endif
     }
 
-    ea.cmd = cmd;
     if (!may_have_range)
 	ea.line1 = ea.line2 = default_address(&ea);
     else if (parse_cmd_address(&ea, &errormsg, FALSE) == FAIL)
--- a/src/testdir/test_debugger.vim
+++ b/src/testdir/test_debugger.vim
@@ -993,7 +993,6 @@ func Test_Backtrace_DefFunction()
   call RunDbgCmd(buf, 'step', ['line 1: vim9script'])
   call RunDbgCmd(buf, 'step', ['line 3: def DoAThing(): number'])
   call RunDbgCmd(buf, 'step', ['line 9: export def File2Function()'])
-  call RunDbgCmd(buf, 'step', ['line 9: def File2Function()'])
   call RunDbgCmd(buf, 'step', ['line 13: defcompile'])
   call RunDbgCmd(buf, 'step', ['line 14: File2Function()'])
   call RunDbgCmd(buf, 'backtrace', [
--- a/src/version.c
+++ b/src/version.c
@@ -700,6 +700,8 @@ static char *(features[]) =
 static int included_patches[] =
 {   /* Add new patch number below this line */
 /**/
+    688,
+/**/
     687,
 /**/
     686,