[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to debug Error during redisplay
From: |
Eli Zaretskii |
Subject: |
Re: How to debug Error during redisplay |
Date: |
Fri, 11 Jan 2013 16:08:27 +0200 |
> From: Leo Liu <address@hidden>
> Date: Fri, 11 Jan 2013 19:02:29 +0800
>
> 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.
(gdb) pp current_buffer->name_
or
(gdb) p current_buffer->name_
(gdb) xstring
> So this is triggered by animate-string which slime uses. Weirdly, the
> same code doesn't have this error in 24.2.
Which code is that? can you show it? Or does any use of
animate-string trigger these messages?
> Also if I set inhibit-eval-during-redisplay to t, the error is gone as
> well.
This should not surprise you, since that flag inhibits evaluation of
Lisp expressions during redisplay, including whatever expression that
causes the error.
- How to debug Error during redisplay, Leo Liu, 2013/01/11
- Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/11
- Re: How to debug Error during redisplay, Leo Liu, 2013/01/11
- Re: How to debug Error during redisplay,
Eli Zaretskii <=
- Re: How to debug Error during redisplay, Leo Liu, 2013/01/12
- Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/12
- Re: How to debug Error during redisplay, Leo Liu, 2013/01/12
- Re: How to debug Error during redisplay, Leo Liu, 2013/01/12
- Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/12
- Re: How to debug Error during redisplay, Leo Liu, 2013/01/12
- Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/12
- Re: How to debug Error during redisplay, Stephen Berman, 2013/01/12
- Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/12
Re: How to debug Error during redisplay, Stefan Monnier, 2013/01/11