xdebug

How to debug PHP application using Eclipse PDT (xdebug and zend debugger)

我只是一个虾纸丫 提交于 2019-12-04 13:34:38
问题 I'm working on one application. I am using Eclipse php Helios IDE for developing php application. I wanted to know below things related to this IDE, so that i can implement PHP application instantly as well as very efficiently : 1) How to do remote debugging using Eclipse PHP Helios IDE 2) What is the pros and cons of xdebug and zend debugger 3) Which debugger should we use from xdebug, zend debugger. 4) Is there any other debugger available apart from above two mentioned. Below links i

PHP (WAMP) - Exlipse PDT, xDebug: not stopping at breakpoint

青春壹個敷衍的年華 提交于 2019-12-04 12:33:49
I am able to debug only if I check the Option "Break at First line" . If I un-check it and place a breakpoint at some line then the debugger doesn't stop at that line. I need the debugger to stop at the breakpoints I set, not at the fist line of the file. I've added the following lines in my php.ini file: zend_extension = "c:/wamp/bin/php/php5.3.8/ext/php_xdebug-2.1.2-5.3-vc9.dll" xdebug.remote_enable = on xdebug.remote_handler = dbgp xdebug.remote_host = localhost xdebug.remote_port = 9000 I'm also being able to debug properly on Notepad++ DBGp debugger with this same setting. There are

Why does foreach increase refcount by 2 instead of 1?

不羁岁月 提交于 2019-12-04 12:23:50
问题 NikiC stated in another thread: Right before [a foreach] iteration the $array is "soft copied" for use in foreach. This means that no actual copy is done, but only the refcount of the zval of $array is increased to 2. However, my test code is showing a different result: $array = array(0, 1, 2); xdebug_debug_zval('array'); // refcount=1, is_ref=0 // so far so good foreach ($array as $key => $value) { xdebug_debug_zval('array'); // refcount=3, is_ref=0 } // why is refcount 3 instead of 2? Just

Passing PHP arguments into NetBeans into a page that features symfony url-routing

我怕爱的太早我们不能终老 提交于 2019-12-04 11:49:35
I am doing the Jobeet tutorial that features url routing. The url routing (I think that's the proper term) makes urls look like this http://localhost:8080/frontend_dev.php/job/extreme-sensio/paris-france/2/web-designer I would like to debug into this page however I cannot properly pass arguments into NetBeans. I set the arguments in NetBeans "Run Configuration" area to this job/extreme-sensio/paris-france/2/web-designer however the url that is executed is this (notice the ? that NetBeans automatically appends to index file) http://localhost:8080/frontend_dev.php?job/extreme-sensio/paris-france

Xdebug triggered by Code Sniffer in PHPStorm

血红的双手。 提交于 2019-12-04 11:42:08
I have both xdebug and Code Sniffer working great on my installation of PHPStorm, but the one really annoying part is that the debugger now seems to be treating Code Sniffer errors as breakpoints and interrupts the code to let me know of style warnings while I'm trying to test out code. What can I do to prevent Code Sniffer from being caught by the remote debugger in PHPStorm? PS: I'm running Apache, using virtual hosts to map certain URLs to folders on my computer, and code sniffer never triggered PHPStorm's remote debugger explicitly, while my site caused PHPStorm to ask me if I wanted to

Auto setting xdebug.remote_host ip address with vagrant/puppet

此生再无相见时 提交于 2019-12-04 11:41:20
问题 I'm in the process of setting up a Vagrant environment using puppet for provisioning. I'm stuck with one issue, I would like xdebug to 'just work' when running vagrant up however I need to specify the host machines ip address in the php.ini file xdebug.remote_host , obviously this is going to be different on each machine the config is used so I would like a way to automatically update that value when issuing vagrant up . VagrantFile: config.vm.network :forwarded_port, guest: 9000, host: 9000

最全Phpstorm+Xdebug动态调试配置

泄露秘密 提交于 2019-12-04 11:05:47
整理人:pt007@vip.sina.com 1、准备环境 主机:window10 Phpstorm版本:2018.2.1 X64 Phpstudy版本:2018 PHP版本:5.6.27 php开发工具下载: https://www.php.cn/xiazai/gongju 2、安装步骤 2.1 安装Xdebug 本地的环境是用phpStudy搭建的,直接在phpStudy可以勾选Xdebug: // 打开并配置php.ini,保存后记得重启phpstudy: php.ini文件位置:E:\phpStudy2018\PHPTutorial\php\php-5.6.27-nts\ [XDebug] zend_extension="E:\phpStudy2018\PHPTutorial\php\php-5.6.27-nts\ext\php_xdebug.dll" xdebug.profiler_output_dir="E:\phpStudy2018\PHPTutorial\tmp\xdebug" xdebug.trace_output_dir="E:\phpStudy2018\PHPTutorial\tmp\xdebug" xdebug.remote_enable=1 xdebug.profiler_enable_trigger=0 xdebug.remote_handler

php eclipse debugging

血红的双手。 提交于 2019-12-04 10:53:25
I am runing a php script using eclipse. when a set breakpoint and run the script it throws me this error. form the error it is apparent that i have change something the php.ini file. but i dont know what i have to change to make either zend or xdebug. even i dont know what the differnce b/w them. following the error The session could not be started. In order to generate debug information, please make sure that the debugger is properly configured as a php.ini directive I ran into this error also, and my issue turned out to be a misconfiguration of Eclipse. In Eclipse, I had configured (in

Netbeans xdebug nightmare

泪湿孤枕 提交于 2019-12-04 10:24:49
I know what you're thinking, ANOTHER netbeans xdebug post? Well, I've tried everything I've seen in other posts, and nothing seems to work. Here's my setup: OS: Ubuntu 9.10 PHP: 5.2.1 Netbeans: 6.8 The following is in my /etc/php5/apache2/php.ini zend_extension=/usr/lib/php5/20060613/xdebug.so xdebug.remote_enable=1 xdebug.remote_handler=dbgp xdebug.remote_host=localhost xdebug.remote_port=9000 xdebug.idekey="netbeans-xdebug" I've tried switching ports (I've tried 9001, 9002, and 9034 so far), using zend_extension_ts, adding additional xdebug parameters in the config file, but nothing seems to

Disabling xdebug when running composer

邮差的信 提交于 2019-12-04 07:25:35
问题 When running composer diagnose , I get the following error : The xdebug extension is loaded, this can slow down Composer a little. Disabling it when using Composer is recommended. How can I disable xdebug only when I'm running Composer? 回答1: Update : The issue has been fixed in Composer 1.3. Update composer to the latest version by executing composer self-update , instead of trying the following workaround. Here is my modification of @ezzatron's code. I have updated the script to detect ini