| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | 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.
| Rich Felker | 2014-01-02 | 1 | -3/+3 |
| * | cleanup various minor issues reported by nsz•••the changes to syscall_ret are mostly no-ops in the generated code,
just cleanup of type issues and removal of some implementation-defined
behavior. the one exception is the change in the comparison value,
which is fixed so that 0xf...f000 (which in principle could be a valid
return value for mmap, although probably never in reality) is not
treated as an error return.
| Rich Felker | 2011-09-26 | 1 | -2/+2 |
| * | fix brk/sbrk behavior to match the real legacy functions | Rich Felker | 2011-05-22 | 1 | -1/+3 |
| * | global cleanup to use the new syscall interface | Rich Felker | 2011-03-20 | 1 | -1/+1 |
| * | initial check-in, version 0.5.0 | Rich Felker | 2011-02-12 | 1 | -0/+7 |
