By kengrimm
on Tue, 08/20/2013 - 21:46
I'm running vuforia with an android 3d toolkit called rajawali on a samsung GS2. On identification of a marker I get the following segfault. Can anyone tell me what could be causing this? 08-20 15:20:09.952: I/DEBUG(20857): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***08-20 15:20:09.952: I/DEBUG(20857): Build fingerprint: 'samsung/SGH-T989/SGH-T989:4.0.4/IMM76D/UVLI4:user/release-keys'08-20 15:20:09.952: I/DEBUG(20857): pid: 21027, tid: 21051 >>> com.example.rajawalivuforiaexample <<<08-20 15:20:09.952: I/DEBUG(20857): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000000408-20 15:20:09.952: I/DEBUG(20857): r0 415a9160 r1 00000000 r2 0077ec08 r3 0000000108-20 15:20:09.952: I/DEBUG(20857): r4 415a6b38 r5 00000000 r6 007111a0 r7 5c597b8c08-20 15:20:09.952: I/DEBUG(20857): r8 00000000 r9 b6100001 10 c0000005 fp 579a0cdc08-20 15:20:09.952: I/DEBUG(20857): ip 00000b61 sp 5c597b48 lr 408b2067 pc 408cff48 cpsr 2800003008-20 15:20:09.952: I/DEBUG(20857): d0 bf7d87d7be0cb2aa d1 00000000bc9295fb08-20 15:20:09.952: I/DEBUG(20857): d2 c0d0835042491b1d d3 3f800000437baa3808-20 15:20:09.952: I/DEBUG(20857): d4 0000000000000000 d5 000000000000000008-20 15:20:09.952: I/DEBUG(20857): d6 3f80000000000000 d7 3f8000003f80000008-20 15:20:09.952: I/DEBUG(20857): d8 3feeb851eb851eb8 d9 3ff000000000000008-20 15:20:09.952: I/DEBUG(20857): d10 3feffffffffffffe d11 3ff000000000000008-20 15:20:09.952: I/DEBUG(20857): d12 3f9e766ba9a2e38a d13 3f4707560010560608-20 15:20:09.952: I/DEBUG(20857): d14 3fe00952f3c61b08 d15 3fdfd02d7f6f39b108-20 15:20:09.952: I/DEBUG(20857): d16 008104b041c96908 d17 72656b72614d656d08-20 15:20:09.952: I/DEBUG(20857): d18 3ff0000000000000 d19 000000000000000008-20 15:20:09.952: I/DEBUG(20857): d20 b92377ce858a5d48 d21 38e9f5135cb87c5508-20 15:20:09.952: I/DEBUG(20857): d22 3e21ee9ebdb4b1c4 d23 bda8fae9be8838d408-20 15:20:09.952: I/DEBUG(20857): d24 0000000000000000 d25 000000000000000008-20 15:20:09.952: I/DEBUG(20857): d26 0000000000000000 d27 000000000000000008-20 15:20:09.952: I/DEBUG(20857): d28 3f12e56543e542a3 d29 3f145e0ea5beda2c08-20 15:20:09.952: I/DEBUG(20857): d30 0000000000000000 d31 000000000000000008-20 15:20:09.952: I/DEBUG(20857): scr 68000011
SEGFAULT on marker identification
Looks like this may be caused by some threading issue, but it is very hard to tell from the logs.