#50896 [Opn-Bgs]: Bus error on execution on a MIPS system
ID: 50896 Updated by: j...@php.net Reported By: angel at wututu dot com -Status: Open +Status: Bogus Bug Type: Reproducible crash Operating System: GNU/Linux PHP Version: 5.2snapshot-201002171530 New Comment: No problem. No testing, no way to reproduce - bogus. Previous Comments: [2010-02-26 13:13:52] angel at wututu dot com Hi! Sorry to say that, but I no longer have access to that machine for testing this bug :/ At this moment I saw the Bus Error inside QEMU but copying the file over the device when running it got stuck, with no error message, I had to ctrl+c it to exit. With QEMU I was using Ubuntu 9.10, and inside the device there was an special version of openwrt. About the -M option I don't remember much of it, I suppose it was mips or mipsel. And that's all I can say about that, sorry :( [2010-02-24 07:33:38] ahar...@php.net I can't reproduce this on a Debian testing install within a mipsel QEMU VM: the current PHP 5.2 and 5.3 SVN branches compile and appear to work normally, at least for trivial scripts. So, a few questions: Are you only seeing the Bus Errors on the actual MIPS devices, or within QEMU as well? Are you using a particular Linux distribution? Which machine type are you emulating with QEMU (ie what -M option, if any, are you passing to qemu-system-mipsel)? Have you tried a minimal build without any extensions enabled (ie just ./configure --enable-debug)? Does PHP still Bus Error out in that case? (If PHP works OK without any extensions, then it would be incredibly helpful if you were able to narrow down the problem to a particular extension that causes PHP to crash when it's compiled in.) [2010-02-22 16:09:02] angel at wututu dot com Well... not cross compiling. I'm compiling it natively inside a virtual machine because I can't use the final machine because it lacks memory. [2010-02-19 08:34:06] j...@php.net -Status: Open +Status: Bogus Oh, you're cross-compiling this. We do not support that out-of-box, you're totally on your own with it. [2010-02-18 08:38:03] angel at wututu dot com -Status: Feedback +Status: Open -PHP Version: 5.3SVN-2010-02-10 +PHP Version: 5.2snapshot-201002171530 The backtrace in this case is more or less the same as before: (gdb) run Starting program: /build/php5.2-201002171530/sapi/cli/php warning: no loadable sections found in added symbol-file /usr/lib/libiconv.so.2 Program received signal SIGBUS, Bus error. 0x0071e704 in _zend_mm_alloc_int (heap=0x91f300, size=13) at /build/php5.2-201002171530/Zend/zend_alloc.c:1897 1897ZEND_MM_CHECK_BLOCK_LINKAGE(best_fit); (gdb) backtrace #0 0x0071e704 in _zend_mm_alloc_int (heap=0x91f300, size=13) at /build/php5.2-201002171530/Zend/zend_alloc.c:1897 #1 0x0074a5b4 in zend_register_functions (scope=0x0, functions=0x911ad0, function_table=value optimized out, type=value optimized out) at /build/php5.2-201002171530/Zend/zend_operators.h:287 #2 0x0074358c in zend_startup (utility_functions=value optimized out, extensions=value optimized out, start_builtin_functions=1) at /build/php5.2-201002171530/Zend/zend.c:676 #3 0x006ead00 in php_module_startup (sf=value optimized out, additional_modules=0x0, num_additional_modules=0) at /build/php5.2-201002171530/main/main.c:1710 #4 0x007ef254 in php_cli_startup (sapi_module=0x0) at /build/php5.2-201002171530/sapi/cli/php_cli.c:389 #5 0x007efdd8 in main (argc=1, argv=0x7f948dc4) at /build/php5.2-201002171530/sapi/cli/php_cli.c:748 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/50896 -- Edit this bug report at http://bugs.php.net/?id=50896edit=1
#50896 [Opn-Bgs]: Bus error on execution on a MIPS system
ID: 50896 Updated by: j...@php.net Reported By: angel at wututu dot com -Status: Open +Status: Bogus Bug Type: Reproducible crash Operating System: GNU/Linux PHP Version: 5.2snapshot-201002171530 New Comment: Oh, you're cross-compiling this. We do not support that out-of-box, you're totally on your own with it. Previous Comments: [2010-02-18 08:38:03] angel at wututu dot com -Status: Feedback +Status: Open -PHP Version: 5.3SVN-2010-02-10 +PHP Version: 5.2snapshot-201002171530 The backtrace in this case is more or less the same as before: (gdb) run Starting program: /build/php5.2-201002171530/sapi/cli/php warning: no loadable sections found in added symbol-file /usr/lib/libiconv.so.2 Program received signal SIGBUS, Bus error. 0x0071e704 in _zend_mm_alloc_int (heap=0x91f300, size=13) at /build/php5.2-201002171530/Zend/zend_alloc.c:1897 1897ZEND_MM_CHECK_BLOCK_LINKAGE(best_fit); (gdb) backtrace #0 0x0071e704 in _zend_mm_alloc_int (heap=0x91f300, size=13) at /build/php5.2-201002171530/Zend/zend_alloc.c:1897 #1 0x0074a5b4 in zend_register_functions (scope=0x0, functions=0x911ad0, function_table=value optimized out, type=value optimized out) at /build/php5.2-201002171530/Zend/zend_operators.h:287 #2 0x0074358c in zend_startup (utility_functions=value optimized out, extensions=value optimized out, start_builtin_functions=1) at /build/php5.2-201002171530/Zend/zend.c:676 #3 0x006ead00 in php_module_startup (sf=value optimized out, additional_modules=0x0, num_additional_modules=0) at /build/php5.2-201002171530/main/main.c:1710 #4 0x007ef254 in php_cli_startup (sapi_module=0x0) at /build/php5.2-201002171530/sapi/cli/php_cli.c:389 #5 0x007efdd8 in main (argc=1, argv=0x7f948dc4) at /build/php5.2-201002171530/sapi/cli/php_cli.c:748 [2010-02-17 15:59:17] j...@php.net Is the gdb backtrace same for it? Does it happen with latest PHP-5.2 snapshot? (found at http://snaps.php.net/ ) ? [2010-02-01 17:25:29] angel at wututu dot com Still the same error with the snapshot: Generating phar.php /bin/sh: line 1: 29472 Bus error ` if test -x /build/php5.3-201002010930/sapi/cli/php; then /build/php5.3-201002010930/build/shtool echo -n -- /build/php5.3-201002010930/sapi/cli/php -n; if test x != x; then /build/php5.3-201002010930/build/shtool echo -n -- -d extension_dir=/build/php5.3-201002010930/modules; for i in bz2 zlib phar; do if test -f /build/php5.3-201002010930/modules/$i.la; then . /build/php5.3-201002010930/modules/$i.la; /build/php5.3-201002010930/build/shtool echo -n -- -d extension=$dlname; fi; done; fi; else /build/php5.3-201002010930/build/shtool echo -n -- /build/php5.3-201002010930/sapi/cli/php; fi;` -d 'open_basedir=' -d 'output_buffering=0' -d 'memory_limit=-1' -d phar.readonly=0 -d 'safe_mode=0' /build/php5.3-201002010930/ext/phar/build_precommand.php ext/phar/phar.php make: *** [ext/phar/phar.php] Error 138 And when being run: root@(none):/build/php5.3-201002010930# ./sapi/cli/php Bus error Let's see if someone can fix it or at least point me how to fix it. [2010-02-01 10:07:09] angel at wututu dot com Description: I've been trying to cros-compile PHP for an embedded MIPS device with no luck, so I decided to build a developing environment inside a virtual machine with QEMU for developing PHP inside first. I have been trying different options for configure and all I get is a Bus Error 138 when I run the executable. I've seen there is another thread about this same error and I applied the patches but the error was still present. I've tried to debug a little the code to find where the error is. I'm explaining it right now: I ran it first under gdb: -- GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as mipsel-unknown-linux-gnu... (gdb) run Starting program: /build/php-5.3.1/sapi/cli/php warning: no loadable sections found in added symbol-file /usr/lib/libiconv.so.2 starting php right now at main... Program received signal SIGBUS, Bus error. 0x00a51634 in _zend_mm_alloc_int (heap=0xef92f0, size=14) at /build/php-5.3.1/Zend/zend_alloc.c:1892 1892ZEND_MM_CHECK_BLOCK_LINKAGE(best_fit); (gdb) backtrace #0 0x00a51634 in _zend_mm_alloc_int (heap=0xef92f0, size=14) at /build/php-5.3.1/Zend/zend_alloc.c:1892 #1 0x00a53018 in _emalloc
