On 04/11/14 06:00, Joe Watkins wrote: > I'm not saying we should not extend the features of phpdbg, but, we > should do it knowing what it actually is, knowing that it is > fundamentally different to xdebug.
Having just hit another 'white screen' problem on a site I'm trying to update, I do wonder if there is an alternative debug approach that would help speed the process. I have used xdebug in the past, but on the whole the debug tools built into the framework allow fairly quick tracking of a problem and isolating it. So the question is ... just where are the strengths of each and is either useful for day to day debugging, or more appropriate for debugging the internal operation of PHP? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
