Glenn Weavind

Problem was at my end - better use of the tools fixed the issue. Please close.

Haven't done that - looking at the perl5db.pl at that section it's their crash handler {=head2 C<dbdie> The debugger's own C<$SIG{DIE}> handler. Handles providing a stack trace by loading C<carp> and calling C<carp::longmess()> to get it. We turn off single stepping and tracing during the call to C<carp::longmess> to avoid debugging it - we just want to use it.</carp::longmess></carp::longmess()></carp></dbdie> If C<dielevel> is zero, we let the program being debugged handle the exceptions. If it's...

Haven't done that - looking at the perl5db.pl at that section it's their crash handler {=head2 C<dbdie> The debugger's own C<$SIG{DIE}> handler. Handles providing a stack trace by loading C<carp> and calling C<carp::longmess()> to get it. We turn off single stepping and tracing during the call to C<carp::longmess> to avoid debugging it - we just want to use it.</carp::longmess></carp::longmess()></carp></dbdie> If C<dielevel> is zero, we let the program being debugged handle the exceptions. If it's...

PadWalker 2.3, XML::LibXML 2.0205 (just updated a touch - no change).

perl debugger crashes