unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: 张海君 <netjune@icloud.com>
To: Alan Mackenzie <acm@muc.de>
Cc: "21205@debbugs.gnu.org" <21205@debbugs.gnu.org>
Subject: bug#21205: Error during redisplay: (jit-lock-function 3491)
Date: Mon, 10 Aug 2015 22:43:26 +0800	[thread overview]
Message-ID: <786E8547-4CDE-4693-B13B-0EAAEEA64045@icloud.com> (raw)
In-Reply-To: <20150807205255.GA2653@acm.fritz.box>

Yes, it is fixed. Thanks for your great work!

> 在 2015年8月8日,04:52,Alan Mackenzie <acm@muc.de> 写道:
> 
> Hello, Eli and Netjune.
> 
> On Fri, Aug 07, 2015 at 03:54:10PM +0300, Eli Zaretskii wrote:
>>> From: 张海君 <netjune@icloud.com>
>>> Date: Fri, 07 Aug 2015 18:43:54 +0800
> 
>>> Run emacs with "emacs -Q", and then eval the following code:
>>> ------------------------------------------------------------
>>> (setq font-lock-maximum-decoration 2
>>>      jit-lock-defer-time 0.05)
>>> (setq-default show-trailing-whitespace t)
>>> ------------------------------------------------------------
> 
>>> Then open the attached c file, and scroll down the buffer with key C-v C-v ... until the end of buffer.
>>> Switch to the message buffer *Message*. There are some error message as the following:
>>> ------------------------------------------------------------------------------
>>> Error during redisplay: (jit-lock-function 3102) signaled (error "Invalid search bound (wrong side of point)")
> 
>> The errors are triggered by c-syntactic-re-search-forward.  Here's the
>> backtrace from the first such error, with the current master:
> 
> [ .... ]
> 
>>  Lisp Backtrace:
>>  "re-search-forward" (0x825430)
>>  "c-syntactic-re-search-forward" (0x8259f0)
>>  "c-font-lock-declarators" (0x825fd0)
>>  0x1c9cda0 PVEC_COMPILED
>>  "font-lock-fontify-keywords-region" (0x826b30)
>>  "font-lock-default-fontify-region" (0x8270d0)
>>  "c-font-lock-fontify-region" (0x827680)
>>  "font-lock-fontify-region" (0x827c28)
> 
> [ .... ]
> 
> Thanks for that, Eli!  It made it fairly easy to track down the bug,
> which was simply failing to check if point had advanced too far at one
> critical place in c-font-lock-declarators.
> 
> Netjune: would you please try out the following patch (it should apply
> cleanly to the cc-fonts.el in ..../emacs-24.5/lisp/progmodes/), and
> confirm that the bug has been fixed, or tell me what is still causing
> problems.
> 
> 
> 
> diff -r 88b4140d56af cc-fonts.el
> --- a/cc-fonts.el    Tue May 12 10:03:55 2015 +0000
> +++ b/cc-fonts.el    Fri Aug 07 20:41:38 2015 +0000
> @@ -1141,6 +1141,7 @@
>                 (looking-at "{"))
>            (c-safe (c-forward-sexp) t) ; over { .... }
>              t)
> +            (< (point) limit)
>            ;; FIXME: Should look for c-decl-end markers here;
>            ;; we might go far into the following declarations
>            ;; in e.g. ObjC mode (see e.g. methods-4.m).
> 
> 
> Thanks for the bug report!
> 
> -- 
> Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2015-08-10 14:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 10:43 bug#21205: Error during redisplay: (jit-lock-function 3491) 张海君
2015-08-07 12:54 ` Eli Zaretskii
2015-08-07 20:52   ` Alan Mackenzie
2015-08-10 14:43     ` 张海君 [this message]
2015-08-10 17:27       ` 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=786E8547-4CDE-4693-B13B-0EAAEEA64045@icloud.com \
    --to=netjune@icloud.com \
    --cc=21205@debbugs.gnu.org \
    --cc=acm@muc.de \
    /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).