Uri Guttman <[EMAIL PROTECTED]> wrote:
> >>>>> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
> DS> At 03:22 PM 8/18/2001 -0400, Uri Guttman wrote:
> >> i didn't see any references to support debugging an external perl
> >> process. ...
>
> DS> Good point. ... listen on some port/pipe/doodad and set a flag
> DS> to kick into the remote debugger if someone connects to it?
>
> this is a tricky problem as we can't just grab the remote process like
> gdb can these days using /proc or something.
Why can't we do that?
The way I'd really like to kick in the debugger is to start up gdb
and just say:
(gdb) call perl_debug_enable()
(gdb) continue
It would be very useful to have a collection of gdb-callable
routines for integrating the Perl debugger with perl (internals)
debugging. I'd love to be able to do:
(gdb) call perl_debug_break("my_sub")
The other thing that I would like is a way of pausing in Perl code
and waiting for a debugger to attach. This would make it much easier
to debug mod_perl for example.
Other than these two wishes, the current Perl debugger is fine.
It seems like overkill (and a security nightmare) to come up with a
special remote debugging solution. Is there some reason we're going
to need to debug perl on a platform without a real debugger? You
don't have any plans to compete with Java in the embedded device
space, do you Dan? ;)
- Ken
