![]() Latest known issues are regarded to version 1.10. If you are having problems with "Register Provider" then try updating to the latest Zend Framework. If you are trying to debug a Zend Framework project, make sure you set the Run Configuration - you can do this by selecting the "properties" of the project. XAMPP 1.7.1 is fine, with XDebug 2.0.4 VC 5.2 thread-safe. The workaround prevents the IDE from stopping at breakpoints. If you set up XDebug as described here, the Apache server crashes when you run or debug a file or project. Please see the application event log for more detail.ĭo NOT use XAMPP 1.7.0. The application has failed to start because its side-by-side configuration is incorrect. PHP Warning: PHP Startup: Unable to load dynamic library 'c:/wamp/bin/php/php5.2.9-1/ext/php_xdebug-2.0.4-5.3.0-vc9.dll'. If you are mapping server paths to project paths, you must map the full project folders to each other, not the parent folders. If there’s any other Zend modules in php.ini, comment them out. Make sure there’s nothing Zend other than xDebug in either phpinfo, php -m on the command line (if you’ve got command line php) or php.ini. ![]() I believe you might need to reinstall PHP, to make sure that it is "no". If it’s "yes", this could be a big problem. In your phpinfo, check that "Debug build" IS "No". I don’t know if this helped, but xdebug now works, so it didn’t hurt. I also uncommented the report_zend_debug = 0 line to make sure that this is off and not competing. This isn’t essential, but it helps a lot. ![]() Look at your other debugging-related php.ini settings. If this might affect you (it probably doesn’t), put 127.0.0.1 instead. Occasionally, on some systems, localhost isn’t localhost. The really important ones are the host, and making sure that whatever port you set in php.ini is matched by your client. ![]() If this gives you a fancy error screen with backtraces and some orange colouring, that’s a good sign - that’s xdebug at work!ĭon’t obsess over every php.ini option. Also, don’t forget to try them through a browser as well as the command line. When they hang, they can tie up the port and complicate the question. Only use those socket-based php test files like sparingly. It might be waiting for a browser to start a session - try it! I think has how. If netstat says port 9000 is busy listening, this is what it’s supposed to do. Generally, 'fail to bind' type errors are a sign that something is using the port in question. (on *nix) Use the command "netstat -a | grep tcp" when you need to see what’s going on with port 9000 there are often different php.inis for command line and for web server PHP. Always check there aren’t any other php.ini files you haven’t configured (on *nix, "find / -name php.ini"). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |