[Vladimir Marangozov] > ... > In order to pave the way for alternatives to libc's malloc, we must > propose a clean solution. Hence it would be good to collect as much > opinions/reactions on the subject as possible and settle on an > interface which would be convenient for everybody. I can't imagine a rational *objection* to cleaning this stuff up. BTW, at work we bumped into a horrible problem with malloc under Linux: Linux "overcommits", meaning that malloc may return success, yet subsequent reference to the malloc'ed memory may segfault! Absolutely sucks, and the Linux developers aren't inclined to fix it (they made an analogy to overbooking plane flights -- even MS wouldn't be so lame <wink>). This showed up on a "small platform" project, where swap space was so small as to be essentially not there. For that and a gazillion other reasons, I (like you) would be much happier if it were easy to plug in a malloc replacement, and I agree that requires reworking of the current code. just-do-it-ly y'rs - tim
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4