I've found that this varies a bit depending on the problem and the environment. For well controlled items in a limited environment tracking down the details with xdebug remote debugging can be very useful. In other cases I've found that using other methods for collecting data and getting a peak into what is going on has been necessary.
I'll give a for instance. Tracking down an issue that seems to only crop up at odd, unpredictable times, with many variables in play. Not sure if the issue is dependent on the request being served from a specific datacenter, interacting with a specific cache server, database server or if there was something different/special about that particular user. In cases like that we've ended up deploying live debug triggers that collect large amounts of info when the specific problem is triggered. On Sat, Sep 3, 2011 at 11:42 PM, Bryan Petty <[email protected]> wrote: > On a large coding project, I don't understand how anyone can work > without xdebug and an IDE with xdebug debugging support (or whatever > the Zend equivalent is). -- Joseph Scott [email protected] http://josephscott.org/ _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
