|author||Rich Felker <firstname.lastname@example.org>||2014-01-02 17:03:34 -0500|
|committer||Rich Felker <email@example.com>||2014-01-02 17:03:34 -0500|
disable sbrk for all values of increment except 0
use of sbrk is never safe; it conflicts with malloc, and malloc may be used internally by the implementation basically anywhere. prior to this change, applications attempting to use sbrk to do their own heap management simply caused untrackable memory corruption; now, they will fail with ENOMEM allowing the errors to be fixed. sbrk(0) is still permitted as a way to get the current brk; some misguided applications use this as a measurement of their memory usage or for other related purposes, and such usage is harmless. eventually sbrk may be re-added if/when malloc is changed to avoid using the brk by using mmap for all allocations.
Diffstat (limited to 'VERSION')
0 files changed, 0 insertions, 0 deletions