bug#25212: REPL aborts when a stack overflow is triggered twice

bug#25212: REPL aborts when a stack overflow is triggered twice

[Steff]

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

bug#25212: REPL aborts when a stack overflow is triggered twice

[Andy Wingo]

On Thu 15 Dec 2016 20:34, Steff <steffhip@googlemail.com> 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