Hi, I'm needing a malloc() replacement that is highly efficient, fast and portable. So far, so good - the Hoard allocator seems to meet these requirements very nicely.
I also need it to be secure, where "secure" is going to depend a bit on what's available. That's where it gets nasty. At the very least, I really need the ability to lock the memory against swapping and (where supported) change the read/write permissions on a malloc()ed block. Now, I've no problems adding the locks/permissions code to my own application, but to do that I need the size of a malloc()ed block. Does Hoard have an API or otherwise expose that information? If not, are there any quick-n-dirty ways of me (or anyone else!) building such capabilities into the Hoard allocator? For that matter, are these actually going to be useful to provide security? Has anyone else run into a situation where they needed to be able to control access to a memory block? If so, what sort of methods proved useful? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/hoard/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
