Log in or register to post comments

We have a signal 4 Error.

November 17, 2011 - 12:11am #1

Hi.

We have a Android mobile phone. (in Unity3D)

OS : ver. 2.2.2
Model number : DeTron-1
Kernel : 2.6.32.9
CPU : Qualcomm 600Mhz (Unity set ARM6)
RAM : 512

This is Error log at DDMS

01-06 08:05:47.281: VERBOSE/ProcessManager(120): [AM] processCheck (com.PRISMAR.VMuseum , 10076, activity, com.PRISMAR.VMuseum/.RainbowExtend)
01-06 08:05:47.291: INFO/ActivityManager(120): Start proc com.PRISMAR.VMuseum for activity com.PRISMAR.VMuseum/.RainbowExtend: pid=893 uid=10076 gids={3003, 1006}
01-06 08:05:47.361: INFO/WindowManager(120): Setting rotation to 1, animFlags=1
01-06 08:05:47.381: INFO/ActivityManager(120): Config changed: { scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=2 layout=34 uiMode=17 seq=11 FlipFont=0}
01-06 08:05:47.461: DEBUG/taeil86s(120): =========================deactivate===========================
01-06 08:05:47.671: INFO/DEBUG(889): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-06 08:05:47.671: INFO/DEBUG(889): Build fingerprint: 'TCT/mercury/mercury/IL1:2.2.2/FRG83G/sc01.CT9B_MA00.06:eng/release-keys'
01-06 08:05:47.671: INFO/DEBUG(889): pid: 893, tid: 893 >>> com.PRISMAR.VMuseum 01-06 08:05:47.671: INFO/DEBUG(889): signal 4 (SIGILL), fault addr 80c21000
01-06 08:05:47.671: INFO/DEBUG(889): r0 0000aab8 r1 00000000 r2 80d4e210 r3 000003ec
01-06 08:05:47.671: INFO/DEBUG(889): r4 80c20fdc r5 00128888 r6 0000cd68 r7 aca903cc
01-06 08:05:47.671: INFO/DEBUG(889): r8 aca11240 r9 0000cd68 10 41e86bf0 fp 00000000
01-06 08:05:47.671: INFO/DEBUG(889): ip aca904a4 sp beb331c8 lr aca404d7 pc 80c21000 cpsr 20000010
01-06 08:05:47.671: INFO/DEBUG(889): d0 0000005a42b40000 d1 3ff0000042b40000
01-06 08:05:47.671: INFO/DEBUG(889): d2 bfd3441350baf6de d3 c1493000c1323800
01-06 08:05:47.671: INFO/DEBUG(889): d4 4900000040dcb000 d5 000000000006e580
01-06 08:05:47.671: INFO/DEBUG(889): d6 4515a00000000800 d7 40800000c48ee000
01-06 08:05:47.671: INFO/DEBUG(889): d8 0000000000000000 d9 0000000000000000
01-06 08:05:47.671: INFO/DEBUG(889): d10 0000000000000000 d11 0000000000000000
01-06 08:05:47.671: INFO/DEBUG(889): d12 0000000000000000 d13 0000000000000000
01-06 08:05:47.671: INFO/DEBUG(889): d14 0000000000000000 d15 0000000000000000
01-06 08:05:47.671: INFO/DEBUG(889): scr 80000012
01-06 08:05:47.741: INFO/DEBUG(889): #00 pc 00021000 /data/data/com.PRISMAR.VMuseum/lib/libQCAR.so
01-06 08:05:47.741: INFO/DEBUG(889): #01 pc 000404d4 /system/lib/libdvm.so
01-06 08:05:47.741: INFO/DEBUG(889): #02 pc 0005770a /system/lib/libdvm.so
01-06 08:05:47.741: INFO/DEBUG(889): #03 pc 00015fe8 /system/lib/libdvm.so
01-06 08:05:47.741: INFO/DEBUG(889): #04 pc 0001c7c4 /system/lib/libdvm.so
01-06 08:05:47.751: INFO/DEBUG(889): #05 pc 0001b65c /system/lib/libdvm.so
01-06 08:05:47.751: INFO/DEBUG(889): #06 pc 00050838 /system/lib/libdvm.so
01-06 08:05:47.751: INFO/DEBUG(889): #07 pc 00050a3a /system/lib/libdvm.so
01-06 08:05:47.751: INFO/DEBUG(889): #08 pc 0005b31a /system/lib/libdvm.so
01-06 08:05:47.751: INFO/DEBUG(889): #09 pc 000153a0 /system/lib/libdvm.so
01-06 08:05:47.751: INFO/DEBUG(889): #10 pc 0001c7c4 /system/lib/libdvm.so
01-06 08:05:47.751: INFO/DEBUG(889): #11 pc 0001b65c /system/lib/libdvm.so
01-06 08:05:47.751: INFO/DEBUG(889): #12 pc 000509ca /system/lib/libdvm.so
01-06 08:05:47.761: INFO/DEBUG(889): #13 pc 00058402 /system/lib/libdvm.so
01-06 08:05:47.761: INFO/DEBUG(889): #14 pc 00015fe8 /system/lib/libdvm.so
01-06 08:05:47.761: INFO/DEBUG(889): #15 pc 0001c7c4 /system/lib/libdvm.so
01-06 08:05:47.761: INFO/DEBUG(889): #16 pc 0001b65c /system/lib/libdvm.so
01-06 08:05:47.761: INFO/DEBUG(889): #17 pc 00050838 /system/lib/libdvm.so
01-06 08:05:47.761: INFO/DEBUG(889): #18 pc 0003e0c0 /system/lib/libdvm.so
01-06 08:05:47.761: INFO/DEBUG(889): #19 pc 00032936 /system/lib/libdvm.so
01-06 08:05:47.761: INFO/DEBUG(889): #20 pc 0002de48 /system/lib/libandroid_runtime.so
01-06 08:05:47.761: INFO/DEBUG(889): #21 pc 0002ecfe /system/lib/libandroid_runtime.so
01-06 08:05:47.771: INFO/DEBUG(889): #22 pc 00008c86 /system/bin/app_process
01-06 08:05:47.771: INFO/DEBUG(889): #23 pc 0000d356 /system/lib/libc.so
01-06 08:05:47.771: INFO/DEBUG(889): code around pc:
01-06 08:05:47.771: INFO/DEBUG(889): 80c20fe0 e3500000 e92d4010 e08f2002 e24dd008
01-06 08:05:47.771: INFO/DEBUG(889): 80c20ff0 e3a01000 e5820004 e58d1004 0a000007
01-06 08:05:47.771: INFO/DEBUG(889): 80c21000 e3002004 e5903000 e3402001 e28d1004
01-06 08:05:47.771: INFO/DEBUG(889): 80c21010 e1a0e00f e593f018 e3500000 0a000006
01-06 08:05:47.771: INFO/DEBUG(889): 80c21020 eb01bddd e59f1070 e08f1001 eb01bc30
01-06 08:05:47.771: INFO/DEBUG(889): code around lr:
01-06 08:05:47.771: INFO/DEBUG(889): aca404b4 9903d02f 1c306f32 21076731 f0039204
01-06 08:05:47.771: INFO/DEBUG(889): aca404c4 4b20fe29 20df9007 008258f9 21005888
01-06 08:05:47.771: INFO/DEBUG(889): aca404d4 990747a0 1c301c04 fe1cf003 67339b04
01-06 08:05:47.771: INFO/DEBUG(889): aca404e4 429c4b19 3b02d015 d012429c 429c3304
01-06 08:05:47.771: INFO/DEBUG(889): aca404f4 4b16d00f 98024911 187918fa 90009f03
01-06 08:05:47.771: INFO/DEBUG(889): stack:
01-06 08:05:47.771: INFO/DEBUG(889): beb33188 80c03f60 /data/data/com.PRISMAR.VMuseum/lib/libQCAR.so
01-06 08:05:47.771: INFO/DEBUG(889): beb3318c 80c013e0 /data/data/com.PRISMAR.VMuseum/lib/libQCAR.so
01-06 08:05:47.771: INFO/DEBUG(889): beb33190 00000000
01-06 08:05:47.771: INFO/DEBUG(889): beb33194 b0004da4 /system/bin/linker
01-06 08:05:47.771: INFO/DEBUG(889): beb33198 b001a18c
01-06 08:05:47.771: INFO/DEBUG(889): beb3319c 80c20fdc /data/data/com.PRISMAR.VMuseum/lib/libQCAR.so
01-06 08:05:47.771: INFO/DEBUG(889): beb331a0 00008d44 /system/bin/app_process
01-06 08:05:47.771: INFO/DEBUG(889): beb331a4 80c00000 /data/data/com.PRISMAR.VMuseum/lib/libQCAR.so
01-06 08:05:47.771: INFO/DEBUG(889): beb331a8 aca11240 /system/lib/libdvm.so
01-06 08:05:47.771: INFO/DEBUG(889): beb331ac 0000cd68 [heap]
01-06 08:05:47.771: INFO/DEBUG(889): beb331b0 41e86bf0
01-06 08:05:47.771: INFO/DEBUG(889): beb331b4 b0003371 /system/bin/linker
01-06 08:05:47.771: INFO/DEBUG(889): beb331b8 aca903cc /system/lib/libdvm.so
01-06 08:05:47.771: INFO/DEBUG(889): beb331bc b0015a6c
01-06 08:05:47.771: INFO/DEBUG(889): beb331c0 df002777
01-06 08:05:47.771: INFO/DEBUG(889): beb331c4 e3a070ad
01-06 08:05:47.771: INFO/DEBUG(889): #00 beb331c8 80c20fdc /data/data/com.PRISMAR.VMuseum/lib/libQCAR.so
01-06 08:05:47.771: INFO/DEBUG(889): beb331cc 00000000
01-06 08:05:47.771: INFO/DEBUG(889): beb331d0 80c20fdc /data/data/com.PRISMAR.VMuseum/lib/libQCAR.so
01-06 08:05:47.781: INFO/DEBUG(889): beb331d4 aca404d7 /system/lib/libdvm.so
01-06 08:05:47.781: INFO/DEBUG(889): #01 beb331d8 ad11298d /system/lib/libnativehelper.so
01-06 08:05:47.781: INFO/DEBUG(889): beb331dc 000007ff
01-06 08:05:47.781: INFO/DEBUG(889): beb331e0 0012c548 [heap]
01-06 08:05:47.781: INFO/DEBUG(889): beb331e4 45a81f40 /dev/ashmem/mspace/dalvik-heap/2 (deleted)
01-06 08:05:47.781: INFO/DEBUG(889): beb331e8 00000000
01-06 08:05:47.781: INFO/DEBUG(889): beb331ec 00128894 [heap]
01-06 08:05:47.781: INFO/DEBUG(889): beb331f0 00128898 [heap]
01-06 08:05:47.781: INFO/DEBUG(889): beb331f4 00000001
01-06 08:05:47.781: INFO/DEBUG(889): beb331f8 41e86c04
01-06 08:05:47.781: INFO/DEBUG(889): beb331fc beb33270 [stack]
01-06 08:05:47.781: INFO/DEBUG(889): beb33200 0012c548 [heap]
01-06 08:05:47.781: INFO/DEBUG(889): beb33204 45a81f40 /dev/ashmem/mspace/dalvik-heap/2 (deleted)
01-06 08:05:47.781: INFO/DEBUG(889): beb33208 40052388 /dev/ashmem/mspace/dalvik-heap/zygote/0 (deleted)
01-06 08:05:47.781: INFO/DEBUG(889): beb3320c aca5770f /system/lib/libdvm.so
01-06 08:05:48.191: INFO/ActivityManager(120): Process com.PRISMAR.VMuseum (pid 893) has died.

Re: We have a signal 4 Error.

March 27, 2012 - 6:38pm #4

Are you stuck trying to push the application to the device? What does the Eclipse log say?

Can you build and run one of the Android samples?

- Kim

Re: We have a signal 4 Error.

March 27, 2012 - 9:34am #3

Hi
I am a little new to android.
well i have installed everything according to instructions provided.
when i run the application . .
it gets stuck in installing framemarkers.apk

nothing happens after that :(

can you please help?

Re: We have a signal 4 Error.

November 17, 2011 - 8:48am #2

The QCAR Unity extension currently only works with ARMv7 devices. This is mentioned in the Supported Devices documentation:

Quote:

Devices with Armv7 or higher are required to run the Unity QCAR
Extension for Unity.

- Kim

Log in or register to post comments