On 27 Feb 2008, at 17:14, Andy Armstrong wrote:
Looks to be that the best place is at the two lines (yes, the code
there is duplicated, or almost so - bleah) with the comment "Pop
the single-step value off the stack." This is after the code has
returned control to the debugger, so at that point you can check
Test::Builder->new->current_test and to see if you've hit the test
you want yet, $DB::sub to make sure you're not in a Test:: module,
and then set $DB::single to 1 to stop execution at that point.
OK, that sounds good - I'll investigate further, thanks.
Hmm. Evil thought - if I set $DB::single to a reference to an object
that's overloaded to numify to whatever value for $single I want the
debugger to see - and that object has a DESTROY method then I can
implicitly detect $single being popped (because the ref. will go out
of scope and be destroyed) without invasive debugger surgery.
Possibly :)
--
Andy Armstrong, Hexten
