PHPStorm Debugging stopped...
I updgraded yesterday to Lion 10.7.3 and noticed that doing so, my debugging coincidently stopped working.
I've tried several time to re-initialize debugging sessions, resetting configurations, reloading the little bookmarklets, ... everything... I even r&r'd xdebug...
With first-line debugging on, I get a debug-window message in the IDE that briefly says that it's waiting for a connection with some random integer value...then I get the pink message at the bottom that tells me it can't connect to the debugger.... Browser-initiated sessions just run -- never connect.
Using PHPStorm 2.1.4...
So, any information on xdebug/phpstorm playing nice with 10.7.3 Lion? Any ideas on getting this working again?
Lost half-a-day yesterday trying to figure this out (again)...there's GOT to be an easier way.
Thanks...
Please sign in to leave a comment.
I set-up my index.php script as an entry point for the debugger-run -- with breakpoint set to the first line...
cannot connect to xdebug...
no xdebug logfiles are being generated...
Hello Micheal,
Sorry for delay.
Did you enable 'xdebug.remote_log' option (see http://xdebug.org/docs/remote#remote_log)? Please check you phpinfo() output.
Thank you for feedback!
Remote logging enabled...it was working prior to the 10.7.2 update, just like everything else...
I get the (very) brief message in the debug window that it's waiting for a session with a key {intvalue} before I get "cannot connect to the debugger..."
relevant php.ini info:
Hello Micheal,
Please note that the value of the xdebug.remote_log option should be a path in your local file system. See http://xdebug.org/docs/remote#remote_log.
Please set a correct value and provide a log.
Thank you for feedback!
Hi Nikolay,
Setting the xdebug.remote_log had no effect...
It wasn't set before, when it was working, just to let you know...everything quit working after the 10.7.2 update...
I have a simple index.php script and when I attempt to run the the debugger (Shift+F9), I get the "waiting for key from ide with value xxxx" message flashes up (so quickly I can't get exact verbiage) before the "debug connection with xdebug was not established"....and there's nothing in the xdebug log file.
Executing with debug-mode on from the browser has no effect. I have a cookie set under XDEBUG_SESSION with the following values set:
I've gone around in circles so much on this...is there an easy way to zero-state the debugger settings and then start-over?
What's the best tutorial document to set this up for this release? (2.1.5 PHPStorm and OS X 10.2.7)
Thanks!
--mike
Ran a quick test from the command line using this script to show that my installation xdebug is working:
And got the expected output:
0.00115990638733
0.034453868866
wierdness deluxe continues to be 0-bytes written to my xdebug.log file...
Also, I tried connecting to xdebug from netbeans but that failed too...
Thinking more seriously about Apple's 10.7.2 and XCode updates as root cause...has anyone on your end gotten the debugger working with this (new) environment?
Thanks...
Hello Micheal,
First of all please note that script running from command line and script running on a server usually use different php.ini files.
Also please try to use the latest stable version instead of development.Thank you for feedback!
I know that, thanks. I've not got a separate ini file for my cli php -- it's showing the same dump info...and I'm still on 2.1.5 for the IDE...I tried the 3.0 EAP to see if I could isolate the issue to the IDE but it didn't work there either.
Still waiting to hear if anyone's gotten this working on 10.7.2 with the XCode update...
Thanks!
--mike
Micheal,
I mean stable version of Xdebug.
Thank you for feedback!
ooo - nice catch...
ok - so re-compiled and installed xdebug so that I have the below config reported via the browser....
and still the same responses from the IDE -- waiting for the incoming IDE connection with value {x}...then: Debug connection with Xdebug was not established...nothing in the debug log...
Micheal,
I still see mistakes in your php.ini settings:
Thank you for feedback!
Morning Nickolay,
I've completely disabled the xdebug.ini file and am loading xdebug params from the php.ini file. Even though I have remote_enable set to 1, it still shows as Off in the phpinfo() output.
According to Xdebug man page, is the connection cannot be established, the script will continue as if the value was set to 0. Is this why the remote_enable is showing as Off?
I've changed the remote_host value to "localhost" in the php.ini and in the PHPStorm configuration. I am runnning everything off my laptop.
I've also reset the value for idekey back to the default: 'PHPSTORM'. What's interesting here is that the change does not propogate to the local value:
PHPSTORM
I reset the remote_log to a path with my source base just to test that the reset is working:
but there is still zero output to the debug log when I proc debugging from either PHPStorm or from the browser.
I have (within PHPStorm) Xdebug Proxy as:
IDEkey: PHPSTORM
Host: localhost
Port: 9000
I ran my phpinfo() output through the xdebug checker:
And I generated new bookmarklets...
When I attempt a debugging session, I still get the same errors: waiting for IDE connection with Key: {integer} (it flashes very quickly so not sure about exact verbiage) and then the pink message "Debug connection with Xdebug was not established"
When I launch from the browser, the app just runs in-window and never flips focus back over to PHPStorm.
Thanks for all your help, Nickolay -- I know this is a huge pain...
--mike
Micheal,
Xdebug debugging functionality completely dependent on 'xdebug.remote_enable' option (logging won't work when option is disabled).Ensure that the option is enabled in your script (check the value of the 'ini_get('xdebug.remote_enable')' call).
Also please try to use latest PhpStorm EAP build (we provided debugging autoconfiguration there) with your stable version of Xdebug.Thank you for feedback!
Hey Nickolay --
As usual, thanks for your patience and perseverance.
I got xdebug.remote_enable setting to finally be on and my debugger is back! In all fairness to you and your product, the problem was a typo in my php.ini file: xdebug.remote.enable != xdebug.remote_enable. Geh. PBCK.
So life is awesome again - thanks again for all your help and willingness to deal with this issue for so long!
You're the best!
--mike
Micheal,
You're welcome!
Thank you for feedback!