• 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: Problems with object observing own key
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problems with object observing own key


  • Subject: Re: Problems with object observing own key
  • From: Colin Cornaby <email@hidden>
  • Date: Sun, 11 May 2008 14:19:44 -0700

#0	0x94eb4993 in NSKVODeallocateBreak
#1	0x94e267c4 in NSKVODeallocate
#2	0x94d7d57f in NSPopAutoreleasePool
#3	0x945b1e54 in -[NSApplication run]
#4	0x9457f030 in NSApplicationMain
#5	0x00008208 in main at main.m:13


On May 11, 2008, at 2:08 PM, Hamish Allan wrote:

On Sun, May 11, 2008 at 9:36 PM, Colin Cornaby <email@hidden> wrote:

Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger.

What's does the stack trace look like from this breakpoint?

Hamish

_______________________________________________

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: Problems with object observing own key
      • From: "Kyle Sluder" <email@hidden>
References: 
 >Problems with object observing own key (From: Colin Cornaby <email@hidden>)
 >Re: Problems with object observing own key (From: "Hamish Allan" <email@hidden>)

  • Prev by Date: Re: Problems with object observing own key
  • Next by Date: Re: wordRangeForRange implememtation
  • Previous by thread: Re: Problems with object observing own key
  • Next by thread: Re: Problems with object observing own key
  • Index(es):
    • Date
    • Thread