in reply to manipulating call stack

In your package, make @CARP_NOT include all of the packages that you're overriding methods in. Alternately make @CARP_NOT in the package you overrode methods in be its existing @CARP_NOT or existing @ISA plus your package name.

There are subtle differences between the two, but either should help for most simple cases. (Suppose that A is a subclass of B is a subclass of C and you've overridden foo in B. The first won't succeed if your foo is called from A and the second won't succeed if your foo is called from C.)

If those, or a combination of those, don't solve your problem, then you have 2 possible solutions. The first is to load Carp::Heavy, then override Carp::trusts with a function of your own choosing that does whatever you want. (Carp should really have a hook for that purpose, but I didn't think of it when I should have, and at this point I'm not motivated to design and implement one. If you want to do so, be my guest.) The second is to override the methods with an eval so your new functions have the right package.