Re: Can't trace into an Obj-C call?
Re: Can't trace into an Obj-C call?
- Subject: Re: Can't trace into an Obj-C call?
- From: Dave Camp <email@hidden>
- Date: Tue, 13 Nov 2007 11:35:07 -0800
On Nov 13, 2007, at 11:10 AM, Rick Mann wrote:
So, I'm new to Obj-C, but so far my experience is not winning me
over. This problem may be more in Xcode than in the language.
If I put a breakpoint on line 10, and then use the debugger to Step
Into (Control-T in my bindings), first it steps past that, then it
steps into all the message send glue, and then I get lost, and it
never seems to step into the method.
CodeWarrior had a setting for "Don't step into glue code" that was
very convenient.
However, something else is going on. If I put an additional
breakpoint on line 17, and Continue from line 10, then the stack at
line 10:
Which is not what I would expect. I would expect to see a line for
showChartInspector between #0 and #1 in the second stack. Is this
Xcode being bad, or is this something inherent in the Obj-C call
mechanism? I hope it's the former, because the latter seems less
than useless. If it's the former, how do I fix it?
No, it shouldn't be doing that.
Are you debugging the debug build with optimizations turned off?
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden