Lines Matching refs:segment

132 A process' virtual address space is divided into segments.  A segment is
139 The @dfn{text segment} contains a program's instructions and literals and
144 The @dfn{data segment} is working storage for the program.  It can be
150 The @dfn{stack segment} contains a program stack.  It grows as the stack
1447 space's data segment).
2894 @code{brk} sets the high end of the calling process' data segment to
2897 The address of the end of a segment is defined to be the address of the
2898 last byte in the segment plus 1.
2901 the data segment.  (This is considered success, by the way.)
2903 The function fails if it would cause the data segment to overlap another
2904 segment or exceed the process' data storage limit (@pxref{Limits on
2908 and the stack are in the same segment.  Data storage allocation grows
2909 upward from the bottom of the segment while the stack grows downward
2910 toward it from the top of the segment and the curtain between them is
2919 The request would cause the data segment to overlap another segment or
2925 @c segment, whether it succeeds or fails.  The GNU C library Brk determines
2937 end of the data segment as an offset @var{delta} from the current end
2939 the data segment instead of zero.
2942 of the data segment is.
3528 pages of the code, data and stack segment, as well as shared libraries,