Internal to ptkdb the variable $DB::no_stop_at_start, will prevent the debugger from stopping immediately when the program starts up. You can create a .ptkdbrc file which supports several api calls to the debugger. One of them is: condbrkpt($fname, $line, $expr) Which will set a conditional breakpoint in $fname at $line and will eval $expr and only stop if it's true.

update:

Breakpoints can even be included into the code if necessary. 


sub BEGIN {
    $DB::no_stop_at_start = 1 ;
}
Devel::ptkdb::condbrkpt(__FILE__,__LINE__+1, 'int($ARGV[0]) > 2') if d
+efined $DB::single ;
print "hello world\n" ;

[download]
Update: Snippet of code for inline breakpoint function: snip

In reply to Re: Breaking into debugger by ptkdb
in thread Breaking into debugger by Sprad

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.