Posted February 22nd, 2010 by smclenithan
Before upgrading yesterday my debug mode was set to xdebug because DBG just was not hitting the breakpoints and this worked fine.
But now Xdebug does not render php (but it does hit breakpoints), php code is spat out to the browser. DBG does render the php fine but it does not hit any breakpoint ever,, even ones that always should like on a require_once line.
Any idea on what is wrong here or what I should do?
// Steve
juanc says:
Are you using the latest build from here?
http://www.jcxsoftware.com/download.php
Also, are you using your own web server or VS.Php's built-in engine?
smclenithan says:
Built-in server.
Didn't notice there was already an update, installing now and will report back.
smclenithan says:
Updated to the latest build on the download page. Same results. DBG renders PHP fine but never hits breakpoints.
Xdebug doesn't render PHP. Spits out everything to the browser.
juanc says:
Is this with a standard project with no custom settings, etc? Using the built-in engine?
BTW, DBG does not work with the built-in engine. That is why breakpoints don't stop. DBG is not supported on 5.3
smclenithan says:
After an extensive session of bashing my head on the keyboard I realized the problem is the new php settings.
<? must be <?php
and several other things. But this was the major issue.
Can I change this in the php.ini that is generated or is it overwritten every time?
smclenithan says:
Figured that part out. Odd side effect though. The custom specified php.ini listens to my settings about short_open tags, but it is not loading ANY PDO drivers even though they are all set to on, the same as in the default one. Any thoughts on this?
smclenithan says:
Found that if I edit php-xdebug.ini in the vs.php install directory and don't specify a custom ini file this one will be copied over and the extensions will run fine. Set my short open tag settings here and all is good.
Still would like to know why none of the extensions/pdo drivers load when using a custom ini file though.