View Issue Details

IDProjectCategoryView StatusLast Update
0000658XdebugUncategorizedpublic2013-05-23 22:46
Reporterrautiola Assigned Toderick  
Status resolvedResolutionno change required 
PlatformXAMPP 1.7.4 Beta2 [PHP: 5.3.3]OSWindowsOS VersionXP SP3
Product Version2.1.0 
Summary0000658: Eclipse/Xdebug crashes when debugging drupal
DescriptionEclipse/Xdebug crashes randomly - but very, very often - when debugging drupal in Eclipse. I have been debugging my other php scripts without problems for more than a year, but when trying to debug drupal cause crash. Eclipse throws a small window saying "Apache HTTP server has encountered a problem and needs to close etc.". Then looking at the data of the error report it says (among other things): "ModName: php_xdebug-2.1.0-5.3-vc6.dll", "ModVer:" and "Offset: 0000bf44". I can provide a screenshot from the crash if that helps. I'm using the Xampp 1.7.4 Beta2, but the same happen other versions of Xampp as well.
TagsNo tags attached.
Operating System
PHP Version5.3.3


has duplicate 0000669 resolvedderick eclipse / xampp crsahes when selecting 'variables' tab 



2011-01-27 18:06

reporter   ~0001654

Last edited: 2011-01-27 18:06


I can confirm this problem.

I have this problem few months, but not with drupal, but with Zend Framework Application, the environment is the same, latest Eclipse/PDT latest stable XDebug and PHP 5.3.1-5.3.3.

This issue kill my Apache server ( latest stable version) very often 3 times from 10 debug sessions.

Faulting application name: httpd.exe, version:, time stamp: 0x4cbbe9e8
Faulting module name: php_xdebug-2.1.0-5.3-vc6.dll, version:, time stamp: 0x4c29c7d8
Exception code: 0xc0000005
Fault offset: 0x0000bf44
Faulting process id: 0x938
Faulting application start time: 0x01cbb9419ec841dc
Faulting application path: C:\Program Files (x86)\Apache Software Foundation\Apache2.2\bin\httpd.exe
Faulting module path: C:\Program Files (x86)\PHP\ext\php_xdebug-2.1.0-5.3-vc6.dll
Report Id: 88720566-2535-11e0-9e20-005056c00008


2011-01-27 19:36

reporter   ~0001655

Do you know if this can be solved somehow? As you know very well, it's very time consuming when you have to close Xampp and Eclipse, disable some drupal modules, restart Xampp and Eclipse and Apache, try again by starting debugger, enable drupal modules (if you are lucky to get that point) etc... Br, Markku R


2011-03-29 09:39

reporter   ~0001697

Having exactly the same issue debugging Wordpress with Eclipse on Windows. Virtually unusable. Have tried this on XP and Vista with the same results.


2011-03-30 21:54

administrator   ~0001702

