Re: Accuracy of breakpoints
Re: Accuracy of breakpoints
- Subject: Re: Accuracy of breakpoints
- From: Jason Molenda <email@hidden>
- Date: Mon, 19 Jun 2017 23:04:33 -0700
> On Jun 19, 2017, at 4:07 PM, Steve Mills <email@hidden> wrote:
>
>> On Jun 19, 2017, at 10:20, Alex Zavatone <email@hidden> wrote:
>>
>> On a daily basis, I see my iOS project breakpoints jumping up a line or down
>> a line.
>>
>> I remember reading something somewhere about how there is a setting for
>> “breakpoint accuracy”. I filed it in my brain for use later and forgot
>> about it.
>
> I've never heard of such a setting. The only time I see this happen is when
> you synch your source with the server. Xcode doesn't know how to move the
> break points to the line that they used to be on, now that there are more or
> fewer lines before it.
If you put a breakpoint on a source line that doesn't have any code generated,
it'll be migrated down to the next source line that does have code. Put a
breakpoint on a comment line and you'll see this happening. If optimization is
enabled, source lines have a loose correspondence to the generated assembly
instructions so stepping and breakpoints can be odd. Putting a breakpoint on a
non-statement line, like an opening brace or closing brace of a block of code,
can lead to unexpected results.
Source code being modified outside the view of Xcode could result in
breakpoints not being set where you intended, as Steve suggests.
I don't know of any breakpoint accuracy setting, fwiw.
If you're in doubt, do a clean build of your program (clean + build), and
you're not building with optimization enabled, I'd expect breakpoints to work
predictably.
_______________________________________________
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