[android-developers] Re: Dalvik SegFaults while using CMU Sphinx4

2010-08-02 Thread Luis D. Pedrosa 
Thanks for the help!

You are absolutely right, the error I'm getting on Froyo is a
different one and is basically related to Sphinx's dependency on the
javax.sound.sampled library. The behavior is still a bit awkward, but
Dalvik does not crash, and this error I can debug and fix (or try).

Regards,

Luis D. Pedrosa

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

[android-developers] Re: Dalvik SegFaults while using CMU Sphinx4

2010-08-02 Thread Luis D. Pedrosa 
I would be more than happy to document the process, although, at some
point, I will most likely have to make changes to Sphinx that are
specific to our project and not useful outside of it.

Thanks for the encouragement!

-- Luis D. Pedrosa

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

[android-developers] Dalvik SegFaults while using CMU Sphinx4

2010-07-27 Thread Luis D. Pedrosa 
Hi all,

I am a part of a project that involves automatically offloading
portions of an application's execution to a cloud of servers. As such,
we try to run traditionally difficult algorithms on our Android
phones, in particular, speech recognition algorithms, namely the CMU
Sphinx4 library.

The Sphinx4 library, itself, is open-source and written in Java, so I
was expecting a fairly simple porting, however I have run into a bit
of trouble. After ironing out most of the kinks and minor
discrepancies between Android's Java and J2SE, I have reached a point
where Dalvik just dies on me. The phone simply returns to the home
screen without a warning or a 'Force Close' button and LogCat
(included below) shows me that my process has terminated with signal
11 (SIGSEGV).

When I try to debug the issue by stepping through the code line by
line, I can never pin point an exact place that consistently causes
the crash, but it does crash every time. I have tried this out on
Android 1.6 with an HTC Dream Phone, Android 2.1-update1 with a
Motorola Droid, and Android 2.2 in the emulator and it happens on all
of them.

I am pretty much stumped. Has anyone seen anything like this happening
before? Are there any rules of thumb to circumvent or debug this sort
of issue? Should I report this as a bug in some bugtracker?

If it's useful, I can post some example code that will cause the
crash.

Thanks!

Kind regards,

Luis D. Pedrosa



07-26 17:36:55.707: INFO/DEBUG(2353): *** *** *** *** *** *** *** ***
*** *** *** *** *** *** *** ***
07-26 17:36:55.707: INFO/DEBUG(2353): Build fingerprint: 'verizon/
voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys'
07-26 17:36:55.707: INFO/DEBUG(2353): pid: 25633, tid: 25633  
mobiprog.apps.AndroidTranscriber 
07-26 17:36:55.707: INFO/DEBUG(2353): signal 11 (SIGSEGV), fault addr
0048
07-26 17:36:55.707: INFO/DEBUG(2353):  r0   r1 ad03e2d0  r2
bee9e7d4  r3 
07-26 17:36:55.707: INFO/DEBUG(2353):  r4 447df798  r5 ad081f50  r6
4000e920  r7 400094b8
07-26 17:36:55.707: INFO/DEBUG(2353):  r8 ad00ee40  r9 bd18  10
4186b760  fp 
07-26 17:36:55.707: INFO/DEBUG(2353):  ip ad082ba0  sp bee9e808  lr
ad05a84d  pc ad05c2c8  cpsr 6030
07-26 17:36:55.895: INFO/DEBUG(2353):  #00  pc 0005c2c8  /
system/lib/libdvm.so
07-26 17:36:55.902: INFO/DEBUG(2353):  #01  pc 0005d63e  /
system/lib/libdvm.so
07-26 17:36:55.902: INFO/DEBUG(2353):  #02  pc 00056ce0  /
system/lib/libdvm.so
07-26 17:36:55.902: INFO/DEBUG(2353):  #03  pc 000139b8  /
system/lib/libdvm.so
07-26 17:36:55.902: INFO/DEBUG(2353):  #04  pc 00019338  /
system/lib/libdvm.so
07-26 17:36:55.902: INFO/DEBUG(2353):  #05  pc 00018804  /
system/lib/libdvm.so
07-26 17:36:55.902: INFO/DEBUG(2353):  #06  pc 0004eed0  /
system/lib/libdvm.so
07-26 17:36:55.902: INFO/DEBUG(2353):  #07  pc 0004eef8  /
system/lib/libdvm.so
07-26 17:36:55.910: INFO/DEBUG(2353):  #08  pc 0005c478  /
system/lib/libdvm.so
07-26 17:36:55.910: INFO/DEBUG(2353):  #09  pc 0005d116  /
system/lib/libdvm.so
07-26 17:36:55.910: INFO/DEBUG(2353):  #10  pc 0005d198  /
system/lib/libdvm.so
07-26 17:36:55.910: INFO/DEBUG(2353):  #11  pc 000568da  /
system/lib/libdvm.so
07-26 17:36:55.910: INFO/DEBUG(2353):  #12  pc 000139b8  /
system/lib/libdvm.so
07-26 17:36:55.910: INFO/DEBUG(2353):  #13  pc 00019338  /
system/lib/libdvm.so
07-26 17:36:55.910: INFO/DEBUG(2353):  #14  pc 00018804  /
system/lib/libdvm.so
07-26 17:36:55.918: INFO/DEBUG(2353):  #15  pc 0004eba6  /
system/lib/libdvm.so
07-26 17:36:55.918: INFO/DEBUG(2353):  #16  pc 00056dc4  /
system/lib/libdvm.so
07-26 17:36:55.918: INFO/DEBUG(2353):  #17  pc 000139b8  /
system/lib/libdvm.so
07-26 17:36:55.918: INFO/DEBUG(2353):  #18  pc 00019338  /
system/lib/libdvm.so
07-26 17:36:55.918: INFO/DEBUG(2353):  #19  pc 00018804  /
system/lib/libdvm.so
07-26 17:36:55.918: INFO/DEBUG(2353):  #20  pc 0004eed0  /
system/lib/libdvm.so
07-26 17:36:55.918: INFO/DEBUG(2353):  #21  pc 0003afbe  /
system/lib/libdvm.so
07-26 17:36:55.957: INFO/DEBUG(2353):  #22  pc 00027f58  /
system/lib/libandroid_runtime.so
07-26 17:36:55.957: INFO/DEBUG(2353):  #23  pc 00028cc4  /
system/lib/libandroid_runtime.so
07-26 17:36:55.957: INFO/DEBUG(2353):  #24  pc 8cd8  /
system/bin/app_process
07-26 17:36:55.957: INFO/DEBUG(2353):  #25  pc c228  /
system/lib/libc.so
07-26 17:36:55.957: INFO/DEBUG(2353): code around pc:
07-26 17:36:55.965: INFO/DEBUG(2353): ad05c2b8 f7fe6d31 4603fdfb
f1b06cb8 d1043fff
07-26 17:36:55.965: INFO/DEBUG(2353): ad05c2c8 e048f8d3 31be
4820d00a 182a4f20
07-26 17:36:55.965: INFO/DEBUG(2353): ad05c2d8 19e92006 f7b29303
f7d9e9e8 9b03fc1d
07-26 17:36:55.965: INFO/DEBUG(2353): code around lr:
07-26 17:36:55.965: INFO/DEBUG(2353): ad05a83c