Re: ZeroLink unknown symbol __ZTv0_n12_NSoD0Ev
Re: ZeroLink unknown symbol __ZTv0_n12_NSoD0Ev
- Subject: Re: ZeroLink unknown symbol __ZTv0_n12_NSoD0Ev
- From: Chris Espinosa <email@hidden>
- Date: Wed, 3 Nov 2004 11:37:46 -0800
Let's step back a bit from the usefulness of c++filt and go back to the
original problem, which was that when using ZeroLink, the app crashed
on launch, emitting a cryptic error message.
ZeroLink saves time by not linking your application. That means that
any link errors are not caught at build time, but at run time. You may
catch them soon, you may catch them later, you may not run in to them
for quite a while. That's the tradeoff you're making: speed over
accuracy, and it's most useful when you are making small changes to
individual methods or functions. It's a lot less useful when you're
making more significant changes.
I recommend doing a Deployment (non-zero-link) build whenever you
change an #include or add or remove frameworks or link libraries. That
ensures the linker is run and that linkage errors are caught at build
time -- at which time you get more sensible error messages (because
Xcode passes them through c++filt for you).
When your application builds, links, and runs in Deployment build
style, then you can go back to Development for bug fixing and minor
changes, to get the benefit of faster turnaround.
Chris
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