#15333 [Com]: strndup access violation

ID: 15333 Comment by: j.mak@1000mbit.nl Reported By: david@harksystems.com Status: Feedback Bug Type: IIS related Operating System: Windows 2000 Pro PHP Version: 4.2.1 New Comment: Just to add it to the list: Same problem here. Never got PHP to work through IIS. Tested it on Win2K Pro (SP2, no patches), Win2K Adv. Server (sp2 + srp1), Win2K Adv. Server (SP3 + latest patches). The machines vary from Duron cpu's, Celeron's, P3's, Athlon XP+'s. A request to a .php file would work for 1 or 2 times, but then the 'Invalid access to memory location' error in my browser. The php files tried where some files with only HTML (not one php tag), or just the <? phpinfo(); ?>. The PHP behaves fine when used with Apache-Win32, or from the command-line. I've never seen PHP (from versions 4.1.2 to 4.2.2) work on Win2K + IIS :(. Previous Comments: ------------------------------------------------------------------------ [2002-09-07 00:09:09] kalowsky@php.net Umm that should only be feedbacked, not closed. ------------------------------------------------------------------------ [2002-09-07 00:04:16] kalowsky@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 There was a bug for dual processors that fixed this. Please try the latests version (4.2.3) to see if this is fixed. ------------------------------------------------------------------------ [2002-09-06 21:08:16] tshazli@linuxmail.org Ok, here is the thing: I have 2 servers load balancing each other. had this problem with one of our servers (PIII dual processor) but not with the other which is a single processor. I tried to format the server, reinstall everything all over again, not apply microsoft patches/fixes...etc. still the problem occurs ONLY on the dual processor server. Then I tried to take one processor out of that box and guess what...IT worked flawlessly. I stress tested it with heavy load test for hours and not once I got the error ever again. I put the processor back to the box and tested it. I got the error again. I tried that many times. Always get the error with dual processor but not even once with single processor. So how to work around the problem? use single processor server. What causes the problem? dont know..It is between PHP and IIS. I am trying to find out the problem by debuging the services but if anyone is interested in reproducing the problem and trying to debug it, use dual processor with win2000 server and IIS5 with any php ver >=4.2.1 and use ADODB or MSSQL connections. Stress test it and you will get the error. ------------------------------------------------------------------------ [2002-09-05 00:14:11] home@NOSPAMwebpanache.com Hi, Just to contribute had PHP with ISAPI dll working fine until a few days ago. It seems that applying the lastest Microsoft security fixes created the problem. The latest applied fix was MS02-048.... ------------------------------------------------------------------------ [2002-08-29 08:30:41] jean-francois_larvoire@hp.com Hello, I have the same problem too. And it is reproductible. This is with the ISAPI version of PHP 4.2.2 under Windows XP. I get the following error message in the XP Error Log, when trying to access a page from another PC. A copy of the test file that causes the problem is at http://jf.larvoire.free.fr/calendrier.php3. Pressing on the "Next month" button crashes the PHP DLL. Jean-Francois Larvoire vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv The HTTP server encountered an unhandled exception while processing the ISAPI Application ' php4ts!zend_strndup + 0x2B + 0x17C99F70 '. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ------------------------------------------------------------------------ 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/15333 -- Edit this bug report at http://bugs.php.net/?id=15333&edit=1