I have a large perl script that checks clean when
running perl -c scriptname. It also executes when called without
throwing error messages but suddenly, any line I give it while in the
debugger initially reports "Line [any_number] not breakable.
I can load the script with perl -d scriptname, type a
few n's to go past the calls for use net::dns and other called
modules until I get to the beginning of execution and then I can
type b someline# that is supposed to be breakable and it takes
it and traces normally.
Has anybody ever seen this behavior before?
Normally you get something similar to it if you try to
debug broken code and have failed to check syntax. Fixing the
syntax opens everything up again but this behavior I am seeing
now is unusual especially since the code even runs.
What I am asking is what sort of construction can cause
all executable lines to initially deny the setting of break
points even though the code still runs?
It might be a great feature to include in code one was
providing to others if they wanted to discourage reverse
engineering. Of course I am somewhat joking, but the effect
right now is to make trouble-shooting a large hassle.
I have not added any new perl modules to this script in
a long time and up until a few days ago, it debugged normally
when one needed to do so.
Thanks for any suggestions as to what to look for.
Martin McCormick
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
