From: Eli Zaretskii <eliz@gnu.org>
To: Nathan Trapuzzano <nbtrap@nbtrap.com>
Cc: 15778@debbugs.gnu.org
Subject: bug#15778: 24.3; cperl-mode causes emacs to lock up
Date: Fri, 01 Nov 2013 16:41:20 +0200 [thread overview]
Message-ID: <83iowcb2wf.fsf@gnu.org> (raw)
In-Reply-To: <87mwlob9lz.fsf@nbtrap.com>
> From: Nathan Trapuzzano <nbtrap@nbtrap.com>
> Cc: 15778@debbugs.gnu.org
> Date: Fri, 01 Nov 2013 08:16:24 -0400
>
> > Please attach a debugger and show the backtrace. The file etc/DEBUG
> > explains how to look for a place that infloops, perhaps you could
> > follow that and provide a more detailed information.
>
> There's an infinite loop somewhere in exec_byte_code. I've attached the
> backtrace at the point. Moreover, sending emacs a SIGUSR2 does invoke
> the lisp debugger with the following message:
>
> Debugger entered--entering a function:
> * #[0 "\301\300\302\"\207" [(0 1) set-match-data evaporate] 3 "\n\n(fn)"]()
> * funcall(#[0 "\301\300\302\"\207" [(0 1) set-match-data evaporate] 3 "\n\n(fn)"])
> jit-lock-fontify-now(1111 1611)
> jit-lock-function(1111)
> redisplay_internal\ \(C\ function\)()
>
> If this is not enough, I can try to look into it more later.
I cannot reproduce this. Does it happen in "emacs -Q"?
next prev parent reply other threads:[~2013-11-01 14:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 11:19 bug#15778: 24.3; cperl-mode causes emacs to lock up Nathan Trapuzzano
2013-11-01 11:46 ` Eli Zaretskii
2013-11-01 12:16 ` Nathan Trapuzzano
2013-11-01 14:41 ` Eli Zaretskii [this message]
2013-11-01 14:59 ` Nathan Trapuzzano
2013-11-01 16:26 ` Eli Zaretskii
2013-11-01 17:21 ` Nathan Trapuzzano
2013-11-01 20:23 ` Stephen Berman
2013-11-03 0:00 ` Stephen Berman
2013-11-03 12:00 ` Nathan Trapuzzano
2013-11-03 13:41 ` Stephen Berman
2013-11-03 13:59 ` Nathan Trapuzzano
2013-11-03 19:39 ` Stephen Berman
2013-11-03 19:48 ` Nathan Trapuzzano
2013-11-03 22:22 ` Stephen Berman
2013-11-03 22:50 ` Nathan Trapuzzano
2013-11-04 1:48 ` Stefan Monnier
2013-11-04 2:29 ` Nathan Trapuzzano
2013-11-04 3:52 ` Stefan Monnier
2013-11-03 14:15 ` Stefan Monnier
2013-11-03 14:23 ` Nathan Trapuzzano
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83iowcb2wf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15778@debbugs.gnu.org \
--cc=nbtrap@nbtrap.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.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).