ID: 20268 Updated by: [EMAIL PROTECTED] -Summary: PHP (module or CLI) crashes with Bus Error on startup Reported By: bdabney at dallasnews dot com -Status: Open +Status: Critical Bug Type: Scripting Engine problem -Operating System: Solaris 9 +Operating System: any 64bit PHP Version: 4CVS-2002-11-05 New Comment:
Need to be addressed before 4.3.2 goes out the door. Previous Comments: ------------------------------------------------------------------------ [2003-02-23 04:36:04] [EMAIL PROTECTED] http://news.php.net/article.php?group=php.bugs&article=24417 http://news.php.net/article.php?group=php.bugs&article=24418 ------------------------------------------------------------------------ [2003-02-23 03:44:18] j-devenish at users dot sourceforge dot net Sigh. Since my entire post of 10/11 Nov has been deleted, and I did not receive an e-mail copy of my post via the bug submission system, I have no record of what I said. Presumably I stated that I, too, had encountered the problem, that I couldn't even install PHP 4.3, that it was due to int/long size mismatches on LP64 platforms, and then indicated the strategy I had used to work around it (via patches). I posted patches and test result information (for HEAD of the day and also for 4.3.0pre2) to php-dev on 11 November 2002. Thread subject was "64-bit PHP 4.3 (extensive long vs int problems)". Those patches are now out of date because (on the downside) further int/long problems have crept in and (on the upside) some test cases have been improved. ------------------------------------------------------------------------ [2003-02-23 03:17:09] [EMAIL PROTECTED] [To: j-devenish at users dot sourceforge dot net] PLEASE do NOT add such long diffs to bug reports! Instead put them on some site and add an URL to them here. (I deleted those comments from here now since they're pretty useless as the bug system mangles them anyway) ------------------------------------------------------------------------ [2003-02-21 10:16:39] ddhill at zk3 dot dec dot com Forgot to mention - bug 21822 has the same root cause as this one. ------------------------------------------------------------------------ [2003-02-21 10:15:39] ddhill at zk3 dot dec dot com I am glad to see someone is looking at the OnUpDateInt issue, and I think adding an OnUpdateLong is a good way to go. On Tru64 the int* vs. long* can cause some really hard to track errors because if the storage area is an int and is treated as a long, 32 bits of data following the int gets scrubbed with apparently no reason. I dug through a bunch of the 4.3.1 code and there is quite a mix of int an long being passed to OnUpdateInt, either directly or indirectly as in the case of zlib (which is where I encountered it). Blindly changeing OnUpdateInt to use int* will not work as there are quite a few longs being passed into the routine. The right answer seems to be adding OnUpdateLong and then doing a code sweep of the core and extensions to make sure the right one is called, which seems to be the thrust of the previous response. I hope these changes will show up in the mainstream soon. thanks! ------------------------------------------------------------------------ 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/20268 -- Edit this bug report at http://bugs.php.net/?id=20268&edit=1
