Re: libgmalloc without DYLD_FORCE_FLAT_NAMESPACE?!
Re: libgmalloc without DYLD_FORCE_FLAT_NAMESPACE?!
- Subject: Re: libgmalloc without DYLD_FORCE_FLAT_NAMESPACE?!
- From: boga <email@hidden>
- Date: Fri, 3 Dec 2004 22:54:53 +0100
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.
What about writing a "libSystem.B_libgmalloc" that would delegate every
call to libSystem except the malloc's?
Is it possible?!
Then i could get libgmalloc work by using the DYLD_IMAGE_SUFFIX.
By the way we could use libgmalloc until we've converted our app to
MachO...
(the dyld flat namespace doesn't affect CFM programs)
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