# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #124434] # in the subject line of all future correspondence about this issue. # <URL: https://rt.perl.org/Ticket/Display.html?id=124434 >
<lucasb> m: Failure.new(Exception.new) <camelia> rakudo-moar a073f5: OUTPUT«No exception handler located for catch [...] <lucasb> m: Failure.new(Exception.new); 1 <camelia> rakudo-moar a073f5: OUTPUT«(signal SEGV)» <lucasb> I don't know why the last statement is special for rakudo... <moritz> it's not evaluated in sink context <lucasb> In "2;3;4", only 2 and 3 get warnings for useless use <moritz> which is kinda a bug <moritz> in the general case, when you have code inside a block, the last statement is returned <moritz> hence it's not in sink context <moritz> and we haven't fixed that for the mainline <jnthn> For the mainline, we didn't fix it 'cus the REPL wants it that way also... <moritz> right * jnthn will investigate the SEGV <moritz> m: Failure.new(Exception.new).sink <camelia> rakudo-moar a073f5: OUTPUT«(signal SEGV)» <moritz> there ya go <lucasb> moritz++ * masak submits rakudobug <moritz> Exception.new leaves $!ex and $!bt undefined <moritz> but the rest of the code assumes that they are set <moritz> and it's the catching/throwing code that generates a new exception and binds $!ex and $!bt into them <jnthn> moritz: Still shouldn't SEGV either way...
