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 21:38:15 +0800 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1357997922 16147 80.91.229.3 (12 Jan 2013 13:38:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 12 Jan 2013 13:38:42 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 12 14:38:56 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 1Tu1IW-0000PX-C7 for ged-emacs-devel@m.gmane.org; Sat, 12 Jan 2013 14:38:56 +0100 Original-Received: from localhost ([::1]:41880 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tu1IG-0001Ac-De for ged-emacs-devel@m.gmane.org; Sat, 12 Jan 2013 08:38:40 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:35796) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tu1IC-0001AX-Lf for emacs-devel@gnu.org; Sat, 12 Jan 2013 08:38:39 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tu1IB-0005Ez-8m for emacs-devel@gnu.org; Sat, 12 Jan 2013 08:38:36 -0500 Original-Received: from mail-da0-f43.google.com ([209.85.210.43]:33073) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tu1IB-0005Es-2p for emacs-devel@gnu.org; Sat, 12 Jan 2013 08:38:35 -0500 Original-Received: by mail-da0-f43.google.com with SMTP id u36so1176570dak.16 for ; Sat, 12 Jan 2013 05:38:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:references:face:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=sfOzDgtD8PaLncgJlsjOfdFsvQmqmJIH1MSm3VBnsIA=; b=lI0PcTvja6LkP8W27zARSnwBbx+3ZQTzyCfLyapRUy3Vp5iste6Pe0VwbanwgmtYTo RQugql6CJ75ok7tJrA7f6FvmAEC5fb6FiBV9UsnBH2Q9lSb04eIKId9pIQYh9NyoPU6j UYp+yno7OfMj32f2gEAlnkuz6f2Qt1PueK4CYAOqGpDTCuIe2JUWdX73fNf29Auzn5O2 fDurzMmjJYBPW9drGvZZcFGsRYAJVGycTIy0KwszaxhvdJjOHw6+DGNb/ZUQYzxUDv1p fhWwarmP6ZEDTBwTR07kx29bXETXFBvq7t0E1x5Fv89X6Aq8NlsJT8FWqx4nGYSeZpku l5lw== X-Received: by 10.68.245.167 with SMTP id xp7mr241294912pbc.75.1357997914171; Sat, 12 Jan 2013 05:38:34 -0800 (PST) Original-Received: from localhost ([182.48.109.8]) by mx.google.com with ESMTPS id qb3sm4635396pbb.35.2013.01.12.05.38.27 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sat, 12 Jan 2013 05:38:33 -0800 (PST) Face: iVBORw0KGgoAAAANSUhEUgAAACkAAAApAQAAAACAGz1bAAABKElEQVQYlWNg3NIt5FDPUPt7 4+X79Qyucz5/ugik+L2PBgKpyphaIK921q23QDnG0NBQoMr/vaWl9f8ZLL78uPv5PwN7RETfzXoG jhmFz27XM0RXmpuY/WfY+fv0Mc56BvFybfXA/wwL5t/wF61n2PU59axXPcOVzbmSW/8zrNt1benC /ww70hqUU/4zKCtrT9jwn8FhwynbufUMendE2aLqGRpdX9al1zM8eh17lKeeQcTMrdD5P8P3j/YT Q/8zXHSb7p1Qz/C4OM2JuZ7hgtI7K6AjqsMnf8j4z8C6xG1tw3+GqpqvsVn/GTzmpD9j/8/wP/oZ S/l/Bka+QO/g/wy15ueeFQL9N1O8mPU/g+umV3t1gdT0/1bTgHLqYVeXAlWKpMWt+w8Az82C9nHf X0cAAAAASUVORK5CYII= In-Reply-To: (Stefan Monnier's message of "Sat, 12 Jan 2013 08:08:53 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.91 (OS X 10.8.2) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 209.85.210.43 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:156273 Archived-At: On 2013-01-12 21:08 +0800, Stefan Monnier wrote: > We should really improve jit-lock.el to provide a "debugging mode" where > it somehow runs the code at some other time than during redisplay, so it > can be debugged better. Is it possible to teach it to be verbose in this case? In time of this, I find myself hoping the message can tell me which function other than jit-lock-function has caused the error. Leo