Re: ZeroLink unknown symbol __ZTv0_n12_NSoD0Ev
Re: ZeroLink unknown symbol __ZTv0_n12_NSoD0Ev
- Subject: Re: ZeroLink unknown symbol __ZTv0_n12_NSoD0Ev
- From: Andy Wiese <email@hidden>
- Date: Wed, 3 Nov 2004 14:38:07 -0600
On Nov 3, 2004, at 1:37 PM, Chris Espinosa wrote:
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 _______________________________________________
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
I have not been able to seriously debug this problem yet, but I am
perplexed by the fact that with ZeroLink turned off, I can build and
debug just fine, with no link errors. Doesn't that imply that ld is
able to resolve some reference that ZeroLink does not? In this case it
is an ostream dtor, and there are fairly few of those used in this
current test app so I hope I can narrow it down. Maybe I need to
declare an explicit destructor for some ostream class and that will fix
it. I don't want to lose ZeroLink, so I'd better figure it out.
_______________________________________________
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