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

[download]

Dave.

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

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


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.