symbol resolution

[Eli Boling]

> But the usual symbol resolution rules don't always apply to shared objects;
> apart from things like -B symbolic which specifically override them,
> the normal behavior of dlopen does not make symbols in the loaded object
> available to subsequently loaded libraries.  This means that if a
> particular typeinfo is defined in multiple dynamically loaded objects but
> not in the main executable, the definitions will not be combined properly,
> and comparison will produce false negatives.

Yep.  This is a problem that we've long had, and we've had no reasonable way to
deal with it outside of doing name comparisons.  We've never been able to
resolve the issue to our satisfaction.  The ELF linkage model might provide
relocations that will help, but nothing will help under Win32/Win64, so far as
I know.

-Eli