From: Ricardo Wurmus <rekado@elephly.net>
To: Vasilij Schneidermann <mail@vasilij.de>
Cc: 41404@debbugs.gnu.org
Subject: bug#41404: Crash "Too many root sets" when executing code from stdin in elisp mode
Date: Wed, 20 May 2020 02:52:02 +0200 [thread overview]
Message-ID: <87d06zfmx9.fsf@elephly.net> (raw)
In-Reply-To: <20200519154828.GA2067@odonien.localdomain>
Vasilij Schneidermann <mail@vasilij.de> writes:
> The attached reproducer script requires Emacs and Guile. When running it, the
> REPL prints out many lines, the last ones being:
>
> $1884 = #f
> $1885 = #f
> $1886 = #f
> $1887 = #f
> $1888 = #f
> $1889 = #f
> $1890 = #f
> $1891 = #f
> $1892 = #f
> Too many root sets
> ./repro.sh: line 11: 2014 Aborted (core dumped) guile --language=elisp < elisp-spec.el
>
> This happens both for Guile 2.2.6 on Arch and Guile 3.0.2 on Debian Sid,
> launched with `docker run --rm -i -t debian:sid bash`.
I can reproduce this on the wip-elisp branch as well.
--
Ricardo
prev parent reply other threads:[~2020-05-20 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 15:48 bug#41404: Crash "Too many root sets" when executing code from stdin in elisp mode Vasilij Schneidermann
2020-05-20 0:52 ` Ricardo Wurmus [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d06zfmx9.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=41404@debbugs.gnu.org \
--cc=mail@vasilij.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.
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).