Talk:Sbrk

Technical tag

The article doesn't seem more technical than is required for describing unix system calls. Can anyone give justify the "too technical" tag? Spa c explosion ^[talk] 23:43, 15 November 2010 (UTC)[reply]

Well, at least the error code part is unnecessary and also inaccurate. In different Unix flavors, there can be different error codes - for example, in Solaris, errno might be se to EAGAIN if not enough memory is currently available. 82.181.71.84 (talk) 01:35, 11 December 2010 (UTC)[reply]

Rewrite

I've marked a request for the article to be rewritten because of a few flaws. The language used for instance is appallingly simplistic, like random information has been appended over time. I'd also like to see some detail of the actual brk system call presented (I can only find a small amount of information on the man page) and the difference between the "wrapper" function and the system call itself defined clearly. Lastly, each system with differing details of the routine should be listed. — Preceding unsigned comment added by 124.185.12.106 (talk) 10:59, 19 February 2012 (UTC)[reply]

Legacy

This article should discuss how use of these functions is discouraged (e.g. because may conflict with internal use by the c library, instead recommending malloc) and even deprecated (e.g. removed from posix, e.g. unnecessary with mmap).. Cesiumfrog (talk) 04:42, 5 March 2020 (UTC)[reply]

Confusing use of "data segment"

Brk changes boundary of end of heap and otherwise unassigned free virtual memory, not the size of the segment used for global/static initialized data. 178.165.169.249 (talk) 09:55, 30 October 2022 (UTC)[reply]