nm displays the symbol table associated with an object, archive library of objects, or executable file. nm recognizes several different file types that may contain symbol tables:
- object files ending in .obj. These files may be Intel OMF (Object Module Format) files or COFF (Common Object File Format) files.
- library files, which normally end in .lib and contain one or more OMF or COFF files.
- Windows executable files, which normally end in .exe, that contain a symbol table compatible with those produced by PLINK86, the Microsoft Linker, the Watcom Linker, or the Borland Linker.
- A symbol table may be created from a .map file (such as those produced by Microsoft link) by using unstrip to create a symbol table compatible with PLINK86.
Note that nm does not list entry points in a DLL, unless there is a symbol table associated with it.
By default, nm lists the symbols in file in alphabetical order by name and provides the following information on each:
File or object name (if you specified
- Symbol name
- Symbol type:
Not all of these symbol types are available on all systems. For instance, not all systems support the ability to determine different segment information.
absolute symbol, global
absolute symbol, local
uninitialized data (bss), global
uninitialized data (bss), local
initialized data, global
initialized data, local
line number entry (see
no defined type, global; this is an unspecified type, compared to the undefined type U
no defined type, local; this is an unspecified type, compared to the undefined type U
section symbol, global
section symbol, local
text symbol, global
text symbol, local (static)
- Symbol value
- Symbol size, if applicable
prefixes each line with the file name or archive member name.
displays all symbols, including line number entries on systems which support them.
displays only global (external) and static symbols.
displays full output. This is the default, since this implementation does not suppress any output.
displays only global symbols.
is equivalent to
displays output in octal (same as
-t o). -P
displays output in a portable POSIX-compliant format, with blanks separating the output fields. If you specified
-Aand file is not a library, the format is
file: name type value size
If you specified
-Aand file is a library, the format is
file[object_file]: name type value size
where object_file is the object file in the library which contains the symbol being described. If you did not specify
-A, the format is
name type value size
If you did not also specify the
-toption, nm displays value and size in hexadecimal.
If you did not specify
-Aand the command line contains more than one file, or file is a library, nm displays a line preceding the list of symbols for each specified file or each object file in a specified library. If file is a library, this line has the following format:
If file is not a library, the format is simply
does not sort output.
reverses sort order.
includes symbol size for each symbol.
defines the numeric value formatting base. The format shall be one of d, o, or x, for decimal, octal, or hexadecimal, respectively. If this option is not used, numbers are displayed in decimal.
displays only undefined symbols.
sorts output by value.
displays information in hexadecimal (same as
Possible exit status values are:
Failure due to any of the following:
If a file does not contain a symbol table, nm displays a warning and goes to the next file, but this is not considered an error.
POSIX.2. x/OPEN Portability Guide 4.0. All UNIX systems. Windows Server 2012. Windows 8.1. Windows Server 2012 R2. Windows 10. Windows Server 2016. Windows Server 2019.
On Windows systems, data (D, d) and uninitialized data (B, b) are not currently recognized in executable files, as this involves trying to guess segment types. All such symbols come out as text (T, t) symbols.
PTC MKS Toolkit for Developers
PTC MKS Toolkit for Interoperability
PTC MKS Toolkit for Professional Developers
PTC MKS Toolkit for Professional Developers 64-Bit Edition
PTC MKS Toolkit for Enterprise Developers
PTC MKS Toolkit for Enterprise Developers 64-Bit Edition
PTC Windchill Requirements and Validation
PTC MKS Toolkit 10.3 Documentation Build 39.