DWARF format and stripping
DWARF format and stripping
- Subject: DWARF format and stripping
- From: Greg Hurrell <email@hidden>
- Date: Wed, 31 May 2006 21:27:58 +0200
In my projects I use a include a shell script build phase that
performs stripping. This allows me greater control over the stripping
of my shipped product. When trying to use the dwarf-with-dsym
DEBUG_INFORMATION_FORMAT I get errors in my build like this:
[compilation, linking phases...]
[stripping shell script...]
GenerateDSYMFile
cd /Users/ghurrell/work/Test/trunk
/usr/bin/dsymutil -o /Users/ghurrell/work/build/Release/
TestRunner.dSYM /Users/ghurrell/work/build/Release/TestRunner
ERROR: No debug map or DWARF data was found to link.
It's obvious that this is occurring because dsymutil depends on
something that's getting stripped previously. Is there any way to get
around this ordering problem? What are my options?
1. Forget about using dwarf-with-dsym?
2. Forget about using a shell-script stripping phase?
3. Move to a kludgey aggregate target model in which I have one
target for my product, and another target (an aggregate) which
depends on the built product and then performs stripping on it?
This latter workaround looks a bit kludgey to me because it will
double the number of targets I have in my projects, and the variables
and environments that get passed to my shell script won't be the same
as those that get passed during the product's shell-script phases,
which means I will have to hard-code more of the values and it will
make the stripping more fragile.
And one final question...
4. Does anyone have any pointers on what kind of workflow is
necessary to interpret user-submitted crash reports when using dwarf-
with-dsym? I know how to use atos on an unstripped binary that
contains STABS-format debugging information. But I have no idea at
all what the paradigm is with dsym files. The release notes and the
man pages only talk about DWARF at build-time; they don't really say
much about what you have to do working with it latter on in the
picture...
Cheers,
Greg
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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