xdebug

# composer require oygza/aliyun-php-sdk-afs You are running composer with xdebug enabled. This has a major impact on runtime performance. See https://getcomposer.org/xdebug The "https://packagist.laravel-china.org/packages.json" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed Failed to enable crypto failed to open stream: operation failed https://packagist.laravel-china.org could not be fully loaded, package information was loaded from the local cache and may be out of date

I have the following function: function foo($p) { if ($p == null) throw new Exception('bla'); if ($p == null) { throw new Exception('bla'); } [...] } My Test for this function is not covering the lines throwing the exception. But PHPUnit tells me the first 'throw'-statement is coverd, the second not. Maybe the first is interpreted, but it is not executed. So I don't want to get the message '100%' if I have not reached 100%. Is this a bug in xDebug or do I have the possibility to configure xDebug/PHPUnit? xDebug's code coverage metrics are statement-based rather than line-based. What this means

I'm using (or trying to anyway) use the bundled XDebug with XAMPP 1.7.2. It comes bundled with Apache 2.2.12, PHP 5.3.0, XDebug 2.0.5 and Zend (not sure on version) This is a totally fresh install of XAMPP, the only thing I've added to php.ini (at xampp/php/php.ini) is: zend_extension_ts = "C:\xampp\php\extensions\php_xdebug.dll" [xdebug] xdebug.auto_trace = 1 xdebug.collect_includes = 1 xdebug.collect_params = 1 xdebug.collect_return = 1 xdebug.default_enable = 1 xdebug.extended_info = 1 xdebug.show_local_vars = 0 xdebug.show_mem_delta = 1 xdebug.trace_format = 1 xdebug.trace_options = 0

I use PHPStorm along with Xdebug to step through my code. PHPStorm is running on a Windows 7 machine, and my local webserver is running on a separate CentOS 6.4 machine. I've done a phpinfo(); to verify that Xdebug is being loaded by PHP, and it is. The following are the settings for my Xdebug in the PHP.ini: [xdebug] zend_extension="/usr/lib/php/modules/xdebug.so" xdebug.remote_enable = 1 xdebug.remote_port = 9000 xdebug.remote_host = "192.168.1.130" xdebug.remote_log = "/var/log/httpd/xdebug_log" I similarly setup PHPStorm to use my CentOS server as the debugging server, and I listen for

My problem: When launching a debug configuration from Eclipse for one of my php pages, the page opens successfully in Chrome but the Eclipse debugger freezes at 57% (in the bottom right hand corner of Eclipse) and never progresses further. The set breakpoints are never reached. My setup: MAMP 2.2 PHP 5.3.3 Eclipse Kepler Eclipse PDT Xdebug 2 virtual hosts with roots at /Applications/MAMP/htdocs Apache Port: 80 MySql Server Port: 3306 My virtual hosts setup within MAMP is working fine. Below are screenshots concerning the Xdebug setup: I suspect the problem is being caused by my virtual hosts.

Facts about my system Ubuntu 15.10 Php 5.6.11 Symfony 2.7 PhpStorm 10 xDebug 2.4 I really struggle getting xdebug to work under my Symfony project in PhpStorm. I installed xdebug configured the php.ini file in my /etc/php5/apache2/php.ini and in the cli folder [xdebug] zend_extension=/usr/lib/php5/20131226/xdebug.so xdebug.remote_enable = 1 xdebug.remote_port = 9000 xdebug.idekey = PHPSTORM xdebug.remote_host=127.0.0.1 But when I "Start listening for PHP Debug Connections" and set breakpoints in my application and run tests with breakpoints in it, Xdebug just doesn't break the programm. php -v

最近在用Go重构一个PHP项目，代码写的有点乱，也没文档，没注释，总之就是功能基本靠猜， 然后我找了个小工具快速理清代码执行流程，帮助自己理解代码逻辑。 首先打开xdebug的分析器 xdebug.profiler_enable = 1 xdebug.profiler_output_dir = /tmp 分析器有什么用，有兴趣可以去 xdebug官网 自己去看。 但是xdebug分析器输出的内容对人是不友好的，使用工具才能方便的看到自己想要的，这里我们使用 webgrind 帮助我们查看这个内容。 webgrind依赖python和graphviz，安装完成之后修改webgrind的config.php文件 /** * Path to python executable */ static $pythonExecutable = '/usr/bin/python'; /** * Path to graphviz dot executable */ static $dotExecutable = '/usr/local/bin/dot'; 然后在webgrind目录下执行 php -S 127.0.0.1:19000 //使用php内置http服务器，php version >= 5.4 webgrind可以生成流程图和分析每个方法函数的执行时间