xdebug

xdebug breakpoints work but step over does not

假装没事ソ 提交于 2019-11-28 01:08:55
I have installed Xampp on Windows (Well actually both xampp and wamp but both have the same problem), and enabled xdebug. I have installed the latest eclipse for php with pdt included. The breakpoints are working correctly however if I press f6 or f5 the current line does not get updated, the variables change as if I had stepped to the following line but the highlighted line remains the same. Any ideas? I attach some screenshots to make it easier to understand: Breakpoint works: I press f6, lineno and $a changes in the 'Debug' and 'Variables' window: I press f6 again: I tried updating to the

Netbeans + Xdebug + php not working

雨燕双飞 提交于 2019-11-28 00:51:15
问题 My netbeans does not work the breakpoints using xdebug, my configuration looks correct, so I configured the first time I ran up to stop debugging the first time since then has never worked, someone had this problem? The version of my netbeans is 6.8 and the version of php is 2.5.2. my php.ini: zend_extension_ts = d:\wamp\bin\php\php5.2.5\ext\php_xdebug-2.0.2-5.2.5.dll xdebug.remote_enable=on xdebug.remote_handler=dbgp xdebug.remote_host=localhost xdebug.remote_port=9000 xdebug.idekey=netbeans

XDebug, how to disable remote debugging for single .php file?

爷,独闯天下 提交于 2019-11-27 23:42:00
问题 I'm using Eclipse IDE + remote Xdebug. EclipseIDE is listening 9000 port for some kind of Xdebug information. There are some php scripts running by cron on server. So, every cron execution xdebug is sending information to my workstation and EclipseIDE is trying to find this file in my project. But file couldn't be find because cron running scrits do not relate to the project I'm working with. So, every cron run Eclipse IDE is alerting this message http://img2.pict.com/22/fc/86/3299517/0

How do I examine defined constants in PHP?

时光总嘲笑我的痴心妄想 提交于 2019-11-27 22:54:31
I'm stepping through the source code of CodeIgniter with Xdebug in NetBeans and I'm looking for a way to see defined constants as they are defined. If it's not possible, are there any other ways to display all defined constants? Take a look at the get_defined_constants function. It will return an array of all the defined constants in the code up to the point of the function call. You can then use print_r to print out the array. This kind of practice I use is quite decent as it shows only custom/user created constants. print_r(var_export(get_defined_constants(true)['user'], true)); Wrap this

Netbeans and Xdebug in Linux

▼魔方 西西 提交于 2019-11-27 19:52:06
I have installed Xdebug, and I can confirm from phpinfo() that it is correctly installed. I have taken all the steps given in all of the sites that come up with I google "netbeans xdebug install, etc". It still does not work in Netbeans. Is there any advice that someone can offer? Here is my php.ini debug section... [xdebug] zend_extension = /usr/lib/php5/20090626/xdebug.so xdebug.remote_enable = 1 xdebug.remote_mode = "req" xdebug.remote_handler = dbgp xdebug.remote_host = 127.0.0.1 xdebug.remote_port = 9000 xdebug.idekey = "netbeans-xdebug" Any help would be greatly appreciated! Since the

Check if xdebug is working

▼魔方 西西 提交于 2019-11-27 18:26:52
Without installing a texteditor or an IDE, is it possible to test if xdebug is working, i.e. if it can debug php code? The only part xdebug comes up in phpinfo() is the following: Additional .ini files parsed /etc/php5/apache2/conf.d/mysql.ini, /etc/php5/apache2/conf.d/mysqli.ini, /etc/php5/apache2/conf.d/pdo.ini, /etc/php5/apache2/conf.d/pdo_mysql.ini, /etc/php5/apache2/conf.d/xdebug.ini It is not mentioned in the phpinfo() anywhere else. Without actually doing some debugging, I guess you can't be certain that a debugger is working. But you can be pretty sure -- I guess one should assume that

How to trigger XDebug profiler for a command line PHP script?

我只是一个虾纸丫 提交于 2019-11-27 16:38:47
XDebug offers the configuration directive "xdebug.profiler_enable_trigger" that allows to activate profiling by passing the GET or POST parameter "XDEBUG_PROFILE" when calling a script via HTTP. This is handy if you don't want profiling for ALL of your scripts but only for a few special cases without always changing your PHP configuration. Is there a way to achieve the same behavior for command line PHP programs? I tried to pass the "XDEBUG_PROFILE" as a command line argument but it didn't work. In general, profiling command line PHP works well, but I'd like to have the same per-call

phpStorm中使用xdebug工具调试docker容器中的程序

匆匆过客 提交于 2019-11-27 16:36:18
前提准备 phpstorm开发软件 + dnmp(docker + nginx + mysql +php) 配置好hosts 映射比如 /etc/hosts 127.0.0.1 tp5.dev 为现有的php环境安装好 xdebug 扩展,安装成功之后可以通过页面输出 phpinfo() 查看是否安装成功xdebug 安装能够进行调试的ieda环境,一般对于php程序开发者来说,使用 phpStorm 较多,本文也是通过这个讲述。 成熟的 docker 构建的环境。 可以使用 https://github.com/yeszao/dnmp 配置xdebug [XDebug] ;开启xdebug支持远程调试 xdebug.remote_enable=1 ;远程调试的主机,一般都是docker宿主机器,本地调试就是本机,ip可以通过`docker inspect 容器名获得` xdebug.remote_host=172.19.0.2 ;远程调试机器的端口,一般是9000,和后面讲到的phpStorm里面保持一致 xdebug.remote_port=9000 ;idekey 对接调试的密钥,和后面phpStorm里面的务必保持一致 xdebug.idekey=PHPSTORM ;自动触发调试,可以将这个值设为1; xdebug.remote_autostart=1

Disable HTML stack traces by Xdebug

夙愿已清 提交于 2019-11-27 15:56:14
问题 The administrator has installed Xdebug 2.1.1 in our shared PHP 5.3.0 server in order to use its debugger. Now, I can hardly read the stack traces of uncatched exceptions because they are formatted by Xdebug with annoying colours that interact badly with the site's CSS: Since PHP runs as Apache module, I've tried to disable this feature in an .htaccess file but I can't make it go: php_flag xdebug.default_enable Off php_flag xdebug.overload_var_dump Off php_flag xdebug.show_exception_trace Off

php xdebug: How to profile forked process

被刻印的时光 ゝ 提交于 2019-11-27 14:08:35
问题 I am running a PHP daemon to be profiled. The started php process loads all required data, forks itself to distribute workload over all cores, waits for the forked children to finish, and collects the results generated by the children. Since I am sharing CLI environment with other users, I need to start xdebug profiling by injecting php.ini values into the shell call. $ php -d xdebug.profiler_enable=1 -d xdebug.profiler_output_dir="/home/xxx" daemon.php The generated cachegrind-file, how ever