From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Daimrod <daimrod@gmail.com>
Cc: Carsten Dominik <carsten@orgmode.org>, 17484@debbugs.gnu.org
Subject: bug#17484: 24.3.91; Emacs Pretest (emacs-24.3.91.tar.xz) freeze
Date: Wed, 14 May 2014 12:52:53 -0400 [thread overview]
Message-ID: <jwvvbt8uxd3.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <8761l84du5.fsf@tanger.home> (daimrod@gmail.com's message of "Wed, 14 May 2014 23:47:14 +0900")
> 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
next prev parent reply other threads:[~2014-05-14 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87d2fiaxjw.fsf@tanger.home>
[not found] ` <jwvzjilygsq.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <87tx8tajs5.fsf@tanger.home>
2014-05-13 17:59 ` bug#17484: 24.3.91; Emacs Pretest (emacs-24.3.91.tar.xz) freeze Stefan Monnier
2014-05-14 1:12 ` Daimrod
2014-05-14 3:34 ` Daimrod
2014-05-15 9:58 ` Bastien
[not found] ` <8738gbtlce.fsf@bzg.ath.cx>
2014-05-15 10:11 ` Daimrod
[not found] ` <87d2ff1hcw.fsf__9581.27144626833$1400148801$gmane$org@tanger.home>
2014-05-15 10:23 ` Bastien
[not found] ` <878uq3s5lf.fsf@bzg.ath.cx>
2014-05-15 12:30 ` Daimrod
[not found] ` <8761l958zb.fsf@tanger.home>
2014-05-14 13:37 ` Stefan Monnier
[not found] ` <jwvk39owkip.fsf-monnier+emacsbugs@gnu.org>
2014-05-14 14:47 ` Daimrod
2014-05-14 16:52 ` Stefan Monnier [this message]
2014-05-29 2:52 ` Daimrod
2014-05-29 4:07 ` 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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvvbt8uxd3.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=17484@debbugs.gnu.org \
--cc=carsten@orgmode.org \
--cc=daimrod@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).