change data segment size NAME brk, sbrk - change data segment size LIBRARY Standard C library ( libc , -lc ) SYNOPSIS #include <u...change data segment size NAME brk, sbrk - change data segment size LIBRARY Standard C library ( libc , -lc ) SYNOPSIS #include <u......in this scenario. SEE ALSO brk (2), getpagesize (2), getrlimit (2), mlock (2), mmap (2), sbrk (2), malloc (3), realloc (3) Your favorite text book on operating systems for more …...bytes, and is rounded down to the system page size. This limit affects calls to brk (2), sbrk (2), and (since Linux 4.7) mmap (2), which fail with the error ENOMEM upon encounte…...bytes, and is rounded down to the system page size. This limit affects calls to brk (2), sbrk (2), and (since Linux 4.7) mmap (2), which fail with the error ENOMEM upon encounte…...bytes, and is rounded down to the system page size. This limit affects calls to brk (2), sbrk (2), and (since Linux 4.7) mmap (2), which fail with the error ENOMEM upon encounte…...bytes, and is rounded down to the system page size. This limit affects calls to brk (2), sbrk (2), and (since Linux 4.7) mmap (2), which fail with the error ENOMEM upon encounte…...bytes, and is rounded down to the system page size. This limit affects calls to brk (2), sbrk (2), and (since Linux 4.7) mmap (2), which fail with the error ENOMEM upon encounte…...TURE or both. If MCL_FUTURE has been specified, then a later system call (e.g., mmap (2), sbrk (2), malloc (3)), may fail if it would cause the number of locked bytes to exceed …...TURE or both. If MCL_FUTURE has been specified, then a later system call (e.g., mmap (2), sbrk (2), malloc (3)), may fail if it would cause the number of locked bytes to exceed …...TURE or both. If MCL_FUTURE has been specified, then a later system call (e.g., mmap (2), sbrk (2), malloc (3)), may fail if it would cause the number of locked bytes to exceed …...TURE or both. If MCL_FUTURE has been specified, then a later system call (e.g., mmap (2), sbrk (2), malloc (3)), may fail if it would cause the number of locked bytes to exceed …...TURE or both. If MCL_FUTURE has been specified, then a later system call (e.g., mmap (2), sbrk (2), malloc (3)), may fail if it would cause the number of locked bytes to exceed …