Omniscient Debugging is an idea that looks very very sexy. In short: it's a complete trace of a program after it ran - all variable assignments, function calls, exception throws/catches, etc. Once your program finished, you can retrace its whole execution history, step by step.

Imagine that your program failed. So, you have to run it again, fill in lots of "print" statements, perhaps even firing up the debugger and starting throwing breakpoints in. With ODB, it's not necessary. Even for multithreaded programs, it provides a completely deterministic run history that can be used (and in fact, was displayed in action) to find bugs very quickly. People who use it swear by it, hotly claiming that it shaves off huge amounts of debugging time.

Now, that catch is - this ODB thingie was developed for Java, since its virtual machine allows a simple & relatively efficient implementation of an ODB to sit on it. It probably isn't too applicable to compiled code.

But I guess Perl can have support for this as well ? Perl 6, especially, which also runs on top of a VM... Can Parrot support this ? The Perl 6 compiler, perhaps (inserting "timestamping" instructions before/after assignment/call instructions)


In reply to "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.