From: Eli Zaretskii <eliz@gnu.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: How to debug Error during redisplay
Date: Sat, 12 Jan 2013 14:30:32 +0200 [thread overview]
Message-ID: <831udqtwgn.fsf@gnu.org> (raw)
In-Reply-To: <m2zk0ek41g.fsf@gmail.com>
> From: Leo Liu <sdl.web@gmail.com>
> Date: Sat, 12 Jan 2013 19:56:59 +0800
>
> 1. Install adaptive-wrap.el from ELPA
> 2. Install sbcl or clisp or any CL supported by slime
> 1. Emacs -q -l t.el (t.el assumes sbcl, which you may want to change)
> 2. M-x slime
Thanks, so it sounds like the culprit might be adaptive-wrap, and not
slime or animate-string.
However, I hope there's a simpler way to debug this. Please run Emacs
under GDB, put a breakpoint in Fstringp, where it is about to return
Qnil:
DEFUN ("stringp", Fstringp, Sstringp, 1, 1, 0,
doc: /* Return t if OBJECT is a string. */)
(Lisp_Object object)
{
if (STRINGP (object))
return Qt;
return Qnil; <<<<<<<<<<<<<<<<<<<<<<<<
}
and then run your recipe to reproduce the problem. (I hope this
breakpoint won't break too many times in unrelated cases; if it does,
we can figure out a way to make the breakpoint smarter.) When the
breakpoint breaks, the backtrace should tell us which Lisp code caused
it. Please show both the C and Lisp parts of the backtrace.
Thanks.
next prev parent reply other threads:[~2013-01-12 12:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 9:03 How to debug Error during redisplay Leo Liu
2013-01-11 10:25 ` Eli Zaretskii
2013-01-11 11:02 ` Leo Liu
2013-01-11 14:08 ` Eli Zaretskii
2013-01-12 5:25 ` Leo Liu
2013-01-12 9:43 ` Eli Zaretskii
2013-01-12 11:56 ` Leo Liu
2013-01-12 12:03 ` Leo Liu
2013-01-12 13:49 ` Eli Zaretskii
2013-01-12 13:58 ` Leo Liu
2013-01-12 14:31 ` Eli Zaretskii
2013-01-12 17:17 ` Stephen Berman
2013-01-12 12:30 ` Eli Zaretskii [this message]
2013-01-11 14:56 ` Stefan Monnier
2013-01-12 5:26 ` Leo Liu
2013-01-12 13:08 ` Stefan Monnier
2013-01-12 13:38 ` Leo Liu
2013-01-12 13:52 ` Eli Zaretskii
2013-01-12 14:07 ` Leo Liu
2013-01-12 14:38 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831udqtwgn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sdl.web@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.