PAGESTUFF(1) General Commands Manual PAGESTUFF(1)NAME
pagestuff - Mach-O file page analysis tool
SYNOPSIS
pagestuff file [-a] [-p] [pagenumber...]
DESCRIPTION
pagestuff displays information about the specified logical pages of a file conforming to the Mach-O executable format. For each specified
page of code, symbols (function and static data structure names) are displayed. If no pages are specified, symbols for all pages in the
__TEXT, __text section are displayed.
The options to pagestuff(1) are:
-a Displays all pages. All other arguments are ignored.
-p Print a list of the sections of the specified Mach-O file, with offsets and lengths. All other arguments are ignored. Note that
the size(1) tool given arguments "-m -l -x" displays a much more concise listing.
SEE ALSO Mach-O(5), size(1)Apple Computer, Inc. January 3, 2001 PAGESTUFF(1)
Check Out this Related Man Page
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)
What is the point of this? Whenever I close my shell it appends to the history file without adding this. I have never seen it overwrite my history file.
# When the shell exits, append to the history file instead of overwriting it
shopt -s histappend (3 Replies)
Greetings,
I'm trying to delete a file with a weird name from within Terminal on a Mac.
It's a very old file (1992) with null characters in the name: ââWord FinderÂŽ Plusâ˘.
Here are some examples of what I've tried:
12FX009:5 dpontius$ ls
ââWord FinderÂŽ Plusâ˘
12FX009:5 dpontius$ rm... (29 Replies)