Re: strange debugger behavior
Re: strange debugger behavior
- Subject: Re: strange debugger behavior
- From: Jim Ingham <email@hidden>
- Date: Wed, 11 Jul 2007 14:27:18 -0700
As you can sort of guess from the FOUNDATION_STATIC_INLINE types,
what's going on is that the debugger doesn't know that inlined code
actually constitutes a "function" call. As far as it knows, the
source lines of the inlined function are just injected straight into
the current function. Thus it doesn't know to step past all the
inlined source lines.
The stabs debug format had no information about inlined code
whatsoever, so we really couldn't do anything about this. One of the
nice things about the switch to the DWARF debug format was that it did
record inlining instances in a useful way. But there were bugs in
gcc's debug output that we had to fix to get this working correctly,
and then we had to implement the code that used it in gdb and the
Xcode debugger. We did for Leopard based Xcode tools.
Jim
On Jul 11, 2007, at 1:57 PM, David Harper wrote:
Hi,
Why does the Xcode debugger insist on making me step into C utility
functions? For example, if a line in my code contains the function
NSMakeRange(x,y), stepping over the line forces me to step into a
file called NSRange.h which contains some methods that return
FOUNDATION_STATIC_INLINE types...
_______________________________________________
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
_______________________________________________
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