#20023 [Opn->Fbk]: Page Fault on Socket read
| From: | iliaa@php.net | Date: | Mon, 09 Dec 2002 15:23:14 +0000 |
| Subject: | #20023 [Opn->Fbk]: Page Fault on Socket read | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-27189@lists.php.net to get a copy of this message | ||
ID: 20023
Updated by: iliaa@php.net
Reported By: sven.schnitzke@t-online.de
-Status: Open
+Status: Feedback
Bug Type: Sockets related
Operating System: Win 98 SP2
PHP Version: 4.2.2 4.3
New Comment:
Please try using this CVS snapshot:
http://snaps.php.net/php4-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php4-win32-latest.zip
Previous Comments:
------------------------------------------------------------------------
[2002-11-07 11:07:23] sven.schnitzke@t-online.de
Addendum:
I got hold of a Windows Me system and installed PHP 4.2.2
and 4.3 on it with the following results:
My initial complaint regarding the page fault when a local
telnet is ripped off the socket is specific to the OS
(perhaps the wsock32.dll ver? Win 98:4.10.1998 Me:4.90.3000)
On Win 98 it occurs with telnet 4.90.3000.1 and 5.00.1717.1
and on Me it does not occur at all. This is independent of
the location of the telnet client, same or foreign machine.
Not so with PHP 4.3 CVS 1 Nov 16:12:01:
Socket_read dies on Win Me with the same symtoms as on Win
98. It also does not matter witch machine telnet is running on.
------------------------------------------------------------------------
[2002-11-01 17:08:04] sven.schnitzke@t-online.de
I tried again with 4.3 Build Nov 1, 2002 16:12:01
and no luck:
socket_get_status complains over the result from
socket_select stating that this is "not a valid stream
resource", socket_last_error says: "0" and
socket_get_peername knows about the correct ip and port.
Then comes socket_read and dies with a page fault in
module <unknown> at 0000:00000003. This occurs either
upon entering a character in a telnet client on the
same machine or upon closing the connection from such
a client prior to entering anything from there. Killing
the telnet client results in a page fault in php4ts.
My installation is without any php related stuff in
%WINDIR% or %WINSYSDIR%, just a PATH set to the folder
containing the .EXE. I launch the script from a CLI
set to the folder of the .EXE with the command:
php -f "absolute path to script.php"
"extension_dir" is specified absolutely in php.ini and
the output of phpinfo() looks reasonable (sockets enabled
and path to extensions correctly specified).
A parallel inst of 4.2.2 running the same script can
read the characters from the telnet client and dies only
when the telnet client is killed without a correct shutdown
of the socket.
------------------------------------------------------------------------
[2002-10-28 07:55:57] iliaa@php.net
Please try using this CVS snapshot:
http://snaps.php.net/php4-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php4-win32-latest.zip
------------------------------------------------------------------------
[2002-10-25 13:09:03] sven.schnitzke@t-online.de
I didn't update - I did a new parallel inst of 4.3
obviously leading to some inst issues. These are covered
in another bug thread because they seem to be due to the
environmental diffences between CGI and module mode.
One thing is certain: 4.3 behaves different from 4.2.2
using the same inst strategy - I will try to sort it out.
Sven
------------------------------------------------------------------------
[2002-10-24 01:55:00] sniper@php.net
you most likely didn't update PHP correctly.
Just make sure you first REMOVE all existing PHP related
binaries (dlls, etc.) and then install the new version.
------------------------------------------------------------------------
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/20023
--
Edit this bug report at http://bugs.php.net/?id=20023&edit=1