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