Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
NDK debug - How to resolve symbols from libc.so
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  4 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
android777  
View profile  
 More options Feb 16 2011, 12:12 pm
From: android777 <anilreddy...@gmail.com>
Date: Wed, 16 Feb 2011 09:12:21 -0800 (PST)
Local: Wed, Feb 16 2011 12:12 pm
Subject: NDK debug - How to resolve symbols from libc.so
I was running my app on emulator and the app crashed leaving me
unknown symbols on logcat and the debugger. Here is my output from
logcat and gdb.

ndk-gdb output :

Program received signal SIGSTOP, Stopped (signal).
0xafd0eb08 in __futex_syscall3 () from /home/anil/workspace/
FFMPEGFinal/obj/local/armeabi/libc.so
(gdb) bt
#0  0xafd0eb08 in __futex_syscall3 () from /home/anil/workspace/
FFMPEGFinal/obj/local/armeabi/libc.so
#1  0xafd107b0 in __pthread_cond_timedwait_relative () from /home/anil/
workspace/FFMPEGFinal/obj/local/armeabi/libc.so
Cannot access memory at address 0xbea768e4

LogCat Output :

02-15 23:42:39.347: INFO/DEBUG(31): *** *** *** *** *** *** *** ***
*** *** *** *** *** *** *** ***
02-15 23:42:39.347: INFO/DEBUG(31): Build fingerprint: 'generic/sdk/
generic/:2.2/FRF91/43546:eng/test-keys'
02-15 23:42:39.366: INFO/DEBUG(31): pid: 996, tid: 1024  >>>
ffmpeg.app <<<
02-15 23:42:39.381: INFO/DEBUG(31): signal 11 (SIGSEGV), fault addr
00000020
02-15 23:42:39.381: INFO/DEBUG(31):  r0 4739ad38  r1 001260e0  r2
00000001  r3 00000000
02-15 23:42:39.381: INFO/DEBUG(31):  r4 817dcde4  r5 4739ad38  r6
44e929f8  r7 4184ff94
02-15 23:42:39.381: INFO/DEBUG(31):  r8 4739ad80  r9 4184ff8c  10
4184ff78  fp 00268e38
02-15 23:42:39.448: INFO/DEBUG(31):  ip ab2145cc  sp 4739ace8  lr
8103c084  pc 81030c30  cpsr 20000010
02-15 23:42:40.061: INFO/DEBUG(31):          #00  pc 00030c30  /data/
data/ffmpeg.app/lib/libffmpeg.so
02-15 23:42:40.061: INFO/DEBUG(31):          #01  pc 0003c080  /data/
data/ffmpeg.app/lib/libffmpeg.so
02-15 23:42:40.190: INFO/DEBUG(31):          #02  pc 00013974  /system/
lib/libdvm.so
02-15 23:42:40.190: INFO/DEBUG(31):          #03  pc 0003de3c  /system/
lib/libdvm.so
02-15 23:42:40.217: INFO/DEBUG(31):          #04  pc 00037216  /system/
lib/libdvm.so
02-15 23:42:40.303: INFO/DEBUG(31):          #05  pc 00018714  /system/
lib/libdvm.so
02-15 23:42:40.310: INFO/DEBUG(31):          #06  pc 0001e8c4  /system/
lib/libdvm.so
02-15 23:42:40.472: INFO/DEBUG(31):          #07  pc 0001d790  /system/
lib/libdvm.so
02-15 23:42:40.487: INFO/DEBUG(31):          #08  pc 00053eec  /system/
lib/libdvm.so
02-15 23:42:40.527: INFO/DEBUG(31):          #09  pc 00054102  /system/
lib/libdvm.so
02-15 23:42:40.608: INFO/DEBUG(31):          #10  pc 0004825a  /system/
lib/libdvm.so
02-15 23:42:40.626: INFO/DEBUG(31):          #11  pc 0001103c  /system/
lib/libc.so
02-15 23:42:40.626: INFO/DEBUG(31):          #12  pc 00010b20  /system/
lib/libc.so
02-15 23:42:40.666: INFO/DEBUG(31): code around pc:
02-15 23:42:40.677: INFO/DEBUG(31): 81030c10 ea00001b e59f3090
e7943003 e5933000
02-15 23:42:40.757: INFO/DEBUG(31): 81030c20 e58d3024 e59f3080
e7943003 e5933000
02-15 23:42:40.780: INFO/DEBUG(31): 81030c30 e5933020 e1a02003
e59f306c e7943003
02-15 23:42:40.786: INFO/DEBUG(31): 81030c40 e5832000 e59d3024
e28dc004 e1a0e003
02-15 23:42:40.786: INFO/DEBUG(31): 81030c50 e8be000f e8ac000f
e89e000f e88c000f
02-15 23:42:40.786: INFO/DEBUG(31): code around lr:
02-15 23:42:40.807: INFO/DEBUG(31): 8103c064 e59f30a4 e7943003
e5933000 e3530000
02-15 23:42:40.816: INFO/DEBUG(31): 8103c074 da000015 e28d3018
e1a00003 ebffd2cb
02-15 23:42:40.826: INFO/DEBUG(31): 8103c084 e3a03b96 e58d304c
e59d3028 e58d3000
02-15 23:42:40.826: INFO/DEBUG(31): 8103c094 e3a00006 e59f3074
e08f3003 e1a01003
02-15 23:42:40.886: INFO/DEBUG(31): 8103c0a4 e59f306c e08f3003
e1a02003 e59d304c
02-15 23:42:40.886: INFO/DEBUG(31): stack:
02-15 23:42:40.908: INFO/DEBUG(31):     4739aca8  00000001
02-15 23:42:40.917: INFO/DEBUG(31):     4739acac  00000007
02-15 23:42:40.956: INFO/DEBUG(31):     4739acb0  418aba0c  /dev/
ashmem/dalvik-LinearAlloc (deleted)
02-15 23:42:40.997: INFO/DEBUG(31):     4739acb4  80846dad  /system/
lib/libdvm.so
02-15 23:42:41.049: INFO/DEBUG(31):     4739acb8  00126118  [heap]
02-15 23:42:41.049: INFO/DEBUG(31):     4739acbc  00268e38  [heap]
02-15 23:42:41.116: INFO/DEBUG(31):     4739acc0  44e82938  /dev/
ashmem/mspace/dalvik-heap/2 (deleted)
02-15 23:42:41.116: INFO/DEBUG(31):     4739acc4  8083d9b9  /system/
lib/libdvm.so
02-15 23:42:41.116: INFO/DEBUG(31):     4739acc8  8083d99d  /system/
lib/libdvm.so
02-15 23:42:41.137: INFO/DEBUG(31):     4739accc  00241c58  [heap]
02-15 23:42:41.137: INFO/DEBUG(31):     4739acd0  ab2150d8
02-15 23:42:41.137: INFO/DEBUG(31):     4739acd4  afd10510  /system/
lib/libc.so
02-15 23:42:41.137: INFO/DEBUG(31):     4739acd8  001260e0  [heap]
02-15 23:42:41.178: INFO/DEBUG(31):     4739acdc  ab2150d8
02-15 23:42:41.178: INFO/DEBUG(31):     4739ace0  df002777
02-15 23:42:41.178: INFO/DEBUG(31):     4739ace4  e3a070ad
02-15 23:42:41.178: INFO/DEBUG(31): #00 4739ace8  00126118  [heap]
02-15 23:42:41.178: INFO/DEBUG(31):     4739acec  4739ad74
02-15 23:42:41.178: INFO/DEBUG(31):     4739acf0  44e929f8  /dev/
ashmem/mspace/dalvik-heap/2 (deleted)
02-15 23:42:41.178: INFO/DEBUG(31):     4739acf4  4184ff94
02-15 23:42:41.178: INFO/DEBUG(31):     4739acf8  4739ad80
02-15 23:42:41.178: INFO/DEBUG(31):     4739acfc  4184ff8c
02-15 23:42:41.178: INFO/DEBUG(31):     4739ad00  00126118  [heap]
02-15 23:42:41.178: INFO/DEBUG(31):     4739ad04  4739ad74
02-15 23:42:41.251: INFO/DEBUG(31):     4739ad08  44e929f8  /dev/
ashmem/mspace/dalvik-heap/2 (deleted)
02-15 23:42:41.260: INFO/DEBUG(31):     4739ad0c  00000000
02-15 23:42:41.260: INFO/DEBUG(31):     4739ad10  817dcde4  /data/data/
ffmpeg.app/lib/libffmpeg.so
02-15 23:42:41.260: INFO/DEBUG(31):     4739ad14  817dcde4  /data/data/
ffmpeg.app/lib/libffmpeg.so
02-15 23:42:41.260: INFO/DEBUG(31):     4739ad18  00000000
02-15 23:42:41.260: INFO/DEBUG(31):     4739ad1c  8103c084  /data/data/
ffmpeg.app/lib/libffmpeg.so
02-15 23:42:41.260: INFO/DEBUG(31): #01 4739ad20  00126118  [heap]
02-15 23:42:41.332: INFO/DEBUG(31):     4739ad24  00000000
02-15 23:42:41.332: INFO/DEBUG(31):     4739ad28  42c3e41f  /data/
dalvik-cache/system@framew...@framework.jar@classes.dex
02-15 23:42:41.332: INFO/DEBUG(31):     4739ad2c  44e82938  /dev/
ashmem/mspace/dalvik-heap/2 (deleted)
02-15 23:42:41.416: INFO/DEBUG(31):     4739ad30  44e929f8  /dev/
ashmem/mspace/dalvik-heap/2 (deleted)
02-15 23:42:41.416: INFO/DEBUG(31):     4739ad34  00241c58  [heap]
02-15 23:42:41.416: INFO/DEBUG(31):     4739ad38  001260e0  [heap]
02-15 23:42:41.416: INFO/DEBUG(31):     4739ad3c  ab2150d8
02-15 23:42:41.436: INFO/DEBUG(31):     4739ad40  00000000
02-15 23:42:41.436: INFO/DEBUG(31):     4739ad44  afd103f0  /system/
lib/libc.so
02-15 23:42:41.436: INFO/DEBUG(31):     4739ad48  00126118  [heap]
02-15 23:42:41.436: INFO/DEBUG(31):     4739ad4c  000000ff
02-15 23:42:41.510: INFO/DEBUG(31):     4739ad50  42c3e41f  /data/
dalvik-cache/system@framew...@framework.jar@classes.dex
02-15 23:42:41.559: INFO/DEBUG(31):     4739ad54  4184ff2c
02-15 23:42:41.559: INFO/DEBUG(31):     4739ad58  000001e0
02-15 23:42:41.559: INFO/DEBUG(31):     4739ad5c  00000140
02-15 23:42:41.606: INFO/DEBUG(31):     4739ad60  000003c0
02-15 23:42:41.606: INFO/DEBUG(31):     4739ad64  00000004
02-15 23:42:41.606: INFO/DEBUG(31):     4739ad68  00000000
02-15 23:42:41.606: INFO/DEBUG(31):     4739ad6c  ad34912d  /system/
lib/libandroid_runtime.so
02-15 23:42:41.616: INFO/DEBUG(31):     4739ad70  00000000
02-15 23:42:41.616: INFO/DEBUG(31):     4739ad74  47829008
02-15 23:42:41.616: INFO/DEBUG(31):     4739ad78  4739ada0
02-15 23:42:41.616: INFO/DEBUG(31):     4739ad7c  80813978  /system/
lib/libdvm.so


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
alan  
View profile  
 More options Feb 16 2011, 4:11 pm
