• 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: Weird crash in -[NSSearchField setRecentSearches:]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Weird crash in -[NSSearchField setRecentSearches:]


  • Subject: Re: Weird crash in -[NSSearchField setRecentSearches:]
  • From: Greg Parker <email@hidden>
  • Date: Fri, 07 Nov 2014 11:14:55 -0800

> On Nov 7, 2014, at 5:06 AM, Jerry Krinock <email@hidden> wrote:
>
>> On 2014 Nov 04, at 01:33, Quincey Morris <email@hidden> wrote:
>>
>> The fact that NSNotificationCenter is involved tells you that this is *not* KVO related.
>
> OK, then that makes me even more upset that all I can get from po $rdi, po $rdx, po $rcx, etc. when I need them nowadays is those damned “Couldn’t materialize: couldn’t read the value of register” errors, even though my Edit Scheme > Info says my configuration is Debug, whose optimization setting is -O0, Deployment Postprocessing is NO and Strip Linked Product is NO.  Does anyone know - is this new opacity the price we must pay for recent optimizations in OS X?

Which frame are you in when you try to read the register (the top frame, or some other frame)? What does `register read rdi` display in the top frame?


>> Personally, I’d worry about entry #4. Surely ‘objc_msgSend_corrupt_cache_error’ has got to be very, very bad.
>
> I hadn’t noticed that, but your remark makes sense.  Unfortunately, a Google search of objc_msgSend_corrupt_cache_error returns 0 results.  If I remove the underscores, I get one result indicating that, yes, this could be due to a deallocced observer.

objc_msgSend_corrupt_cache_error is trying to print some diagnostic info before crashing. You should usually debug it as if it were a crash in objc_msgSend itself: zombies, guard malloc, etc. The contents of the diagnostics will occasionally offer clues that the object was valid but the class was hit by a memory smasher.

In this case objc_msgSend_corrupt_cache_error is itself crashing while trying to decode the data, which doesn't help distinguish "good object" from "bad object".


--
Greg Parker     email@hidden     Runtime Wrangler



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: Weird crash in -[NSSearchField setRecentSearches:]
      • From: Jerry Krinock <email@hidden>
References: 
 >Weird crash in -[NSSearchField setRecentSearches:] (From: Jerry Krinock <email@hidden>)
 >Re: Weird crash in -[NSSearchField setRecentSearches:] (From: Quincey Morris <email@hidden>)
 >Re: Weird crash in -[NSSearchField setRecentSearches:] (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Re: Saving a Document style app
  • Next by Date: Re: Weird crash in -[NSSearchField setRecentSearches:]
  • Previous by thread: Re: Weird crash in -[NSSearchField setRecentSearches:]
  • Next by thread: Re: Weird crash in -[NSSearchField setRecentSearches:]
  • Index(es):
    • Date
    • Thread