Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
A perl build with -DDEBUGGING can show much information during execution, for example each op being executed, and the contents of the stack after each op:
$ perl587 -Dst -e'$a = "abc"; $a .= 1' EXECUTING... => (-e:0) enter => (-e:0) nextstate => (-e:1) const(PV("abc"\0)) => PV("abc"\0) (-e:1) gvsv(main::a) => PV("abc"\0) UNDEF (-e:1) sassign => PV("abc"\0) (-e:1) nextstate => (-e:1) gvsv(main::a) => PV("abc"\0) (-e:1) const(IV(1)) => PV("abc"\0) IV(1) (-e:1) concat => PV("abc1"\0) (-e:1) leave


In reply to Re: "omniscient debugging" for Perl by dave_the_m
in thread "omniscient debugging" for Perl by spurperl

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?

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

How do I use this?Last hourOther CB clients
Other Users?
Others about the Monastery: (1)
As of 2024-05-25 13:14 GMT
Find Nodes?
    Voting Booth?

    No recent polls found