LLDB-Debugging | The LLDB Debugging in C , Swift , Objective-C , Python | Code Inspection library

I'm not sure this helps, but what is going on is a little more complicated than you think.

Swift strings are actually structs, so if you stopped on the line before you assign to self.text.label, and assign a new value to your label var, you are actually changing the contents of the struct, which should by all rights mean that when you assign to self.text.label from that struct, it really should pick up the new value...

The reason that doesn't work is that the swift compiler is smart about unboxing these structs so that it doesn't do unnecessary dereferences when possible. This happens even at -Onone.

So for instance, in your example the swift compiled code has already unboxed the string and emitted code that directly references the contents. Changing the actual string contents doesn't change the references to the unboxed contents already in the assignment code, and so your change doesn't take.

You can see this IRL: if you make the compiler unable to know what the contents of the string are, it can't do this unboxing, and then you will see your debugger changes take effect.

Using this example code: