And another note (sorry I do it in parts...)

From looking around I understand that the problem to enable the debugger. In Apache, when wanted to enable the debugger, it seems that special code was needed:
From modperl archive (http://www.geocrawler.com/archives/3/182/2000/12/0/4895655/) -
> there is quite a bit of overhead when -d is enabled. have a look at
> Apache::DB.xs, there's in init_debugger() function todo what -d does. if
> another method was added to turn it off, after the registry script was
> compiled, the overhead would be reduced a great deal.

shushu

my $a = new OVERLOADED "value";
[download]

I haven't been motivated enough to see what the inside of a Safe::Hole->reval looks like but now that you've decided to go perlguts your first thing to do is to look at the B module. In my sig you'll notice an example of a script getting the current CV via B::svref_2object(sub {} )->OUTSIDE. I would initially recommend you read Gisle Aas' Illustrated PerlGuts, then Simon Cozens' internals tutorial and if that isn't enough descend into perlguts and perlhack. The key here is you're just walking structures. You aren't going to have to alter stuff so the documentation is to guide you in using B to walk all over.

__SIG__
printf "You are here %08x\n", unpack "L!", unpack "P4", pack "L!", B::
+svref_2object(sub{})->OUTSIDE
[download]