Re: Inline functions get debugger confused about source files
Re: Inline functions get debugger confused about source files
- Subject: Re: Inline functions get debugger confused about source files
- From: Alastair Houghton <email@hidden>
- Date: Wed, 18 Jul 2007 13:30:26 +0100
On 18 Jul 2007, at 01:17, Rua Haszard Morris wrote:
I see that issue all the time, especially with C++/classes code,
where you will step into a header file for certain breakpoints, and
my workaround is to find a way to debug using a breakpoint in a
different place :(
For what it's worth, not every such instance is an occurrence of the
bug that has been mentioned. At least, I don't think it is. A lot
of the time the problem is merely that the inline function happens to
be in a header file and so that's where you go when you step into
it. I think the bug that was being reported was that the debugger
didn't return to the original function when the inline function's
execution was complete.
Also, setting breakpoints on inline functions in header files is
clearly never going to be as straightforward as setting them
elsewhere, because the function's code can appear in many places in
your program.
If turning off inlining doesn't solve the problem for you, you might
consider moving code out of your header files into a separate source
file, at least for the debug version of your code.
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
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