Xcode is optimizing debug builds, screwing up the debugger
Xcode is optimizing debug builds, screwing up the debugger
- Subject: Xcode is optimizing debug builds, screwing up the debugger
- From: Jens Alfke <email@hidden>
- Date: Wed, 14 Aug 2013 08:59:12 -0700
| 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.
This seems like a pretty glaring bug. And it’s apparently been around for a while, because I’ve had problems like this for a year at least. Anyone got a clue why it does this?
—Jens |
_______________________________________________
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