I work in a Mac (OSX 10.10.3 Yosemite), with Bitnami XAMPP 5.6.3, Netbeans 7.3.1, and the xdebug configuration showed down. With my "normal" PHP projects everything works fine, but now I am trying to learn Zend Framework, and I have installed ZendFramework-1.12.17, for which I reached to obtain a "Hello world" in a PHP 5.3 project, but when I try to debug the same project, the status bar of the debbuger remains "Waiting for connection netbeans-xdebug" forever.
I searched the web, but I think that this is so specific case that I could only find an answer on this forum recomending to install XAMPP 1.7.0 :( very old version) that has Zend Extension Manager, something that 1) doubt it can work with my configuration and 2) can affect my other projects.
Can someone help me please? Thank you and best regards.
In php.ini:
zend_extension = /Applications/XAMPP/xamppfiles/lib/php/extensions/no-debug-non-zts-20131226/xdebug.so
/xdebug.so
xdebug.remote_enable=1
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.remote_host=127.0.0.1
xdebug.remote_port=9000
Related
I made a mistake and allowed Ubuntu 18.04 updates to be installed. NetBeans 12.1 cannot connect to Xdebug after doing this with the same configuration. I think the problem is with the newer version of Xdebug (3.0.2).
# cat /etc/php/7.2/apache2/conf.d/20-xdebug.ini
zend_extension=xdebug.so
xdebug.remote_enable=on
xdebug.remote_log="/var/log/xdebug.log"
xdebug.remote_host=localhost
xdebug.remote_handler=dbgp
xdebug.remote_port=9003
Anyone faced such problem?
I have spent a whole day and a half trying to get the NetBeans ISE 12.0 debugger working - it was always hanging on “Waiting For Connection (netbeans-xdebug)”.
I have now solved this - as you say, Xdebug version 3 is very different to version 2 and most of the documentation on the web has not caught up. This is the page that you need: Upgrade Guide
This is the configuration that works for me (I kept my IDE setting to use port 9000):
zend_extension=/usr/lib/php/20180731/xdebug.so
xdebug.mode=debug
xdebug.start_with_request=trigger
xdebug.client_host=127.0.0.1
xdebug.client_port=9000
The problem:
I can not get xdebug to work with PhpStorm or NetBeans in localhost. I have the proper Xdebug ext installed based on the wizard. I can see Xdebug is installed properly from phpinfo() and php -v output. I got a new hard drive at work with a new OS install and ever since then I can't get Xdebug setup to work.
I can not get the breakpoints to hit when accessing the application through the web/Postman. It's like the breakpoints aren't there or no connection is detected. There is no log file generated.
What does work:
In PhpStorm I hit the debug phpunit.xml icon then it runs my PHPUnit tests and Xdebug does work, breakpoints are hit, and log files are generated.
I have tried:
Many versions of Xdebug including 2.55, 2.60, 2.61 both 64 and 32 bit and both thread safe and non thread safe
Hosting with php -S and with XAMPP Apache
NetBeans and PhpStorm
My php.ini xdebug section
[Xdebug]
zend_extension=C:\xampp7.1\php\ext\php_xdebug-2.6.1-7.1-vc14.dll
xdebug.remote_enable=1
xdebug.var_display_max_depth = -1
xdebug.var_display_max_children = -1
xdebug.var_display_max_data = -1
xdebug.remote_host=127.0.0.1
xdebug.remote_port=9000
xdebug.remote_log=C:\xampp7.1\php\ext\xdebug.log
xdebug.idekey="PHPSTORM"
I don't know what else to try. I thought maybe it could be a company firewall issue or something but none of my coworkers have this issue nor did I before the new HD. I'm on Windows 10 Enterprise could it be some Windows configuration?
Credit to LazyOne for figuring out the solution!
Adding xdebug.remote_autostart=1 to the php.ini worked! Thanks so much
I'm attempting to install xdebug on to my atom in order to debug my magento 2 code on a wamp server. I think i have installed xdebug successfully according to my phpinfo() file however when I come to attach a debugger in atom, xdebug doesn't appear.
My php.ini settings are:
; XDEBUG Extension
[xdebug]
zend_extension ="c:/wamp64/bin/php/php7.1.16/zend_ext/php_xdebug-2.6.0-7.1-
vc14-x86_64.dll"
xdebug.remote_host=127.0.0.1
xdebug.remote_enable = 1
xdebug.remote_connect_back=1
xdebug.remote_port = 9000
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.remote_autostart=true
;xdebug.profiler_enable = off
;xdebug.profiler_enable_trigger = Off
;xdebug.profiler_output_name = cachegrind.out.%t.%p
;xdebug.profiler_output_dir ="c:/wamp64/tmp"
;xdebug.show_local_vars=0
I haven't managed to find a complete tutorial online that works. I was following the Atom Tutorial, however I could not get it to work. I think the error may be with the IDE key as i'm not sure what to do with it. I've followed almost every youtube video but it still seems i'm doing something wrong.
If someone could post a working tutorial I would very much appreciate it. Thanks in advance :)
Screenshot of the problem
PHP Version 7.1.16
Xdebug Version 2.6.1
I've seen in the comment section of the question, that you have moved to Visual Studio Code, But I'll write down this answer anyway as someone else may find it helpful.
I've also came across this issue: "Debugger not attached".
When you install php-debug it require one more package: atom-debug-ui - which is not the issue.
Once php-debug is installed it also recommends to install couple more packages: ide-php and atom-ide-ui. The latter package can be problematic as it also contains it's own debugger UI.
Therefore when you install all four packages, there are two set of debugger UIs running on your Atom IDE.
To overcome this, what you should do is disabling atom-ide-ui's debugger. You can also go ahead and uninstall atom-ide-ui as it's not required for php-debug to run. If ide-php package depends on atom-ide-ui, you can uninstall ide-php as well.
I understand the question is about a setup which runs on WAMP. I've written this article on how to set it up on Ubuntu based Linux. In that article I've provided all the details you want. I don't think it would be too hard to translate the information to Windows based setup.
I'm running Eclipse on Ubuntu 13.1 (I know, the worst Linux ever).
The fact is that I'm not used to Eclipse moved from Komodo 2 weeks ago, and the main reason why I'd migrated to Eclipse is debugging. But I can't put that to work. I already follow some tutorials with no joy.
My Xdebug is installed and working (checked with phpinfo()). I'm configuring Eclipse to work with Xdebug, but when I start the debugging it ignores the break points, even if I check to "Break at First Line" it won't break.
Here's a summary of the scenario that I have:
System: Ubuntu 13.1 64bits
PHP: 5.5.3-1ubuntu2.1
Xdebug: 2.2.3
Eclipse Platform: 3.6.2
PDT: 2.2.1
Tnx!
Problem solved! Actually the xdebug was installed but I missed one configuration. The xdebug.ini file was with only the following line:
zend_extension=/usr/lib/php5/20121212/xdebug.so
I'd added the following lines:
xdebug.remote_enable=1
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.remote_host=127.0.0.1
xdebug.remote_port=9000
and it's working! Just reconfigured the eclipse debug and is working.
I'm having a very hard time getting a breakpoint to hit in some php code. I don't do much php so might be newbie error.
I've read though the other questions, PDT Install Instructions, and XDebug Install Instructions
For both debuggers, the instructions expect a config section to show up in the phpinfo() and it doesn't for me.
Some info about my current setup
Windows
AMPPS
PHP 5.2.17
Website runs fine
I need some help with things to check or ideas what I might need to do differently.
I'm stuck pretty much for now.
You can follow this post to install Xdebug for PHP in AMPPS.
Two main things that fixed my issues.
Turned off Iron PHP Loader
copied the non-ts XDebug .dll, even though the php config shows thread safe = enabled. This dll seems to work
The config settings are below for reference:
;Stuff to allow debugging in eclipse
zend_extension="C:\Program Files (x86)\Ampps\php\ext\php_xdebug-2.2.3-5.3-vc9.dll"
xdebug.remote_enable=On
xdebug.remote_autostart=On
xdebug.remote_handler=dbgp
xdebug.remote_host=127.0.0.1
xdebug.remote_port=9000
xdebug.remote_mode=req
You do have to make sure and add the extra xdebug configurations or eclipse won't cooperate.