nlist man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

nlist_ia(3C)							  nlist_ia(3C)

NAME
       nlist_ia:  nlist(), nlist64() - get entries from name list on Integrity
       systems

SYNOPSIS
       Command: [flag]... [library]...

   Remarks
       The use of symbol table type and value information is  inherently  non‐
       portable.   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 Itanium-based systems.	For and on PA-
       RISC systems, see nlist_pa(3C).

DESCRIPTION
       and have basically the same functionality and they can process  SOM  or
       ELF  files.   The  structure is the same as and is used for source code
       compatibility.

       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	struc‐
       ture.   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.  If the file searched is an
       ELF file, the section index is also inserted.  For SOM files, the  sub‐
       space  index  is	 inserted.   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 exam‐
       ining 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.	  How‐
       ever,  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
Integrity Systems Only						  nlist_ia(3C)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net