Is there existing art for capturing stack info (per Carp::longmess) that's lighter-weight than calling longmess?

At $work we annotate exceptions with a stacktrace so that we can ensure we log it for any exception that remains uncaught; we've been using that for a couple of years now, and it has been of huge benefit.

However a recent attempted CPAN module upgrade turned out to cause a huge performance degradation, which turned out to be because the module was using exceptions (in large numbers) as part of its normal processing, and the cost of the longmess() annotation suddenly becomes huge.

Given that the vast majority of these exceptions are caught, so never need a stacktrace logged, I'm now looking for a cheaper way to capture and attach the stacktrace info without going through the full serialization that longmess does. Kinda like a continuation, except we don't need to continue.

Thanks in advance for any suggestions.

Hugo