Unhandled win32 exception ocurred in vsphp_dbg.exe[10472]
Posted July 27th, 2008 by artosca
Just installed the new version 2.5.3.4870 and I am getting the error above. The debugger simply aborts and dies. It is aborting on the second or third breaking point.
I tried to use both php_xdebug-2.0.3-5.2.5.dll and php_xdebug-2.0.2-5.2.5.dll. Same result.
My setup is the following:
PHP 5.2.4
Apache 2.2.9
VS 2008
My project is using an external Apache server running on the same machine (I am not using the internal server of VS.PHP). Didn't try to run with the internal server because I would need to configure too many things in my app and I am against a deadline.
Please see if you can reproduce the same exception with my configuration.
I will have to roll back to the previous version of VS.PHP which was working perfectly on my setup.
Art


There is an issue with
There is an issue with XDebug that if you try to evaluate an invalid expression it dies.
Could you please check if that's the case?
As an alternative you could try to use DBG.
I contact the XDebug team about a way to address this issue.
If you don't think you are evaluating an invalid expression, please enable xdebug.remote_log and post the log here to review it.
Thanks,
Issue with new VS 2.5.4870 Debug Exception
The expression does not have to be an invalid expression for this to occur. It will and can abort on a perfectly valid statement.
See my information in forum topic "Debugger Aborts with Fault Dialog error". It gives sample code of a statement that XDebug generates an exception in VSPHP 2.5.3.4870 but works in the last 3 versions of VSPHP just fine and is a valid statement.
I also sent in a screen shot attachment so that you can see it is coming from XDebug not Apache.
Neal Davis
Not an XDebug issue
I am using a previous VS.PHP version (2.5.1.xxxx) with the same XDebug dll and it works fine. The php expression is valid.
My guess is that the problem is related to the Apache version (2.2.9 in my case) and vsphp_dbg.exe.
I did test XDebug 2.0.3 and 2.0.2 with the VSPHP 2.5.3.4870 and both gave the same result:
"Unhandled win32 exception ocurred in vsphp_dbg.exe"
Have you tried to run the debugger with an external Apache server? Have you tried with an Apache 2.2.x version?
I don't have the version 2.5.3.4870 installed anymore. I had to roll back to the previous version so I could continue to work.
Neil, what is your setup?
Art
Art, I just fixed a problem
Art,
I just fixed a problem with vsphp_dbg.exe
Please give it a try here:
http://www.jcxsoftware.com/jcx/vsphp-dev?build=2.5.3.4881
I will give a try
I will try it and report back to you here.
Thanks!
Looks good!
I tested with several breakpoints in different places and couldn't reproduce the exception.
Whatever you guys did looks like it is fixed. I will continue to work with this new version and report back if I run into the exception again.
BTW, I am using the 2.5.3.4883 version (from today's build).
My setup again:
External Apache 2.2.9
PHP 5.2.4
Windows XP Professional SP3
VS 2008
php_xdebug-2.0.3-5.2.5.dll
Thank you for the very fast response on this.
Art
can't install update
Hi, I am trying to download the new version (2.5.3.4881) and it seems to be corrupt, it won't install, says it couldn't be opened. The reason I tried this is that I also tried the update (2.5.1...) and it keeps crashing when it hits a break point.
thanx
The 4881 is not working but 4883 is
Use the 4883 version. I had the same problem as you.
The 4883 instals fine.
Art
sweeeet
That worked, and I haven't experienced any crashes yet.
thanx
4883 was working beautifully
4883 was working beautifully for me, but after upgrading to 2,5,3,4907 apache is crashing once again.
Interesting becasue there
Interesting becasue there was no changes to debugging between these two builds.
Do you want to try the 2.6 build? We have made some improvements there.
Thanks
2,6,1,4909 still crashes
2,6,1,4909 still crashes here.
The original report was
The original report was vsphp_dbg.exe crashing. Is that what you are seeing now? Or is it Apache now instead?
"An unhandled win32
"An unhandled win32 exception occurred in Apache.exe"
this is xdebug crashing most
this is xdebug crashing most likely. You can try DBG instead and see if you have better luck.