From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 34910@debbugs.gnu.org
Subject: bug#34910: 27.0.50; Too much matching reentrancy
Date: Tue, 19 Mar 2019 12:01:42 +0200 [thread overview]
Message-ID: <8336njuqrd.fsf@gnu.org> (raw)
In-Reply-To: <443195D9-DFEB-4E67-AEFE-556C3D900113@acm.org> (message from Mattias Engdegård on Tue, 19 Mar 2019 10:27:09 +0100)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Tue, 19 Mar 2019 10:27:09 +0100
> Cc: dancol@dancol.org, 34910@debbugs.gnu.org
>
> The should be no question that "stack overflow" + debugger is the correct and intended behaviour, should it?
I don't know yet. I asked you to elaborate on the reasons for your
expectations, and I still hope you will humor me. Because just
taking the problem's manifestations at face value, one could argue
that the precise error message is immaterial, as long as it points to
the right direction, and "stack overflow in regexp matcher" is as
obscure as the other message. But maybe I'm missing something, which
is why I asked you to elaborate on your reasoning.
Thanks.
next prev parent reply other threads:[~2019-03-19 10:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 21:34 bug#34910: 27.0.50; Too much matching reentrancy Mattias Engdegård
2019-03-19 8:05 ` Eli Zaretskii
2019-03-19 9:27 ` Mattias Engdegård
2019-03-19 10:01 ` Eli Zaretskii [this message]
2019-03-19 12:25 ` Mattias Engdegård
2019-03-19 12:31 ` Eli Zaretskii
2019-03-30 9:29 ` Eli Zaretskii
2019-03-19 12:50 ` Mattias Engdegård
2019-03-30 9:30 ` Eli Zaretskii
2019-03-30 11:18 ` Mattias Engdegård
2019-03-30 14:52 ` Daniel Colascione
2019-03-30 12:55 ` Stefan Monnier
2019-03-30 13:05 ` Mattias Engdegård
2019-03-30 13:37 ` Eli Zaretskii
2019-03-30 16:22 ` Stefan Monnier
2019-03-30 17:10 ` Daniel Colascione
2019-03-30 19:06 ` Mattias Engdegård
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8336njuqrd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34910@debbugs.gnu.org \
--cc=mattiase@acm.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.