ID: 19567 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: No Feedback Bug Type: IIS related Operating System: Windoes 2000 SP2 PHP Version: 4.2.3 New Comment:
No feedback was provided for this bug for over 2 weeks, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". Previous Comments: ------------------------------------------------------------------------ [2002-11-03 10:51:24] [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-09-25 16:50:34] [EMAIL PROTECTED] Thanks. I think this is entirely possible. I have tried to check the error on apache but am on work time and we are a microsoft shop. So i'm stuck with IIS. The rest of php seems to work fine except for the print array function that crashes the web server. oh well ------------------------------------------------------------------------ [2002-09-25 04:21:49] [EMAIL PROTECTED] I don't know phpMySearch but since you mention php_curl, it could be the same problem with CURL as described in bug 19301. Just a thought. It could also be something completely different. ------------------------------------------------------------------------ [2002-09-24 18:11:52] [EMAIL PROTECTED] changed status ------------------------------------------------------------------------ [2002-09-24 17:45:43] [EMAIL PROTECTED] Tried the latest snapshot. Still get the same error. this is the output from the spider.php file start: http://csmtemlst-web/development URL = (begin >)=> http://csmtemlst-web/development need parse start load PHP has encountered an Access Violation at 77F83941 The web server is a Compaq ProLiant DL360 G2 Dual processor Any ideas ------------------------------------------------------------------------ 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/19567 -- Edit this bug report at http://bugs.php.net/?id=19567&edit=1
