From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28850@debbugs.gnu.org
Subject: bug#28850: 26.0.90; Error running timer 'jit-lock-stealth-fontify': (error "Invalid search bound (wrong side of point)")
Date: Tue, 17 Oct 2017 16:42:34 +0000 [thread overview]
Message-ID: <20171017164234.GA4725@ACM> (raw)
In-Reply-To: <83lgkcgzs9.fsf@gnu.org>
Hello, Eli.
On Sun, Oct 15, 2017 at 19:07:50 +0300, Eli Zaretskii wrote:
> This bug is bugging me for quite some time now, and my hopes for it to
> be resolved are now gone, so I finally sat down to debug it.
> I have jit-lock-stealth turned on in my sessions, so whenever I
> restart Emacs (e.g., when I build a new binary, or after a system
> restart), and restore my session using desktop.el, Emacs starts
> fontifying in the background. At some point, sometimes more than
> once, I get this error:
> Error running timer 'jit-lock-stealth-fontify': (error "Invalid search bound (wrong side of point)")
> Today I ran Emacs under a debugger, and caught this error. The
> details are below, but in a nutshell, CC mode's fontification
> functions call re-search-forward with BOUND that is before point. I
> hope the data below is enough to understand why that happens and fix
> it; if not, please tell what additional data is needed to diagnose the
> problem.
> Here're the C and Lisp backtraces from the error, and some relevant
> data that explains why the error happened:
Thanks for the bug report, and what you've worked out, so far. I'm
afraid it's going to be several days before I get a chance to look at it
properly, with things in Real Life interfering significantly at the
moment. I will look at it, though.
[ .... ]
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-10-17 16:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 16:07 bug#28850: 26.0.90; Error running timer 'jit-lock-stealth-fontify': (error "Invalid search bound (wrong side of point)") Eli Zaretskii
2017-10-17 16:42 ` Alan Mackenzie [this message]
2017-10-22 20:13 ` Alan Mackenzie
2017-10-24 14:46 ` Eli Zaretskii
2017-10-24 20:33 ` Alan Mackenzie
2017-10-25 19:11 ` Alan Mackenzie
2017-10-26 16:44 ` Eli Zaretskii
2017-10-26 18:36 ` Alan Mackenzie
2019-04-30 1:51 ` Basil L. Contovounesios
2019-04-30 9:24 ` Alan Mackenzie
2019-04-30 11:33 ` Alan Mackenzie
2019-04-30 12:57 ` Basil L. Contovounesios
2019-04-30 13:32 ` Alan Mackenzie
2019-04-30 13:44 ` Basil L. Contovounesios
2019-04-30 15:35 ` Eli Zaretskii
2019-04-30 15:50 ` Alan Mackenzie
2019-05-06 18:44 ` Alan Mackenzie
2019-05-07 0:35 ` Basil L. Contovounesios
2019-04-30 15:30 ` Eli Zaretskii
2019-04-30 15:43 ` Alan Mackenzie
2019-04-30 15:26 ` Eli Zaretskii
2019-05-01 18:49 ` Eli Zaretskii
2019-05-04 12:41 ` Alan Mackenzie
2019-05-04 13:36 ` Eli Zaretskii
2019-05-05 9:06 ` Alan Mackenzie
2019-05-06 15:35 ` Eli Zaretskii
2019-05-06 18:10 ` Alan Mackenzie
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=20171017164234.GA4725@ACM \
--to=acm@muc.de \
--cc=28850@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).