Apple

In the meantime for debugging purposes as a workaround you can copy the value into a local variable in order to be able to see it while debugging. Optimization will eliminate the unnecessary extra copy when building for release.

Kate Stone email@hidden

 Xcode Low Level Tools

On Feb 22, 2016, at 11:37 AM, Kate Stone <email@hidden> wrote:

We’ll look into it as a potential LLDB issue since it definitely looks like a real problem. The command “frame variable i” clearly shows that we don’t think a value is available on the current thread even after it is set:

(int) i = <No TLS data currently exists for this thread.>

Kate Stone email@hidden
 Xcode Low Level Tools

Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden

References:

>XCode debugger does not show values for static __thread local variables in C (From: "Johann 'Myrkraverk' Oskarsson" <email@hidden>)

>Re: XCode debugger does not show values for static __thread local variables in C (From: Kate Stone <email@hidden>)

Prev by Date: Re: Xcode and distribution certificates

Next by Date: Re: git invalid developer path

Previous by thread: Re: XCode debugger does not show values for static __thread local variables in C

Next by thread: Xcode build server now failing on another project I added to it.

Index(es):

Date

Thread