Bad .get_results in a exception handler gives infinite recursion

[NotFound]

A bad .get_results in a exception handler generates a exception when used. That exception is catched by the same handler, that generates a exception that is catched by the same handler...

This example illustrates it:

.sub main :main
    push_eh catchall
    $P0 = new ['Exception' ]
    throw $P0
catchall:
    .get_results($P1, $P2)
.end

[jkeenan]

I probably don't understand the problem here, but tonight I put this PIR into a file and attempted to execute it.

$ cat bad.pir
# Copyright (C) 2006-2009, Parrot Foundation.
# $Id: skeleton.pir 38369 2009-04-26 12:57:09Z fperrad $

.sub main :main
    push_eh catchall
    $P0 = new ['Exception' ]
    throw $P0
catchall:
    .get_results($P1, $P2)
.end

# Local Variables:
#   mode: pir
#   fill-column: 100
# End:
# vim: expandtab shiftwidth=4 ft=pir:

$ ./parrot bad.pir
$ 

I.e., no output; no evidence of error. Is there something wrong with that?

kid51

[NotFound]

Looks like now the extra results gets null assigned, but I don't know if this an intentional change or a bug.

[whiteknight]

The extra value is null-assigned after the PCC refactors and other subsequent changes. This is the correct behavior (certainly better than an infinite recursion loop). I'm closing this ticket. If we do not like the current behavior and want to change it to something else, we can open a second ticket for that.