PHP 4.0 Bug #7296 Updated: PHP Memory Errors(Access Violations)

ID: 7296 Updated by: sniper Reported By: primeevil@thecodevault.net Old-Status: Feedback Status: Closed Bug Type: Reproduceable crash Assigned To: Comments: No feedback, considered fixed. --Jani Previous Comments: --------------------------------------------------------------------------- [2001-01-07 03:58:23] sniper@php.net Does this happen with PHP 4.0.4 ? --Jani --------------------------------------------------------------------------- [2000-12-07 19:12:00] sniper@php.net User reported having same problem with latest build from php4win.de --Jani --------------------------------------------------------------------------- [2000-12-07 11:55:12] sniper@php.net Reopen, if this still happens when using latest snapshot from http://snaps.php.net/ --Jani --------------------------------------------------------------------------- [2000-11-02 15:43:08] dbeu@php.net can you compile a debug build and paste the call stack here? --------------------------------------------------------------------------- [2000-10-17 17:35:46] primeevil@thecodevault.net With my news script, NewsIt, there is a problem with "compiling" the news. For some reason PHP crashes with memory read errors. MSVC++ Debug reveals that it's an Access Violation. The error, before debug, is as follows: php.exe - Application Error The instruction at "0x77fc999b" referenced memory at "0x00b1d54d". The memory could not be "read". When debug is entered it has this error message: Unhandled exception in php.exe (NTDLL.DLL): 0xC0000005: Access Violation. These are the five lines of ASM, starting with the problem line: 77FC999B mov cl,byte ptr [eax+5] 77FC999E test cl,1 77FC99A1 je 77FCAFF2 77FC99A7 mov word ptr [eax+2],di 77FC99AB cmp di,80h This happens before anything is written to the file. E-mail me for the script, because the function that builds the news is too large. --------------------------------------------------------------------------- The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online. ATTENTION! Do NOT reply to this email! To reply, use the web interface found at http://bugs.php.net/?id=7296&edit=2