From: Steff <steffhip@googlemail.com>
To: 25212@debbugs.gnu.org
Subject: bug#25212: REPL aborts when a stack overflow is triggered twice
Date: Thu, 15 Dec 2016 20:34:46 +0100 [thread overview]
Message-ID: <046cba2f-de9b-25e6-bfc0-f2d2b85ebbd1@gmail.com> (raw)
When a Stack Overflow occured the new prompt of the REPL becomes fragile
an sometimes crashes on invalid inputs.
A reliant way to make the REPL abort, is by triggering a stack overflow
twice.
Affected Version: 2.0.13
Way to reproduce:
scheme@(guile-user)> (define x (lambda () (x) (x))) ;;; define a
function provoking a stack-overflow
scheme@(guile-user)> (x) (x) ;;; first call of
this function is caught but second aborts the REPL
<unnamed port>:2:0: In procedure x:
<unnamed port>:2:0: Throw to key `vm-error' with args `(vm-run "VM:
Stack overflow" ())'.
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
[1] 13794 abort (core dumped) guile
next reply other threads:[~2016-12-15 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 19:34 Steff [this message]
2017-01-09 21:50 ` bug#25212: REPL aborts when a stack overflow is triggered twice Andy Wingo
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=046cba2f-de9b-25e6-bfc0-f2d2b85ebbd1@gmail.com \
--to=steffhip@googlemail.com \
--cc=25212@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.
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).