Hi, > On 6 Feb 2016, at 01:08, Kyle Sluder <k...@ksluder.com> wrote: > > On Fri, Feb 5, 2016, at 09:48 AM, Dave wrote: >> >>> On 4 Feb 2016, at 23:11, Kate Stone <k8st...@apple.com> wrote: >>> >>> Can you confirm whether Jim’s suspicion is correct that you’re looking at >>> the value before initialization? If so, it’s more of a fact of life that >>> in C family languages there’s no way to know for certain whether a variable >>> is initialized or just happens to contain some arbitrary uninitialized >>> memory. >> >> Yes, it’s initialised and I can see values into it if I log them. It’s >> just the debugger that is hosed. > > Are you running a debug or release build of your application?
Debug Release. A but more information on this. I saw this problem quite a while ago but then it stopped happening. I didn’t see it again for quite a while then at the time I started this thread it happened again….. After tracking a down a bug in my code it went away…… The bug was to do with looking at objects that had been restored with NSKeyedArchiver, which was causing backlinks to not be self-referential Basically in a initWithCoder method on one of my objects in the archive, I had something like this: myDictionary = [theCoder decodeObjectForKey:@“pSomeProp"]; self.pSomeProp = [[NSMutableDictionary alloc] initWithDictionary:myDictionary copyItems:YES]; I changed it to: self.pSomeProp = [[NSMutableDictionary alloc] initWithDictionary:myDictionary copyItems:NO]; And it fixed by backlink problem and *ALSO* the problem with the debugger went away……. Not sure what this means but it seems like a clue to me? All the Best Dave _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
