From: Lars Ingebrigtsen <larsi@gnus.org>
To: Pip Cet <pipcet@gmail.com>
Cc: Andy Moreton <andrewjmoreton@gmail.com>,
46906@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#46906: 28.0.50; byte compiler infloops trying to compile infloop
Date: Fri, 05 Mar 2021 14:16:04 +0100 [thread overview]
Message-ID: <87o8fxrbaj.fsf@gnus.org> (raw)
In-Reply-To: <CAOqdjBe4_aMTO13XjkZq3SOSHEEb7R9pBXsiN=YhJAPx0mnFaw@mail.gmail.com> (Pip Cet's message of "Thu, 4 Mar 2021 12:15:17 +0000")
Pip Cet <pipcet@gmail.com> writes:
> I think we're just going to have to put in a test which, on systems
> with the bug, loops indefinitely. We could make it "expensive", though
> it isn't, really.
>
> (I'm not sure how many people are trying to run the Emacs 28 testsuite
> against Emacs 27, or anything like that. It might be a non-issue.)
It's probably not an issue in practice, but it does seem rather
unsatisfactory that we don't have a mechanism for doing tests for
infloops in general.
I wonder whether we could cobble up something just for ert. For
instance... doing a
(start-process ... "sleep 1; kill -s SIGUSR1 $EMACS_PID") or similar,
and then hook the SIGUSR1 handler to... er... do something useful
here.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-03-05 13:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 21:14 bug#46906: 28.0.50; byte compiler infloops trying to compile infloop Pip Cet
2021-03-03 21:44 ` Pip Cet
2021-03-03 23:33 ` Andy Moreton
2021-03-04 7:17 ` Pip Cet
2021-03-04 9:15 ` Juri Linkov
2021-03-04 10:19 ` Pip Cet
2021-03-04 11:16 ` Lars Ingebrigtsen
2021-03-04 12:15 ` Pip Cet
2021-03-05 13:16 ` Lars Ingebrigtsen [this message]
2021-03-04 17:58 ` Juri Linkov
2021-03-04 18:50 ` Pip Cet
2021-03-05 13:17 ` Lars Ingebrigtsen
2022-06-20 0:00 ` Lars Ingebrigtsen
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=87o8fxrbaj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=46906@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=juri@linkov.net \
--cc=pipcet@gmail.com \
/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).