Hi!

Could you please upgrade to Xdebug 2.4.0RC2? I've fixed various things in there. If you can still reproduce it there, could you create a remote debugging log with that very simple script that you showed? You can make one by setting xdebug.remote_log=c:\temp\xdebug.org (pick a path the web server can write to please).

cheers,
Derick

Hi Derick

In the original report I noted that I am using php_xdebug-2.4.0rc2-7.0-vc14-nts.dll which appears to be the latest and greatest on the XDebug.org site. If I have not understood your request and there there is another version I should use please point me in the right direction.

Assuming the version I'm using is OK, I've attached a zip file containing two log files. One called xdebug-success.log shows stepping through the PHP code below without including $a as a watch. When you decode the base64 strings you will see there are watches for variables called $node, $activeDimensions and $dim (you can ignore these).

The other file, called xdebug-fail.log, show the same debugging experience but with an extra watch on the variable $a which is set in the code. This causes the XDebug session to fail and, so, not return an XML string which Eclipse reports as an error.

The version of Eclipse used is Neon (though the problem also occurs in Luna) and the version of the PHP Development Tool plugin used in Neon is 3.7 which as far as I can tell is as up-to-date as it is possible to be.

Let me know how else I can help.

<?php
ini_set( 'display_errors', true );

echo "Test for Derick";
$ver = phpversion();

$a = array();
$a['x'] = 'y';
$a['y'] = array( 'a' => 'b' );

return;

Sorry - had missed you used RC2 from your report. I've updated the version in the report's field too (which had beta1). This is exactly what I needed to try to reproduce and fix it. Thanks!

Sorry for the confusion. Thanks for taking a look. PHP 7.0 is quoted as being up to 2.5 times faster but in the case of the application I'm working on the improvement is much greater. I had hoped to use it debug mode because getting to the relevant part while debugging is equally much faster.

I just released Xdebug 2.4.0RC3, which hopefully addresses stability issues on Windows: http://xdebug.org/#2015_12_12 — Can you please try that? Make also sure you run this with PHP 7.0.0 (or later), and not a PHP 7 Release Candidate.

In case it does not solve the problem, please provide a full but short reproducible test case that I can run myself. That includes hopefully a single script, and an accompanying remote debugging log (which you can make by setting xdebug.remote_log=c:\windows\temp\xdebug.log in php.ini).

The latest version appears to make no difference. The attached file contains a log showing successfully stepping over the code above while not evaluating the expression $a. It also shows stepping over the code above while $a is an expression. In this case the debug session fails stepping over the line:

$a['x'] = 'y';

Bill

Let me add that I've used your latest and greatest (32-bit VC14 NTS) and the corresponding version of PHP 7.0 released on Dec 3rd.

Can I please have the exact script(s) that you used for the two logs? I need it to match it with the line numbers in the logs?

I copied the lines above into a php file and used these lines to produce the most recently attached file. Are you not able to reproduce this problem? If so, it would be great to know what you are doing differently so that you do not see a problem when using vanilla Eclipse and PDT.

I can reproduce this now.

I think I have this fixed in Git. Can you try php_xdebug-master-7.0-vc14-nts.dll from the tarball at http://xdebug.org/files/xdebug-vc14-latest.tgz ? This should have the fix too.

Yes, that's great it seems to work. I will be using over the next few days because PHP 7.0 is so much faster. If I find any more issues I will be sure to report them.

Perfect - I'll close this one. Please open a new issue if you find something else.