From: alan <a...@birtles.org.uk>
Date: Wed, 16 Feb 2011 13:11:17 -0800 (PST)
Local: Wed, Feb 16 2011 4:11 pm
Subject: Re: NDK debug - How to resolve symbols from libc.so

have you looked up these addresses?
02-15 23:42:40.061: INFO/DEBUG(31):          #00  pc 00030c30  /data/
data/ffmpeg.app/lib/libffmpeg.
so
02-15 23:42:40.061: INFO/DEBUG(31):          #01  pc 0003c080  /data/
data/ffmpeg.app/lib/libffmpeg.so


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
android777  
View profile  
 More options Feb 16 2011, 5:34 pm
From: android777 <anilreddy...@gmail.com>
Date: Wed, 16 Feb 2011 14:34:26 -0800 (PST)
Local: Wed, Feb 16 2011 5:34 pm
Subject: Re: NDK debug - How to resolve symbols from libc.so
how to lookup the addresses?

On Feb 16, 3:11 pm, alan <a...@birtles.org.uk> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
alan  
View profile  
 More options Feb 17 2011, 4:22 am
From: alan <a...@birtles.org.uk>
Date: Thu, 17 Feb 2011 01:22:47 -0800 (PST)
Local: Thurs, Feb 17 2011 4:22 am
Subject: Re: NDK debug - How to resolve symbols from libc.so

use addr2line


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »