Re: Can't seem to debug with Xcode 3.2 and 10.6.8
Re: Can't seem to debug with Xcode 3.2 and 10.6.8
- Subject: Re: Can't seem to debug with Xcode 3.2 and 10.6.8
- From: Stephen Kay <email@hidden>
- Date: Mon, 26 Nov 2012 02:54:27 -0500
- Thread-topic: Can't seem to debug with Xcode 3.2 and 10.6.8
on 11/26/12 1:18 AM, Quincey Morris at email@hidden
wrote:
> 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?
Thanks for your reply.
3.2 Period. I guess that would be 3.2.0. Is there something ambiguous about
that? It's the version that installs by default with my 10.6 installer disk.
>> 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).
This is not a hack, as far as I understand it. When I first tried to compile
the code, I was told with an error that " GCC 4.2 is not compatible with the
Mac OS X 10.4 SDK "
After researching this, I saw this thread:
http://stackoverflow.com/questions/1165361/setting-gcc-4-2-as-the-default-co
mpiler-on-mac-os-x-leopard
While this talked about setting GCC 4.2 as the default compiler, for some
reason I had to go the opposite direction, and set GCC 4.0 as the default
compiler. I agree that /usr/bin was a misdirection from this thread. It only
worked after I modified /Developer/usr/bin.
If there is some other way to force my projects to use GCC 4.0, I could not
find it. But this seems to have worked.
> 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?
Yes. Same situation. The breakpoints don't activate, they never hit.
>> 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.
Well, it's already set to DWARF automatically in the project settings, I
don't know what else I would need to do to accomplish that...
> 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.
OK, thanks.
- Stephen
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Stephen Kay
Karma-Lab :: developers of KARMA
http://www.karma-lab.com
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
_______________________________________________
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