From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: How can I debug a problem triggered from jit-lock's background fontification? Date: Mon, 07 Mar 2011 23:58:05 -0800 Message-ID: <4D75E18D.4010009@gmail.com> References: <20110206205403.GA5978@muc.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDF6ED181CC09465BFE3B2DCA" X-Trace: dough.gmane.org 1299571106 17170 80.91.229.12 (8 Mar 2011 07:58:26 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 8 Mar 2011 07:58:26 +0000 (UTC) Cc: Alan Mackenzie , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 08 08:58:22 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PwroC-00049T-Ty for ged-emacs-devel@m.gmane.org; Tue, 08 Mar 2011 08:58:21 +0100 Original-Received: from localhost ([127.0.0.1]:35419 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PwroC-00041f-BE for ged-emacs-devel@m.gmane.org; Tue, 08 Mar 2011 02:58:20 -0500 Original-Received: from [140.186.70.92] (port=36449 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pwro6-00041X-0C for emacs-devel@gnu.org; Tue, 08 Mar 2011 02:58:15 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pwro4-0008Kv-Ma for emacs-devel@gnu.org; Tue, 08 Mar 2011 02:58:13 -0500 Original-Received: from mail-iw0-f169.google.com ([209.85.214.169]:63564) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pwro4-0008Kl-ID for emacs-devel@gnu.org; Tue, 08 Mar 2011 02:58:12 -0500 Original-Received: by iwl42 with SMTP id 42so6494933iwl.0 for ; Mon, 07 Mar 2011 23:58:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type; bh=32fjOZ0lXSy0Ioy7fXfdV19QWZTrPNLLNfTGHe4ZB2c=; b=VHmIOdZvB6x7/IL0RKV0cPXXd/Eyh5vvvh5NbNgogR6wBfHptfC23ENQyjQBF68/mq 5SBMonQQ80PrG4GDaRqM7EcMwiLf4QwXK0piSxWEgskN7SmbYkePxeB2L4cpJIz7XFOG 30qqhIz8M4PpFMXheqs8M2BRRH9+maDx9DzFY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type; b=OMFQSNK+oPa3GuP3CTpM14gAzjGfTZSLrzfgpVBL4FkfisDqEVQf2Q6GqJQ2V8ssFR /4IQRdlKLcYj3tqwAaHUqaAE+K7sD5iFaLla61fKMhrPLyipzkvHC3Z9u+sVqnHyyk7A Bu8b1s7ZqGnTaiW3RZ+sGpF9SshHRpbjnV2cc= Original-Received: by 10.43.59.130 with SMTP id wo2mr4064310icb.88.1299571091849; Mon, 07 Mar 2011 23:58:11 -0800 (PST) Original-Received: from [192.168.1.2] (c-67-183-23-114.hsd1.wa.comcast.net [67.183.23.114]) by mx.google.com with ESMTPS id 19sm412053ibx.1.2011.03.07.23.58.07 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 07 Mar 2011 23:58:08 -0800 (PST) User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 In-Reply-To: X-Enigmail-Version: 1.1.1 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.214.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:136870 Archived-At: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDF6ED181CC09465BFE3B2DCA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2/7/11 7:40 AM, Stefan Monnier wrote: >> I have instrumented the CC Mode function for Edebug, yet something see= ms >> to be inhibiting the invocation of Edebug from inside jit. No doubt >> there's a good reason for this, but it has been getting on my nerves f= or >> years. I've run into this problem as well. I actually use lazy-lock for C and C++ (because the deferred fontification seems to work better), and the failure mode there even stranger: when breaking into edebug, emacs will split the current window as many times as it can until something dies from stack exhaustion. I can usually recover from this situation by switching to another buffer, killing the original, and killing the excess windows, but it's quite annoying. > Yes, the problem is that jit-lock is called when redisplay is needed so= > it's tricky to let Edebug work at this time (it's easy to make it work > with redisplay inhibited, but then you'll need to use it blindly ;-). What about redisplay to a tty frame? >> Would somebody please suggest a way I can debug the actions of >> jit-locking from Edebug, or possibly some other way of making progress= =2E >=20 > I've had to deal with this problem, as you can imagine, and I feel > your pain. The way I generally handle this problem is as follows: Speaking of which, quitting Emacs in the middle of a hard lisp loop during redisplay on X11 (GTK and no-toolkit), nor OS X (AppKit) doesn't seem to have any effect. I've discovered that running under gdb, breaking into Emacs with C-z, and setting debug_on_next_call to 1 works, but it's cumbersome. Is quitting during redisplay *supposed* to work? --------------enigDF6ED181CC09465BFE3B2DCA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) iEYEARECAAYFAk114Y8ACgkQ17c2LVA10Vt0PQCfdeAakogYME0WtroQczTReed0 JgoAoOfkG55frNoJTxH6YJZ7vHt7/u5s =DLR2 -----END PGP SIGNATURE----- --------------enigDF6ED181CC09465BFE3B2DCA--