I know I should not but ... sometimes I even do add debug prints into other peoples modules (on my development machine). But I do mark them and delete them afterwards.
And I do look inside whenever I get a message like this and try to understand what the heck is going on down there. Besides I can learn something reading other people's code.
I believe this helps a lot, imagine you COULDN'T go and look at&modify that library. Imagine you did not know what went wrong inside and couldn't find out.
Anyway I do not use the commandline debuger, I use ptkdb instead. Maybe it doesn't allow me to set a break point that's triggered only each 7th time and only if there is a process with ID 15764 on the machine, but it gives me more context. A matter of personal preference of course.
To get back to DBI ... is there any chance you call an ->execute() with too many params? Could you change the die() on line 301 of DBI/ProxyServer.pm to Carp::confess(), to see what command in your script caused the problem?
Jenda
In reply to Re: DBI/module debugging?
by Jenda
in thread DBI/module debugging?
by kechari
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |