Perl: the Markov chain saw | |
PerlMonks |
Re: Disabling a hardcoded breakpointby hexcoder (Curate) |
on Mar 11, 2016 at 08:43 UTC ( [id://1157406]=note: print w/replies, xml ) | Need Help?? |
You wrote: The obvious and naive way is to comment out that bp and restart with frustration when the bp was discovered in a loop after a long processing. If your are running the debugger interactively (with the -d option), you could continue the run with the c command instead of restarting. If the script is run without the debugger, the line $DB::single = 1; has no effect (but causes a warning with -w), so I have some difficulty to recognize the merits of this method. Obviously you could grep for $DB::single in your Perl sources to find any left-overs... BTW: I am using an automatic breakpoint to catch the cause of any warnings during a run under the debugger. That is, whenever I get a warning about an undefined value being used in an addition for example, I let the debugger stop right there, so I can investigate the context that led to this behavior. The original source does not need to be modified (see here for details).
In Section
Seekers of Perl Wisdom
|
|