Getting useful stack traces on Android

Archived Forums Questions & Answers
1

I am working on a game for Android. While testing on an HTC Desire with Android 2.1, the game crashes early on. Unfortunately, the stack trace reported by adb logcat is completely useless since it has no relevant symbols:

I/DEBUG   (   63): stack:
I/DEBUG   (   63):     49ceba40  00bcd8d0  [heap]
I/DEBUG   (   63):     49ceba44  0046bf00  [heap]
I/DEBUG   (   63):     49ceba48  00bcd8d0  [heap]
I/DEBUG   (   63):     49ceba4c  4a88eb65  
I/DEBUG   (   63):     49ceba50  00000000  
I/DEBUG   (   63):     49ceba54  0046bf00  [heap]
I/DEBUG   (   63):     49ceba58  00c1d260  [heap]
I/DEBUG   (   63):     49ceba5c  00405b20  [heap]
I/DEBUG   (   63):     49ceba60  00000000  
I/DEBUG   (   63):     49ceba64  afd102f0  /system/lib/libc.so
I/DEBUG   (   63):     49ceba68  afd4372c  /system/lib/libc.so
I/DEBUG   (   63):     49ceba6c  00000013  
I/DEBUG   (   63):     49ceba70  00b27d00  [heap]
I/DEBUG   (   63):     49ceba74  49cec800  
I/DEBUG   (   63):     49ceba78  e3a070ad  
I/DEBUG   (   63):     49ceba7c  ef9000ad  
I/DEBUG   (   63): #00 49ceba80  00000000  
I/DEBUG   (   63):     49ceba84  afd0c737  /system/lib/libc.so
I/DEBUG   (   63):     49ceba88  b0014df8  
I/DEBUG   (   63):     49ceba8c  b0004a94  /system/bin/linker
I/DEBUG   (   63):     49ceba90  b000c448  /system/bin/linker
I/DEBUG   (   63):     49ceba94  00000000  
I/DEBUG   (   63):     49ceba98  4ba51244  
I/DEBUG   (   63):     49ceba9c  b000c448  /system/bin/linker
I/DEBUG   (   63):     49cebaa0  00000000  
I/DEBUG   (   63):     49cebaa4  4ba51244  
I/DEBUG   (   63):     49cebaa8  49cec800

It is likely that the error (a segmentation fault) is occurring inside a C# script, but without a way to know where, the game cannot be debugged. So how do you get a useful stack trace with Unity 3 and Android?

I have the same error, I am using the HTC Desire HD Android 2.3.3 using Unity3d 3.4

 –

2 Answers

2
2

I am not sure if this web page is helpful for you I am trying to have it all work in my head but seems like it touches on some good points.

http://bootloader.wikidot.com/linux:android:crashlog

3

I have the fix!

Goto Unity3d.com and install the latest version. If you have 3.4.2f2 Android deployment has a bug, but their latest version 3.4.2f3 resolves this. You can not update your editor through the “check for updates” goto unity3d.com and download it from there as it is not recognized as a new update.