in reply to Debugging DESTROY calls in forking application

Print statements? Setting hundreds of debug points? Is there any good way to overload DESTROY without loosing the original functions?

You could do this with e.g. Class::Method::Modifiers, or see:

  • Comment on Re: Debugging DESTROY calls in forking application