Databases
StackOverflow2013
Postsdbo
POGetting to the bottom of crash
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGetting to the bottom of crash
    primarykey
    data
    text
    <p>I have the following crash that I can't replicate on demand but does happen enough to get noticed by the users.</p> <p>This crash report has been symbolicated as well. How would you find out the cause!!! This only seems to happen on 4.1</p> <pre><code>Exception Type: SIGSEGV Exception Codes: SEGV_ACCERR at 0x9f069184 Crashed Thread: 0 Thread 0 Crashed: 0 libobjc.A.dylib 0x000027d8 objc_msgSend + 16 1 CoreFoundation 0x0007d749 ____CFXNotificationPost_old_block_invoke_1 + 45 2 libSystem.B.dylib 0x000d5984 _dispatch_call_block_and_release + 20 3 libSystem.B.dylib 0x000d66b0 _dispatch_continuation_pop + 72 4 libSystem.B.dylib 0x000d69fc _dispatch_main_queue_callback_4CF + 220 5 CoreFoundation 0x0002789b __CFRunLoopRun + 1335 6 CoreFoundation 0x00027277 CFRunLoopRunSpecific + 231 7 CoreFoundation 0x0002717f CFRunLoopRunInMode + 59 8 GraphicsServices 0x000045f3 GSEventRunModal + 115 9 GraphicsServices 0x0000469f GSEventRun + 63 10 UIKit 0x00004123 -[UIApplication _run] + 403 11 UIKit 0x0000212f UIApplicationMain + 671 12 MyApp 0x000024e3 main (main.m:17) </code></pre> <p>I have since managed to get a little more info, but not much. </p> <pre><code>2012-02-12 18:03:04.556 MyApp[462:307] (null): unrecognized selector sent to class 0x3e0a360c 2012-02-12 18:03:04.618 MyApp[462:307] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '(null): unrecognized selector sent to class 0x3e0a360c' *** Call stack at first throw: ( 0 CoreFoundation 0x33506ed3 __exceptionPreprocess + 114 1 libobjc.A.dylib 0x30412811 objc_exception_throw + 24 2 CoreFoundation 0x335086ff +[NSObject(NSObject) doesNotRecognizeSelector:] + 102 3 CoreFoundation 0x334b01d9 ___forwarding___ + 508 4 CoreFoundation 0x334aff90 _CF_forwarding_prep_0 + 48 5 Foundation 0x302a86b3 _nsnote_callback + 142 6 CoreFoundation 0x334e4749 ____CFXNotificationPost_old_block_invoke_1 + 44 7 libSystem.B.dylib 0x31d05984 _dispatch_call_block_and_release + 20 8 libSystem.B.dylib 0x31d066b0 _dispatch_continuation_pop + 72 9 libSystem.B.dylib 0x31d069fc _dispatch_main_queue_callback_4CF + 220 10 CoreFoundation 0x3348e89b __CFRunLoopRun + 1334 11 CoreFoundation 0x3348e277 CFRunLoopRunSpecific + 230 12 CoreFoundation 0x3348e17f CFRunLoopRunInMode + 58 13 GraphicsServices 0x31b5e5f3 GSEventRunModal + 114 14 GraphicsServices 0x31b5e69f GSEventRun + 62 15 UIKit 0x341bd123 -[UIApplication _run] + 402 16 UIKit 0x341bb12f UIApplicationMain + 670 </code></pre> <p>Now all of my addObservers are block based so I can't see why it would lead to an unrecognised selector.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USLee Armstrong
    1. USLee Armstrong
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGetting to the bottom of crash
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGetting to the bottom of crash
      1. USLee Armstrong
      1. VTBountyStart
    3. VO
      singulars
      1. POGetting to the bottom of crash
      1. USNightFury
      1. VTFavorite
    1. COI don't know, so I'm not posting an answer, but it looks like it's trying to invoke a Block that's already been released?
      singulars
      1. POGetting to the bottom of crash
      1. USJasarien
    2. CONot sure if this is the reason, but I'd check if I was removing objects as observers (to `NSNotificationCenter`) before deallocing.
      singulars
      1. POGetting to the bottom of crash
      1. USalex-i
    3. COIs your crash just because of NSNotification only, sure? Try to comment out that code and run.
      singulars
      1. POGetting to the bottom of crash
      1. USMrunal
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload