Has any other project seen this problem? SETI@home is dying with SIGILL on Snapdragon processors. The first problem was in the function strtod() in libc.so. The address of the fault differs between versions of libc, but the instruction is always the same...
SIGILL: illegal instruction #00 pc 000233ca /system/lib/libc.so (strtod+840) [0xee403b61] #01 pc 0056d43c /data/data/edu.berkeley.boinc/client/pro (_ZSt14__convert_to_vIdEvPKcRT_RSt12_Ios_IostateRKPi+0x60) [0xebea53b9] So I compiled with a static libc, and now the following error appears. Again same opcode on all machines but different addresses depending upon the version of libm.so SIGILL: illegal instruction #00 pc 0000e508 /system/lib/libm.so (floor+208) [0xee700ba1] #01 pc 00031fe0 /data/data/edu.berkeley.boinc/client/pro (_ZN12SETI_WU_INFOC2ERK15workunit_header+0x460) [0xebff3915] There doesn't seem to be a functioning libm.a in the NDK, (what is there seems to be just stubs to calls in the .so) so there's not much I do about it. There are no problems on other ARM processors except the snapdragon family. _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
