Sponsored Content
Top Forums UNIX for Dummies Questions & Answers UNIX community...help your Mac brother! Post 407 by Neo on Saturday 2nd of December 2000 12:00:11 AM
Old 12-02-2000
MySQL

Interesting. Thanks for the link. I'm sure our members will enjoy looking at a UNIX/Mach/BSDLite based Mac OS.
 

3 More Discussions You Might Find Interesting

1. AIX

big brother monitoring tool - make failed

Hi, Does anyone has installed bb on a unix system ? I am trying to install bb on aix 5.3 but I have the following message: If someone can help me probably there is a tool that I need to install ? I don't have C compiler I install gcc instead and gcc++ etc ... bb:/home/bb/bb1.9g-btf/src/ $ make... (0 Replies)
Discussion started by: touny
0 Replies

2. AIX

Big Brother

Have anyone heard of "Big Brother"? This is a tool to monitor system with GUI screen and ease system administration work. It can show you whether the system have CPU more than threshold by showing a green light or red light.. You can set any checking so that it will assist to monitor and show you... (8 Replies)
Discussion started by: kwliew999
8 Replies

3. What is on Your Mind?

How Much Vacation Do You Take? | UNIX.com Community | Annual Vacation (YouTube)

Here is another simple YT video co-produced with our video partner. How Much Vacation Do You Take? | UNIX.com Community | Annual Vacation https://youtu.be/MSy553qS654 Background sound track is called "Caribbean Paradise" Sounds like something wisecracker would have played in one... (0 Replies)
Discussion started by: Neo
0 Replies
GET_END(3)						     Library Functions Manual							GET_END(3)

NAME
get_end, get_etext, get_edata - get values of UNIX link editor defined symbols SYNOPSIS
#include <mach-o/getsect.h> unsigned long get_end(); unsigned long get_etext(); unsigned long get_edata(); DESCRIPTION
These routines provide a stopgap measure to programs that use the UNIX link-editor defined symbols. Use of these routines is very strongly discouraged. The problem is that any program that is using UNIX link editor defined symbols (_end, _etext or _edata) is making assumptions that the program has the memory layout of a UNIX program. This is an incorrect assumption for a program built by the Mach-O link editor. The reason that these routines are provided is that if very minimal assumptions about the layout are used and the default format and memory layout of the Mach-O link editor is used to build the pro- gram, some things may work by using the values returned by these routines in place of the addresses of their UNIX link-editor defined sym- bols. So use at your own risk, and only if you know what your doing. Or better yet, convert the program to use the appropriate Mach or Mach-O functions. If you are trying to allocate memory use vm_allocate(2), if you are trying to find out about your address space use vm_region(2) and if you are trying to find out where your program is loaded use the dyld(3) functions. The values of the UNIX link-editor defined symbols _etext, _edata and _end are returned by the routines get_etext, get_edata, and get_end respectively. In a Mach-O file they have the following values: get_etext returns the first address after the (__TEXT,__text) section, note this my or may not be the only section in the __TEXT segment. get_edata returns the first address after the (__DATA,__data) section, note this my or may not be the last non-zero fill section in the __DATA segment. get_end returns the first address after the last segment in the executable, note a shared library may be loaded at this address. SEE ALSO
ld(1), dyld(3) Apple Computer, Inc. April 10, 1998 GET_END(3)
All times are GMT -4. The time now is 11:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy