IssueTracker

Decoded stack trace:

pid: 2710, tid: 3087  >>> com.startapp.wallpaper.browser <<<
signal 11 (SIGSEGV), fault addr 00000014
  r0 0011de28  r1 44934428  r2 000000a4  r3 00000000
  r4 005ac1a8  r5 44934418  r6 0011de28  r7 44934428
  r8 4689dda0  r9 42b5def4  10 42b5dee0  fp 0062cf60
  ip 00000000  sp 4689dd78  lr ad215ec7  pc af55aaaa

Stack Trace:
  RELADDR   FUNCTION                                                                                  
FILE:LINE
  0005aaaa  EVP_DigestUpdate                                                                          
/usr/local/google/buildbot/repo_clients/git_eclair-
release/external/openssl/crypto/evp/digest.c:213
  v------>  NativeCrypto_EVP_DigestUpdate                                                              
/usr/local/google/buildbot/repo_clients/git_eclair-release/dalvik/libcore/x-
net/src/main/native/org_apache_harmony_xnet_provider_jsse_NativeCrypto.cpp:346
  00015ec4  NativeCrypto_EVP_DigestUpdate(_JNIEnv*, _jclass*, env_md_ctx_st*,
_jbyteArray*, int, int)  /usr/local/google/buildbot/repo_clients/git_eclair-
release/dalvik/libcore/x-
net/src/main/native/org_apache_harmony_xnet_provider_jsse_NativeCrypto.cpp:346
  0000ecb4  dvmPlatformInvoke                                                                          
/usr/local/google/buildbot/repo_clients/git_eclair-
release/dalvik/vm/arch/arm/CallEABI.S:243

Thank you very much!

I think I fixed the error. Maybe it could be helpful for you too.

I was using a MessageDigest to digest lots of data arrays but I wasn't reseting the
instance. Check it out because it was crashing the application with a SIGSEV.

I hope it was helpful.

can you give us a small repeatable test case so we can find and fix the bug (or confirm that we've already fixed it --- much of that code has been rewritten in froyo).

Here you are. It's a brief example which crashes on my Nexus.

Hope it was helpful

I would try it in Froyo but I have not received the upgrade yet.

your example still crashes in froyo. i'll investigate.

(fyi, if you ever want to test against the current release but don't have a device, you can download the SDK and test in the emulator. the SDK is released before any devices get the corresponding code.)

the problem in the sample code is that MessageDigest is stateful and thus not thread-safe. you can't use a MessageDigest simultaneously from multiple threads and get meaningful results. rather than return nonsense, Android goes one step further and actually crashes. we could add synchronization, but that would slow down correct code, and cause incorrect code to silently return wrong results. so it's arguably better to keep the current behavior and crash.

i will update the documentation to (a) explicitly mention thread safety and (b) include an example showing how to use MessageDigest correctly, but i don't think i can usefully change the behavior.

I understand my code is wrong due to MessageDigest methods aren't synchronized but it must never stop the program with a SIGSEV. It is very difficult to debug. So I would reconsider the solution.

Anyway, I am very pleased and grateful for the help.

D/AccessibilityManager: current package=com.activa.one.singlerecognition, accessibility manager mIsFinalEnabled=false, mOptimizeEnabled=false, mIsUiAutomationEnabled=false, mIsInterestedPackage=false
A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x28 in tid 25330 (nglerecognition)
Process 25330 terminated.

because of this fatal error app crashes I am very pleased and grateful for the help.

 Fatal signal 11 (SIGSEGV), code 1, fault addr 0x38d20944 in tid 7589