So I apologize for the lack of clear error messages. The code is detached, so I have to trap __DIE__ and write to syslog. This is done as follows:
$SIG{__DIE__} = \&die_catcher;
...
#
# die_catcher
#
# Try to log the call stack if we die
#
sub die_catcher {
for my $caller ( CallStack() ) {
alog(LOG_ERR, $caller);
}
}
...
#
# Courtesy of Perl Monks http://www.perlmonks.org/?node_id=51097
#
sub CallStack {
local $@;
eval { confess( '' ) };
my @stack = split m/\n/, $@;
shift @stack for 1..3; # Cover our tracks.
return wantarray ? @stack : join "\n", @stack;
}
I'm not really that familiar with Carp, I'll see what I can figure out to make it give a more complete backtrace.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.