Error message: "unexpected script termination, debugging termination" while debugging PHP using Xdebug and Eclipse

Question

When debugging, the following error appears:

Php.ini settings:

xdebug.remote_enable=true xdebug.remote_host=localhost xdebug.remote_port=9000 xdebug.remote_handler=dbgp 

Answer 1

Assuming no syntax errors, make sure you don't have a clock that causes the script to crash when the debugger tries to evaluate them.

In my experience, this is the most common cause of such an early death.

Regardless, you can also change your internal web browser, since IE tends to provide critical error messages or use an external browser session (and use remote debugging).

Answer 2

If you use mod_fcgid in your apache

the default value set for FcgidIOTimeout is 40 seconds, so you can complete this xdebug in 40 seconds

to change this value you need to add the following line to the apache httpd.conf file

 FcgidIOTimeout 600 

it is within 10 minutes, you can set this value for any other period according to your requirement

Even I had the same problem, I found this solution for further details by following the links below

http://jonathonhill.net/2011-05-05/uploading-large-files/ (linked link that provides information about the value) http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html (and search FcgidIOTimeout)

Answer 3

deleting watch expressions solved this problem for me

Answer 4

I ran into the same problem on a different platform.

Starting x64 linux with Eclipse 3.7.2, PHP 5.4.3 and Xdebug 2.2.0, this error message may appear when viewing variables.

See Xorg issue # 797 and issue # 824 .

I can confirm that this problem is not resolved in version 2.2.0. Permission will be executed after 2.2.0, so you will need to download git copy (check the download page ).

After compiling the git version, the problem is fixed.

Answer 5

I also had this problem, after some time I decided to return to version 2.2rc, because the latest version of this problem does not occur (in fact, this is not always, but "sometimes", you just need to restart it).

Prior to that, I tried 2.3dev with no luck either.