Quantcast
Channel: Questions in topic: "crash"
Viewing all articles
Browse latest Browse all 2383

Android native crash in Bluestacks on startup without usable backtrace

$
0
0
After the unity splash screen running my game in Bluestacks I get a hard crash with the report below: 12-30 02:26:22.341 6059 6147 E CRASH : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 12-30 02:26:22.341 6059 6147 E CRASH : Version '2020.2.0f1 (3721df5a8b28)', Build type 'Development', Scripting Backend 'il2cpp', CPU 'arm64-v8a' 12-30 02:26:22.341 6059 6147 E CRASH : Build fingerprint: 'google/taimen/taimen:7.1.2/NOF26V/4565141:user/release-keys' 12-30 02:26:22.341 6059 6147 E CRASH : Revision: '0' 12-30 02:26:22.341 6059 6147 E CRASH : ABI: 'arm64' 12-30 02:26:22.350 6059 6147 E CRASH : Timestamp: 2020-12-30 02:26:22-0500 12-30 02:26:22.350 6059 6147 E CRASH : pid: 6059, tid: 6147, name: Thread-4 >>> com.RMIO.InfiniSweeper <<< 12-30 02:26:22.350 6059 6147 E CRASH : uid: 10065 12-30 02:26:22.350 6059 6147 E CRASH : signal 4 (SIGILL), code 0 (SI_USER), fault addr -------- 12-30 02:26:22.350 6059 6147 E CRASH : x0 00007c2f91000480 x1 00007c2f90112f50 x2 0000000000000001 x3 00000000000001c7 12-30 02:26:22.350 6059 6147 E CRASH : x4 000000000e194a20 x5 0000000000000088 x6 0000000000000000 x7 0000000000001401 12-30 02:26:22.350 6059 6147 E CRASH : x8 0000000000000001 x9 00000000000001c7 x10 00007c2f90112f50 x11 0000000000000002 12-30 02:26:22.350 6059 6147 E CRASH : x12 0000000000000000 x13 0000000000000000 x14 0000000000005052 x15 0000000000008006 12-30 02:26:22.351 6059 6147 E CRASH : x16 0000000000000001 x17 0000000000000001 x18 0000000000008006 x19 000000000630be80 12-30 02:26:22.351 6059 6147 E CRASH : x20 0000000000000070 x21 0000000000000010 x22 00007c2f91000480 x23 0000000000000070 12-30 02:26:22.351 6059 6147 E CRASH : x24 0000000000000000 x25 00007c2f91000000 x26 0000000000000006 x27 000000000630c240 12-30 02:26:22.351 6059 6147 E CRASH : x28 00007c2f603767b0 x29 00007c2f1dfffdb0 12-30 02:26:22.351 6059 6147 E CRASH : sp 00007c2f1dfff9c0 lr 000000000e11f7c0 pc 000000000630be7c 12-30 02:26:22.351 6059 6147 E CRASH : 12-30 02:26:22.351 6059 6147 E CRASH : backtrace: 12-30 02:26:22.351 6059 6147 E CRASH : #00 pc 000000000002ae7c Compared to all of the posts I could find debugging native traces, this one seems interesting in that it doesn't have a fault address, and the backtrace is one line listed as "anonymous". I've attempted to use ndk-stack to get turn this into something usable, however, it just spits the same thing back out, which I guess isn't surprising, given that the original trace doesn't even list what .so file it's in, which appears to be generally the case in other native crash dumps. - Version '2020.2.0f1 (3721df5a8b28)' - Build type 'Development', - Scripting Backend 'il2cpp' - CPU 'arm64-v8a' For what it's worth, I've not had any issues running the builds on my actual Pixel 3 device. I'm not sure if this is a quirk of Bluestacks specifically, or if this would mean that other actual Android devices would end up with a similar experience. Any information on where to proceed from here would be useful.

Viewing all articles
Browse latest Browse all 2383

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>