nlist_pa(4) Kernel Interfaces Manual nlist_pa(4)NAME
nlist_pa: nlist, nlist64 - structure formats for PA-RISC systems
SYNOPSIS
Remarks
The exact content of the structures defined below can be best found by examining It varies somewhat between various HP-UX implementations.
This manpage describes on PA-RISC systems. For on Integrity systems, see nlist_ia(4).
DESCRIPTION
and can be used to extract information from the symbol table in an object file (see nlist(3C)). They are basically the same tool except
can only process SOM files on a PA-RISC 32-bit system while can process SOM and ELF files on either a PA-RISC 32-bit or 64-bit system.
Since symbol tables are machine dependent (as defined in each implementation's copy of a header file, is defined to encapsulate the differ-
ences.
The nlist function, either or when used with the corresponding nlist structure, can be used to extract certain information about selected
symbols in the symbol table. The data associated with each symbol is machine specific, thus only the name and position of the field in the
function is standardized by HP-UX. The rest of the structure includes at least the value and type of the symbol. The names and meanings
of all fields not standardized will change no more than necessary.
SEE ALSO nlist(3C), a.out(4).
PA-RISC Systems Onlynlist_pa(4)
Check Out this Related Man Page
nlist_pa(3C)nlist_pa(3C)NAME
nlist_pa: nlist(), nlist64() - get entries from name list on PA-RISC systems
SYNOPSIS
nlist()
Command: [flag]... cfile...
nlist64()
Command: [flag]... cfile... [library]...
Remarks
The use of symbol table type and value information is inherently nonportable. The use of or should reduce the effort required to port a
program that uses such information, but complete portability across all HP-UX implementations cannot be expected.
This manpage describes and for PA-RISC systems. For and on Integrity systems, see nlist_ia(3C).
DESCRIPTION
and have basically the same functionality except that uses the structure and can process SOM or ELF files. uses the structure and can only
process SOM files.
The or function examines the name list in the executable file whose name is pointed to by file_name, and selectively extracts a list of
values and puts them in the array of structures pointed to by nl. The array of structures initially contains only the names of variables.
Once the or function has been called, the variable names are augmented with symbol information. The list is terminated by a null name,
which consists of a null string in the variable-name position of the structure. The name list of the file is searched for each variable
name. If the name is found, the symbol's type, scope, and value in the file is inserted into the name list structure. For if the file
searched is an ELF file, the section index is also inserted. For and SOM files, the subspace index is inserted. On wide-mode systems, the
symbol value is 64-bit. If the file searched is a SOM file, then the value field is zero padded. If the name is not found, the fields in
the name list structure are set to 0. The structures and are defined in the include file See a.out(4) and nlist(4) for further description
of the symbol table structure.
The file must have the organization and symbol table described for an file in a.out(4). The information is extracted from the symbol table
used by the linker, ld(1).
On machines that have such a file, this subroutine is useful for examining the system name list kept in file In this way programs can
obtain system addresses that are up to date.
RETURN VALUE
All structure fields are set to 0 if the file cannot be found or if it is not a valid object file containing a linker symbol table.
and return:
An error occurred.
Success.
WARNINGS
The header file is automatically included by for compatibility. However, including is discouraged if the only information needed from is
for use by or If is included, the line may need to follow it.
SEE ALSO ld(1), elf(3E), a.out(4), nlist(4).
STANDARDS CONFORMANCE PA-RISC Systems Onlynlist_pa(3C)