search

KeshaviPhone / plcrashreporter

Automatically exported from code.google.com/p/plcrashreporter
Other
0 stars 0 forks source link

BAD_ACCESS instead of NSObjectInaccessibleException. CoreData could not fulfill a fault ... #56

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Manually delete some related object of target object from database.
2. Try to use some of property of target object

What is the expected output? What do you see instead?
I see BAD_ACCESS instead of NSObjectInaccessibleException.

What version of the product are you using? On what operating system?
1.1_rc2. iOS 6.0

Please provide any additional information below.

Original issue reported on code.google.com by exxbr...@gmail.com on 19 Dec 2012 at 12:39

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Sorry SIGSEGV instead of BAD_ACCESS.
Additional info: 
1. It was reproduced only on device.
2. Self written UncaughtExceptionHandler catches exception well.

Crash log started like

Exception Type:  SIGSEGV
Exception Codes: SEGV_ACCERR at 0x120b743b
Crashed Thread:  0

Thread 0 Crashed:
0   libobjc.A.dylib                     0x32198564 0x32195000 + 13668
1   libobjc.A.dylib                     0x3219a1d7 0x32195000 + 20951
2   CoreFoundation                      0x37eb6605 0x37df4000 + 796165

And no exception reason.

Original comment by exxbr...@gmail.com on 19 Dec 2012 at 1:21

GoogleCodeExporter commented 9 years ago 
I'd need to see a full symbolicated report or a buildable test case to be able 
to make any particular determinations.

Original comment by landon.j.fuller@gmail.com on 19 Dec 2012 at 4:50

GoogleCodeExporter commented 9 years ago 
Here is report attached.

Original comment by exxbr...@gmail.com on 20 Dec 2012 at 12:03

Attachments:

GoogleCodeExporter commented 9 years ago 
Here are good crash logs. They are from simulator not from device (like 
previous).

Original comment by exxbr...@gmail.com on 20 Dec 2012 at 12:35

Attachments:

GoogleCodeExporter commented 9 years ago 
I'm not sure this is a bug in PLCrashReporter, so much as a failure that 
behaves non-deterministically in the face of concurrency. The crash itself is 
occurring in in Apple's __handleUncaughtException before the PLCrashReporter 
exception handler is triggered, which would largely preclude PLCrashReporter 
being involved in the failure path.

Original comment by landon.j.fuller@gmail.com on 1 Jan 2013 at 8:59

GoogleCodeExporter commented 9 years ago

Original comment by landon.j.fuller@gmail.com on 4 Jan 2013 at 8:06