Related thread http://devnet.jetbrains.net/message/5457450#5457450

This is not enough information for me; can you please provide a short, self-contained script (preferrably < 10 lines) and a remote debugging log (see http://xdebug.org/docs/all_settings#remote_log on how to make one).

I will try to get this done, but please understand that I am also in the middle of a couple of larger projects, so it may not be right away. If I can get to this maybe during our holiday in a week or so, I may be able to put the problem build of xDebug back and generate a log for you. I appreciate your understanding on this.

In the meantime, I hope you can do some testing with the MAC OS Snow Leopard (completely updated), using the native server that comes with OS X, using PHPStorm v3~4 and the RC version of xDebug I am referring to.

I am doing something really very simple using a function like:

function redirect_to($location = NULL)
{
if ($location != NULL) {
header("Location: {$location}");
exit;
}
}

The file name of $location being passed is the name of a local file in the same folder, calling the function like this: redirect("filename.php");

I see it was crossed out in my description, but the behavior looks very much like "bug 0000532 fixed in [2010-02-27]" to me. The debug session just terminated the session and reports disconnecting from PHPStorm in both the IDE and the browser.

Again, our holiday time is in about a week.

Regards,

-John

I don't have a Mac, so I can't test on that. However, the most important thing for me is:

• a short script
• a remote debug log that shows the problem and matches a debugging session for the short script.

without that, I probably can't reproduce it, and hence not fix the bug.

I set the setting: "xdebug.remote_log="/Users/john/Desktop/xdebug.log" and substituted the .so file that causes the error. I can indeed reproduce it using PHPStorm 4.0RC3 (and previous release versions).

Unfortunately, no xDebug log is being created. I have tried a few locations with no resulting log file.

I believe I have provided a code snipit that is adequate to reproduce the error.

I can't be the only in the universe with a MAC and that uses xDebug.

Trying to help you here but I can't seem to provide you with a log file per the instructions on your webpage.

Please try the just released Xdebug 2.2.0RC2, which I believe fixes this issue. I think it's a duplicate of 0000774.

Seems to have resolved this issue. If I see more issues I will report them.

What do you think the time frame will be, an estimation that of course is subject to change, will be the final release date for xdebug 2.2.x?

Hoping to release 2.2.0 on Wednesday.