PHP 4.0 Bug #6375: php.exe Eception: access violation(0xc0000005), Address: 0x1007cefa

From: Date: Sun, 27 Aug 2000 11:35:04 +0000
Subject: PHP 4.0 Bug #6375: php.exe Eception: access violation(0xc0000005), Address: 0x1007cefa
Groups: php.dev 
Request: Send a blank email to php-dev+get-30810@lists.php.net to get a copy of this message
From: peter@helpnet.com.au Operating system: NT 4.0 SP6a PHP version: 4.0.1pl2 PHP Bug Type: Reproduceable crash Bug description: php.exe Eception: access violation(0xc0000005), Address: 0x1007cefa I converted a PHP3 test site to PHP4 on my NT workstation. Apache, PHP4 and MySQL ran for a week without error then started this access error today. Using Opera 4.02, php.exe dumps then goes away and I can use the system. Using Netscape 4.08, NT goes in to a CPU loop. The index page uses frames so may work slightly different in Netscape and Opera. I looked in the task manager when NT was 100% CPU busy and found 2 php.exe tasks listed. I could not cancel either task and could not get NT to reboot. I had to do the "old big thumb on hardware reset button". The only change to the system today was to delete StarOffice 5.1 and install 5.2. Just before the error, I had the site successfully using PHP4 sessions based on MySQL and had deleted PHPLIB. PHP4 is running as cgi. The php.ini is almost 100% default as supplied. A week ago I added an include directory, changed error reporting to E_ALL, expanded script memory to 8Mb and changed session.save_handler to user. Yesterday I added ldap.dll then took it out after the first few access errors. The error is the same with dlls in winnt/system32 or in cgi-bin. Although neither changed between PHP working and PHP failing, I will have a look for an updated Apache and an updated MySQL. I will also try commenting out recent code. I had an access violation with PHP3 that turned out to be funny code in PHPLIB. It was writtten in an obtuse form so I clarrified the code then put in extra error checking (isset etc.). That made that error go away. I already have careful variable status checking in the new code so it is unlikely to be that sort of error. I also tried with the Internet disconnected in case it was picking up something from a link to the production site. No change in the error. Thats it. Everything else is installed straight out of the box with not extras turned on.

« previous php.dev (#30810) next »