I would need a proper backtrace (see, and if you can, a simple script and a remote_log (see I've uploaded a debug pack for 2.1.0-5.3-vc6.dll as attachment to this report. (For fun, do try 2.1.1 though please).


2011-03-31 14:58

reporter   ~0001712

Unfortunately, 2.1.1 does not solve the issue. As it turns out, it is crashing when the variable view panel is open. As long as that is closed, it seems to work. Inspect works fine. Also, syntax highlighting is still not working. Had to disable it. Thought I read another post where syntax highlighting was fixed. Anyway, if you keep the expressions and variables panels closed and disable syntax highlighting it works pretty well.

If I can figure out how to send you a backtrace, I will. Not sure what is meant by, "I've uploaded a debug pack for 2.1.0-5.3-vc6.dll". Can't seem to find the file.



2011-05-20 10:17

reporter (13,059 bytes)


2011-05-20 10:18

reporter   ~0001747


A user of my application is having similar problems, he managed to get backtrackes of it, I attached them in
If you need more information, let me know.


2011-06-10 15:45

reporter   ~0001753

I have had this issue debugging Joomla in Windows Vista 64-bit with Xdebug and Eclipse. As a work-around, I find it works if I keep the Variables view closed and just use the Expressions view. However, this is a major limitation. It would be very helpful to get this issue resolved.


2011-07-29 22:00

reporter   ~0001767

Don't know if this help, I have same kind of issue, but it relate to array depth xdebug handle in Variables view. And you can change it. Widnow > Preferences > PHP > Debug > Installed Debug > Xdebug > Configure enlarge the "Max array depth" solved my issue.


2011-08-09 14:08

reporter   ~0001773


I can partially confirm efeng's workaround. I enlarged the "Max array depth" from to 50 but that alone didn't do the job. What I had to do: Ensure that the variables view is NOT selected (it can be there but in background). Step to a breakpoint and do an inspect of some variable once -> The variables view now displays all variables correctly.


2011-08-15 08:24

reporter   ~0001787

Hi Everybody,

I'm new to Eclipse and XDebug, so if i say something stupid - please don't flame me. I'm using Eclipse PDT as my IDE, and since ZendDebugger failed miserably, i decided to try XDebug. Plus everybody (who i know that develops in PHP) said that it's superior debugger.

I'm trying to setup Eclipse/XDebug for Joomla extension development. I've used another IDE with no debugger, but as web app grows it's a huge setback to work without a debugger, it's not the most efficient way to work.

As this issue, and other issues related to it point out, my problem is Eclipse throwing: "unexpected termination of script, debugging ended" error when i run the debugger, if "Variables" tab is visible. My problem is not related to Drupal, (as i said above I'm working with Joomla) but I'm sure the source of this issue is the same. And though other subjects might be describing my problem more accurately, i didn't want to write to to threads/issues which were marked as "duplicate" of this by admins.

I actually tried to do this setup of Eclipse + XDebug on older machine which had Windows XP and Apache/PHP/MySQL were installed and configured separately. That setup did not have this problem, which makes me think if maybe the issue is also XAMPP related (i'm using XAMPP for a first time now). Is anybody else who has this problem using Apache/PHP without XAMPP package? Just an idea...

I did as zenobios advised. I made sure that "Variables" tab is not selected prior to debugging. Once i hit first breakpoint, i inspect the variable and once it shows me the variable contents, i can safely view the "Variables" tag. More than that, on next session it works even if "Variables" tab has been selected initially. On 3rd try however same thing happens: "unexpected termination of script, debugging ended".

It's a nice workaround, which at least will let me work little bit if I'm careful. So THANK YOU zenobios = kudos+1 :) *thumbs up*

Here is a link to file with my XDebug remote log contents:

I cant use MS Debug Diagnostics Tool as instructed in the link above, since I'm running Windows 7. Debug Diagnostics Tool only shows very small part, saying "Analysis Only". So i cant create rules etc... Though I've downloaded PHP Debug .pdt file set into my PHP installation. Not sure how to use them without full Debug Diagnostics Tool though....

Here are my XDebug settings in PHP:

zend_extension = D:\xampp\php\ext\php_xdebug-2.1.2-5.3-vc6.dll
xdebug.default_enable = "On"
xdebug.profiler_output_dir = "D:\xampp\tmp"
xdebug.remote_enable = true
xdebug.remote_handler = "dbgp"
xdebug.remote_host = "localhost"
xdebug.remote_log = "D:\xampp\php\log\xdebug_log\xdebug_remote.log"
xdebug.remote_port = 10000
xdebug.show_local_vars = 1
xdebug.trace_output_dir = "D:\xampp\tmp"

(I've tried also setting my XDebug max array options higher, but yielded same result. Are these correct options of which efeng was speaking? Or i misunderstood totally?)
xdebug.var_display_max_depth = 100
xdebug.var_display_max_data = 2048
xdebug.var_display_max_children = 512

(I don't know if this is going to help any, but just in case...)
And here is Windows EVENT VIEWER error message that is generated during the crash:

Faulting application name: httpd.exe, version:, time stamp: 0x4cbbe9e8
Faulting module name: php_xdebug-2.1.2-5.3-vc6.dll, version:, time stamp: 0x4e317b06
Exception code: 0xc0000005
Fault offset: 0x0000bee9
Faulting process id: 0x508
Faulting application start time: 0x01cc5b1d0a3c1891
Faulting application path: D:\xampp\apache\bin\httpd.exe
Faulting module path: D:\xampp\php\ext\php_xdebug-2.1.2-5.3-vc6.dll
Report Id: 4e063037-c710-11e0-a423-005056c00008

If i can provide anything else, please let me know. It's very important for me to get this working (as I'm sure for everybody else), and I'll do anything that i can to help find the source of this problem.

Thank you everybody for reading this long message.


2013-04-12 22:20

reporter   ~0002452

its this going to be fixed?
this bug makes the debugger almost unusable. sometimes i can debug and watch variables, and sometimes the debugger crashes almost instantaneously.
it seems that the bug has something to do with the size of the call stack. but im not sure


2013-04-13 15:35

reporter   ~0002453

Last edited: 2013-04-13 15:36

I was having this problem (as reported on 2011-06-10), but after upgrading to XAMPP 1.7.7 (PHP 5.3.8 and XDEBUG 2.1.1) XDebug is mostly stable and I can use the Variables view. I found that I need to have "Show super globals in variable view" turned off. But with that, I can use the Variables view OK. The only time I crash now is if I forget to disable or delete certain expressions in the expressions view and stop at a place where an expression causes an error. Hope that helps someone.


2013-05-22 05:49

administrator   ~0002483

Could you please try Xdebug 2.2.3 which has just been released? I am suspecting that release might fix this issue.


2013-05-23 21:57

reporter   ~0002489

aparently with the new version its solved.


2013-05-23 22:46

administrator   ~0002490

Apparently fixed in 2.2.3!

Issue History

Date Modified Username Field Change
2011-01-26 07:28 rautiola New Issue
2011-01-27 18:06 snop Note Added: 0001654
2011-01-27 18:06 snop Note Edited: 0001654
2011-01-27 19:36 rautiola Note Added: 0001655
2011-03-29 09:39 screamatthewind Note Added: 0001697
2011-03-30 21:54 derick Note Added: 0001702
2011-03-30 21:55 derick Relationship added has duplicate 0000669
2011-03-31 14:58 screamatthewind Note Added: 0001712
2011-05-20 10:17 bhofmann File Added:
2011-05-20 10:18 bhofmann Note Added: 0001747
2011-06-10 15:45 dextercowley Note Added: 0001753
2011-07-29 22:00 efeng Note Added: 0001767
2011-08-09 14:08 zenobios Note Added: 0001773
2011-08-15 08:24 crashedfx Note Added: 0001787
2013-04-12 22:20 Jarry Note Added: 0002452
2013-04-13 15:35 dextercowley Note Added: 0002453
2013-04-13 15:36 dextercowley Note Edited: 0002453
2013-05-22 05:49 derick Note Added: 0002483
2013-05-22 05:49 derick Assigned To => derick
2013-05-22 05:49 derick Status new => feedback
2013-05-23 21:57 Jarry Note Added: 0002489
2013-05-23 22:46 derick Note Added: 0002490
2013-05-23 22:46 derick Status feedback => resolved
2013-05-23 22:46 derick Resolution open => no change required
2016-07-31 12:36 derick Category Usage problems => Usage problems (Crashes)
2016-07-31 12:38 derick Category Usage problems (Crashes) => Usage problems (Wrong Results)
2020-03-12 16:35 derick Category Usage problems (Wrong Results) => Variable Display
2020-03-12 16:38 derick Category Variable Display => Uncategorized