Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Journal of jjore (6662)

Thursday June 28, 2007
02:57 PM

Module idea: Devel::DebugNow

[ #33628 ]

Enables the debugging runloop whenever requested so instances of $^P setting can take effect regardless of whether the program was started with the -d parameter or not.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • When you run perl without -d option, then you get OP_NEXTSTATE instead of OP_DBSTATE opcodes. Switching to the debugging runops loop doesn't fix this. Or am I missing something?
    • Nope, I guess it wouldn't change that. I don't know what an OP_DBSTATE is though. I've seen them but never looked at them.
  • ...so this would be a very small module. AFAICT you can have what you want as long as the code was compiled with at least minimal $^P flags -- just toggle $DB::trace to enable or disable the debugger. I did this in Sepia, and it doesn't seem to cause any trouble. Surprisingly, $^P also has no measurable performance impact when done "right" (see this Perlmonks thread [perlmonks.org]).