<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 21 May 2013 13:22:43 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Zend Developer Zone: Tracing PHP Applications with xdebug]]></title>
      <guid>http://www.phpdeveloper.org/news/9318</guid>
      <link>http://www.phpdeveloper.org/news/9318</link>
      <description><![CDATA[<p>
Continuing on from <a href="http://www.phpdeveloper.org/news/9209">the previous part</a> of his series, <i>Stefan Priebsch</i> has posted <a href="http://devzone.zend.com/article/2871-Tracing-PHP-Applications-with-xdebug">part two</a> of his look at using XDebug over at the Zend Developer Zone.
</p>
<blockquote>
Welcome to the second installment of our five-part series of articles on xdebug, the PHP developer's swiss army knife extension. The installation of xdebug and its basic features were covered last week. This week, we will explore the tracing feature of xdebug.
</blockquote>
<p>
He details what tracing is and how it's helpful (no more repetitive var_dumps!) in finding issues in your code. He shows how to set up a trace log, add the code to your application to pass debugging information off to the log and how to add additional information to the log to make narrowing down the error even easier.
</p>]]></description>
      <pubDate>Thu, 27 Dec 2007 09:31:00 -0600</pubDate>
    </item>
  </channel>
</rss>
