🚀 go-pugleaf

Even Microsoft advises against this chicanery (for those with VC6 search
on LNK4096). I doubt that the Unix community would sanction this type of
thing either (and I don't know if Unix environments even let you do it).

Suppose, for example, that you execute:

	void* ptr = malloc(42); // malloc bound to libc #1

and subsequently do

	free( ptr );		// free bound to libc #2

You are hosed, well and truely. Similar _opportunities_, somewhat
disguised, occur with tempnam/free and strdup/free.

Cheers, John.

Arthur Gold wrote:
> 
> Perhaps someone can help me here.
> 
> I have a need, within a shared object, to have multiple instances of
> libc in my address space (this has to do with tracing library access),