nm

[XSI) ] ![[Option Start]]( Write only external (global) and static symbol information. ![[Option End]]( [XSI) ] ![[Option Start]]( Produce full output. Write redundant symbols ( .text , .data , and .bss ), normally suppressed. ![[Option End]]( Write each numeric value in the specified format. The format shall be dependent on the single character used as the format option-argument: The input file shall be an object file, an object-file library whose format is the same as those produced by the ar utility for link editing, or an executable file. The nm utility may accept additional implementation-defined object library formats for the input file. Provide a default value for the internationalization variables that are unset or null. (See XBD Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.) If set to a non-empty string value, override the values of all the other internationalization variables. Determine the locale for character collation information for the symbol-name and symbol-value collation sequences. Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error. [XSI) ] ![[Option Start]]( Determine the location of message catalogs for the processing of LC MESSAGES. ![[Option End]]( This information may be supplemented by additional information specific to the implementation. If -A is specified and the corresponding file operand names a library. In this case, shall name the object file in the library containing the symbol being described: Mechanisms for dynamic linking make this utility less meaningful when applied to an executable file because a dynamically linked executable may omit numerous library routines that would be found in a statically linked executable. The option list was significantly reduced from that provided by historical implementations. It was recognized that mechanisms for dynamic linking make this utility less meaningful when applied to an executable file (because a dynamically linked executable file may omit numerous library routines that would be found in a statically linked executable file), but the value of nm during software development was judged to outweigh other limitations. The default output format of nm is not specified because of differences in historical implementations. The -P option was added to allow some type of portable output format. After a comparison of the different formats used in SunOS, BSD, SVR3, and SVR4, it was decided to create one that did not match the current format of any of these four systems. The format devised is easy to parse by humans, easy to parse in shell scripts, and does not need to vary depending on locale (because no English descriptions are included). All of the systems currently have the information available to use this format. The format given in nm STDOUT uses characters between the fields, which may be any number of characters required to align the columns. The single-character types were selected to match historical practice, and the requirement that implementation additions also be single characters made parsing the information easier for shell scripts. This utility is marked as supported when both the User Portability Utilities option and the Software Development Utilities option are supported. The nm utility is removed from the User Portability Utilities option. User Portability Utilities is now an option for interactive utilities.