[interfacekit] Re: Allocator blues

>You won't see any calls from the BBlockCache to your malloc/free 
routines,
>since the Be BBlockCache is already compiled & linked, and it will 
directly 
>call the routines in libroot.so. If you add your own malloc/free code, 
only 
>your program will call them. 

        Yes, I came to this realization the other day.  Silly me....  At least 
it was educational :)

>But why are you doing all this at all? Simply write a test program, to 
>see how BBlockCache works, and then do your on implementation of it.

        Because it's not obvious how it works, even using a test program.  If 
you request a hideously large amount of memory (I tried 1-4 GB) from a 
BBlockCache (which I do as part of the test suite I wrote), it doesn't 
seem to work at all the same way as when you make the same request of 
malloc() (which is what my implementation tries to do - very time 
consuming :)  However, the BeBook docs say that in fact BBlockCache does 
use malloc(). 
        Dammit why did they have to try and be smart :)  I'd be done with this 
class ages ago....

        Graham

Other related posts: