ID: 6229
Comment by: ek1 at cec dot wustl dot edu
Reported By: chris-php-bugs at digitaria dot com
Status: Closed
Bug Type: Reproducible Crash
Operating System: Windows 2000 SP1
PHP Version: 4.0.1pl2
New Comment:
I'm getting the 'memory cannot be read' error on Windows 2000 when
running php script that gets the data from mysql.
Here is the simple script I run:
<html>
<body>
<?php
$db=mysql_connect("localhost", "root");
mysql_select_db("mydb", $db);
$result = mysql_query("SELECT * FROM employees", $db);
printf("First Name: %s<br>\n", mysql_result($result, 0, "first"));
printf("Last Name: %s<br>\n", mysql_result($result, 0, "last"));
printf("Address: %s<br>\n", mysql_result($result, 0, "address"));
printf("Position: %s<br>\n", mysql_result($result, 0, "position"));
?>
</html>
</body>
Please let me know what I can do to fix this.
Thank you,
Eduard Kotysh
Previous Comments:
------------------------------------------------------------------------
[2000-11-27 09:45:48] [EMAIL PROTECTED]
No feedback. Closed.
--Jani
------------------------------------------------------------------------
[2000-10-28 01:30:34] [EMAIL PROTECTED]
please report wheter this problem is still existent, if not please
provide a short reproducing script.
------------------------------------------------------------------------
[2000-08-17 20:32:59] chris-php-bugs at digitaria dot com
There appears to be some sort of library conflict with 4.0.1pl2 and
Windows 2000 (running as a CGI). I get errors like those below every
time php.exe executes:
Application popup: php.exe - Application Error : The instruction at
"0x77fca8ac" referenced memory at "0x00080101". The memory could not be
"written".
(The instruction address here may vary by about 16 bytes; the memory
address has always been 0x00080101 or 0x00080100)
Application popup: php.exe - Application Error : The instruction at
"0x77fca9ea" referenced memory at "0x00000010". The memory could not be
"read".
The requests are in fact processed correctly and there is no trace of a
message in the PHP error logs. Before applying Service Pack 1, there
was a good chance (5-50%) that a CGI error ("FATAL: erealloc():
Unable to allocate (a number between 15 and 30K) bytes") would be sent
to the browser. Post Service Pack 1, I have yet to see the CGI error
but the application error log message is generated for each request.
Our client should be moving to a Linux/Apache setup within 2 weeks but
I think it'd be a good idea to investigate W2k stability in any case. I
can provide pcAnywhere access to the remote server to a trusted
individual.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=6229&edit=1
