ID: 20023 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: Closed Bug Type: Sockets related Operating System: Win 98 SP2 PHP Version: 4.2.2 4.3 New Comment:
Hello "iliaa", as it seems from first tests you have got this one! I tried it on W98 SP2 with PHP4.4 2002-12-10 8:29 and it doesn't crash any more. Thanks a lot! I will also try on Win Me and stressing it soon. Sorry for having been such a pain. Thanks again! Previous Comments: ------------------------------------------------------------------------ [2002-12-09 09:23:13] [EMAIL PROTECTED] 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-11-07 11:07:23] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] 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 ------------------------------------------------------------------------ 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