| LLDB has relaxed the restriction on where you can use “po” for developers who weren’t always clear on whether a given _expression_ resulted in an Objective-C object or not. It will now print the description of an Objective-C object, or fall back to the behavior of the _expression_ evaluator “p” for non-objects.
Xcode Runtime Analysis Tools
On May 17, 2014, at 3:46 PM, Alex Zavatone < email@hidden> wrote:
But I think that's the point
We want po to display the contents, no matter if they are structs or NSObjects.
If you want to take the sample I posted earlier, it can be made to display those core foundation data objects in addition to the NSObject.s
On May 17, 2014, at 6:17 AM, João Varela wrote: I don't think that is the problem. The problem is that NSRect is not an NSObject-based object, but a C struct and po may not work properly with structs, as according to the docs of LLDB po prints out the description of a ObjC description.
You can check that here (search for NSRect):
and here (search for po):
HTH
>I think that rects have structs inside them so you'll have to expose them yourself.
>That's my guess.
>On May 17, 2014, at 2:15 AM, Roland King wrote:
> I have a similar problem today but no amount of casting helps, here's mine
>
> (lldb) po textField.constraints
> error: instance method 'preparedContentRect' has incompatible result types in different translation units ('<unknown type>' vs. 'NSRect' (aka 'CGRect'))
> note: instance method 'preparedContentRect' also declared here
> note: declared here with type 'NSRect' (aka 'CGRect')
> error: 1 errors parsing _expression_
|