Most of the time I can figure out bugs from the error logs. Sometimes
the errors are so meaningless, especially when SOAP is involved, that
I end up sprinkling dozens of prints around the sources to see what
comes up, narrow it down, rinse and repeat, and eventually find the
bug and take out all the prints. It's a right royal pain in the arse.
This mod_perl debug is a major improvement, but it has its own
drawbacks. A lot of the code I am stuck with uses Mason, and Mason
apparently splits it up into little chunks to eval so it is hard to
read the source in any reasonable fashion. One major help is "use
DB;" which lets me add "$DB::single = 1" where I want the debugger to
break. Even then, client timeouts play havoc with the whole mess.
What I would dearly love would be a SOAP server debugger which worked
thru the client interface, a remote control debugger so to speak. But
that sounds like a pretty tricky thing to implement without gaping
security holes, and it would probaby have the same timeout issues.
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / [EMAIL PROTECTED]
GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
