Emacs Stack Exchange is a question and answer site for those using, extending or developing Emacs. It only takes a minute to sign up.
Sign up to join this community
I'm trying to debug the infamous Unrecognized entry in undo list undo-tree-canary, and after having Emacs debugger triggered on error, I want to move back and forth between stack frames and to examine state of variables. Sort of what frame 3 command in gdb would do.
Unfortunately I haven't found this question asked before, and searching through Emacs documentation haven't been fruitful for me.
Simply move point in the *Backtrace* buffer to the corresponding line of the frame you're interested in.
examine state of variables
Then press v (debugger-toggle-locals) to show local variables in the frame, or e (debugger-eval-expression) to evaluate an expression in the frame's context. Note that you won't have access to lexical variables when the function is byte compiled.
primitive-undo was called with, in particular "list" arg is set to "(undo-tree-canary)" text. But when I move point in *Backtrace* buffer over this line and evaluate list expecting to see its value, I get "void variable list". Same happens if I additionally press enter over the function, thus getting redirected to the source. The source of simple.el isn't byte-compiled for me.
e to inspect variables in *Backtrace* buffer (I've used M-: instead). Still, for every possible stack frame, when I evaluate with e the argument that the function in frame was called with, I get "void variable", even though I can see value of the argument inside the backtrace.
primitive-undo using debug-on-entry? I noticed it seems to mess up the frames so the debugger gets a bit confused.
toggle-debug-on-error, can it have a similar problem? Btw, thanks for the hint about v, when I press it over primitive-undo, I get only 2 local variables, and none of them are arguments of the function, screenshot. I guess this is a bug in Emacs itself, right?
