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? > > > LLDB is doing its best to tell you what the memory currently appears to be. > > I’d hate to see its worst job then! > > > If his suspicion is not correct and you’re seeing something unexpected we > > would definitely want to look at this issue more closely. If that’s the > > case please file a bug via bugreport.apple.com > > <http://bugreport.apple.com/>. We take issues with debugger reliability > > very seriously. > > Well apparently its already been filed, so feel free to fix it anytime > you like….. What’s the bug number? --Kyle > > 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/kyle%40ksluder.com > > This email sent to k...@ksluder.com _______________________________________________ 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
