From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Monnier Subject: bug#17484: 24.3.91; Emacs Pretest (emacs-24.3.91.tar.xz) freeze Date: Wed, 14 May 2014 12:52:53 -0400 Message-ID: References: <87d2fiaxjw.fsf@tanger.home> <87tx8tajs5.fsf@tanger.home> <87r43x5fmm.fsf@tanger.home> <8761l958zb.fsf@tanger.home> <8761l84du5.fsf@tanger.home> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47088) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WkcRW-0004dj-Sn for emacs-orgmode@gnu.org; Wed, 14 May 2014 12:54:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WkcRP-0005Er-EF for emacs-orgmode@gnu.org; Wed, 14 May 2014 12:54:10 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <8761l84du5.fsf@tanger.home> (daimrod@gmail.com's message of "Wed, 14 May 2014 23:47:14 +0900") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Daimrod Cc: Carsten Dominik , 17484@debbugs.gnu.org > Is there a way to disable the effect of `inhibit-quit' in `jit-lock' so > C-g interrupt again in order to get an elisp-backtrace with > `debug-on-quit'. > Otherwise, what's the best way to debug this? Looking closer at > `org-adaptive-fill-function'? You can try `debug-on-event'. There's jit-lock-debug-mode but it doesn't disable inhibit-quit. So you'll need to additionally use (advice-add 'jit-lock--debug-fontify :around (lambda (fun &rest args) (with-local-quit (apply fun args)))) Of course sometimes this doesn't work because jit-lock-debug-mode changes the way things are executed and the bug may not manifest itself any more, but it's worth a try. Another source of info is to M-x trace-function RET org-adaptive-fill-function RET M-x trace-function RET org-element-at-point RET M-x trace-function RET org-element--cache-sync RET M-x trace-function RET org-element--cache-process-request RET Then reproduce the hang, then break the hang somehow (maybe with the jit-lock-debug hack above, or maybe with debug-on-event, or with C-g C-g C-g, ...), then look at the *trace..* buffer. Stefan