Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot

Re^3: Request help for work around for bug in perl 5.10.1 (backtrace)

by tye (Sage)
on Dec 12, 2012 at 22:34 UTC ( #1008601=note: print w/replies, xml ) Need Help??

in reply to Re^2: Request help for work around for bug in perl 5.10.1 (weak magic)
in thread [Solved] Request help for work around for bug in perl 5.10.1

I'm not really that familiar with Carp, I'll see what I can figure out to make it give a more complete backtrace.

The problem wasn't that the backtrace was unacceptable. The problem was that you simply failed to log @_ (really just $_[0]), which is the most important thing to log when logging inside of a __DIE__ handler.

Luckily, the backtrace also happened to include a truncated version of that message. But the solution isn't to try to get the backtrace to not truncate. The solution is to log $_[0] directly (along with the backtrace).

In this particular case, the interesting backtrace is the C backtrace, but that isn't as easy to get (you'd likely need a non-stripped build and gcc and...).

- tye        

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1008601]
[karlgoethebier]: Good morning, in my scratchpad is a section "For review". Do you think it's worth a tiny meditation or a cool use? Thanks, Karl
[karlgoethebier]: ...or too simple, useless effort?

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (4)
As of 2017-09-24 08:39 GMT
Find Nodes?
    Voting Booth?
    During the recent solar eclipse, I:

    Results (273 votes). Check out past polls.