Re: Bug#63760: xemacs21: bad content in backtrace window
[ Please remove Cc: xemacs-patches(a)xemacs.org when replying
to this mail. ]
dwitch <ydirson(a)altern.org> writes:
I trigger debug-on-error from the Options/General menu from
"xemacs21
-q". When triggering an error I sometime have stange infos (unmatched
closing paren on some lines) in the backtrace buffer, which make
debugger-mode barf - I can't use debugger-frame ('b') on frames
following the first of these parens.
[...]
====
(let ((i 1) j)
(nconc i j))
====
And the backtrace it produces:
=====
Signaling: (wrong-type-argument 1 listp)
nconc(1 nil)
(let ((i 1) j) (nconc i j))
)
^
eval((let ((i 1) j) (nconc i j)))
eval-interactive((let ((i 1) j) (nconc i j)))
eval-last-sexp(nil)
call-interactively(eval-last-sexp)
This patch fixes that parenthesis. This patch is for 21.2
but I think it applies to 21.1 cleanly.
2000-05-11 Yoshiki Hayashi <yoshiki(a)xemacs.org>
* eval.c (Fbacktrace): Don't output a line with only right
parenthesis.
Index: eval.c
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/src/eval.c,v
retrieving revision 1.27.2.22
diff -u -r1.27.2.22 eval.c
--- eval.c 2000/04/06 21:57:49 1.27.2.22
+++ eval.c 2000/05/11 05:26:07
＠＠ -4901,8 +4901,8 ＠＠
Fprin1 (backlist->args[i], stream);
}
}
+ write_c_string (")\n", stream);
}
- write_c_string (")\n", stream);
backlist = backlist->next;
}
}
--
Yoshiki Hayashi