Android app crashes with SIGABRT Signal 6 only while Eclipse debugging -


i have app runs fine on device without debugger attached. however, have problem when debugging in eclipse:

when main thread suspended 10 seconds or more (for example after hitting breakpoint), main thread throws sigabrt, apparently coming libc.

the explanation think of message queue on main thread, when not being polled, overflowing messages coming thread. however, don't see heap growing when main thread suspended. moreover, while app has 20 threads between services, content providers, broadcast receivers, http , map worker threads, etc., can't think of source of excessive messages.

so question is: how fix problem? tools can use , how go finding causing app crash while sitting suspended in debugger?

edit 1:

the thing in logcat is:

02-05 22:23:54.861: i/dalvikvm(26795): threadid=3: reacting signal 3 02-05 22:23:54.901: d/dalvikvm(26795): threadid=1: still suspended after undo (sc=1 dc=1) 02-05 22:23:54.901: i/dalvikvm(26795): wrote stack traces '/data/anr/traces.txt' 02-05 22:23:58.905: a/libc(26795): fatal signal 6 (sigabrt) @ 0x000002f5 (code=0), thread 26795 (om.myapp) 

edit 2:

further investigation leads me believe android intentionally killing process because mistakenly thinks ui thread hung. problem not in app. question is: how stop android killing process while debugging?

android intentionally kills process because thinks ui thread hung, anr right. debugging purposes can,

go settings -> developer options , check show anrs.

this show app not responding dialog apps running in background. can click wait button in dialog prevent system killing process until debugger attaches. note dialog opened automatically apps running in foreground. background apps, have enable option


Comments

Popular posts from this blog

python - Subclassed QStyledItemDelegate ignores Stylesheet -

java - HttpClient 3.1 Connection pooling vs HttpClient 4.3.2 -

SQL: Divide the sum of values in one table with the count of rows in another -