119

My code in a UITableViewController:

delegate.myData = [myData objectAtIndex:indexPath.row];

How can I see the values of delegate.myData or indexPath.row in the Debugger? delegate.myData should be an array and indexPath.row an int. I can only see memory addresses of the objects delegate and indexPath but where are myData and row?

alt text

1
  • Right-click in the Debug area, which is below the Code Editor, and choose the Add Expression... context menu item. Enter the variable here, e.g. delegate.myData and that's it. Please check my answer: stackoverflow.com/a/70614719/1245231 Commented Jan 6, 2022 at 23:13

8 Answers 8

152

Check this How to view contents of NSDictionary variable in Xcode debugger?

I also use

po variableName
print variableName

in Console.

In your case it is possible to execute

print [myData objectAtIndex:indexPath.row]  

or

po [myData objectAtIndex:indexPath.row]
Sign up to request clarification or add additional context in comments.

5 Comments

Thank you! I try a lot: "print [myData objectAtIndex:indexPath.row]", "po [myData objectAtIndex:indexPath.row]", "print indexPath.row", "po indexPath.row", ... But every time I got the message "There is no member named row." This works: "print indexPath" and "po indexPath". So I tried using "[]" instead to ".": "po [indexPath row]" -> "Can't print the description of a NIL object." "po [indexPath getRow]" -> "Target does not respond to this message selector." :-(
try print (int)[indexPath row]
po [myData objectAtIndex:(int)[indexPath row]]
@VanDuTran I'm pretty sure the equivalent to po obj in swift is po print(obj).
This was perfect for finding computed properties' values too. Thanks!
35

I agree with other posters that Xcode as a developing environment should include an easy way to debug variables. Well, good news, there IS one!

After searching and not finding a simple answer/tutorial on how to debug variables in Xcode I went to explore with Xcode itself and found this (at least for me) very useful discovery.

How to easily debug your variables in Xcode 4.6.3

In the main screen of Xcode make sure to see the bottom Debug Area by clicking the upper-right corner button showed in the screenshot.

Debug Area button

Debug Area in Xcode 4.6.3

Now set a Breakpoint – the line in your code where you want your program to pause, by clicking the border of your Code Area.

Breakpoint

Now in the Debug Area look for this buttons and click the one in the middle. You will notice your area is now divided in two.

Split Debug Area

Should look like this

Now run your application.

When the first Breakpoint is reached during the execution of your program you will see on the left side all your variables available at that breakpoint.

Search Field

You can expand the left arrows on the variable for a greater detail. And even use the search field to isolate that variable you want and see it change on real time as you "Step into" the scope of the Breakpoint.

Step Into

On the right side of your Debug Area you can send to print the variables as you desire using the mouse's right-button click over the desired variable.

Contextual Menu

As you can see, that contextual menu is full of very interesting debugging options. Such as Watch that has been already suggested with typed commands or even Edit Value… that changes the runtime value of your variable!

Comments

21

Also you can:

  1. Set a breakpoint to pause the execution.
  2. The object must be inside the execution scope
  3. Move the mouse pointer over the object or variable
  4. A yellow tooltip will appear
  5. Move the mouse over the tooltip
  6. Click over the two little arrows pointing up and down
  7. A context menu will pop up
  8. Select "Print Description", it will execute a [object description]
  9. The description will appear in the console's output

IMHO a little bit hidden and cumbersome...

3 Comments

In my xcode "Print Description" not working ,so how can i enable it?
@kirtiavaiya the application must be on pause, and your variable needs to be inside the current scope to be printed. Also you cannot print "self.variable" directly, but you can use Andriy solution for printing _<variable's name>. For example: for self.btnHello write in the console "po _btnHello" (this only works if you haven't changed the getter method's name)
@LightMan yes, its as you said, but then also its not working
11

Your confusion stems from the fact that declared properties are not (necessarily named the same as) (instance) variables.

The expresion

indexPath.row

is equivalent to

[indexPath row]

and the assignment

delegate.myData = [myData objectAtIndex:indexPath.row];

is equivalent to

[delegate setMyData:[myData objectAtIndex:[indexPath row]]];

assuming standard naming for synthesised properties.

Furthermore, delegate is probably declared as being of type id<SomeProtocol>, i.e., the compiler hasn’t been able to provide actual type information for delegate at that point, and the debugger is relying on information provided at compile-time. Since id is a generic type, there’s no compile-time information about the instance variables in delegate.

Those are the reasons why you don’t see myData or row as variables.

If you want to inspect the result of sending -row or -myData, you can use commands p or po:

p (NSInteger)[indexPath row]
po [delegate myData]

or use the expressions window (for instance, if you know your delegate is of actual type MyClass *, you can add an expression (MyClass *)delegate, or right-click delegate, choose View Value as… and type the actual type of delegate (e.g. MyClass *).

That being said, I agree that the debugger could be more helpful:

  • There could be an option to tell the debugger window to use run-time type information instead of compile-time information. It'd slow down the debugger, granted, but would provide useful information;

  • Declared properties could be shown up in a group called properties and allow for (optional) inspection directly in the debugger window. This would also slow down the debugger because of the need to send a message/execute a method in order to get information, but would provide useful information, too.

Comments

7

You can print values onto console window at run-time. Below are steps :

  1. Place a break-point for which you want to get values
  2. Now perform step-by-step debug.
  3. Place a cursor on variable/delegate whose value is to be checked at run-time.
  4. Now this will show description of variable/delegate
  5. Clicking on "i" will show detailed description
  6. This will also print details onto console window.

Screenshot for printing details on console window

3 Comments

Does this work on swift, I'm new to swift cant see the values of object like we use to see in obj c.
@umairhhhs This post is for Objective-C only.
Im wondering why this is not in swift editor because that was very helping and time saving feature.
1

This gets a little complicated. These objects are custom classes or structs, and looking inside them is not as easy on Xcode as in other development environments.

If I were you, I'd NSLog the values you want to see, with some description.

i.e:

NSLog(@"Description of object & time: %i", indexPath.row);

2 Comments

Yes, NSLog is a possibility but not a comfortable alternative to debugging. I am very surprised that there is no way to display the desired values. That belongs for the basic functionality of a development environment.
Most infuriating thing about XCode. Pathetic.
1

Try Run->Show->Expressions

Enter in the name of the array or whatever you're looking for.

3 Comments

Thank you! I entered "indexPath.row" and "delegate.myData" in the expression-window but every time appears "out of scope" in the column "Summary" :-(
np, I had the same issue until I found it ;)
set a breakpoint right after you set your array or whatever and you should find the value in Expressions. Good luck
1

Right-click in the Debug area, which is below the Code Editor, and choose the Add Expression... context menu item. Enter the variable here, e.g. delegate.myData and that's it.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.