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: Jerry Krinock <email@hidden>
- Date: Wed, 14 Aug 2013 10:20:19 -0700
On 2013 Aug 14, at 08:59, Jens Alfke <email@hidden> wrote:
> 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 see the same thing, Xcode 4.6.3, in the Build Settings, rightmost column, "OS X Default" is set to "Fastest, Smallest" for both Release and Debug. As far as I know, there is no way to change settings at the "OS X Default" level.
I wanted to see if this was possibly causing the issue I asked about a few days ago [1], which is that when I try to read registers I get "Couldn't materialize struct" and "13 registers were unavailable". Apparently it is not, because in my current project, Optimization Level > Debug is overridden to "None" at the Target level, for all relevant targets.
I set it to "None" at the Project level.
Jerry
[1] http://prod.lists.apple.com/archives/xcode-users/2013/Aug/msg00035.html
_______________________________________________
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