aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/debugger.c
diff options
context:
space:
mode:
authorzeertzjq <zeertzjq@outlook.com>2022-08-14 06:32:00 +0800
committerzeertzjq <zeertzjq@outlook.com>2022-08-15 10:14:52 +0800
commit98ab0bb5f7d2138be0b6019769e237e42aafad1a (patch)
tree6899f42d0caeed8cd23a386669b3adf40d987989 /src/nvim/debugger.c
parent1c164689a4ef243be2a0e1b4332c9b6c56b5b031 (diff)
downloadrneovim-98ab0bb5f7d2138be0b6019769e237e42aafad1a.tar.gz
rneovim-98ab0bb5f7d2138be0b6019769e237e42aafad1a.tar.bz2
rneovim-98ab0bb5f7d2138be0b6019769e237e42aafad1a.zip
vim-patch:8.2.1297: when a test fails it's often not easy to see where
Problem: When a test fails it's often not easy to see what the call stack is. Solution: Add more entries from the call stack in the exception message. https://github.com/vim/vim/commit/a5d0423fa16f18b4576a2a07e50034e489587a7d Use docs from latest Vim.
Diffstat (limited to 'src/nvim/debugger.c')
-rw-r--r--src/nvim/debugger.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/nvim/debugger.c b/src/nvim/debugger.c
index 76e1caff49..663f4feb08 100644
--- a/src/nvim/debugger.c
+++ b/src/nvim/debugger.c
@@ -99,7 +99,7 @@ void do_debug(char_u *cmd)
xfree(debug_newval);
debug_newval = NULL;
}
- char *sname = estack_sfile();
+ char *sname = estack_sfile(false);
if (sname != NULL) {
msg(sname);
}
@@ -324,7 +324,7 @@ static void do_checkbacktracelevel(void)
debug_backtrace_level = 0;
msg(_("frame is zero"));
} else {
- char *sname = estack_sfile();
+ char *sname = estack_sfile(false);
int max = get_maxbacktrace_level(sname);
if (debug_backtrace_level > max) {
@@ -337,7 +337,7 @@ static void do_checkbacktracelevel(void)
static void do_showbacktrace(char_u *cmd)
{
- char *sname = estack_sfile();
+ char *sname = estack_sfile(false);
int max = get_maxbacktrace_level(sname);
if (sname != NULL) {
int i = 0;