Re: lightweight stack info

[LanX]

We just had a similar problem a day ago.

Re: Bizarre Proc::Daemon error # die-handler

I don't see a faster way to get the backtrace - only the possibility to filter out messages from the problematic module.(like already suggested)

Either always check caller for the source (well you already got the backtrace anyway) or try to localize your die handler.

If you are very desperate you can also try to write XS-code to speed up you're handler, but I think logging to the file system should be you're bottleneck°. (Did you already run benchmarks?)

In this case logging to a DB could be an option.

HTH! :)

update

°) but after reading your question a third time, this doesn't seem to be the problem