diff options
| author |   Samuel Thibault <samuel.thibault@ens-lyon.org> | 2020-08-05 23:48:58 +0200 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2020-08-05 23:52:04 +0200 |
| commit | 8c6beab4e1c03ac57150241015486e3f497c17cc (patch) | |
| tree | 621433d7b20cfaace9183cb364e50dc686ac8623 /scripts/build-many-glibcs.py | |
| parent | hurd: Implement basic sched_get/setscheduler (diff) | |
| download | glibc-8c6beab4e1c03ac57150241015486e3f497c17cc.tar.xz glibc-8c6beab4e1c03ac57150241015486e3f497c17cc.zip | |
hurd: Rework sbrk
Making the brk start exactly at the end of the main application binary was
requiring to get it through the _end symbol, which does not work any more
with recent toolchains, and actually produces in libc.so a confusing
external _end symbol that produces odd results, see
https://sourceware.org/bugzilla/show_bug.cgi?id=23499
Trying to do so is quite outdated anyway with the tendency for address
randomization.
Using _end was also allowing to include the main binary data within
the RLIMIT_DATA, but this also seems outdated with dynamic library
loading, and nowadays' memory consumption via malloc and mmap rather than
statically-allocated data.
This adds a BRK_START macro in <vm_param.h> that just tells where we
want to start the brk, and thus removes the _end symbol.
* sysdeps/mach/hurd/i386/vm_param.h: New file.
* sysdeps/mach/hurd/brk.c: Use BRK_START as brk start instead of _end.
Also ignore __data_start.
* hurd/Versions: Remove _end symbol.
* sysdeps/mach/hurd/i386/libc.abilist: Remove _end symbol.
Diffstat (limited to 'scripts/build-many-glibcs.py')
0 files changed, 0 insertions, 0 deletions