<?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>Wed, 19 Jun 2013 01:58:09 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Kevin Schroeder's Blog: Remote Debugging with the Zend Debugger and PHPUnit]]></title>
      <guid>http://www.phpdeveloper.org/news/17888</guid>
      <link>http://www.phpdeveloper.org/news/17888</link>
      <description><![CDATA[<p>
<i>Kevin Schroeder</i> has <a href="http://www.eschrade.com/page/remote-debugging-with-the-zend-debugger-and-phpunit/">a quick new post</a> with a one-liner you can use to get remote debugging working with Zend Debugger and PHPUnit.
</p>
<blockquote>
I'm trying to do some remote debugging with PHPUnit on a remote system.  I was following the rules I had <a href="http://www.eschrade.com/page/debugging-a-php-cli-script/">written about in a previous article</a> but for some reason I could not get path mapping to work.  So I figured I'd ping the Studio lead developer because as soon as I did that I'd get it to work.  Well, that's what happened. 
</blockquote>
<p>
His fix comes in the form of setting a command-line parameter, QUERY_STRING, with the correct parameter order so the paths will get mapped back to the correct project. This parameter is a URL-encoded set of parameters that do things like start the debugging, set up the hostname for the debugger to point to and map the "original URL" back to your choice of values.
</p>]]></description>
      <pubDate>Tue, 01 May 2012 09:27:47 -0500</pubDate>
    </item>
  </channel>
</rss>
