Address Sanitizer changes the way local variables are represented on the stack (to protect from stack buffer overflows), so this might be a bug in the debug info generation. If you can provide a small reproducer, then please file a bug at bugreport.apple.com <http://bugreport.apple.com/>.
Also, is "size" a local variable or is it an instance variable of a C++ object? Is the issue only present in C++ code? Thanks, Kuba > On 7 Sep 2016, at 01:23, Jens Alfke <j...@mooseyard.com> wrote: > > In the latest Xcode 8 beta, while debugging I’m getting a lot of those > dreaded “Couldn’t materialize” errors from LLDB, where it can’t get the value > of a variable. To be precise, the variable’s value doesn’t show up in the > variables pane, and when I try to print it with LLDB I get: > > (lldb) p size > error: Couldn't materialize: couldn't get the value of variable size: > variable not available > error: errored out in DoExecute, couldn't PrepareToExecuteJITExpression > > This is intermittent, but it happens even in debug builds, when I’m stopped > at an ordinary breakpoint (not crashed). > It does seem to go away if I turn off the Address Sanitizer, but for obvious > reasons I prefer to leave that on when I’m debugging. > > Anyone else getting a lot of these in Xcode 8? Is it known to Apple yet? > > —Jens > > PS: Xcode 8 beta 6, latest macOS Sierra beta, building a Mac target, > debugging C++ code.
_______________________________________________ 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
