StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18441148
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-08-26T09:42:01.837
FavoriteCount
0
LastActivityDate
2013-08-26T12:24:55.480
LastEditDate
2013-08-26T12:24:55.480
LastEditorUserId
139985
OwnerUserId
139985
ParentId
18440592
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
This bit of code is never going to work. An uncaught exception handler is called after a thread has terminated due to an exception that was not caught. If you then attempt to re-throw the exception, there will be nothing else to catch it. <ul> <li>If you want to have your re-thrown exception handled in the normal, you have to do the logging further up the stack.</li> <li>The only other option you have is to explicitly chain to another <code>UncaughtExceptionHandler</code>.</li> </ul> <hr> I suspect that the freeze is you are experiencing is a direct consequence of the current thread dying. <hr> FOLLOWUP: <blockquote> ... is there some other way in Android to intercept exceptions at a global level, without using Thread.setDefaultUncaughtExceptionHandler? </blockquote> AFAIK, no. <blockquote> Or how would the chaining look like? </blockquote> Something like this: <pre><code>public void uncaughtException(Thread thread, final Throwable ex) { // do report ... getSomeOtherHandler(...).uncaughtException(thread, ex); } </code></pre> Or, since ThreadGroup implements <code>UncaughtExceptionHandler</code>, ... <pre><code>public void uncaughtException(Thread thread, final Throwable ex) { // do report ... thread.getThreadGoup().uncaughtException(thread, ex); } </code></pre> Basically, you just call some other handler. It's not rocket science. But note that you can't catch and recover from an exception in the "normal" way once you've landed in one of these handlers.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCrash app in Thread.setDefaultUncaughtExceptionHandler
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USStephen C
UserOwnerUserId
1. USStephen C
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCrash app in Thread.setDefaultUncaughtExceptionHandler
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COThanks for this info - is there some other way in Android to intercept exceptions at a global level, without using `Thread.setDefaultUncaughtExceptionHandler`? Or how would the chaining look like?
 singulars
 PostPostId
 PO
 UserUserId
 USFlo

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.