ID: 20922 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: Open Bug Type: Sockets related Operating System: linux debian latest unstable PHP Version: 4.4.0-dev New Comment:
hmm ok, here is the thing.. the script failed on socket_select - but it was from a previous error before i did socket select i also did a file() on an url - the server was down so i guess somehow the error just got projected to another socket without the file($url) code i cant replicate it's behaviour, so i removed it. my original report is still valid - socked_select() seemed to stop in its tracks after that invalid file($url) request. (I had debug output before and after to see why/how it hangs and i haddnt suspected file($url) since it wen't without verbosity on that part) Previous Comments: ------------------------------------------------------------------------ [2002-12-11 01:08:29] [EMAIL PROTECTED] Please provide a complete, self-contained and short example script which can be used to reproduce this. ------------------------------------------------------------------------ [2002-12-10 17:31:35] [EMAIL PROTECTED] ughm sorry for my rushed english, what i ment to say is.. the snapshot version produces the same output as rc2, just without the crash. ------------------------------------------------------------------------ [2002-12-10 17:12:12] [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 One more try: TRY THE SNAPSHOT. Not the RC2..(snapshot, as in the given url..) ------------------------------------------------------------------------ [2002-12-10 11:11:26] [EMAIL PROTECTED] same result on windows rc2, just no more crash ------------------------------------------------------------------------ [2002-12-10 09:15:09] [EMAIL PROTECTED] Please try the snapshot, iirc, there were some fixed done which are NOT in RC2. ------------------------------------------------------------------------ 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/20922 -- Edit this bug report at http://bugs.php.net/?id=20922&edit=1
