On Nov 25, 2012, at 19:47 , Stephen Kay < email@hidden> wrote: I've got an old Carbon CodeWarrior application that I've been porting to
Xcode. I've managed to take it from Xcode 2.5 on 10.4.11 up to (now) Xcode
3.2 on 10.6.8.
3.2.6? 3.2.5? An earlier 3.2? Building against the 10.4u SDK. I've made the changes to the
symbolic links in /Developer/usr/bin and /usr/bin so it compiles with GCC
4.0.
Xcode shouldn't be using anything in /usr/bin, unless you have scripts that force access to tools in that location. Hacking links in /Developer isn't supported, of course, though I wouldn't *expect* that to be the cause of your problem (unless you've inadvertently pointed Xcode to a different version of gdb). Everything compiles and builds - but I can't figure out how to make the
debugger in Xcode 3.2 work. I see that the debugging interfaces have change
quite a bit, so I likely don't yet understand what's going on. I was able to
debug fully in Xcode 2.5, and 3.0 (the little bit I played with that
version).
But when I add a breakpoint in my code in Xcode 3.2 (in the main project,
not in a shlib for example), it immediately turns yellow with a blue
outline. In the breakpoints window, the breakpoint shows up in a light
greyish font, and under the checkmark column, it has a minus sign. If I
click on this to try to make it become a checkmark, it immediately goes back
to the minus sign.
There can be situations where Xcode doesn't know how to resolve breakpoints at the time you set them, but needs to wait until the app is actually loaded for running. Did you look at the breakpoints after the app was running? The main "Activate/Deactivate Breakpoints" button is turned on (pressed in
and a dark gray color), Build and Debug is shown next to it - but none of my
breakpoints work. Any ideas what I'm doing wrong?
My guess is that Xcode is unable to find all of the debugging information it needs to resolve breakpoints. It's possible that this is a result of modifying /Developer, but more likely it's an issue with build settings.
For example, at some point, the default/recommended debug information format changed from STABS to DWARF. Maybe you need to change to DWARF. Or perhaps you have some optimization or linker setting that prevents debug info from being used.
I'd suggest you try creating a brand new template project with your current Xcode configuration, and check if breakpoints work there. If not, chances are you broke something in /Developer. If they work, chances are you need to update some build settings in the real project.
|