<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Configuration issues with Xdebug on Debian Etch</title>
	<link>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/</link>
	<description>PHP, Macs and life in general</description>
	<pubDate>Thu, 24 Jul 2008 23:30:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: s0enke</title>
		<link>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9612</link>
		<author>s0enke</author>
		<pubDate>Wed, 30 Jan 2008 20:37:03 +0000</pubDate>
		<guid>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9612</guid>
					<description>yes, the full path must be provided for zend_extension directive. That's by nature. And the OS doesn't matter, it's no Debian specific issue.</description>
		<content:encoded><![CDATA[<p>yes, the full path must be provided for zend_extension directive. That&#8217;s by nature. And the OS doesn&#8217;t matter, it&#8217;s no Debian specific issue.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: gaetano</title>
		<link>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9613</link>
		<author>gaetano</author>
		<pubDate>Wed, 30 Jan 2008 20:50:31 +0000</pubDate>
		<guid>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9613</guid>
					<description>Short answer - yes!
Somebody from internals will have to tell you why, though.
One thing I really never understood is the difference between loading modules as extensions or zend_extensions, and wgat is the best choice if a module supports both ways...</description>
		<content:encoded><![CDATA[<p>Short answer - yes!<br />
Somebody from internals will have to tell you why, though.<br />
One thing I really never understood is the difference between loading modules as extensions or zend_extensions, and wgat is the best choice if a module supports both ways&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Derick</title>
		<link>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9614</link>
		<author>Derick</author>
		<pubDate>Wed, 30 Jan 2008 21:00:50 +0000</pubDate>
		<guid>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9614</guid>
					<description>Yes, you have to use the full path for the zend_extension lines. It's (unfortunately) just how it is. I tried to make it a bit clearer in the Xdebug docs now.</description>
		<content:encoded><![CDATA[<p>Yes, you have to use the full path for the zend_extension lines. It&#8217;s (unfortunately) just how it is. I tried to make it a bit clearer in the Xdebug docs now.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Sean Coates</title>
		<link>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9617</link>
		<author>Sean Coates</author>
		<pubDate>Wed, 30 Jan 2008 21:25:37 +0000</pubDate>
		<guid>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9617</guid>
					<description>Yes, zend_extension needs a full path.

S</description>
		<content:encoded><![CDATA[<p>Yes, zend_extension needs a full path.</p>
<p>S</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Mikey</title>
		<link>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9618</link>
		<author>Mikey</author>
		<pubDate>Wed, 30 Jan 2008 21:31:14 +0000</pubDate>
		<guid>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9618</guid>
					<description>Seems to be the way to go on Debian-like systems. I did not have any other choice on my linux box running Kubuntu 7something, only the full path worked.

Which reminds me that I need to send a postcard as well...</description>
		<content:encoded><![CDATA[<p>Seems to be the way to go on Debian-like systems. I did not have any other choice on my linux box running Kubuntu 7something, only the full path worked.</p>
<p>Which reminds me that I need to send a postcard as well&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Jan Schneider</title>
		<link>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9619</link>
		<author>Jan Schneider</author>
		<pubDate>Wed, 30 Jan 2008 22:35:11 +0000</pubDate>
		<guid>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9619</guid>
					<description>Yes, zend_extension always requires the full path. That caught me a few times too. Mix that with having to tackle _debug to the settings name when using a debug build, and you can be sure to mess this up at least once before getting it right. :)</description>
		<content:encoded><![CDATA[<p>Yes, zend_extension always requires the full path. That caught me a few times too. Mix that with having to tackle _debug to the settings name when using a debug build, and you can be sure to mess this up at least once before getting it right. <img src='http://blog.lucke.info/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Bruce Weirdan</title>
		<link>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9620</link>
		<author>Bruce Weirdan</author>
		<pubDate>Wed, 30 Jan 2008 22:49:14 +0000</pubDate>
		<guid>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9620</guid>
					<description>Yes, you have to use absolute path - this is clearly stated in Xdebug's installation manual (and manuals for every other zend extensions out there).</description>
		<content:encoded><![CDATA[<p>Yes, you have to use absolute path - this is clearly stated in Xdebug&#8217;s installation manual (and manuals for every other zend extensions out there).</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Pierre</title>
		<link>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9622</link>
		<author>Pierre</author>
		<pubDate>Wed, 30 Jan 2008 23:50:21 +0000</pubDate>
		<guid>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9622</guid>
					<description>Hi!

Yes, a zend_extension is not the same as a standard php extension. It does not use the extension path. I always forget it too, or every two installs ;)</description>
		<content:encoded><![CDATA[<p>Hi!</p>
<p>Yes, a zend_extension is not the same as a standard php extension. It does not use the extension path. I always forget it too, or every two installs <img src='http://blog.lucke.info/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: PHPDeveloper.org</title>
		<link>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9707</link>
		<author>PHPDeveloper.org</author>
		<pubDate>Fri, 01 Feb 2008 14:48:32 +0000</pubDate>
		<guid>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9707</guid>
					<description>&#60;strong&#62;Carsten Lucke's Blog: Configuration issues with Xdebug on Debian Etch...&#60;/strong&#62;


For anyone that's had an issue with getting XDebug to work ......</description>
		<content:encoded><![CDATA[<p>&lt;strong&gt;Carsten Lucke&#8217;s Blog: Configuration issues with Xdebug on Debian Etch&#8230;&lt;/strong&gt;</p>
<p>For anyone that&#8217;s had an issue with getting XDebug to work &#8230;&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: luckec</title>
		<link>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9719</link>
		<author>luckec</author>
		<pubDate>Fri, 01 Feb 2008 21:28:07 +0000</pubDate>
		<guid>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-9719</guid>
					<description>I guessed that it wasn't a Debian-specific problem. Debian is great and if the (dir-based) config wouldn't be so modular I may not even have noticed this problem. Just because I probably would have used a full path in the first place.

&gt;(Derick): I tried to make it a bit clearer in the Xdebug docs now.
Derick, there's probably no way to miss this, now. 
BTW: Would you prefer a postcard from Munich, Berlin or Mumbai? ;-)</description>
		<content:encoded><![CDATA[<p>I guessed that it wasn&#8217;t a Debian-specific problem. Debian is great and if the (dir-based) config wouldn&#8217;t be so modular I may not even have noticed this problem. Just because I probably would have used a full path in the first place.</p>
<p>>(Derick): I tried to make it a bit clearer in the Xdebug docs now.<br />
Derick, there&#8217;s probably no way to miss this, now.<br />
BTW: Would you prefer a postcard from Munich, Berlin or Mumbai? <img src='http://blog.lucke.info/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: PHP Encoder</title>
		<link>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-13737</link>
		<author>PHP Encoder</author>
		<pubDate>Sun, 23 Mar 2008 09:33:23 +0000</pubDate>
		<guid>http://blog.lucke.info/2008/01/30/configuration-issues-with-xdebug-on-debian-etch/#comment-13737</guid>
					<description>In fact it would be great if extension could take full path as well...</description>
		<content:encoded><![CDATA[<p>In fact it would be great if extension could take full path as well&#8230;</p>
]]></content:encoded>
				</item>
</channel>
</rss>
