4 ms·
Could you use this as a malloc/free replacement or is it missing something?
by joelthelion 9y ago
Could you use this as a malloc/free replacement or is it missing something?
- alvil 9y ago+1 for this
- exikyut 9y agoSee the other comments here. It's overly simplistic, so not particularly efficient.
- masklinn 9y agoMore importantly, it's implemented in terms of malloc in the first place: > In this repository, that memory is supplied by malloc
- sitkack 9y agoMaybe one could make a LD_PRELOAD shim to re-export malloc from this lib. https://github.com/ice799/malloc_wrap https://github.com/ice799/malloc_wrap
- masklinn 9y agoAside from not being a good allocator, it's implemented on top of an existing malloc so it doesn't actually work.
- apenwarr 9y agoRemoving the calls to existing malloc on an embedded system would be trivial. Just point it at a predefined RAM area instead. It uses malloc only so you can play with it on a full featured OS, not because they left something out.