emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to debug Error during redisplay


From: Leo Liu
Subject: Re: How to debug Error during redisplay
Date: Fri, 11 Jan 2013 19:02:29 +0800
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.92 (OS X 10.8.2)

On 2013-01-11 18:25 +0800, Eli Zaretskii wrote:
> Run Emacs under GDB, put a breakpoint in safe_eval_handler, and see
> which code and in which buffer is responsible.

Thanks for the info; I have forgotten there is always GDB ;)

I don't know how to print current_buffer. I tried:

p current_buffer => $11 = (struct buffer *) 0x1015330a0
pr => 1079299112
xpr => Argument to arithmetic operation not a number or boolean.

But bt gives me this:

--------------------------------
Lisp Backtrace:
"redisplay_internal (C function)" (0x69d758)
"redisplay" (0x5fbf58a0)
"sit-for" (0x5fbf5f30)
"animate-string" (0x5fbf6480)
"if" (0x5fbf6990)
"let" (0x5fbf6cd0)
"progn" (0x5fbf6f30)
"if" (0x5fbf7190)
"slime-startup-message" (0x5fbf7428)
"funcall" (0x5fbf7420)
"slime-repl-update-banner" (0x5fbf7730)
"save-current-buffer" (0x5fbf7c50)
"slime-init-output-buffer" (0x5fbf7da0)
"slime-repl-connected-hook-function" (0x5fbf83c0)
"run-hooks" (0x5fbf83f0)
"let" (0x5fbf88f0)
"let" (0x5fbf8c30)
"ad-Orig-slime-set-connection-info" (0x5fbf8d80)
"with-no-warnings" (0x5fbf9320)
"setq" (0x5fbf9590)
"let" (0x5fbf98d0)
"slime-set-connection-info" (0x5fbf9b68)
"apply" (0x5fbf9c40)
0x5b1d840 Lisp type 6
"funcall" (0x5fbfa090)
"progn" (0x5fbfa4b0)
"if" (0x5fbfa710)
"let*" (0x5fbfaa30)
"progn" (0x5fbfac90)
"cond" (0x5fbfaf40)
"let*" (0x5fbfb260)
0x509f180 Lisp type 6
"apply" (0x5fbfb5b0)
0x5b1ce30 Lisp type 6
"slime-dispatch-event" (0x5fbfc0d0)
"slime-process-available-input" (0x5fbfc750)
"slime-net-filter" (0x5fbfcdc8)
--------------------------------

So this is triggered by animate-string which slime uses. Weirdly, the
same code doesn't have this error in 24.2.

Also if I set inhibit-eval-during-redisplay to t, the error is gone as
well.

Leo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]