Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>When you use the <code>p</code> command, there are several different things lldb can do. </p> <p>For simple concrete types (<code>int</code>, <code>int *</code>) it may only print the value in the variable (10, 0xffffffff83021600). It may have a formatter preference set (e.g. display the <code>int</code> in hexadecimal). It may have a more sophisticated python formatter (which can read different parts of memory and present a high-level view of the object to you). Finally, it may actually run code in your program to come up with a high level view of that variable.</p> <p>In this case, with Xcode 4.6, this looks like a simple <code>NSString</code> ivar and so the expectation is that lldb can use its built-in python formatter for NSString objects. This built-in formatter looks at the object memory and knows how to reconstruct the actual string for display without running any code in your program. In which case, the content of the string should not be modified.</p> <p>Earlier versions (and gdb) may run code in your program to format the string, and it is possible that the program could change a little in the process. There is a lot of work done to ensure that doesn't happen, but the possibility exists.</p> <p>Enrico is suspecting that the built-in python formatter function for <code>NSString</code> may be misbehaving somehow in your program and providing string summaries that change as you re-call the formatter. Please do file a bug report at <a href="http://bugreport.apple.com/" rel="nofollow">http://bugreport.apple.com/</a> with the details for how to reproduce this behavior.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload