Thanks for the reply. I don't have the broken APK, I fixed it yesterday. If I remember correctly, it had something to do with Cursor.getLong being invoked after the Cursor has been closed. Or may be with ContentResolver.delete in the middle of traversal by Cursor. I couldn't realize - I just rewrote the function in a different manner and it worked fine.
Denis On Nov 7, 11:22 am, fadden <[EMAIL PROTECTED]> wrote: > On Nov 6, 4:24 am, denismo <[EMAIL PROTECTED]> wrote: > > > LogCat continuously reports this error: > > 11-06 12:20:57.999: DEBUG/dalvikvm(834): threadid=3: still suspended > > after undo (s=1 d=1) > > There's a weird interaction between the VM and your debugger. The > thread suspended itself and then waited to be woken. However, when it > was woken the thread was still marked as being suspended (s=1) by the > debugger (d=1). > > If you have an APK that reaches this state repeatably I'd be > interested in taking a look at it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
