Re: Debuggin PHP
| From: | Jochem Maas | Date: | Wed, 26 Apr 2006 18:08:39 +0000 |
| Subject: | Re: Debuggin PHP | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-234833@lists.php.net to get a copy of this message | ||
Robert Cummings wrote:
On Wed, 2006-04-26 at 12:44, Jochem Maas wrote:that'll be the old 'put the first debug "echo" in the "middle" of the script" technique :-)hicham wrote:easy way 2: use lots of echo()/var_dump()/print_r() in your code to figure out where it's breaking.If you're trying to track down an error using this technique (by far one of the most popular techniques and time tested), be sure and use your knowledge of binary search algorithms to speed up your search. Applying the heuristic of guessing approximately where it's occurring will help
you greatly also :) This kind of technique though is mostly only necessary when PHP does something stupid like segfault *grin*. Another fantastic technique is if you know the error occurs at a specific location, but don't know how the heck the script got there... you can use debug_backtrace().very good tips!
Cheers, Rob.