This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/21198] malloc, free, _start, _exit etc should automatically zero memory


https://sourceware.org/bugzilla/show_bug.cgi?id=21198

--- Comment #1 from infinity0 at pwned dot gg ---
Someone told me about MALLOC_PERTURB_ (man mallopt) and that is really nice
already, however I think it would further benefit to have an actual build-time
option that results in the behaviour being compiled *into* the resulting
binary, as opposed to being set by the user. (Also the existence of
MALLOC_PERTURB_ could be much more widely advertised.)

The developers can test this and make sure their program doesn't break; most
users have less expertise to do this at run-time. Later, when 99% of programs
work (hopefully this is already the case today) the default can be switched to
ON.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]