Re: Aggressive exception handler making extra work for itself.

On Apr 3, 2007, at 7:12 AM, Jonathan Swartz wrote:

> I noticed this behavior while investigating performance at Amzn,  
> but then forgot about it. I agree - we should only use  
> Devel::StackTrace when needed by our error messages, and perhaps we  
> should allow its use to be turned on/off with a parameter at any rate.
>
> Jesse/Dave, have you come up with a workaround or fix for this yet?

I actually managed to reduce the impact of it enough that it was no  
longer at the top of my stack. Hook::LexWrap was making stack  
traces...incredibly painful due to its overriding of CORE::caller.  
But that's not a reasonable general fix.

-jesse

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
Mason-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-devel