Well, I've filed the bug report: http://code.google.com/p/android/issues/detail?id=3531&sort=-id&colspec=ID%20Type%20Version%20Security%20Status%20Owner%20Summary
But nothing seems to be happening on those reports, it's just pages and pages of untouched bug reports? What should I do? I have to cripple my application just to avoid this stupid segfault? Rich On Jul 30, 1:25 pm, fadden <[email protected]> wrote: > On Jul 29, 6:31 pm, Rich <[email protected]> wrote: > > > D/libc-abort( 1180): abort() called in pid 1180 > > I/DEBUG ( 551): *** *** *** *** *** *** *** *** *** *** *** *** *** > > *** *** *** > > I/DEBUG ( 551): Build fingerprint: 'generic/google_sdk/generic/:1.5/ > > CUPCAKE/148875:eng/test-keys' > > I/DEBUG ( 551): pid: 1180, tid: 1190 >>> org.ale.abtc <<< > > I/DEBUG ( 551): signal 11 (SIGSEGV), fault addr deadbaad > > Can you send me an APK or command-line Java program that causes this? > (I can't find the symbols for that build.) Better yet, file a bug > report on b.android.com and attach it. > > Running out of sockets should not cause a native library to call abort > (). Usually that happens when something calls malloc() or free(), and > dlmalloc discovers that the heap is corrupt. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
