SEGV when running whateverable tests

[AlexDaniel]

OK, this bug report is not extremely useful, but that's about all I can do.

See Raku/whateverable#24 (comment) for some commentary on what happens.

Here's the SEGV caught with gdb: https://gist.github.com/MasterDuke17/0312dd2af1e3b2b498d91cfacc45343c

To reproduce on your own machine you'll need a local irc server, hundreds of rakudo builds and a lot of perl6 modules installed. That's very unlikely, so it's much easier to contact me if you want to play with it. I'll give you access to the server where whateverable runs, the crash is easily reproducible there.

Some discussion: https://irclog.perlgeek.de/perl6/2017-11-19#i_15471050

This is a regression, but I can't tell when it happened. Definitely there was at least one release with this bug included.

This is Rakudo version 2017.10-215-g85105077a built on MoarVM version 2017.10-86-g89fae17a6
implementing Perl 6.c.

[AlexDaniel]

FWIW I'm OK with closing this once it's fixed without tests, if it happens that once the issue is known there's no easy way to write a test for it.

[AlexDaniel]

FWIW this still happens. :(

[AlexDaniel]

Hey @jnthn, can you try following the first few steps on https://github.com/perl6/whateverable/wiki/Installation ?

Then instead of running some bot (like the help page suggests) just run evalable tests:

perl6 t/evalable.t

The bot will exit with signal 11 (SEGV) about half way through. Note that the test suite itself is a separate process, and the actual bot PID will be printed at the beginning (so that you can attach gdb or whatever).

[AlexDaniel]

This is now fixed! I'll close this as a dup of #1660 (same underlying issue).