From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Leo Liu Newsgroups: gmane.emacs.devel Subject: Re: How to debug Error during redisplay Date: Sat, 12 Jan 2013 13:25:10 +0800 Message-ID: References: <83bocwuidc.fsf@gnu.org> <837gnjvmlg.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1357968336 28205 80.91.229.3 (12 Jan 2013 05:25:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 12 Jan 2013 05:25:36 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 12 06:25:54 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TttbK-0007Vw-BH for ged-emacs-devel@m.gmane.org; Sat, 12 Jan 2013 06:25:50 +0100 Original-Received: from localhost ([::1]:47588 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tttb4-0003ej-8x for ged-emacs-devel@m.gmane.org; Sat, 12 Jan 2013 00:25:34 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:50906) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tttb1-0003ee-DN for emacs-devel@gnu.org; Sat, 12 Jan 2013 00:25:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tttaz-0007P6-68 for emacs-devel@gnu.org; Sat, 12 Jan 2013 00:25:31 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:36377) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tttay-0007P2-Va for emacs-devel@gnu.org; Sat, 12 Jan 2013 00:25:29 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Tttb8-0007NI-WD for emacs-devel@gnu.org; Sat, 12 Jan 2013 06:25:39 +0100 Original-Received: from 119.255.41.67 ([119.255.41.67]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 12 Jan 2013 06:25:38 +0100 Original-Received: from sdl.web by 119.255.41.67 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 12 Jan 2013 06:25:38 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 30 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 119.255.41.67 Face: iVBORw0KGgoAAAANSUhEUgAAACgAAAAoBAMAAAB+0KVeAAAAGFBMVEUzRVhbQj4eZqO6SjnT eWpxnMetm5b6/PmidmqrAAAAAWJLR0QAiAUdSAAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1F B9cBBwMLBfKABCMAAAFoSURBVCjPtZI9a8MwEIaFoc7aYDdelQMna0Em3tsSr0XUeE2Q6a22a+v+ fk8fSSBkbDUI6dHpfe9OEvRgiD+ApqKPJgJeB6iUUXWESjUe/ig38AJrhqqvaU2nTIXbNvOQ40fe qdry4kyGoVWsfCQalXpHnJGM01wjWdYbMlXNFdsZDO69m9aqNqxEJqTEgbM5OF7wlEfIoll1Ked4 LbM5X2EdILLokEdmI8z7g5cKED0cuTC930TYhy7ZDekkXVGw/L60TguJePPxcJF48lpsSUWEA/Ju jGFNgJOXc4Hz7TmAdBeu5Ve4AEjOi2/2jfd3cAJZ+IbNrvdjgBZY01b+HTuG3cLws6BJZqVOj/pp T0OqVwx3rFq+QmJwx3loK5JSLEhDIt62+mtC2C+SrAUxEbV6C6v2BRbd6pILBKFpepKZJHgGgrKF sptSUUoczpwg2pQ7ZH1tgs0ou/917mzz6Cs2//C978cv5l07L02orIEAAAAASUVORK5CYII= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.92 (OS X 10.8.2) Cancel-Lock: sha1:xEJz2aAAHuHhICXcj+s7kDstY7U= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:156249 Archived-At: On 2013-01-11 22:08 +0800, Eli Zaretskii wrote: > (gdb) pp current_buffer->name_ > > or > > (gdb) p current_buffer->name_ > (gdb) xstring Thanks. I figured it out too by reading DEBUG more carefully. >> 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? I mean the slime package, the same one running in 24.2 and 24.2.92. It seems to me that in 24.2.92, the code is able to continue without waiting for animate-string to finish. It feels more responsive. >> 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. Thanks. Leo