This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/21198] malloc, free, _start, _exit etc should automatically zero memory
- From: "infinity0 at pwned dot gg" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 24 Feb 2017 00:32:45 +0000
- Subject: [Bug libc/21198] malloc, free, _start, _exit etc should automatically zero memory
- Auto-submitted: auto-generated
- References: <bug-21198-131@http.sourceware.org/bugzilla/>
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.