I have got a crash log, I can locate the source of call stack like
below:

01-19 17:48:56.580 I/DEBUG   (  683):          #00  pc 00011dee  /
system/lib/libc.so
01-19 17:48:56.580 I/DEBUG   (  683):          #01  pc 0000be1c  /
system/lib/libc.so

I use addr2line to identify that it was memory operating error:

_libc_android_abort
dlfree

But I dont't know who invoke "dlfree" function, I can see some
informations after the keyowrd "stack":

01-19 17:48:56.590 I/DEBUG   (  683): stack:
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcb0  00000718
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcb4  afd1455b  /system/
lib/libc.so
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcb8  afd405a0  /system/
lib/libc.so
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcbc  afd4054c  /system/
lib/libc.so
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcc0  00000000
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcc4  afd154e1  /system/
lib/libc.so
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcc8  00000071
01-19 17:48:56.590 I/DEBUG   (  683):     100ffccc  afd1452d  /system/
lib/libc.so
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcd0  00000000
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcd4  afd40328  /system/
lib/libc.so
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcd8  00000000
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcdc  00001728
01-19 17:48:56.590 I/DEBUG   (  683):     100ffce0  00000000
01-19 17:48:56.590 I/DEBUG   (  683):     100ffce4  afd147cb  /system/
lib/libc.so
01-19 17:48:56.590 I/DEBUG   (  683):     100ffce8  df002777
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcec  e3a070ad
01-19 17:48:56.590 I/DEBUG   (  683): #00 100ffcf0  0000b4e8  [heap]
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcf4  c0000000
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcf8  afd418dc  /system/
lib/libc.so
01-19 17:48:56.590 I/DEBUG   (  683):     100ffcfc  afd10538  /system/
lib/libc.so
01-19 17:48:56.590 I/DEBUG   (  683):     100ffd00  afd40328  /system/
lib/libc.so
01-19 17:48:56.590 I/DEBUG   (  683):     100ffd04  fffffbdf
01-19 17:48:56.590 I/DEBUG   (  683):     100ffd08  afd40328  /system/
lib/libc.so
01-19 17:48:56.590 I/DEBUG   (  683):     100ffd0c  afd41724  /system/
lib/libc.so
01-19 17:48:56.590 I/DEBUG   (  683):     100ffd10  0000b000  [heap]
01-19 17:48:56.590 I/DEBUG   (  683):     100ffd14  afd0be21  /system/
lib/libc.so
01-19 17:48:56.600 I/DEBUG   (  683): #01 100ffd18  afd40328  /system/
lib/libc.so
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd1c  afd0be21  /system/
lib/libc.so
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd20  00000002
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd24  0000b4ee  [heap]
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd28  0000c574  [heap]
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd2c  0000b4e8  [heap]
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd30  0000c574  [heap]
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd34  00000006
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd38  000013fc
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd3c  af9059ff  /system/
lib/libcutils.so
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd40  0000b4e8  [heap]
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd44  800056b5  /system/
lib/libaugusta-ril.so
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd48  100ffd6c
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd4c  0000b438  [heap]
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd50  ae6089bc  /system/
lib/libril.so
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd54  afd0cd81  /system/
lib/libc.so
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd58  800056b5  /system/
lib/libaugusta-ril.so
01-19 17:48:56.600 I/DEBUG   (  683):     100ffd5c  ae6042a3  /system/
lib/libril.so

I think it will be helpful to locate the problem, I don't know how to
use these data? Any one can tell me
how to calculate the location of call stack? Thanks very much!

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to