Can you try reducing the test case? For example, let's say it crashes in index.php.

If you make index.php start with the following, does it still crash?

<?php

echo 'hi there';
die;

?>

If this doesn't crash, how low can you move the die; before it does crash?

If you can remove a bunch of code from possibly being the problem, you might be able to narrow it down to a small chunk of code (like just one file you include) that causes it. This might be something you could upload, so other people can reproduce it and possibly fix it.

Unfortunately, just knowing that it can crash when pointed at certain PHP code probably won't lead to a fix very directly or soon. It's sorta like knowing there's a typo somewhere in a bookcase full of books. Sounds pretty believable (there's likely more than just one, in fact), but it's hard to find without more info than that.

-[Unknown]

Hi,

Here's an example of "buggy code". I isolated it by using die() calls on the source code. It's extracted from a function :

$res = database::$db->fetch_result($stmt, 'ROW');

echo '<h2>get_Acces Test 2 post query</h2>';
var_dump($res); //displays the expected value
//die(); //it works

if($res[0][0] > -1) {
...code...
return true; //it fails (won't be returned)
} else {
echo '<h3> test superieur a -1</h3>';
// die(); //it works
return false; //it fails (won't be returned)
}

It seems that the function works properly but its the return keyword seems to fail : when I try to get the result of this function, it crashes. Same error as above. I've upgraded xdebug in 2.3.3, same error. It is not the first function called in the script, the other ones are running properly.

If I find another case like this one where it crash, I'll report it.

Can you still reproduce this with PHP 5.6.28, and Xdebug 2.5.0RC1? Or is this no longer an issue for you?

I could not reproduce this, as there was no reproducible case, and no additional information was presented. I am therefore closing this report.