occasionally SIGBUS crash in JNI

by allstars » Wed, 14 Oct 2009 16:37:00 GMT


Sponsored Links
 hello
my apps contains JNI library
but sometimes when i launch it
it will have SIGBUS error

i use addr2line to check the stack trace

the last stack in my native lib is to invoke a JNI call
then it goes to libdvm

my app doesnt register the native method tables on JNI_Onload
it uses traditional JNI native method , i.e.
Java_com_XXXXXX

i would like to know why SIGBUS occurs occasionally

thanks
--~--~---------~--~----~------------~-------~--~----~



occasionally SIGBUS crash in JNI

by allstars » Wed, 14 Oct 2009 17:38:19 GMT


 nd sometimes i met SIGBUS from other lib
below is the log

Build fingerprint: 'generic/generic/generic/:1.6/Donut/eng.allstars.
20090923.152135:eng/test-keys'
10-14 17:33:35.638: INFO/DEBUG(551): pid: 742, tid: 742 >>>
jp.aplix.midp.p1 <<<
10-14 17:33:35.638: INFO/DEBUG(551): signal 7 (SIGBUS), fault addr
00000000
10-14 17:33:35.638: INFO/DEBUG(551): r0 00000001 r1 00000003 r2
00000003 r3 ffff0fff
10-14 17:33:35.638: INFO/DEBUG(551): r4 00000001 r5 ffffffff r6
00000003 r7 0000bc60
10-14 17:33:35.638: INFO/DEBUG(551): r8 00000160 r9 41049200 10
4104be80 fp 00000000
10-14 17:33:35.648: INFO/DEBUG(551): ip ad084fa4 sp bea27708 lr
afb04764 pc ffff0fc0 cpsr 00000010
10-14 17:33:35.737: INFO/DEBUG(551): #00 pc ffff0fc0
10-14 17:33:35.747: INFO/DEBUG(551): #01 pc 00004760 /
system/lib/libcutils.so
10-14 17:33:35.747: INFO/DEBUG(551): stack:
10-14 17:33:35.747: INFO/DEBUG(551): bea276c8 00000002
10-14 17:33:35.747: INFO/DEBUG(551): bea276cc bea27700 [stack]
10-14 17:33:35.747: INFO/DEBUG(551): bea276d0 00000000
10-14 17:33:35.747: INFO/DEBUG(551): bea276d4 ad337785 /system/
lib/libandroid_runtime.so
10-14 17:33:35.747: INFO/DEBUG(551): bea276d8 4104bc90
10-14 17:33:35.757: INFO/DEBUG(551): bea276dc ad00e4b8 /system/
lib/libdvm.so
10-14 17:33:35.757: INFO/DEBUG(551): bea276e0 0000bc60 [heap]
10-14 17:33:35.757: INFO/DEBUG(551): bea276e4 00000001
10-14 17:33:35.757: INFO/DEBUG(551): bea276e8 00000007
10-14 17:33:35.757: INFO/DEBUG(551): bea276ec ad047511 /system/
lib/libdvm.so
10-14 17:33:35.757: INFO/DEBUG(551): bea276f0 4109ced8
10-14 17:33:35.757: INFO/DEBUG(551): bea276f4 0000bc60 [heap]
10-14 17:33:35.767: INFO/DEBUG(551): bea276f8 ad337785 /system/
lib/libandroid_runtime.so
10-14 17:33:35.767: INFO/DEBUG(551): bea276fc ad040cc1 /system/
lib/libdvm.so
10-14 17:33:35.767: INFO/DEBUG(551): bea27700 df002777
10-14 17:33:35.767: INFO/DEBUG(551): bea27704 e3a070ad
10-14 17:33:35.767: INFO/DEBUG(551): #01 bea27708 41ed7072
10-14 17:33:35.767: INFO/DEBUG(551): bea2770c ad045c55 /system/
lib/libdvm.so
10-14 17:33:35.767: INFO/DEBUG(551): bea27710 00000003
10-14 17:33:35.767: INFO/DEBUG(551): bea27714 00000001
10-14 17:33:35.767: INFO/DEBUG(551): bea27718 00000001
10-14 17:33:35.767: INFO/DEBUG(551): bea2771c 41ed7072
10-14 17:33:35.767: INFO/DEBUG(551): bea27720 4104be90
10-14 17:33:35.767: INFO/DEBUG(551): bea27724 bea27770 [stack]
10-14 17:33:35.767: INFO/DEBUG(551): bea27728 ad00e640 /system/
lib/libdvm.so
10-14 17:33:35.767: INFO/DEBUG(551): bea2772c ad00ed9c /system/
lib/libdvm.so
10-14 17:33:35.767: INFO/DEBUG(551): bea27730 ad084e1c
10-14 17:33:35.777: INFO/DEBUG(551): bea27734 41049200
10-14 17:33:35.777: INFO/DEBUG(551): bea27738 bea27770 [stack]
10-14 17:33:35.777: INFO/DEBUG(551): bea2773c ad017d38 /system/
lib/libdvm.so
10-14 17:33:35.777: INFO/DEBUG(551): bea27740 00000330
10-14 17:33:35.777: INFO/DEBUG(551): bea27744 bea277f8 [stack]
10-14 17:33:35.777: INFO/DEBUG(551): bea27748 0000bc60 [heap]
10-14 17:33:35.777: INFO/DEBUG(551): bea2774c 4104bf04



On Oct 14, 4:36pm, allstars <allstars....@gmail.com> wrote:
--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


occasionally SIGBUS crash in JNI

by Marco Nelissen » Thu, 15 Oct 2009 00:00:39 GMT


 ou're probably passing a NULL pointer to your native code, which is
rarely a good idea.


On Wed, Oct 14, 2009 at 2:37 AM, allstars <allstars....@gmail.com> wrote:

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



Other Threads

1. Bad images when rotating 854x480 resolution

We are facing a problem with 854x480 resolution, using Android 1.6
This problem can be replicated on emulator.
Our target device has 854x480 resolution (NOT 480x854).
If we use  default orientation, which is in our case 854x480, there is
no problem.
If we turn by 90 degrees, which is then 480x854, then we have missing
lines, jumping lines and jumping fonts.
This problem can be seen with standard Android menus but easier in
Aldiko (however, to be clear: it is not dependent on the application,
it is just easier to recognize)
This failure DOES NOT occur when you use 480x854 as default resolution/
orientation.
Could it be a problem in the accuracy of the OGLES library of Android?

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

2. Bantuin ngeroot yah

Hlo suhu suhi..

Aku pke dream singtel
Ini dlm proses downgrade rc29.
Kok logonya yg muncul ada 2 yah? T-mobile ama htc dream?
Apa bener ke gini?

-- 
"Indonesian Android Community [id-android]" 

3. ad ga c flash player untuk eclair???

4. Find the Activity object associated with a Tab in a TabActivity

5. Problem getting a linearlayout to be scrollable

6. Get data to android app from mysql server

7. Automatic scrolling of table when rows are added