Dan Sugalski wrote:
- I implemented Parrot_destroy, which cleans up all internal data structures of an interpreter and frees all used mem.
Right, I understand. (And I really appreciate it--this was a hanging area that didn't get nearly the proper attention it needed) The bit I don't understand is the need for a hook into the process exit.
Then you should have read on ;-)
~8% tests use internal_exception to deliver a test result. Not catching the exception may hide memory leaks in such tests.
More detailled:
Testing for memory leaks uses the same tests as are already in t/*. A test is passed, when the result is ok, and when it doesn't leak mem. This is accomplished by the scipt "testyamd" I checked in. When the exceptions just exits and Parrot_destroy isn't reached, the test would fail.
Yeah, I think I'll do that for right now. What I'd like is a probe for this in configure. Oh, Brent.... :)I did deactivate it some minutes ago. Tinderboxen should be happy again. Waiting for the config test - but it's not an urgent one.
leo
