On Jun 12, 2006, at 9:52 PM, Markian Hlynka wrote: On Jun 10, 2006, at 10:08, Steven Fisher wrote:
On Jun 10, 2006, at 9:00 AM, Steven Fisher wrote:
On Jun 10, 2006, at 8:38 AM, Jonathon Mah wrote:
Is optimization disabled? What build settings are you using?
I'm using the default Debug settings, with just a few changes like include paths since quite a few of the source files are in parent folders. Optimization was on by default, but turning it off doesn't seem to have helped.
A light goes on! Yes, the directory settings seem to be the problem. If I put the xcode project at the root so that none of the paths contain ../, it all works.
An alternative fix may be to use "project relative" in the path type. or maybe it was "absolute". I remember an earlier problem that was very similar to this, where having ../ paths royally messed things up. I don't recall exactly what it was, though. I thought it might have been the debugger, but whatever it was got fixed ages ago, as I've been happily using the debugger for quite a while now... Anyone else remember what I'm talking about?
There was a problem in Xcode 2.2 (the WWDC 2005, Universal-migration release) where ../ style relative references broke dependency analysis, Touch, Compile, Show Assembly Code, and other functions, but full clean builds worked. That was fixed in 2.2.1. I can't find any specific bugs against such references in debugging, but it's plausible that some of the "it won't stop at my breakpoint" reports could be due to something like this. We'll try to isolate.
Chris |