unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ihor Radchenko <yantar92@posteo.net>, 60352@debbugs.gnu.org
Subject: bug#60352: 30.0.50; Keep getting "Error in syntax_table logic for to-the-end intervals"
Date: Tue, 27 Dec 2022 10:13:21 -0500	[thread overview]
Message-ID: <jwvv8lw7vdm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83tu1h10qu.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 27 Dec 2022 14:37:13 +0200")

>> Debugger entered--Lisp error: (error "Error in syntax_table logic for to-the-end intervals")
>>   (re-search-forward "\\(?:\\(?:\\<DEADLINE: *\\(\\(?:<\\(?:[[:digit:]]\\{4\\}-[..." nil move)
>>
>> It only happens in Emacs 30 (master) and is not regular.
>>
>> The error sounds like some kind of internal error.

It is, indeed.

>> Does it signify some Emacs issue? Or may it be third-party code issue?

No, it's a bug in the C code somewhere.
Presumably somewhere between the `regexp-emacs.c` code and the
`syntax.c` code.

The regexp code keeps a global state in `gl_state` to speed up looks up
of the `syntax-table` text-property.  The above error indicates that
this global state is inconsistent for some reason.

Maybe we somehow ran a regexp search during the regexp search?
I know this can happen via the automatic calls to `syntax-propertize`,
but `syntax.c:parse_sexp_propertize` is careful to (re)call
`SETUP_SYNTAX_TABLE` after running ELisp code, so that shouldn't be the
source of the problem.

Maybe there's some other way to re-enter regexp search and that one
isn't careful to call `SETUP_SYNTAX_TABLE` before returning to the outer
regexp search?


        Stefan






  reply	other threads:[~2022-12-27 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27  9:41 bug#60352: 30.0.50; Keep getting "Error in syntax_table logic for to-the-end intervals" Ihor Radchenko
2022-12-27 12:37 ` Eli Zaretskii
2022-12-27 15:13   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-01-20 14:10 ` Ihor Radchenko
2023-01-20 15:13   ` Eli Zaretskii

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=jwvv8lw7vdm.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=60352@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=yantar92@posteo.net \
    /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).