Re: libgmalloc without DYLD_FORCE_FLAT_NAMESPACE?!
Re: libgmalloc without DYLD_FORCE_FLAT_NAMESPACE?!
- Subject: Re: libgmalloc without DYLD_FORCE_FLAT_NAMESPACE?!
- From: Jim Ingham <email@hidden>
- Date: Fri, 3 Dec 2004 10:19:25 -0800
The point of two level namespaces is that code continues to bind to the
version of the symbol that it originally linked to (including the
shared library it came from) even if a symbol of the same name shows up
from another shared library load. But libgmalloc works by overriding
the malloc routines for all the code that uses malloc, so it is in
direct contradiction to the two-level namespace idea. It won't work
without flat namespaces.
Filing a bug saying that you can't use the libgmalloc functionality
because it requires flat namespaces is certainly a useful thing to do -
bugs like this are votes for where we should spend our resources, among
other things. But the solution will more likely be some other way to
provide the functionality, because the whole DYLD_INSERT_LIBRARIES
trick really doesn't work in the face of two-level namespaces.
Jim
On Dec 2, 2004, at 11:55 PM, Fazekas, Miklós wrote:
Is there any chanche of using libgmalloc wihtout the
DYLD_FORCE_FLAT_NAMESPACE?!
Our app is not able to run with DYLD_FORCE_FLAT_NAMESPACE, because of
multiple defined symbols errors.
Shall i file a radar bug?!
Regards,
Miklós
_______________________________________________
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
_______________________________________________
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