Re: Xcode Debugger Showing Wrong File
Re: Xcode Debugger Showing Wrong File
- Subject: Re: Xcode Debugger Showing Wrong File
- From: Jim Ingham <email@hidden>
- Date: Thu, 6 Dec 2007 16:32:11 -0800
On Dec 6, 2007, at 4:05 PM, Steve Sisak wrote:
At 3:48 PM -0800 12/6/07, Jim Ingham wrote:
You're using gcc-3.3 for the ppc side of this target. If you have
to use gcc-3.3 for some reason, then you have to use stabs, the
DWARF support only started with the 4.0 compiler on Mac OS X.
OK, that makes sense.
You should have gotten a valid dSYM for the x86 side of the binary,
but the PPC side of the dSYM is going to be empty, and you'll have
to use the stabs in the ppc side of the binary. Or, if you don't
actually need to use 3.3 on PPC, you can switch to 4.0 and you'll
get DWARF for both architectures.
We still have customers running 10.2.8 on old machines, although I'm
considering requiring 10.3.9 after this release.
Is there any way to use DWARF for i386 and stabs for PPC?
This should pretty much work already.
The build you sent the log for already has all the right bits in the
ppc & x86 binaries. The only potential hangup is what happens when
you run dsymutil on the Universal - mixed stabs & dwarf binaries. It
should find the dwarf "debug map" in the x86 fork of your Universal
binary, and make a dSYM from that, ignoring the empty ppc side. But,
IIRC, the original version of dsymutil would error out if there was a
binary - or fork of a Universal binary - that has no dwarf. The Xcode
3.0 version just gives a warning and continues to the other forks. I
know this fix went into the 3.0 dsymutil, I don't remember whether it
is in the 2.5 version... Anyway for older versions of Xcode you may
need to make the dsym on the x86 binary before doing the lipo.
Note also, you don't have to make a dSYM file for ordinary
development. If you choose the DWARF rather than the DWARF with dSYM
option, then we leave the debug info in the .o files - which makes
linking faster. Doing this will for sure work even though you use
gcc-3.3 for the ppc side. You only need to make the dSYM file if you
want to store your debug information - either so you can give a debug
build to a colleague, or so you can come back and symbolicate a
released build after the release. But for day-to-day iterative
development, you can use "dwarf", rather than dwarf-with-dsym.
Jim
-Steve
_______________________________________________
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