CODEWITHSUNDEEP
xcodeiosdebuggingxcode4breakpoints
Kalle
Kalle

Reputation: 13346

Xcode breakpoint triggers despite wrapping if case being false

Hard to put in words, so here is an screen of this in action: enter image description here

As the text says, it "stopped at breakpoint". The problem is, that if case is false. It shouldn't break, since the breakpoint is within the if case.

I tried putting the int a = 1; and a = 2 around the BriefLog (which is a NSLog style macro) as sometimes it gets confused about lines, but no luck. Any idea what's up with this? Making debugging really hard cause this method is called quite a lot. :(

Upvotes: 0

Views: 168

Answers (2)

Warren Burton
Warren Burton

Reputation: 17381

Try using LLVM2 rather than LLVM GCC.

If your project came from XCode3 especially your compiler may be set at the latter.

The debugger in LLVM GCC code can have a 'personality'.

LLVM2 has a fussier compiler but it's a good thing and the debugging seems to be a lot more stable especially if you use LLDB with OS X projects.

Less non-visited breakpoints and odd non-workingness.

Upvotes: 1

JustSid
JustSid

Reputation: 25318

Its Xcode 4's fault. Debugging of ObjC code is just like playing Poker at a pro table without knowing the rules. File a bug and hope that Xcode 4.1 comes soon and fixes it.

Upvotes: 0

Related Questions