• 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: _CFXPreferencesSetValue crash...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: _CFXPreferencesSetValue crash...


  • Subject: Re: _CFXPreferencesSetValue crash...
  • From: Harry Plate <email@hidden>
  • Date: Tue, 11 Nov 2008 14:30:44 -0800
  • Resent-date: Tue, 11 Nov 2008 14:55:03 -0800
  • Resent-from: Harry Plate <email@hidden>
  • Resent-message-id: <C53F4794.21F12%email@hidden>
  • Resent-to: Xcode <email@hidden>
  • Thread-topic: _CFXPreferencesSetValue crash...

Fritz,

<snip>
>> Thread 0 Crashed:
>> 0   libobjc.A.dylib                   0x95e7c68c objc_msgSend + 28
>> 1   com.apple.CoreFoundation          0x95f6a552
>> CFBundleGetIdentifier + 50
<snip>
> Of course, "runs just fine" just means "runs without crashing." You've
> still got a bug, it just isn't doing anything showy.
>
> A memory error in objc_msgSend almost always means you're attempting
> to use an object that has been released prematurely. Look up
> NSZombieEnabled, and apply it to your project. It should give you some
> clues.
>

Cool. You nailed it! Using NSZombieEnabled gave enough of a hint to uncover
a bug that indeed has been in place for several years. Benign until Leopard.

Thanks for the help!

-harry


 _______________________________________________
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: 
 >Re: _CFXPreferencesSetValue crash... (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Re: _CFXPreferencesSetValue crash...
  • Next by Date: Re: Disk thrashing when opening a project
  • Previous by thread: Re: _CFXPreferencesSetValue crash...
  • Next by thread: C++ STL question
  • Index(es):
    • Date
    • Thread