Re: strange debugger behavior
Re: strange debugger behavior
- Subject: Re: strange debugger behavior
- From: Tommy Nordgren <email@hidden>
- Date: Wed, 11 Jul 2007 23:22:10 +0200
On 11 jul 2007, at 22.57, 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...
_______________________________________________
Here is the full definition form NSRange.h
FOUNDATION_STATIC_INLINE NSRange NSMakeRange(unsigned int loc,
unsigned int len) {
NSRange r;
r.location = loc;
r.length = len;
return r;
}
and from NSObjCRunTime.h:
#if !defined(FOUNDATION_STATIC_INLINE)
#define FOUNDATION_STATIC_INLINE static __inline__
#endif
Because the function is inline, it's code is embedded directly in
the calling function. There is no function call to step over in the
generated code.
------------------------------------------------------
"Home is not where you are born, but where your heart finds peace" -
Tommy Nordgren, "The dying old crone"
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