Re: Xcode Debugger Showing Wrong File
Re: Xcode Debugger Showing Wrong File
- Subject: Re: Xcode Debugger Showing Wrong File
- From: Steve Sisak <email@hidden>
- Date: Thu, 6 Dec 2007 20:10:57 -0500
At 4:32 PM -0800 12/6/07, Jim Ingham wrote:
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...
I'll give 2.5 a try and report back -- I'm running 2.4.1 at the
moment (trying not to change _too_ many variables at once).
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.
Right. Also, I realized after hitting "send" on the last message,
that I can just use 4.0 for the debug builds and do a one-off if I
have to debug something on < 10.3.9.
Having a .dSYM saved for a given release that went out the door seems
like a good thing.
Thanks a lot for the explanations.
-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