On 6.9.2008, at 02:10, Steve Cronin wrote:
Kai;
OK That seems reasonable but:
why do I not see this behavior anywhere else?
Yes, it surprised me a little, too, that I had never seen something
like this. Now if I am right, this occurs only if such a variable
happens to be at a location w
Kai;
OK That seems reasonable but:
why do I not see this behavior anywhere else?
why have I never seen it before now?
why if I restart XCode does the 'bad' instance fall on exactly the
same string?
Thanks,
Steve
On Sep 5, 2008, at 4:11 AM, Kai wrote:
Steve,
looks like the debugger tries
Steve,
looks like the debugger tries to inspect your uninitialized string
pointers. And it happens that the stack location assigned to the 6th
string pointer still contains the address of a now deallocated object
left there when another method exited.
So this is a debugger-only problem an
