On Fri Feb 12 13:35:21 2016, larry wrote: > 10:41 < TimToady> m: say "𢡊" > 10:41 <+camelia> rakudo-moar 691b39: OUTPUT«(signal SEGV)» > 10:42 < TimToady> jnthn: ^^ there's another glitch :) > 10:43 < timotimo> can you also make that with a \x literal, so that i can > more easily copy-paste it? > 10:47 < TimToady> m: say "\xfacf" > 10:47 <+camelia> rakudo-moar 691b39: OUTPUT«(signal SEGV)» > 10:47 < TimToady> m: say "\xfad0" > 10:47 <+camelia> rakudo-moar 691b39: OUTPUT«(signal SEGV)» > 10:48 < [Coke]> O_o > 10:48 < TimToady> m: say "\xfad9" > 10:48 <+camelia> rakudo-moar 691b39: OUTPUT«龎» > 10:49 < TimToady> m: say "\xfad8" > 10:49 <+camelia> rakudo-moar 691b39: OUTPUT«齃» > 10:49 < TimToady> m: say "\xfad7" > 10:49 <+camelia> rakudo-moar 691b39: OUTPUT«(signal SEGV)» > 10:49 < TimToady> there's the boundary > 10:50 < TimToady> that trailing boundary, facf is the leading boundary
Turned out to be a silly thinko of mine that we'd just never managed to run into before. Fixed in MoarVM, and tests covering these added to S15-nfg/concatenation.t (the SEGV golfed to "\xfad7" ~ "\n"). /jnthn