end(3) Library Functions Manual end(3)Name
end, etext, edata - last locations in program
Syntax
extern end;
extern etext;
extern edata;
extern eprol;
Description
These names refer neither to routines nor to locations with interesting contents. The address of is the first address above the program
text, above the initialized data region, and is the first instruction of the user's program that follows the runtime startup routine.
When execution begins, the program break coincides with but it is reset by the routines standard input/output the profile (-p) option of
and so forth. The current value of the program break is reliably returned by sbrk(0). For further information, see
See Alsocc(1), brk(2), malloc(3), stdio(3s)
RISC end(3)
Check Out this Related Man Page
end(3C) Standard C Library Functions end(3C)NAME
end, _end, etext, _etext, edata, _edata - last locations in program
SYNOPSIS
extern int _etext;
extern int _edata;
extern int _end;
DESCRIPTION
These names refer neither to routines nor to locations with interesting contents; only their addresses are meaningful.
_etext The address of _etext is the first location after the program text.
_edata The address of _edata is the first location after the initialized data region.
_end The address of _end is the first location after the uninitialized data region.
USAGE
When execution begins, the program break (the first location beyond the data) coincides with _end, but the program break may be reset by
the brk(2), malloc(3C), and the standard input/output library (see stdio(3C)), functions by the profile (-p) option of cc(1B), and so on.
Thus, the current value of the program break should be determined by sbrk ((char *)0).
References to end, etext, and edata, without a preceding underscore will be aliased to the associated symbol that begins with the under-
score.
SEE ALSO cc(1B), brk(2), malloc(3C), stdio(3C)SunOS 5.10 1 Sep 2003 end(3C)
I have 2 Dell Poweredge 1950 servers running . I have been having intermittent performance issues with the NIC cards on one of them. The two servers are identical and are running the same operating system. The server that has the issue is on the DMZ on a a static IP and is hosting a website. ... (0 Replies)