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: Chris Hanson <email@hidden>
- Date: Wed, 14 Aug 2013 23:12:15 -0700
On Aug 14, 2013, at 8:59 AM, Jens Alfke <email@hidden> wrote:
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.
Xcode doesn’t currently have separate “backstop” values for its build settings based on configuration; configurations are treated as a project-level concept.
Xcode’s project/target templates do contain sensible overrides of the backstop values for things like optimization, whether to build for all or just the active architecture (the architecture of the current run destination), and so on.
-- Chris
|
_______________________________________________
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