Issue tracker: Issues
https://tracker.crystax.net/
https://tracker.crystax.net/favicon.ico?1535920027
2013-03-14T11:27:18Z
Issue tracker
Redmine
CrystaX NDK - Bug #275 (Closed): Test device/test-c++11 hangs while running on armeabi emulator
https://tracker.crystax.net/issues/275
2013-03-14T11:27:18Z
Alexander Z.
zuav@crystax.net
<p>NB: test runs fine on emulator under Linux or on a armeabi device.</p>
CrystaX NDK - Bug #274 (Duplicated): Test device/test-c++0x hangs while running on armeabi emulator
https://tracker.crystax.net/issues/274
2013-03-14T11:19:51Z
Alexander Z.
zuav@crystax.net
<p>NB: test runs fine on emulator under Linux or on a armeabi device.</p>
CrystaX NDK - Bug #273 (Rejected): Test build/flto failed
https://tracker.crystax.net/issues/273
2013-03-13T21:29:02Z
Alexander Z.
zuav@crystax.net
<p>Sample output:</p>
<p>Executable : flto<br>
/tmp/android-ndk-20130312/toolchains/arm-linux-androideabi-4.7/prebuilt/darwin-x86/bin/arm-linux-androideabi-g++ -Wl,--gc-sections -Wl,-z,nocopyreloc --sysroot=/tmp/android-ndk-20130312/platforms/android-8/arch-arm ./obj/local/armeabi/objs/flto/flto.o /tmp/android-ndk-20130312/sources/crystax/libs/armeabi/libcrystax.a -lgcc -no-canonical-prefixes -flto -Wl,--no-undefined -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -L /tmp/android-ndk-20130312/sources/crystax/libs/armeabi -lc -lm -o ./obj/local/armeabi/flto<br>
/tmp/android-ndk-20130312/toolchains/arm-linux-androideabi-4.7/prebuilt/darwin-x86/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: -plugin: unknown option<br>
/tmp/android-ndk-20130312/toolchains/arm-linux-androideabi-4.7/prebuilt/darwin-x86/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: use the --help option for usage information<br>
collect2: error: ld returned 1 exit status<br>
make: *** [obj/local/armeabi/flto] Error 1</p>
CrystaX NDK - Bug #272 (Rejected): Test device/test-gnustl_shared-exception failed to run
https://tracker.crystax.net/issues/272
2013-03-13T20:34:43Z
Alexander Z.
zuav@crystax.net
<p>Sample output:</p>
<a name="COMMAND-optandroidandroid-sdk-linuxplatform-toolsadb-s-emulator-5558-shell-chmod-0755-datalocaltmpndk-testslibtest4_fooso"></a>
<h2 >COMMAND: /opt/android/android-sdk-linux/platform-tools/adb -s emulator-5558 shell chmod 0755 /data/local/tmp/ndk-tests/libtest4_foo.so<a href="#COMMAND-optandroidandroid-sdk-linuxplatform-toolsadb-s-emulator-5558-shell-chmod-0755-datalocaltmpndk-testslibtest4_fooso" class="wiki-anchor">¶</a></h2>
<p>Running device test [x86]: test-gnustl_shared-exception (Lib1_catching_lib2_throwing)<br>
/opt/android/android-sdk-linux/platform-tools/adb -s "emulator-5558" shell "cd /data/local/tmp/ndk-tests && LD_LIBRARY_PATH=/data/local/tmp/ndk-tests ./Lib1_catching_lib2_throwing"<br>
terminate called after throwing an instance of 'std::runtime_error'<br>
what(): OK: Throw in lib2, catch in lib1!<br>
[1] Segmentation fault LD_LIBRARY_PATH=...<br>
test-return-code:139<br>
---> TEST FAILED!!<br>
Running device test [x86]: test-gnustl_shared-exception (Lib_catching_lib_throwing)<br>
/opt/android/android-sdk-linux/platform-tools/adb -s "emulator-5558" shell "cd /data/local/tmp/ndk-tests && LD_LIBRARY_PATH=/data/local/tmp/ndk-tests ./Lib_catching_lib_throwing"<br>
terminate called after throwing an instance of 'std::runtime_error'<br>
what(): OK: Throw in lib, catch in lib!<br>
[1] Segmentation fault LD_LIBRARY_PATH=...<br>
test-return-code:139<br>
---> TEST FAILED!!<br>
Running device test [x86]: test-gnustl_shared-exception (exec_catching_lib2_throwing)<br>
/opt/android/android-sdk-linux/platform-tools/adb -s "emulator-5558" shell "cd /data/local/tmp/ndk-tests && LD_LIBRARY_PATH=/data/local/tmp/ndk-tests ./exec_catching_lib2_throwing"<br>
terminate called after throwing an instance of 'std::runtime_error'<br>
what(): OK: Throw in lib2, catch in exec!<br>
[1] Segmentation fault LD_LIBRARY_PATH=...<br>
test-return-code:139<br>
---> TEST FAILED!!<br>
Running device test [x86]: test-gnustl_shared-exception (exec_catching_lib_throwing)<br>
/opt/android/android-sdk-linux/platform-tools/adb -s "emulator-5558" shell "cd /data/local/tmp/ndk-tests && LD_LIBRARY_PATH=/data/local/tmp/ndk-tests ./exec_catching_lib_throwing"<br>
terminate called after throwing an instance of 'std::runtime_error'<br>
what(): OK: Throw in lib, catch in exec!<br>
[1] Segmentation fault LD_LIBRARY_PATH=...<br>
test-return-code:139<br>
---> TEST FAILED!!<br>
Running device test [x86]: test-gnustl_shared-exception (exec_throwing_lib_catching)<br>
/opt/android/android-sdk-linux/platform-tools/adb -s "emulator-5558" shell "cd /data/local/tmp/ndk-tests && LD_LIBRARY_PATH=/data/local/tmp/ndk-tests ./exec_throwing_lib_catching"<br>
link_image[1891]: 1809 could not load needed library 'libtest2_foo.so' for './exec_throwing_lib_catching' (reloc_library[1306]: 1809 cannot locate '_Z3foov'...<br>
)CANNOT LINK EXECUTABLE<br>
test-return-code:255<br>
---> TEST FAILED!!</p>
CrystaX NDK - Bug #271 (Duplicated): Test device/issue22165-typeinfo failed to run
https://tracker.crystax.net/issues/271
2013-03-13T20:26:37Z
Alexander Z.
zuav@crystax.net
<p>Sample output:</p>
<a name="COMMAND-optandroidandroid-sdk-linuxplatform-toolsadb-s-emulator-5558-shell-chmod-0755-datalocaltmpndk-testslibissue22165_throwableso"></a>
<h2 >COMMAND: /opt/android/android-sdk-linux/platform-tools/adb -s emulator-5558 shell chmod 0755 /data/local/tmp/ndk-tests/libissue22165_throwable.so<a href="#COMMAND-optandroidandroid-sdk-linuxplatform-toolsadb-s-emulator-5558-shell-chmod-0755-datalocaltmpndk-testslibissue22165_throwableso" class="wiki-anchor">¶</a></h2>
<p>Running device test [x86]: issue22165-typeinfo (issue22165_main)<br>
/opt/android/android-sdk-linux/platform-tools/adb -s "emulator-5558" shell "cd /data/local/tmp/ndk-tests && LD_LIBRARY_PATH=/data/local/tmp/ndk-tests ./issue22165_main"<br>
call throw_an_exception()<br>
throw_an_exception()<br>
yep! i am in constructor<br>
terminate called after throwing an instance of 'my_exception'<br>
what(): my exception<br>
[1] Segmentation fault LD_LIBRARY_PATH=...<br>
test-return-code:139<br>
---> TEST FAILED!!</p>
CrystaX NDK - Bug #270 (Closed): Test device/gnustl-shared-1 failed to run
https://tracker.crystax.net/issues/270
2013-03-13T20:22:38Z
Alexander Z.
zuav@crystax.net
<p>Sample output:</p>
<a name="COMMAND-optandroidandroid-sdk-linuxplatform-toolsadb-s-emulator-5558-shell-chmod-0755-datalocaltmpndk-teststest_gnustl_shared_link"></a>
<h2 >COMMAND: /opt/android/android-sdk-linux/platform-tools/adb -s emulator-5558 shell chmod 0755 /data/local/tmp/ndk-tests/test_gnustl_shared_link<a href="#COMMAND-optandroidandroid-sdk-linuxplatform-toolsadb-s-emulator-5558-shell-chmod-0755-datalocaltmpndk-teststest_gnustl_shared_link" class="wiki-anchor">¶</a></h2>
<p>Running device test [x86]: gnustl-shared-1 (test_gnustl_shared_link)<br>
/opt/android/android-sdk-linux/platform-tools/adb -s "emulator-5558" shell "cd /data/local/tmp/ndk-tests && LD_LIBRARY_PATH=/data/local/tmp/ndk-tests ./test_gnustl_shared_link"<br>
terminate called after throwing an instance of 'std::exception'<br>
what(): std::exception<br>
Hello [1] Segmentation fault LD_LIBRARY_PATH=...<br>
test-return-code:139<br>
---> TEST FAILED!!</p>
CrystaX NDK - Bug #269 (Rejected): Test device/exceptions-crash failed to run
https://tracker.crystax.net/issues/269
2013-03-13T20:20:41Z
Alexander Z.
zuav@crystax.net
<p>Sample output:</p>
<a name="COMMAND-optandroidandroid-sdk-linuxplatform-toolsadb-s-emulator-5558-shell-chmod-0755-datalocaltmpndk-teststest_exception_crash_static"></a>
<h2 >COMMAND: /opt/android/android-sdk-linux/platform-tools/adb -s emulator-5558 shell chmod 0755 /data/local/tmp/ndk-tests/test_exception_crash_static<a href="#COMMAND-optandroidandroid-sdk-linuxplatform-toolsadb-s-emulator-5558-shell-chmod-0755-datalocaltmpndk-teststest_exception_crash_static" class="wiki-anchor">¶</a></h2>
<p>Running device test [x86]: exceptions-crash (test_exception_crash_shared)<br>
/opt/android/android-sdk-linux/platform-tools/adb -s "emulator-5558" shell "cd /data/local/tmp/ndk-tests && LD_LIBRARY_PATH=/data/local/tmp/ndk-tests ./test_exception_crash_shared"<br>
terminate called after throwing an instance of 'std::exception'<br>
what(): std::exception<br>
Hello [1] Segmentation fault LD_LIBRARY_PATH=...<br>
test-return-code:139<br>
---> TEST FAILED!!</p>
CrystaX NDK - Bug #268 (Closed): Test device/fenv failed to run
https://tracker.crystax.net/issues/268
2013-03-13T19:33:44Z
Alexander Z.
zuav@crystax.net
<p>NB This is x86 specific error.</p>
<p>Sample output:</p>
<a name="COMMAND-optandroidandroid-sdk-linuxplatform-toolsadb-s-emulator-5558-shell-chmod-0755-datalocaltmpndk-teststest_fenv_c"></a>
<h2 >COMMAND: /opt/android/android-sdk-linux/platform-tools/adb -s emulator-5558 shell chmod 0755 /data/local/tmp/ndk-tests/test_fenv_c<a href="#COMMAND-optandroidandroid-sdk-linuxplatform-toolsadb-s-emulator-5558-shell-chmod-0755-datalocaltmpndk-teststest_fenv_c" class="wiki-anchor">¶</a></h2>
<p>Running device test [x86]: fenv (test_fenv_c)<br>
/opt/android/android-sdk-linux/platform-tools/adb -s "emulator-5558" shell "cd /data/local/tmp/ndk-tests && LD_LIBRARY_PATH=/data/local/tmp/ndk-tests ./test_fenv_c"<br>
ERROR jni/test_fenv.c:116 feclearexcept_fetestexcept: (raised & FE_DIVBYZERO) != 0<br>
ERROR jni/test_fenv.c:121 feclearexcept_fetestexcept: (raised & FE_DIVBYZERO) != 0<br>
test-return-code:1<br>
---> TEST FAILED!!</p>
CrystaX NDK - Bug #267 (Closed): Test device/fenv: build failed
https://tracker.crystax.net/issues/267
2013-03-13T19:11:22Z
Alexander Z.
zuav@crystax.net
<p>Sample output:</p>
<p>Compile thumb : test_fenv_c <= test_fenv.c<br>
/tmp/android-ndk-20130312/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc -MMD -MP -MF ./obj/local/armeabi-v7a/objs/test_fenv_c/test_fenv.o.d -fpic -ffunction-sections -funwind-tables -fstack-protector -march=armv7-a -mfloat-abi=softfp -mfpu=vfpv3-d16 -mthumb -Os -g -DNDEBUG -fomit-frame-pointer -fno-strict-aliasing -finline-limit=64 -I/tmp/android-ndk-20130312/sources/crystax/include -Ijni -DANDROID -Wa,--noexecstack -I/tmp/android-ndk-20130312/platforms/android-3/arch-arm/usr/include -c jni/test_fenv.c -o ./obj/local/armeabi-v7a/objs/test_fenv_c/test_fenv.o <br>
rm -f ./libs/armeabi/gdb.setup ./libs/armeabi-v7a/gdb.setup ./libs/mips/gdb.setup ./libs/x86/gdb.setup<br>
/tmp/cc0nmN5r.s: Assembler messages:<br>
/tmp/cc0nmN5r.s:179: Error: bad instruction <code>vmrs r3,fpscr'<br>
/tmp/cc0nmN5r.s:192: Error: bad instruction</code>vmsr fpscr,r3'<br>
/tmp/cc0nmN5r.s:206: Error: bad instruction <code>vmrs r3,fpscr'<br>
/tmp/cc0nmN5r.s:253: Error: bad instruction</code>vmrs r5,fpscr'<br>
/tmp/cc0nmN5r.s:308: Error: bad instruction <code>vmrs r3,fpscr'<br>
/tmp/cc0nmN5r.s:321: Error: bad instruction</code>vmsr fpscr,r3'<br>
/tmp/cc0nmN5r.s:363: Error: bad instruction <code>vmrs r3,fpscr'<br>
/tmp/cc0nmN5r.s:376: Error: bad instruction</code>vmsr fpscr,r3'<br>
/tmp/cc0nmN5r.s:390: Error: bad instruction <code>vmrs r3,fpscr'<br>
/tmp/cc0nmN5r.s:566: Error: bad instruction</code>vmrs r3,fpscr'<br>
/tmp/cc0nmN5r.s:580: Error: bad instruction <code>vmsr fpscr,r3'<br>
/tmp/cc0nmN5r.s:594: Error: bad instruction</code>vmrs r3,fpscr'<br>
/tmp/cc0nmN5r.s:658: Error: bad instruction <code>vmrs r3,fpscr'<br>
/tmp/cc0nmN5r.s:672: Error: bad instruction</code>vmsr fpscr,r3'<br>
/tmp/cc0nmN5r.s:686: Error: bad instruction <code>vmrs r3,fpscr'<br>
/tmp/cc0nmN5r.s:750: Error: bad instruction</code>vmrs r3,fpscr'<br>
/tmp/cc0nmN5r.s:763: Error: bad instruction <code>vmsr fpscr,r3'<br>
/tmp/cc0nmN5r.s:777: Error: bad instruction</code>vmrs r3,fpscr'<br>
/tmp/cc0nmN5r.s:841: Error: bad instruction <code>vmrs r3,fpscr'<br>
/tmp/cc0nmN5r.s:854: Error: bad instruction</code>vmsr fpscr,r3'<br>
/tmp/cc0nmN5r.s:868: Error: bad instruction `vmrs r3,fpscr'<br>
make: *** [obj/local/armeabi-v7a/objs/test_fenv_c/test_fenv.o] Error 1</p>
CrystaX NDK - Bug #266 (Closed): Test device/test-dynamic-cast failed to run
https://tracker.crystax.net/issues/266
2013-03-13T18:58:50Z
Alexander Z.
zuav@crystax.net
<p>Sample output:</p>
<p>Running device test [armeabi]: test-dynamic-cast (test-dynamic-cast)<br>
/opt/android/android-sdk-linux/platform-tools/adb -s "emulator-5554" shell "cd /data/local/tmp/ndk-tests && LD_LIBRARY_PATH=/data/local/tmp/ndk-tests ./test-dynamic-cast"<br>
[1] Segmentation fault LD_LIBRARY_PATH=...</p>
CrystaX NDK - Bug #265 (Rejected): Test device/issue28598-linker-global-ref failed to run
https://tracker.crystax.net/issues/265
2013-03-13T18:55:54Z
Alexander Z.
zuav@crystax.net
<p>Sample output:</p>
<p>Running device test [armeabi]: issue28598-linker-global-ref (issue28598_main)<br>
/opt/android/android-sdk-linux/platform-tools/adb -s "emulator-5554" shell "cd /data/local/tmp/ndk-tests && LD_LIBRARY_PATH=/data/local/tmp/ndk-tests ./issue28598_main"<br>
global = 0x42 (0x80011004)<br>
global = 0x0 (0x2ed50), ERROR!!!</p>
CrystaX NDK - Bug #264 (Rejected): Test device/issue22165-typeinfo failed to run
https://tracker.crystax.net/issues/264
2013-03-13T18:46:47Z
Alexander Z.
zuav@crystax.net
<p>Sample output:</p>
<p>call throw_an_exception()<br>
throw_an_exception()<br>
yep! i am in constructor<br>
[1] Segmentation fault LD_LIBRARY_PATH=...</p>
CrystaX NDK - Bug #221 (Duplicated): test-iostream hangs on armeabi emulator under Windows and Ma...
https://tracker.crystax.net/issues/221
2013-02-22T15:26:45Z
Alexander Z.
zuav@crystax.net
<p>Research where it hangs.<br>
And why.<br>
And how it can be fixed.</p>
CrystaX NDK - Feature #195 (Closed): Always use prebuilt MINGW toolchain
https://tracker.crystax.net/issues/195
2013-01-31T20:00:07Z
Alexander Z.
zuav@crystax.net
<p>Do not search in PATH for mingw toolchain. Use prebuilt MINGW toolchain like it's done with GCC toolchain on linux hosts.<br>
If prebuilt MINGW toolchain not found then output dirty words and stiop build process.<br>
This change can help to avoid target toolchain builds that are broken because of incorrect MINGW toolchain used.</p>
CrystaX NDK - Feature #178 (Closed): Add complex.h support into crystax lib
https://tracker.crystax.net/issues/178
2013-01-20T19:19:41Z
Alexander Z.
zuav@crystax.net
<p>This is the last feature required for 'fully enabled ISO C99 support' in libstdc++ configure tests to produce 'yes'.</p>