--- Begin Message ---
Subject: |
REPL aborts when a stack overflow is triggered twice |
Date: |
Thu, 15 Dec 2016 20:34:46 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 |
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
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#25212: REPL aborts when a stack overflow is triggered twice |
Date: |
Mon, 09 Jan 2017 22:50:49 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
On Thu 15 Dec 2016 20:34, Steff <address@hidden> writes:
> 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
Yeah this one is gnarly. We couldn't fix it in the 2.0 for various
reasons but addressed it comprehensively in 2.2:
https://wingolog.org/archives/2014/03/17/stack-overflow
Closing as done. 2.2.0 should be out within a month or two.
Andy
--- End Message ---