On 10/24/07, oryann9 <[EMAIL PROTECTED]> wrote: > Why is it when I turn off debug mode, I get no output?
Are you saying that there's a difference in your program's execution depending upon whether Perl's debugger (activated via the -d command line switch) is or is not running? If that's the case, unless somebody is trying to make that happen, the evidence points to a bug in perl (specifically, in the optimizer; since that isn't used when the debugger is running). Or are you talking about a debug mode for the module itself? If that's the problem, you could search the source for places the debug mode is checked. Also, in contrast to the previous case, you can use the Perl debugger to step through the Perl parts of the module and see what's really happening. Or not, as the case may be. (If there's any compiled code, the Perl debugger may not be much help.) It may also be that turning on a debug mode slows down the execution sufficiently to match the speed of a server, or something like that. It seems unlikely in this case, but I've heard of servers which fail when sent multiple requests in a short time interval without a delay. This is the kind of bug that may not show up until you use a fast enough machine against a slow enough server, so you may be the first to be bitten by this bug. You may want to try adding a small delay at key places in your code, to see whether that makes things run better. select(undef, undef, undef, 0.2); # small delay Good luck with it! --Tom Phoenix Stonehenge Perl Training -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
