From zefram@fysh.org

I tried a test case from [perl #​61602] in Rakudo and got this​:

$ perl6

my Int $x = NaN
Type check failed in assignment to '$x'; expected 'Int' but got 'Num'

^D
zsh​: segmentation fault ~/usr/parrot/parrot-blead/bin/perl6
$ perl6 --version
This is perl6 version 2013.09-146-gd7e5e1d built on parrot 5.7.0 revision RELEASE_5_7_0-17-g5264436

Note that the SEGV doesn't happen immediately; it only happens when
exiting the REPL via ^D. The erroneous statement has to be the first
thing in the session, and all elements of the erroneous statement are
required. Other statements can be issued between the erroneous one and
the ^D, and appear to work normally. Issuing another statement *before*
the erroneous one gives a different result​:

$ perl6

123
123
my Int $x = NaN
Type check failed in assignment to '$x'; expected 'Int' but got 'Num'

^D
Null PMC access in push_string()
$

-zefram

From @usev6

This segfault is gone, also​:

$ perl6-p

my Int $x = NaN;
Type check failed in assignment to '$x'; expected 'Int' but got 'Num'

^D
$

$ perl6-p --version
This is perl6 version 2015.01-60-g12db81b built on parrot 7.0.1 revision RELEASE_7_0_1

So the same question as in ticket 115322​: Is this closable or do we need a test for the rakudo.parrot REPL.

@usev6 - Status changed from 'new' to 'open'

From @usev6

As far as I understand, this ticket was specific for the REPL with Rakudo on Parrot.

Since a) the SEGV was resolved and b) support for Parrot was suspended with Rakudo Star Release 2015.02, I'm closing this "parrot only" ticket.

I added the ticket to a list of closed ticket living in the Mu repository​: https://github.com/perl6/mu/blob/master/misc/rt.perl.org/tickets_closed_parrot_only.txt.

In case support for Parrot will be restored in some future release the listed tickets can be checked and re-opened as appropriate.

@usev6 - Status changed from 'open' to 'resolved'