develooper Front page | perl.perl5.porters | Postings from August 2001

Debugging weirdness

Thread Next
August 15, 2001 20:09
Debugging weirdness
Message ID:

Once  upon  a time  I  have  debugged  an  application with  the  perl
debugger, and I have found the following situation:

a,   I   have   set   a  breakpoint   to   a   subroutine,   call   it
Deep::Inside::Sub::_a_: "d Deep::Inside::Sub::_a_"

b, Continued the run with "c"

Then  I  have  found  that  I  got   a  stack  trace  (cluck)  from  a
subroutine,  which  is  called from  Deep::Inside::Sub::_a_,  and  the
perl debugger did not stop at the sub entry point.

I would  be happy if I  can send a bug-report  or I can find  out what
happened,  but I  don't know  what to  check. This  program uses  more
than 100 modules, so triggering this can be very hard...

Any ideas how to catch this bug-like thing?

#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1

Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About