how to debug engine layer crash without stack information?

by kevin ma » Wed, 22 Jul 2009 05:48:50 GMT


Sponsored Links
 Dear all,
    I'm debugging opencore related app & engine. Normally, when met
engine layer crash issue, we will get the stack info printed in the
log as below.

I/DEBUG   (   33):          #00  pc 00111dac  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #01  pc 00112c66  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #02  pc 00105ff0  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #03  pc 00082b98  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #04  pc 00042fe2  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #05  pc 0004346c  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #06  pc 00043088  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #07  pc 00040e18  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #08  pc 000ede86  /system/lib/
libopencoreauthor.so
I/DEBUG   (   33):          #09  pc 000edf48  /system/lib/
libopencoreauthor.so
I/DEBUG   (   33):          #10  pc 000f56b6  /system/lib/
libopencoreauthor.so
I/DEBUG   (   33):          #11  pc 000f50f4  /system/lib/
libopencoreauthor.so
I/DEBUG   (   33):          #12  pc 00032a50  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #13  pc 00032c7c  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #14  pc 00032e44  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #15  pc 001109ec  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #16  pc 00110b40  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #17  pc 0002affe  /system/lib/
libandroid_runtime.so
I/DEBUG   (   33):          #18  pc 000285d4  /system/lib/libutils.so
I/DEBUG   (   33):          #19  pc 0000f8cc  /system/lib/libc.so
I/DEBUG   (   33):          #20  pc 0000f438  /system/lib/libc.so




    But sometimes, we can not get these info. So it's very hard to fix
the bug at that time. Does anyone know some method to solve this
problem? Thanks!

Best Regards,
Kevin
--~--~---------~--~----~------------~-------~--~----~



how to debug engine layer crash without stack information?

by fadden » Wed, 22 Jul 2009 18:23:39 GMT


 


I posted some information about transforming stack traces here:

  


Sponsored Links


how to debug engine layer crash without stack information?

by kevin ma » Thu, 23 Jul 2009 01:22:49 GMT


 Dear fadden,
    Thanks for your great help! The key issue is when my app crash, I can
not get the stack information now. I just wondering when will the stack info
generated and print out, when it will not, when crash met. Thanks!

Best Regards,
Kevin

2009/7/23 fadden <fad...@android.com>


> 



how to debug engine layer crash without stack information?

by fadden » Thu, 23 Jul 2009 19:24:09 GMT


 


Some info here:




Other Threads

1. Multiple line Notification

I use NotificationManager to write a Notification. I want now a
multiple-line text for my notification. Is it possible?
--~--~---------~--~----~------------~-------~--~----~

2. In call dialpad/menu confusion - am I the only one?

Platform improvements are ongoing, and this specific issue is being
addressed in an upcoming release.

j






-- 
Jeff Sharkey
jshar...@android.com

--~--~---------~--~----~------------~-------~--~----~

3. PendingIntent Flag and AlarmManager behavior ?

4. take screenshot programmatically

5. Android Lap top connection

6. ZooShaker is fun for all ages

7. Sample Code