Xcode debugging problem

Question

I have a little problem with the Xcode Debugger. Looks to me the "Step In" function doesn't work like it should. Or just as I expect it to work.

I can step in any method call as long it has no return value:

[myObject DoSomething];

That works find but if the method has a return value, there is no Step In. the Debugger just steps over the method.

double b = [myObject CalculateSomething];

If I do the same with functions instead of methods the debugger always steps into the function call. No matter if it has a return value or not.

Is this a bug? Is it a feature? Is it meant to be that way? I tried it with the current Xcode and the Xcode 4 Beta on a different machines but the debugger refuses to step into methods with return values.

EDIT

Yes I am in debug mode. I get no compiler errors, no warnings. I can easily reproduce this problem any time. A method CalculateSomething -> just do a return 5; and the debugger will not step into it. The value is not zero afterwards, the program works fine.

Only the debugger refuses to step the method or any other method with a return value.

Dou you build in debug mode? Have you declared that method before? Any compiler warnings? Any output on the console? If I'd have to guess, b is zero after the call? — Eiko
– Eiko, Commented Aug 26, 2010 at 12:44

rjobidon · Accepted Answer · 2010-09-03 02:09:49Z

4

In the debug project settings you must disable code optimization option with OPTIMIZATION_LEVEL = NONE.

Good luck!

Source: Working with Xcode Build Settings

answered Sep 3, 2010 at 2:09

rjobidon

3,1653 gold badges33 silver badges37 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

boidkan Over a year ago

Source link out of date. Is this what you linked? developer.apple.com/library/ios/recipes/…

TechZen · Accepted Answer · 2010-08-26 12:48:50Z

0

I haven't seen this problem on Xcode 3.2.3.

However, I have seen cases where the debugger gets confused about methods called against objects returned by imbedded methods e.g.

id myResult=[[self returnAnObject] tellObjectToDoSomething];

Sometimes the debugger doesn't seem to know which method to drop into or it "forgets" that there are two method calls on the line.

If you have customize accessors, you may always drop into the the accessor instead of the outer method (i.e.tellObjectToDoSomething.)

answered Aug 26, 2010 at 12:48

TechZen

64.4k16 gold badges121 silver badges146 bronze badges

Comments

Rose Perrone · Accepted Answer · 2013-08-27 18:08:58Z

0

Turn off code optimization. In Build Settings, change:

enter image description here To:

enter image description here

answered Aug 27, 2013 at 18:08

Rose Perrone

64k61 gold badges216 silver badges251 bronze badges

Collectives™ on Stack Overflow

Xcode debugging problem

3 Answers 3

1 Comment

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related