Here's two nifty recipies for using a debugger at rumtime:

At any arbitrary moment. Perhaps you've got some process that's long running and you occasionally want to stop it, examine its contents and then tell it to continue. Presumably you'd do the moral equivalent of Enbugger->unimport to remove the debugger.

$SIG{USR1} = \ &start_debugger;
sub start_debugger {
    require Enbugger;
    Enbugger->import;
}

[download]

Start the debugger on exception.

$SIG{__DIE__} = sub { require Enbugger; Enbugger->import };

Please share your ideas. You're smart people, I like using other smart people's ideas!

⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

In reply to Re: Enabling or disabliing the debugger at runtime by diotalevi
in thread Enabling or disabliing the debugger at runtime by diotalevi

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.