Bug #10904 Updated: php.exe accesses unreadable memory and crashes

ID: 10904 Updated by: sniper Reported By: pax@volpe.dot.gov Old Status: Open Status: Bogus Bug Type: Reproducible crash Operating System: WINNT SP4 PHP Version: 4.0.5 New Comment: So we'll forget about it.. Previous Comments: ------------------------------------------------------------------------ [2001-09-05 09:57:39] pax@volpe.dot.gov I ported my site to W2K, and as your note indicates the bug does not appear there. I don't care if it is ever fixed for WINNT SP4. ------------------------------------------------------------------------ [2001-07-27 12:26:49] sniper@php.net status: open ------------------------------------------------------------------------ [2001-07-23 10:12:00] pax@volpe.dot.gov Yes. The little loop script still shows it. Other scripts may or may not show it, but it only appears with the second invocation. It is easy to think it is gone because the first time a script runs it usually doesn't happen. If you haven't backed up the browser and opened the script a second time, it could be hiding. Also, I am running WinNT 4 not w2k. If I can suppress the bug by upgrading to w2k, I might. I have been thinking I might have to move the server to Linux. I am currently running 4.0.4pl because I am not set up to link in the modules I need with 4.0.6. ------------------------------------------------------------------------ [2001-07-22 09:20:36] dbeu@php.net can't repoduce this with the apache module or the cgi (4.0.6) under w2k. is this bug still existant for you? ------------------------------------------------------------------------ [2001-06-15 09:59:43] pax@volpe.dot.gov I installed the snapshot from 6/14/2001. I know the installation was successful because PHP issued warnings about not being able to load modules such as GD. I ran it against the small script that demonstrates the defect, and, unfortunately, the defect is still there. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/?id=10904 Edit this bug report at http://bugs.php.net/?id=10904&edit=1