From: Mark H Weaver <mhw@netris.org>
To: Ster Chess <sterchess@gmail.com>
Cc: 27698@debbugs.gnu.org
Subject: bug#27698: Guile takes over system +rant
Date: Sat, 15 Jul 2017 14:52:52 -0400 [thread overview]
Message-ID: <87fudxpm63.fsf@netris.org> (raw)
In-Reply-To: <CAFDv5SCfc+hVXTSuAePjkKTsE-hmVauNnqXvKvp0FXGnOBWfFA@mail.gmail.com> (Ster Chess's message of "Sat, 15 Jul 2017 01:39:29 +0100")
Ster Chess <sterchess@gmail.com> writes:
> I'm sorry if this has already been suggested as a bug, but I couldn't
> find it in the bug tracker. If I create a simple recursive factorial
> function, and choose huge values for it, Guile will happily do my
> bidding and take all the system resources and my whole system becomes
> unusable. This should never happen.
If you want to limit the stack size within Guile, see
'call-with-stack-overflow-handler', described here:
https://www.gnu.org/software/guile/manual/html_node/Stack-Overflow.html
Mark
prev parent reply other threads:[~2017-07-15 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 0:39 bug#27698: Guile takes over system +rant Ster Chess
2017-07-15 18:52 ` Mark H Weaver [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=87fudxpm63.fsf@netris.org \
--to=mhw@netris.org \
--cc=27698@debbugs.gnu.org \
--cc=sterchess@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.
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).