<?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 19:16:52 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Derick Rethans' Blog: What is PHP doing?]]></title>
      <guid>http://www.phpdeveloper.org/news/18222</guid>
      <link>http://www.phpdeveloper.org/news/18222</link>
      <description><![CDATA[<p>
<i>Derick Rethans</i> has a new post to his blog showing how you can, using a few simple unix tools, figure out <a href="http://derickrethans.nl/what-is-php-doing.html">what PHP is doing</a> when your scripts are executing.
</p>
<blockquote>
Sometimes when you have a long running PHP script, you might wonder what the hell it is doing at the moment. There are a few tools that can help you to find out, without having to stop the script. Some of these work only on Linux.
</blockquote>
<p>
He shows you how to use the following commands to track down exactly what your process is working on: strace, ltrace and gdb (a handy debugger that will probably give you more information than you're looking for). He includes some sample output for the commands and gives an example of a PHP script-to-gdb output relationship.
</p>]]></description>
      <pubDate>Fri, 13 Jul 2012 08:30:02 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Derick Rethans' Blog: PHP's segmentation faults GDB-fu]]></title>
      <guid>http://www.phpdeveloper.org/news/11167</guid>
      <link>http://www.phpdeveloper.org/news/11167</link>
      <description><![CDATA[<p>
<i>Derick Rethans</i> has <a href="http://derickrethans.nl/phps_segmentation_faults_gdbfu.php">shared a quick tip</a> for locating a code crashing kind of problem with your application when something like XDebug isn't around.
</p>
<blockquote>
However, because we as PHP developers are lazy, provide a few GDB tricks to make this easier. First of all, it's only really going to work if you haven't stripped the symbols from your PHP and Apache binaries. Secondly, you still need to have the PHP source lying around somewhere.
</blockquote>
<p>
He suggests using GDB to run the backtraces and create a file to help you track down the infinite recursion problem that could be giving you issues. 
</p>]]></description>
      <pubDate>Wed, 08 Oct 2008 09:32:09 -0500</pubDate>
    </item>
  </channel>
</rss>
