Re: Xcode is optimizing debug builds, screwing up the debugger
Re: Xcode is optimizing debug builds, screwing up the debugger
- Subject: Re: Xcode is optimizing debug builds, screwing up the debugger
- From: Fritz Anderson <email@hidden>
- Date: Wed, 14 Aug 2013 13:45:40 -0500
On 14 Aug 2013, at 10:59 AM, Jens Alfke < email@hidden> wrote: For quite a while I’ve been having frustrating problems with the Xcode debugger: breakpoints not being hit or stopping at the wrong line; inability to display variable values (“variable not available”), etc. But only in some projects — others work fine. I just assumed LLDB was intermittently flaky and didn’t investigate too much.
But today I ran into this again, and I dug into the target build settings and saw that the optimization level is “Fastest, smallest” (-Os). Oops, yeah, that’s going to mess up the debugger. :-P But that setting isn’t coming from the project — Xcode is defaulting to full optimization even for the Debug configuration. I changed the setting to No Optimization, and poof, the debugger problems went away.
What version? What template? I just used Xcode 4.6.2 to instantiate an iOS single-view application, and the template set -O0 at the project level for the Debug configuration.
The far-right column, "iOS Defaults," has to be a unified fallback for every setting in every configuration. I'm pretty sure those defaults know nothing about debugging — configurations don't go that deep, and a generic iOS product should be -Os.
Xcode is doing the right thing; the question is, where did that defective template (which does know about configurations) come from?
— F
|
_______________________________________________
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