Apache continuously crashing on Windows XP

Need help installing PHP, configuring a script, or configuring a server? Then come on in and post your questions! We'll try to help the best we can!

Moderator: General Moderators

Post Reply
User avatar
josamoto
Forum Commoner
Posts: 41
Joined: Fri Aug 24, 2007 6:57 am
Location: South Africa
Contact:

Apache continuously crashing on Windows XP

Post by josamoto »

Hi all!

My Apache keeps on crashing, especially when debugging on my XP machine. I get the typical, application crash and will now close screen with the following details (this happens on both my machines at work and at home):

Code: Select all

szAppName: httpd.exe    szAppVer: 2.2.4.0
szModName: php5ts.dll     szModVer: 5.2.4.4
offset: 0009902e.
I have installed Apache 2.2.4, with PHP 5.2.4 on my XP machine both at work and at home. Both also have the Zend Debugger 5.2.6 installed. Useful to know maybe that I'm also using Eclipse (http://www.eclipse.org) as my IDE.

The php.ini section for Zend Debugger is as follows:

Code: Select all

zend_extension_ts=C:/Program Files/PHP/ZendDebugger.dll
zend_debugger.allow_hosts=127.0.0.1
zend_debugger.expose_remotely=always
Any suggestions on how to fix the problem; I've already installed the newest versions of Apache, PHP and Zend Debugger I could find. Should I be using the Thread Safe Version of the Non-Thread Safe Version of Zend Debugger?

Also, how do I quickly switch from a debug run to a non-debugging run with PHP? In other words, how do I disable Zend Debugger without fiddling too much.

Thanks in advance for the help!
User avatar
superdezign
DevNet Master
Posts: 4135
Joined: Sat Jan 20, 2007 11:06 pm

Post by superdezign »

When does it crash? Sometimes, an infinite loop or badly written code will cause it to crash.
User avatar
josamoto
Forum Commoner
Posts: 41
Joined: Fri Aug 24, 2007 6:57 am
Location: South Africa
Contact:

Post by josamoto »

We'll funny enough, I received a few XHTML warnings in Mozilla. I validated the code, got it up to XHTML W3C Standard and the crashing stopped. The crashing used to happen randomly.

It appears, bad XHTML + Zend + Apache on Windows is not a good combination.
User avatar
josamoto
Forum Commoner
Posts: 41
Joined: Fri Aug 24, 2007 6:57 am
Location: South Africa
Contact:

Post by josamoto »

And I've spoken too soon. The crashing is very unpredictable but as far as I can see it's to do with the following code:

Code: Select all

<img src="getBlobImage.php?imageID=1" />
There is nothing wrong with the code, disable Zend Debugger and it works perfectly, I even tried commenting out ALL the code in getBlobImage.php, so it doesn't output anything at all. Apache still crashes.

It's really weird.

Are there any other PHP debuggers I can try that will work with the Eclipse IDE?
User avatar
superdezign
DevNet Master
Posts: 4135
Joined: Sat Jan 20, 2007 11:06 pm

Post by superdezign »

Not sure. I've run into a nasty glitch myself where the server crashes on a certain bit of code. Been messing around with it for weeks now. As far as I can see, it's a problem in my __toString() (or around there), so maybe there's some sort of problem with objects? Try commenting out whatever you can that will stop that from happening and track down the bug little by little.

Runtime bugs are horrible. ;_;
User avatar
josamoto
Forum Commoner
Posts: 41
Joined: Fri Aug 24, 2007 6:57 am
Location: South Africa
Contact:

Post by josamoto »

Yep, runtime bugs are a bugger. Anycase, I'm now trying to install XDebug with Eclipse, maybe using a different debugger will provide different results.

I need to get away from storing images in mySQL in anycase. Personally I think it's bad practice.
User avatar
josamoto
Forum Commoner
Posts: 41
Joined: Fri Aug 24, 2007 6:57 am
Location: South Africa
Contact:

Post by josamoto »

Oops. Still struggling with this one. XDebug has other problems. They released a new PDT version on Eclipse.org which now includes the XDebugger and Zend Debugger.

However, I still keep on getting the crash.

I've even tried setting the zend_debugger.max_msg_size to 10000000, but this apparently only made my problem worse.
Post Reply