comment on

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! :)

Cheers Rolf

(addicted to the Perl Programming Language)

update

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

In reply to Re: lightweight stack info by LanX
in thread lightweight stack info by hv

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Problems? Is your data what you think it is?
	PerlMonks