Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

I have some complicated code that is getting an exception deep inside an eval (specifically "Can't use an undefined value as a symbol reference"). This happens about 1 in every 100,000 transactions, from one of several dozen possible code paths. Without a stack trace I'm pretty stuck.

Is there a way to get caller() information through eval, at the eval level? I know (example below) how to print it locally from a method. But if I don't know in advance where the problem will come from, can I get a stack trace later, bubbled up to the eval?

Note that Carp, I think, won't work, since the exception is caused by a perl error, not an explicit die/carp/cluck.

eval { level2(); }; if($@) { print "Error $@"; #want to print stack trace HERE! } sub level2 { print "This is level2\n"; level3(); } sub level3 { print "This is level3\n"; $i = 0; while(($package, $filename, $line, $subroutine)=caller($i++)) +{ print "caller($i)=$package, $filename, $line, $subrout +ine\n"; } $zero = 0; $zero = 100 / $zero; }
Other monks postings on similar topics include http://www.perlmonks.org/?node_id=226358 and http://www.perlmonks.org/?node_id=211954

In reply to Capturing stack trace in eval by brycen

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others imbibing at the Monastery: (5)
As of 2024-04-24 06:13 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found