Sean --
Nothing in KVO's guts registers arrays as observers, and nothing in
Cocoa Bindings either as far as I know.
For the curious, NSKeyValueObservances are instances of an internal
class that gets instantiated and put in the observation info of
observed object. (Hugely subject to chang
Thanks Mark (and Jim) for the NSZombieEnabled/NSDeallocateZombies
reminder. This showed me that the object has indeed been deallocated
by the time that breakpoint was reached.
Setting an earlier breakpoint I was able to get some more information
on this unknown observer:
Options: Context
--- Sean Todd <[EMAIL PROTECTED]> wrote:
> I have no idea what sort of object 0x6503f00 is or
> how/when it was
> registered. Looking at the address in memory did not
> give me any
> clues. The one interesting bit of info is that the
> address listed with
> its Context is the same as the fir
On Apr 12, 2008, at 8:14 PM, Sean Todd wrote:
Unfortunately, that doesn't work:
grade, Options: Context: 0x1957c0,
Property: 0x18edf0>
)
(gdb) po 0x6500210
Program received signal EXC_BAD_ACCESS, Could not access memory.
Consider setting NSZombieEnabled=YES, NSDeallocateZombies=NO then
Yikes, that's not good. I'd try running with NSZombieEnable = YES to
see if that turns up anything. That should also set
NSDeallocateZombies = NO, which might make gdb po work.
-- Mark
On Apr 12, 2008, at 5:14 PM, Sean Todd wrote:
Unfortunately, that doesn't
Unfortunately, that doesn't work:
Options: Context: 0x1957c0, Property:
0x18edf0>
)
(gdb) po 0x6500210
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0xc007391b
0xfffeff18 in objc_msgSend_rtp ()
The program being debugged was signale
You can copy-and-paste to find out what the surprising observers are,
as in:
(gdb) po 0x19e5a0
-- Mark
On Apr 12, 2008, at 2:59 PM, Sean Todd wrote:
I have a Cocoa document app that uses bindings. After installing
10.5 and Xcode 3.0, I started seeing console
I have a Cocoa document app that uses bindings. After installing 10.5
and Xcode 3.0, I started seeing console output stating that objects
were being deallocated while observers are still registered with them.
After some investigation, I found that the objects being deallocated
had an extra
