From: Juri Linkov <juri@linkov.net>
To: 63272@debbugs.gnu.org
Subject: bug#63272: 29.0.90; xref fails on long lines
Date: Thu, 04 May 2023 18:07:46 +0300 [thread overview]
Message-ID: <86fs8cxr79.fsf@mail.linkov.net> (raw)
1. Create a file with a long line, e.g. type
a C-u 500000 b c
Save the file and commit to git.
(long-line-optimizations-p returns t)
2. Try to search a regexp that matches the whole long line, e.g.
C-x p g a.*c RET
Debugger entered--Lisp error: (error "Stack overflow in regexp matcher")
xref--collect-matches-1("a.*c" "/tmp/file" 1 1 500003 nil)
xref--collect-matches((1 "/tmp/file" "abbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb...") "a.*c" #<buffer *xref-temp*> nil)
#f(compiled-function (hit) #<bytecode 0x122b1e80d7055e69>)((1 "/tmp/file" "abbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb..."))
xref--convert-hits(((1 "/tmp/file" "abbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb...")) "a.*c")
xref-matches-in-files("a.*c" ("/tmp/file"))
project--find-regexp-in-files("a.*c" ("/tmp/file"))
apply(project--find-regexp-in-files ("a.*c" ("/tmp/file")))
#f(compiled-function (&rest args2) #<bytecode -0xae28f07f9498cbf>)()
xref--show-xref-buffer(#f(compiled-function (&rest args2) #<bytecode -0xae28f07f9498cbf>) ((window . #<window 3 on tmp>) (display-action) (auto-jump)))
xref--show-xrefs(#f(compiled-function (&rest args2) #<bytecode -0xae28f07f9498cbf>) nil)
xref-show-xrefs(#f(compiled-function (&rest args2) #<bytecode -0xae28f07f9498cbf>) nil)
project-find-regexp("a.*c")
funcall-interactively(project-find-regexp "a.*c")
call-interactively(project-find-regexp nil nil)
command-execute(project-find-regexp)
next reply other threads:[~2023-05-04 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 15:07 Juri Linkov [this message]
2023-05-04 15:33 ` bug#63272: 29.0.90; xref fails on long lines Dmitry Gutov
2023-05-05 17:50 ` Juri Linkov
2023-05-05 20:49 ` Dmitry Gutov
2023-05-08 15:41 ` Juri Linkov
2023-05-08 18:59 ` Dmitry Gutov
2023-05-04 15:58 ` Gregory Heytings
2023-05-05 9:13 ` Gregory Heytings
2023-05-05 17:39 ` Juri Linkov
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=86fs8cxr79.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=63272@debbugs.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).