After looking at the code and running through a variety of test cases, I am pretty convinced that this issue has long been resolved, but the ticket never updated. In the current code, Parrot_exit already blocks the GC, which should prevent any ill-effects that would have been seen.
So, I'm marking this issue resolved. We can talk about whether the current solution is indeed a good one. Reseting the stack top instead of disabling the GC entirely might make more sense if we start to see a lot of resource-intensive exit handlers. We can talk about this and other issues when they arise at trac. -- Andrew Whitworth a.k.a Whiteknight _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
