• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Crash averted when run under debugger
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Crash averted when run under debugger


  • Subject: Re: Crash averted when run under debugger
  • From: Rick Mann <email@hidden>
  • Date: Fri, 27 Apr 2012 17:38:50 -0700

Ah. I think it's because I have zombies enabled, and that setting only sticks if running from Xcode. If I launch the app from SpringBoard, zombies aren't on.

Turns out, I wasn't unregistering a KVO, so the call was going to bad memory.

--
Rick

On Apr 27, 2012, at 17:31 , Rick Mann wrote:

> I'm running into a KVO-related crash, on device only. Unfortunately, it doesn't happen if I run with the debugger attached. But if I run the exact same binary without the debugger (i.e., launching by tapping its icon), then I can reproduce the crash reliably.
>
> The symbolicated crash log, unfortunately, provides no clue as to which object(s) is involved in the KVO, and I use it in a number of places.
>
> Any techniques I can use to check on this? What's different when running with the debugger attached?
>
> The crash is
>
> Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes: KERN_INVALID_ADDRESS at 0x70015785
> Crashed Thread:  0
>
> Thread 0 name:  Dispatch queue: com.apple.main-thread
> Thread 0 Crashed:
> 0   libobjc.A.dylib               	0x36557f78 objc_msgSend + 16
> 1   Foundation                    	0x34cce74c NSKVOPendingNotificationCreate + 216
> 2   Foundation                    	0x34cce652 NSKeyValuePushPendingNotificationPerThread + 62
> 3   Foundation                    	0x34cc0744 NSKeyValueWillChange + 408
> 4   Foundation                    	0x34d1ace6 -[NSObject(NSKeyValueObservingPrivate) _willChangeValuesForKeys:] + 486
> 5   CoreData                      	0x344b9048 -[NSFaultHandler turnObject:intoFaultWithContext:] + 188
> 6   CoreData                      	0x344ba638 -[NSManagedObject dealloc] + 68
> 7   CoreData                      	0x344b9b74 -[_PFManagedObjectReferenceQueue _processReferenceQueue:] + 840
> 8   CoreData                      	0x344bcfd0 _performRunLoopAction + 196
> 9   CoreFoundation                	0x31cdcb14 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 12
> 10  CoreFoundation                	0x31cdad50 __CFRunLoopDoObservers + 252
> 11  CoreFoundation                	0x31cdb0aa __CFRunLoopRun + 754
> 12  CoreFoundation                	0x31c5e49e CFRunLoopRunSpecific + 294
> 13  CoreFoundation                	0x31c5e366 CFRunLoopRunInMode + 98
> 14  GraphicsServices              	0x356bc432 GSEventRunModal + 130
> 15  UIKit                         	0x328bfe76 UIApplicationMain + 1074
> 16  iPadWeather                   	0x000a69f0 main (main.m:16)
> 17  iPadWeather                   	0x000a6994 start + 32
>
>
>
> Thanks,
> Rick
>
>


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Crash averted when run under debugger (From: Rick Mann <email@hidden>)

  • Prev by Date: Crash averted when run under debugger
  • Next by Date: Re: Tweak auto-completion
  • Previous by thread: Crash averted when run under debugger
  • Next by thread: Checking DDI symbols
  • Index(es):
    • Date
    • Thread