1 \input texinfo @c -*- Texinfo -*-
2 @setfilename binutils.info
3 @settitle @sc{gnu} Binary Utilities
12 @c man begin COPYRIGHT
13 Copyright @copyright{} 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
14 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
16 Permission is granted to copy, distribute and/or modify this document
17 under the terms of the GNU Free Documentation License, Version 1.3
18 or any later version published by the Free Software Foundation;
19 with no Invariant Sections, with no Front-Cover Texts, and with no
20 Back-Cover Texts. A copy of the license is included in the
21 section entitled ``GNU Free Documentation License''.
26 @dircategory Software development
28 * Binutils: (binutils). The GNU binary utilities.
31 @dircategory Individual utilities
33 * addr2line: (binutils)addr2line. Convert addresses to file and line.
34 * ar: (binutils)ar. Create, modify, and extract from archives.
35 * c++filt: (binutils)c++filt. Filter to demangle encoded C++ symbols.
36 * cxxfilt: (binutils)c++filt. MS-DOS name for c++filt.
37 * dlltool: (binutils)dlltool. Create files needed to build and use DLLs.
38 * nlmconv: (binutils)nlmconv. Converts object code into an NLM.
39 * nm: (binutils)nm. List symbols from object files.
40 * objcopy: (binutils)objcopy. Copy and translate object files.
41 * objdump: (binutils)objdump. Display information from object files.
42 * ranlib: (binutils)ranlib. Generate index to archive contents.
43 * readelf: (binutils)readelf. Display the contents of ELF format files.
44 * size: (binutils)size. List section sizes and total size.
45 * strings: (binutils)strings. List printable strings from files.
46 * strip: (binutils)strip. Discard symbols.
47 * windmc: (binutils)windmc. Generator for Windows message resources.
48 * windres: (binutils)windres. Manipulate Windows resources.
52 @title The @sc{gnu} Binary Utilities
53 @ifset VERSION_PACKAGE
54 @subtitle @value{VERSION_PACKAGE}
56 @subtitle Version @value{VERSION}
58 @subtitle @value{UPDATED}
59 @author Roland H. Pesch
60 @author Jeffrey M. Osier
61 @author Cygnus Support
65 {\parskip=0pt \hfill Cygnus Support\par \hfill
66 Texinfo \texinfoversion\par }
69 @vskip 0pt plus 1filll
78 This brief manual contains documentation for the @sc{gnu} binary
80 @ifset VERSION_PACKAGE
81 @value{VERSION_PACKAGE}
83 version @value{VERSION}:
88 Create, modify, and extract from archives
91 List symbols from object files
94 Copy and translate object files
97 Display information from object files
100 Generate index to archive contents
103 Display the contents of ELF format files.
106 List file section sizes and total size
109 List printable strings from files
115 Demangle encoded C++ symbols (on MS-DOS, this program is named
119 Convert addresses into file names and line numbers
122 Convert object code into a Netware Loadable Module
125 Manipulate Windows resources
128 Genertor for Windows message resources
131 Create the files needed to build and use Dynamic Link Libraries
135 This document is distributed under the terms of the GNU Free
136 Documentation License version 1.3. A copy of the license is included
137 in the section entitled ``GNU Free Documentation License''.
140 * ar:: Create, modify, and extract from archives
141 * nm:: List symbols from object files
142 * objcopy:: Copy and translate object files
143 * objdump:: Display information from object files
144 * ranlib:: Generate index to archive contents
145 * readelf:: Display the contents of ELF format files
146 * size:: List section sizes and total size
147 * strings:: List printable strings from files
148 * strip:: Discard symbols
149 * c++filt:: Filter to demangle encoded C++ symbols
150 * cxxfilt: c++filt. MS-DOS name for c++filt
151 * addr2line:: Convert addresses to file and line
152 * nlmconv:: Converts object code into an NLM
153 * windres:: Manipulate Windows resources
154 * windmc:: Generator for Windows message resources
155 * dlltool:: Create files needed to build and use DLLs
156 * Common Options:: Command-line options for all utilities
157 * Selecting the Target System:: How these utilities determine the target
158 * Reporting Bugs:: Reporting Bugs
159 * GNU Free Documentation License:: GNU Free Documentation License
160 * Binutils Index:: Binutils Index
168 @cindex collections of files
170 @c man title ar create, modify, and extract from archives
173 ar [-]@var{p}[@var{mod} [@var{relpos}] [@var{count}]] @var{archive} [@var{member}@dots{}]
174 ar -M [ <mri-script ]
177 @c man begin DESCRIPTION ar
179 The @sc{gnu} @command{ar} program creates, modifies, and extracts from
180 archives. An @dfn{archive} is a single file holding a collection of
181 other files in a structure that makes it possible to retrieve
182 the original individual files (called @dfn{members} of the archive).
184 The original files' contents, mode (permissions), timestamp, owner, and
185 group are preserved in the archive, and can be restored on
189 @sc{gnu} @command{ar} can maintain archives whose members have names of any
190 length; however, depending on how @command{ar} is configured on your
191 system, a limit on member-name length may be imposed for compatibility
192 with archive formats maintained with other tools. If it exists, the
193 limit is often 15 characters (typical of formats related to a.out) or 16
194 characters (typical of formats related to coff).
197 @command{ar} is considered a binary utility because archives of this sort
198 are most often used as @dfn{libraries} holding commonly needed
202 @command{ar} creates an index to the symbols defined in relocatable
203 object modules in the archive when you specify the modifier @samp{s}.
204 Once created, this index is updated in the archive whenever @command{ar}
205 makes a change to its contents (save for the @samp{q} update operation).
206 An archive with such an index speeds up linking to the library, and
207 allows routines in the library to call each other without regard to
208 their placement in the archive.
210 You may use @samp{nm -s} or @samp{nm --print-armap} to list this index
211 table. If an archive lacks the table, another form of @command{ar} called
212 @command{ranlib} can be used to add just the table.
214 @cindex thin archives
215 @sc{gnu} @command{ar} can optionally create a @emph{thin} archive,
216 which contains a symbol index and references to the original copies
217 of the member files of the archives. Such an archive is useful
218 for building libraries for use within a local build, where the
219 relocatable objects are expected to remain available, and copying the
220 contents of each object would only waste time and space. Thin archives
221 are also @emph{flattened}, so that adding one or more archives to a
222 thin archive will add the elements of the nested archive individually.
223 The paths to the elements of the archive are stored relative to the
226 @cindex compatibility, @command{ar}
227 @cindex @command{ar} compatibility
228 @sc{gnu} @command{ar} is designed to be compatible with two different
229 facilities. You can control its activity using command-line options,
230 like the different varieties of @command{ar} on Unix systems; or, if you
231 specify the single command-line option @option{-M}, you can control it
232 with a script supplied via standard input, like the MRI ``librarian''
238 * ar cmdline:: Controlling @command{ar} on the command line
239 * ar scripts:: Controlling @command{ar} with a script
244 @section Controlling @command{ar} on the Command Line
247 @c man begin SYNOPSIS ar
248 ar [@option{-X32_64}] [@option{-}]@var{p}[@var{mod} [@var{relpos}] [@var{count}]] @var{archive} [@var{member}@dots{}]
252 @cindex Unix compatibility, @command{ar}
253 When you use @command{ar} in the Unix style, @command{ar} insists on at least two
254 arguments to execute: one keyletter specifying the @emph{operation}
255 (optionally accompanied by other keyletters specifying
256 @emph{modifiers}), and the archive name to act on.
258 Most operations can also accept further @var{member} arguments,
259 specifying particular files to operate on.
261 @c man begin OPTIONS ar
263 @sc{gnu} @command{ar} allows you to mix the operation code @var{p} and modifier
264 flags @var{mod} in any order, within the first command-line argument.
266 If you wish, you may begin the first command-line argument with a
269 @cindex operations on archive
270 The @var{p} keyletter specifies what operation to execute; it may be
271 any of the following, but you must specify only one of them:
275 @cindex deleting from archive
276 @emph{Delete} modules from the archive. Specify the names of modules to
277 be deleted as @var{member}@dots{}; the archive is untouched if you
278 specify no files to delete.
280 If you specify the @samp{v} modifier, @command{ar} lists each module
284 @cindex moving in archive
285 Use this operation to @emph{move} members in an archive.
287 The ordering of members in an archive can make a difference in how
288 programs are linked using the library, if a symbol is defined in more
291 If no modifiers are used with @code{m}, any members you name in the
292 @var{member} arguments are moved to the @emph{end} of the archive;
293 you can use the @samp{a}, @samp{b}, or @samp{i} modifiers to move them to a
294 specified place instead.
297 @cindex printing from archive
298 @emph{Print} the specified members of the archive, to the standard
299 output file. If the @samp{v} modifier is specified, show the member
300 name before copying its contents to standard output.
302 If you specify no @var{member} arguments, all the files in the archive are
306 @cindex quick append to archive
307 @emph{Quick append}; Historically, add the files @var{member}@dots{} to the end of
308 @var{archive}, without checking for replacement.
310 The modifiers @samp{a}, @samp{b}, and @samp{i} do @emph{not} affect this
311 operation; new members are always placed at the end of the archive.
313 The modifier @samp{v} makes @command{ar} list each file as it is appended.
315 Since the point of this operation is speed, the archive's symbol table
316 index is not updated, even if it already existed; you can use @samp{ar s} or
317 @command{ranlib} explicitly to update the symbol table index.
319 However, too many different systems assume quick append rebuilds the
320 index, so @sc{gnu} @command{ar} implements @samp{q} as a synonym for @samp{r}.
323 @cindex replacement in archive
324 Insert the files @var{member}@dots{} into @var{archive} (with
325 @emph{replacement}). This operation differs from @samp{q} in that any
326 previously existing members are deleted if their names match those being
329 If one of the files named in @var{member}@dots{} does not exist, @command{ar}
330 displays an error message, and leaves undisturbed any existing members
331 of the archive matching that name.
333 By default, new members are added at the end of the file; but you may
334 use one of the modifiers @samp{a}, @samp{b}, or @samp{i} to request
335 placement relative to some existing member.
337 The modifier @samp{v} used with this operation elicits a line of
338 output for each file inserted, along with one of the letters @samp{a} or
339 @samp{r} to indicate whether the file was appended (no old member
340 deleted) or replaced.
343 @cindex contents of archive
344 Display a @emph{table} listing the contents of @var{archive}, or those
345 of the files listed in @var{member}@dots{} that are present in the
346 archive. Normally only the member name is shown; if you also want to
347 see the modes (permissions), timestamp, owner, group, and size, you can
348 request that by also specifying the @samp{v} modifier.
350 If you do not specify a @var{member}, all files in the archive
353 @cindex repeated names in archive
354 @cindex name duplication in archive
355 If there is more than one file with the same name (say, @samp{fie}) in
356 an archive (say @samp{b.a}), @samp{ar t b.a fie} lists only the
357 first instance; to see them all, you must ask for a complete
358 listing---in our example, @samp{ar t b.a}.
359 @c WRS only; per Gumby, this is implementation-dependent, and in a more
360 @c recent case in fact works the other way.
363 @cindex extract from archive
364 @emph{Extract} members (named @var{member}) from the archive. You can
365 use the @samp{v} modifier with this operation, to request that
366 @command{ar} list each name as it extracts it.
368 If you do not specify a @var{member}, all files in the archive
371 Files cannot be extracted from a thin archive.
375 A number of modifiers (@var{mod}) may immediately follow the @var{p}
376 keyletter, to specify variations on an operation's behavior:
380 @cindex relative placement in archive
381 Add new files @emph{after} an existing member of the
382 archive. If you use the modifier @samp{a}, the name of an existing archive
383 member must be present as the @var{relpos} argument, before the
384 @var{archive} specification.
387 Add new files @emph{before} an existing member of the
388 archive. If you use the modifier @samp{b}, the name of an existing archive
389 member must be present as the @var{relpos} argument, before the
390 @var{archive} specification. (same as @samp{i}).
393 @cindex creating archives
394 @emph{Create} the archive. The specified @var{archive} is always
395 created if it did not exist, when you request an update. But a warning is
396 issued unless you specify in advance that you expect to create it, by
400 @cindex deterministic archives
401 Operate in @emph{deterministic} mode. When adding files and the archive
402 index use zero for UIDs, GIDs, timestamps, and use consistent file modes
403 for all files. When this option is used, if @command{ar} is used with
404 identical options and identical input files, multiple runs will create
405 identical output files regardless of the input files' owners, groups,
406 file modes, or modification times.
409 Truncate names in the archive. @sc{gnu} @command{ar} will normally permit file
410 names of any length. This will cause it to create archives which are
411 not compatible with the native @command{ar} program on some systems. If
412 this is a concern, the @samp{f} modifier may be used to truncate file
413 names when putting them in the archive.
416 Insert new files @emph{before} an existing member of the
417 archive. If you use the modifier @samp{i}, the name of an existing archive
418 member must be present as the @var{relpos} argument, before the
419 @var{archive} specification. (same as @samp{b}).
422 This modifier is accepted but not used.
423 @c whaffor ar l modifier??? presumably compat; with
424 @c what???---doc@@cygnus.com, 25jan91
427 Uses the @var{count} parameter. This is used if there are multiple
428 entries in the archive with the same name. Extract or delete instance
429 @var{count} of the given name from the archive.
432 @cindex dates in archive
433 Preserve the @emph{original} dates of members when extracting them. If
434 you do not specify this modifier, files extracted from the archive
435 are stamped with the time of extraction.
438 Use the full path name when matching names in the archive. @sc{gnu}
439 @command{ar} can not create an archive with a full path name (such archives
440 are not POSIX complaint), but other archive creators can. This option
441 will cause @sc{gnu} @command{ar} to match file names using a complete path
442 name, which can be convenient when extracting a single file from an
443 archive created by another tool.
446 @cindex writing archive index
447 Write an object-file index into the archive, or update an existing one,
448 even if no other change is made to the archive. You may use this modifier
449 flag either with any operation, or alone. Running @samp{ar s} on an
450 archive is equivalent to running @samp{ranlib} on it.
453 @cindex not writing archive index
454 Do not generate an archive symbol table. This can speed up building a
455 large library in several steps. The resulting archive can not be used
456 with the linker. In order to build a symbol table, you must omit the
457 @samp{S} modifier on the last execution of @samp{ar}, or you must run
458 @samp{ranlib} on the archive.
461 @cindex creating thin archive
462 Make the specified @var{archive} a @emph{thin} archive. If it already
463 exists and is a regular archive, the existing members must be present
464 in the same directory as @var{archive}.
467 @cindex updating an archive
468 Normally, @samp{ar r}@dots{} inserts all files
469 listed into the archive. If you would like to insert @emph{only} those
470 of the files you list that are newer than existing members of the same
471 names, use this modifier. The @samp{u} modifier is allowed only for the
472 operation @samp{r} (replace). In particular, the combination @samp{qu} is
473 not allowed, since checking the timestamps would lose any speed
474 advantage from the operation @samp{q}.
477 This modifier requests the @emph{verbose} version of an operation. Many
478 operations display additional information, such as filenames processed,
479 when the modifier @samp{v} is appended.
482 This modifier shows the version number of @command{ar}.
485 @command{ar} ignores an initial option spelt @samp{-X32_64}, for
486 compatibility with AIX. The behaviour produced by this option is the
487 default for @sc{gnu} @command{ar}. @command{ar} does not support any of the other
488 @samp{-X} options; in particular, it does not support @option{-X32}
489 which is the default for AIX @command{ar}.
494 @c man begin SEEALSO ar
495 nm(1), ranlib(1), and the Info entries for @file{binutils}.
500 @section Controlling @command{ar} with a Script
503 ar -M [ <@var{script} ]
506 @cindex MRI compatibility, @command{ar}
507 @cindex scripts, @command{ar}
508 If you use the single command-line option @samp{-M} with @command{ar}, you
509 can control its operation with a rudimentary command language. This
510 form of @command{ar} operates interactively if standard input is coming
511 directly from a terminal. During interactive use, @command{ar} prompts for
512 input (the prompt is @samp{AR >}), and continues executing even after
513 errors. If you redirect standard input to a script file, no prompts are
514 issued, and @command{ar} abandons execution (with a nonzero exit code)
517 The @command{ar} command language is @emph{not} designed to be equivalent
518 to the command-line options; in fact, it provides somewhat less control
519 over archives. The only purpose of the command language is to ease the
520 transition to @sc{gnu} @command{ar} for developers who already have scripts
521 written for the MRI ``librarian'' program.
523 The syntax for the @command{ar} command language is straightforward:
526 commands are recognized in upper or lower case; for example, @code{LIST}
527 is the same as @code{list}. In the following descriptions, commands are
528 shown in upper case for clarity.
531 a single command may appear on each line; it is the first word on the
535 empty lines are allowed, and have no effect.
538 comments are allowed; text after either of the characters @samp{*}
539 or @samp{;} is ignored.
542 Whenever you use a list of names as part of the argument to an @command{ar}
543 command, you can separate the individual names with either commas or
544 blanks. Commas are shown in the explanations below, for clarity.
547 @samp{+} is used as a line continuation character; if @samp{+} appears
548 at the end of a line, the text on the following line is considered part
549 of the current command.
552 Here are the commands you can use in @command{ar} scripts, or when using
553 @command{ar} interactively. Three of them have special significance:
555 @code{OPEN} or @code{CREATE} specify a @dfn{current archive}, which is
556 a temporary file required for most of the other commands.
558 @code{SAVE} commits the changes so far specified by the script. Prior
559 to @code{SAVE}, commands affect only the temporary copy of the current
563 @item ADDLIB @var{archive}
564 @itemx ADDLIB @var{archive} (@var{module}, @var{module}, @dots{} @var{module})
565 Add all the contents of @var{archive} (or, if specified, each named
566 @var{module} from @var{archive}) to the current archive.
568 Requires prior use of @code{OPEN} or @code{CREATE}.
570 @item ADDMOD @var{member}, @var{member}, @dots{} @var{member}
571 @c FIXME! w/Replacement?? If so, like "ar r @var{archive} @var{names}"
572 @c else like "ar q..."
573 Add each named @var{member} as a module in the current archive.
575 Requires prior use of @code{OPEN} or @code{CREATE}.
578 Discard the contents of the current archive, canceling the effect of
579 any operations since the last @code{SAVE}. May be executed (with no
580 effect) even if no current archive is specified.
582 @item CREATE @var{archive}
583 Creates an archive, and makes it the current archive (required for many
584 other commands). The new archive is created with a temporary name; it
585 is not actually saved as @var{archive} until you use @code{SAVE}.
586 You can overwrite existing archives; similarly, the contents of any
587 existing file named @var{archive} will not be destroyed until @code{SAVE}.
589 @item DELETE @var{module}, @var{module}, @dots{} @var{module}
590 Delete each listed @var{module} from the current archive; equivalent to
591 @samp{ar -d @var{archive} @var{module} @dots{} @var{module}}.
593 Requires prior use of @code{OPEN} or @code{CREATE}.
595 @item DIRECTORY @var{archive} (@var{module}, @dots{} @var{module})
596 @itemx DIRECTORY @var{archive} (@var{module}, @dots{} @var{module}) @var{outputfile}
597 List each named @var{module} present in @var{archive}. The separate
598 command @code{VERBOSE} specifies the form of the output: when verbose
599 output is off, output is like that of @samp{ar -t @var{archive}
600 @var{module}@dots{}}. When verbose output is on, the listing is like
601 @samp{ar -tv @var{archive} @var{module}@dots{}}.
603 Output normally goes to the standard output stream; however, if you
604 specify @var{outputfile} as a final argument, @command{ar} directs the
608 Exit from @command{ar}, with a @code{0} exit code to indicate successful
609 completion. This command does not save the output file; if you have
610 changed the current archive since the last @code{SAVE} command, those
613 @item EXTRACT @var{module}, @var{module}, @dots{} @var{module}
614 Extract each named @var{module} from the current archive, writing them
615 into the current directory as separate files. Equivalent to @samp{ar -x
616 @var{archive} @var{module}@dots{}}.
618 Requires prior use of @code{OPEN} or @code{CREATE}.
621 @c FIXME Tokens but no commands???
628 Display full contents of the current archive, in ``verbose'' style
629 regardless of the state of @code{VERBOSE}. The effect is like @samp{ar
630 tv @var{archive}}. (This single command is a @sc{gnu} @command{ar}
631 enhancement, rather than present for MRI compatibility.)
633 Requires prior use of @code{OPEN} or @code{CREATE}.
635 @item OPEN @var{archive}
636 Opens an existing archive for use as the current archive (required for
637 many other commands). Any changes as the result of subsequent commands
638 will not actually affect @var{archive} until you next use @code{SAVE}.
640 @item REPLACE @var{module}, @var{module}, @dots{} @var{module}
641 In the current archive, replace each existing @var{module} (named in
642 the @code{REPLACE} arguments) from files in the current working directory.
643 To execute this command without errors, both the file, and the module in
644 the current archive, must exist.
646 Requires prior use of @code{OPEN} or @code{CREATE}.
649 Toggle an internal flag governing the output from @code{DIRECTORY}.
650 When the flag is on, @code{DIRECTORY} output matches output from
651 @samp{ar -tv }@dots{}.
654 Commit your changes to the current archive, and actually save it as a
655 file with the name specified in the last @code{CREATE} or @code{OPEN}
658 Requires prior use of @code{OPEN} or @code{CREATE}.
667 The @sc{gnu} linker @command{ld} is now described in a separate manual.
668 @xref{Top,, Overview,, Using LD: the @sc{gnu} linker}.
676 @c man title nm list symbols from object files
679 @c man begin SYNOPSIS nm
680 nm [@option{-a}|@option{--debug-syms}] [@option{-g}|@option{--extern-only}]
681 [@option{-B}] [@option{-C}|@option{--demangle}[=@var{style}]] [@option{-D}|@option{--dynamic}]
682 [@option{-S}|@option{--print-size}] [@option{-s}|@option{--print-armap}]
683 [@option{-A}|@option{-o}|@option{--print-file-name}][@option{--special-syms}]
684 [@option{-n}|@option{-v}|@option{--numeric-sort}] [@option{-p}|@option{--no-sort}]
685 [@option{-r}|@option{--reverse-sort}] [@option{--size-sort}] [@option{-u}|@option{--undefined-only}]
686 [@option{-t} @var{radix}|@option{--radix=}@var{radix}] [@option{-P}|@option{--portability}]
687 [@option{--target=}@var{bfdname}] [@option{-f}@var{format}|@option{--format=}@var{format}]
688 [@option{--defined-only}] [@option{-l}|@option{--line-numbers}] [@option{--no-demangle}]
689 [@option{-V}|@option{--version}] [@option{-X 32_64}] [@option{--help}] [@var{objfile}@dots{}]
693 @c man begin DESCRIPTION nm
694 @sc{gnu} @command{nm} lists the symbols from object files @var{objfile}@dots{}.
695 If no object files are listed as arguments, @command{nm} assumes the file
698 For each symbol, @command{nm} shows:
702 The symbol value, in the radix selected by options (see below), or
703 hexadecimal by default.
706 The symbol type. At least the following types are used; others are, as
707 well, depending on the object file format. If lowercase, the symbol is
708 local; if uppercase, the symbol is global (external).
710 @c Some more detail on exactly what these symbol types are used for
714 The symbol's value is absolute, and will not be changed by further
719 The symbol is in the uninitialized data section (known as BSS).
722 The symbol is common. Common symbols are uninitialized data. When
723 linking, multiple common symbols may appear with the same name. If the
724 symbol is defined anywhere, the common symbols are treated as undefined
727 For more details on common symbols, see the discussion of
728 --warn-common in @ref{Options,,Linker options,ld.info,The GNU linker}.
733 The symbol is in the initialized data section.
737 The symbol is in an initialized data section for small objects. Some
738 object file formats permit more efficient access to small data objects,
739 such as a global int variable as opposed to a large global array.
742 The symbol is in a section specific to the implementation of DLLs.
745 The symbol is a debugging symbol.
748 The symbols is in a stack unwind section.
752 The symbol is in a read only data section.
756 The symbol is in an uninitialized data section for small objects.
760 The symbol is in the text (code) section.
763 The symbol is undefined.
767 The symbol is a weak object. When a weak defined symbol is linked with
768 a normal defined symbol, the normal defined symbol is used with no error.
769 When a weak undefined symbol is linked and the symbol is not defined,
770 the value of the weak symbol becomes zero with no error. On some
771 systems, uppercase indicates that a default value has been specified.
775 The symbol is a weak symbol that has not been specifically tagged as a
776 weak object symbol. When a weak defined symbol is linked with a normal
777 defined symbol, the normal defined symbol is used with no error.
778 When a weak undefined symbol is linked and the symbol is not defined,
779 the value of the symbol is determined in a system-specific manner without
780 error. On some systems, uppercase indicates that a default value has been
784 The symbol is a stabs symbol in an a.out object file. In this case, the
785 next values printed are the stabs other field, the stabs desc field, and
786 the stab type. Stabs symbols are used to hold debugging information.
788 For more information, see @ref{Top,Stabs,Stabs Overview,stabs.info, The
789 ``stabs'' debug format}.
793 The symbol type is unknown, or object file format specific.
802 @c man begin OPTIONS nm
803 The long and short forms of options, shown here as alternatives, are
809 @itemx --print-file-name
810 @cindex input file name
812 @cindex source file name
813 Precede each symbol by the name of the input file (or archive member)
814 in which it was found, rather than identifying the input file once only,
815 before all of its symbols.
819 @cindex debugging symbols
820 Display all symbols, even debugger-only symbols; normally these are not
824 @cindex @command{nm} format
825 @cindex @command{nm} compatibility
826 The same as @option{--format=bsd} (for compatibility with the MIPS @command{nm}).
829 @itemx --demangle[=@var{style}]
830 @cindex demangling in nm
831 Decode (@dfn{demangle}) low-level symbol names into user-level names.
832 Besides removing any initial underscore prepended by the system, this
833 makes C++ function names readable. Different compilers have different
834 mangling styles. The optional demangling style argument can be used to
835 choose an appropriate demangling style for your compiler. @xref{c++filt},
836 for more information on demangling.
839 Do not demangle low-level symbol names. This is the default.
843 @cindex dynamic symbols
844 Display the dynamic symbols rather than the normal symbols. This is
845 only meaningful for dynamic objects, such as certain types of shared
848 @item -f @var{format}
849 @itemx --format=@var{format}
850 @cindex @command{nm} format
851 @cindex @command{nm} compatibility
852 Use the output format @var{format}, which can be @code{bsd},
853 @code{sysv}, or @code{posix}. The default is @code{bsd}.
854 Only the first character of @var{format} is significant; it can be
855 either upper or lower case.
859 @cindex external symbols
860 Display only external symbols.
863 @itemx --line-numbers
864 @cindex symbol line numbers
865 For each symbol, use debugging information to try to find a filename and
866 line number. For a defined symbol, look for the line number of the
867 address of the symbol. For an undefined symbol, look for the line
868 number of a relocation entry which refers to the symbol. If line number
869 information can be found, print it after the other symbol information.
873 @itemx --numeric-sort
874 Sort symbols numerically by their addresses, rather than alphabetically
879 @cindex sorting symbols
880 Do not bother to sort the symbols in any order; print them in the order
885 Use the POSIX.2 standard output format instead of the default format.
886 Equivalent to @samp{-f posix}.
890 Print size, not the value, of defined symbols for the @code{bsd} output format.
894 @cindex symbol index, listing
895 When listing symbols from archive members, include the index: a mapping
896 (stored in the archive by @command{ar} or @command{ranlib}) of which modules
897 contain definitions for which names.
900 @itemx --reverse-sort
901 Reverse the order of the sort (whether numeric or alphabetic); let the
905 Sort symbols by size. The size is computed as the difference between
906 the value of the symbol and the value of the symbol with the next higher
907 value. If the @code{bsd} output format is used the size of the symbol
908 is printed, rather than the value, and @samp{-S} must be used in order
909 both size and value to be printed.
912 Display symbols which have a target-specific special meaning. These
913 symbols are usually used by the target for some special processing and
914 are not normally helpful when included included in the normal symbol
915 lists. For example for ARM targets this option would skip the mapping
916 symbols used to mark transitions between ARM code, THUMB code and
920 @itemx --radix=@var{radix}
921 Use @var{radix} as the radix for printing the symbol values. It must be
922 @samp{d} for decimal, @samp{o} for octal, or @samp{x} for hexadecimal.
924 @item --target=@var{bfdname}
925 @cindex object code format
926 Specify an object code format other than your system's default format.
927 @xref{Target Selection}, for more information.
930 @itemx --undefined-only
931 @cindex external symbols
932 @cindex undefined symbols
933 Display only undefined symbols (those external to each object file).
936 @cindex external symbols
937 @cindex undefined symbols
938 Display only defined symbols for each object file.
942 Show the version number of @command{nm} and exit.
945 This option is ignored for compatibility with the AIX version of
946 @command{nm}. It takes one parameter which must be the string
947 @option{32_64}. The default mode of AIX @command{nm} corresponds
948 to @option{-X 32}, which is not supported by @sc{gnu} @command{nm}.
951 Show a summary of the options to @command{nm} and exit.
957 @c man begin SEEALSO nm
958 ar(1), objdump(1), ranlib(1), and the Info entries for @file{binutils}.
965 @c man title objcopy copy and translate object files
968 @c man begin SYNOPSIS objcopy
969 objcopy [@option{-F} @var{bfdname}|@option{--target=}@var{bfdname}]
970 [@option{-I} @var{bfdname}|@option{--input-target=}@var{bfdname}]
971 [@option{-O} @var{bfdname}|@option{--output-target=}@var{bfdname}]
972 [@option{-B} @var{bfdarch}|@option{--binary-architecture=}@var{bfdarch}]
973 [@option{-S}|@option{--strip-all}]
974 [@option{-g}|@option{--strip-debug}]
975 [@option{-K} @var{symbolname}|@option{--keep-symbol=}@var{symbolname}]
976 [@option{-N} @var{symbolname}|@option{--strip-symbol=}@var{symbolname}]
977 [@option{--strip-unneeded-symbol=}@var{symbolname}]
978 [@option{-G} @var{symbolname}|@option{--keep-global-symbol=}@var{symbolname}]
979 [@option{--localize-hidden}]
980 [@option{-L} @var{symbolname}|@option{--localize-symbol=}@var{symbolname}]
981 [@option{--globalize-symbol=}@var{symbolname}]
982 [@option{-W} @var{symbolname}|@option{--weaken-symbol=}@var{symbolname}]
983 [@option{-w}|@option{--wildcard}]
984 [@option{-x}|@option{--discard-all}]
985 [@option{-X}|@option{--discard-locals}]
986 [@option{-b} @var{byte}|@option{--byte=}@var{byte}]
987 [@option{-i} @var{interleave}|@option{--interleave=}@var{interleave}]
988 [@option{-j} @var{sectionname}|@option{--only-section=}@var{sectionname}]
989 [@option{-R} @var{sectionname}|@option{--remove-section=}@var{sectionname}]
990 [@option{-p}|@option{--preserve-dates}]
991 [@option{--debugging}]
992 [@option{--gap-fill=}@var{val}]
993 [@option{--pad-to=}@var{address}]
994 [@option{--set-start=}@var{val}]
995 [@option{--adjust-start=}@var{incr}]
996 [@option{--change-addresses=}@var{incr}]
997 [@option{--change-section-address} @var{section}@{=,+,-@}@var{val}]
998 [@option{--change-section-lma} @var{section}@{=,+,-@}@var{val}]
999 [@option{--change-section-vma} @var{section}@{=,+,-@}@var{val}]
1000 [@option{--change-warnings}] [@option{--no-change-warnings}]
1001 [@option{--set-section-flags} @var{section}=@var{flags}]
1002 [@option{--add-section} @var{sectionname}=@var{filename}]
1003 [@option{--rename-section} @var{oldname}=@var{newname}[,@var{flags}]]
1004 [@option{--long-section-names} @{enable,disable,keep@}]
1005 [@option{--change-leading-char}] [@option{--remove-leading-char}]
1006 [@option{--reverse-bytes=}@var{num}]
1007 [@option{--srec-len=}@var{ival}] [@option{--srec-forceS3}]
1008 [@option{--redefine-sym} @var{old}=@var{new}]
1009 [@option{--redefine-syms=}@var{filename}]
1011 [@option{--keep-symbols=}@var{filename}]
1012 [@option{--strip-symbols=}@var{filename}]
1013 [@option{--strip-unneeded-symbols=}@var{filename}]
1014 [@option{--keep-global-symbols=}@var{filename}]
1015 [@option{--localize-symbols=}@var{filename}]
1016 [@option{--globalize-symbols=}@var{filename}]
1017 [@option{--weaken-symbols=}@var{filename}]
1018 [@option{--alt-machine-code=}@var{index}]
1019 [@option{--prefix-symbols=}@var{string}]
1020 [@option{--prefix-sections=}@var{string}]
1021 [@option{--prefix-alloc-sections=}@var{string}]
1022 [@option{--add-gnu-debuglink=}@var{path-to-file}]
1023 [@option{--keep-file-symbols}]
1024 [@option{--only-keep-debug}]
1025 [@option{--extract-symbol}]
1026 [@option{--writable-text}]
1027 [@option{--readonly-text}]
1030 [@option{-v}|@option{--verbose}]
1031 [@option{-V}|@option{--version}]
1032 [@option{--help}] [@option{--info}]
1033 @var{infile} [@var{outfile}]
1037 @c man begin DESCRIPTION objcopy
1038 The @sc{gnu} @command{objcopy} utility copies the contents of an object
1039 file to another. @command{objcopy} uses the @sc{gnu} @sc{bfd} Library to
1040 read and write the object files. It can write the destination object
1041 file in a format different from that of the source object file. The
1042 exact behavior of @command{objcopy} is controlled by command-line options.
1043 Note that @command{objcopy} should be able to copy a fully linked file
1044 between any two formats. However, copying a relocatable object file
1045 between any two formats may not work as expected.
1047 @command{objcopy} creates temporary files to do its translations and
1048 deletes them afterward. @command{objcopy} uses @sc{bfd} to do all its
1049 translation work; it has access to all the formats described in @sc{bfd}
1050 and thus is able to recognize most formats without being told
1051 explicitly. @xref{BFD,,BFD,ld.info,Using LD}.
1053 @command{objcopy} can be used to generate S-records by using an output
1054 target of @samp{srec} (e.g., use @samp{-O srec}).
1056 @command{objcopy} can be used to generate a raw binary file by using an
1057 output target of @samp{binary} (e.g., use @option{-O binary}). When
1058 @command{objcopy} generates a raw binary file, it will essentially produce
1059 a memory dump of the contents of the input object file. All symbols and
1060 relocation information will be discarded. The memory dump will start at
1061 the load address of the lowest section copied into the output file.
1063 When generating an S-record or a raw binary file, it may be helpful to
1064 use @option{-S} to remove sections containing debugging information. In
1065 some cases @option{-R} will be useful to remove sections which contain
1066 information that is not needed by the binary file.
1068 Note---@command{objcopy} is not able to change the endianness of its input
1069 files. If the input format has an endianness (some formats do not),
1070 @command{objcopy} can only copy the inputs into file formats that have the
1071 same endianness or which have no endianness (e.g., @samp{srec}).
1072 (However, see the @option{--reverse-bytes} option.)
1076 @c man begin OPTIONS objcopy
1080 @itemx @var{outfile}
1081 The input and output files, respectively.
1082 If you do not specify @var{outfile}, @command{objcopy} creates a
1083 temporary file and destructively renames the result with
1084 the name of @var{infile}.
1086 @item -I @var{bfdname}
1087 @itemx --input-target=@var{bfdname}
1088 Consider the source file's object format to be @var{bfdname}, rather than
1089 attempting to deduce it. @xref{Target Selection}, for more information.
1091 @item -O @var{bfdname}
1092 @itemx --output-target=@var{bfdname}
1093 Write the output file using the object format @var{bfdname}.
1094 @xref{Target Selection}, for more information.
1096 @item -F @var{bfdname}
1097 @itemx --target=@var{bfdname}
1098 Use @var{bfdname} as the object format for both the input and the output
1099 file; i.e., simply transfer data from source to destination with no
1100 translation. @xref{Target Selection}, for more information.
1102 @item -B @var{bfdarch}
1103 @itemx --binary-architecture=@var{bfdarch}
1104 Useful when transforming a raw binary input file into an object file.
1105 In this case the output architecture can be set to @var{bfdarch}. This
1106 option will be ignored if the input file has a known @var{bfdarch}. You
1107 can access this binary data inside a program by referencing the special
1108 symbols that are created by the conversion process. These symbols are
1109 called _binary_@var{objfile}_start, _binary_@var{objfile}_end and
1110 _binary_@var{objfile}_size. e.g. you can transform a picture file into
1111 an object file and then access it in your code using these symbols.
1113 @item -j @var{sectionname}
1114 @itemx --only-section=@var{sectionname}
1115 Copy only the named section from the input file to the output file.
1116 This option may be given more than once. Note that using this option
1117 inappropriately may make the output file unusable.
1119 @item -R @var{sectionname}
1120 @itemx --remove-section=@var{sectionname}
1121 Remove any section named @var{sectionname} from the output file. This
1122 option may be given more than once. Note that using this option
1123 inappropriately may make the output file unusable.
1127 Do not copy relocation and symbol information from the source file.
1130 @itemx --strip-debug
1131 Do not copy debugging symbols or sections from the source file.
1133 @item --strip-unneeded
1134 Strip all symbols that are not needed for relocation processing.
1136 @item -K @var{symbolname}
1137 @itemx --keep-symbol=@var{symbolname}
1138 When stripping symbols, keep symbol @var{symbolname} even if it would
1139 normally be stripped. This option may be given more than once.
1141 @item -N @var{symbolname}
1142 @itemx --strip-symbol=@var{symbolname}
1143 Do not copy symbol @var{symbolname} from the source file. This option
1144 may be given more than once.
1146 @item --strip-unneeded-symbol=@var{symbolname}
1147 Do not copy symbol @var{symbolname} from the source file unless it is needed
1148 by a relocation. This option may be given more than once.
1150 @item -G @var{symbolname}
1151 @itemx --keep-global-symbol=@var{symbolname}
1152 Keep only symbol @var{symbolname} global. Make all other symbols local
1153 to the file, so that they are not visible externally. This option may
1154 be given more than once.
1156 @item --localize-hidden
1157 In an ELF object, mark all symbols that have hidden or internal visibility
1158 as local. This option applies on top of symbol-specific localization options
1159 such as @option{-L}.
1161 @item -L @var{symbolname}
1162 @itemx --localize-symbol=@var{symbolname}
1163 Make symbol @var{symbolname} local to the file, so that it is not
1164 visible externally. This option may be given more than once.
1166 @item -W @var{symbolname}
1167 @itemx --weaken-symbol=@var{symbolname}
1168 Make symbol @var{symbolname} weak. This option may be given more than once.
1170 @item --globalize-symbol=@var{symbolname}
1171 Give symbol @var{symbolname} global scoping so that it is visible
1172 outside of the file in which it is defined. This option may be given
1177 Permit regular expressions in @var{symbolname}s used in other command
1178 line options. The question mark (?), asterisk (*), backslash (\) and
1179 square brackets ([]) operators can be used anywhere in the symbol
1180 name. If the first character of the symbol name is the exclamation
1181 point (!) then the sense of the switch is reversed for that symbol.
1188 would cause objcopy to weaken all symbols that start with ``fo''
1189 except for the symbol ``foo''.
1192 @itemx --discard-all
1193 Do not copy non-global symbols from the source file.
1194 @c FIXME any reason to prefer "non-global" to "local" here?
1197 @itemx --discard-locals
1198 Do not copy compiler-generated local symbols.
1199 (These usually start with @samp{L} or @samp{.}.)
1202 @itemx --byte=@var{byte}
1203 Keep only every @var{byte}th byte of the input file (header data is not
1204 affected). @var{byte} can be in the range from 0 to @var{interleave}-1,
1205 where @var{interleave} is given by the @option{-i} or @option{--interleave}
1206 option, or the default of 4. This option is useful for creating files
1207 to program @sc{rom}. It is typically used with an @code{srec} output
1210 @item -i @var{interleave}
1211 @itemx --interleave=@var{interleave}
1212 Only copy one out of every @var{interleave} bytes. Select which byte to
1213 copy with the @option{-b} or @option{--byte} option. The default is 4.
1214 @command{objcopy} ignores this option if you do not specify either @option{-b} or
1218 @itemx --preserve-dates
1219 Set the access and modification dates of the output file to be the same
1220 as those of the input file.
1223 Convert debugging information, if possible. This is not the default
1224 because only certain debugging formats are supported, and the
1225 conversion process can be time consuming.
1227 @item --gap-fill @var{val}
1228 Fill gaps between sections with @var{val}. This operation applies to
1229 the @emph{load address} (LMA) of the sections. It is done by increasing
1230 the size of the section with the lower address, and filling in the extra
1231 space created with @var{val}.
1233 @item --pad-to @var{address}
1234 Pad the output file up to the load address @var{address}. This is
1235 done by increasing the size of the last section. The extra space is
1236 filled in with the value specified by @option{--gap-fill} (default zero).
1238 @item --set-start @var{val}
1239 Set the start address of the new file to @var{val}. Not all object file
1240 formats support setting the start address.
1242 @item --change-start @var{incr}
1243 @itemx --adjust-start @var{incr}
1244 @cindex changing start address
1245 Change the start address by adding @var{incr}. Not all object file
1246 formats support setting the start address.
1248 @item --change-addresses @var{incr}
1249 @itemx --adjust-vma @var{incr}
1250 @cindex changing object addresses
1251 Change the VMA and LMA addresses of all sections, as well as the start
1252 address, by adding @var{incr}. Some object file formats do not permit
1253 section addresses to be changed arbitrarily. Note that this does not
1254 relocate the sections; if the program expects sections to be loaded at a
1255 certain address, and this option is used to change the sections such
1256 that they are loaded at a different address, the program may fail.
1258 @item --change-section-address @var{section}@{=,+,-@}@var{val}
1259 @itemx --adjust-section-vma @var{section}@{=,+,-@}@var{val}
1260 @cindex changing section address
1261 Set or change both the VMA address and the LMA address of the named
1262 @var{section}. If @samp{=} is used, the section address is set to
1263 @var{val}. Otherwise, @var{val} is added to or subtracted from the
1264 section address. See the comments under @option{--change-addresses},
1265 above. If @var{section} does not exist in the input file, a warning will
1266 be issued, unless @option{--no-change-warnings} is used.
1268 @item --change-section-lma @var{section}@{=,+,-@}@var{val}
1269 @cindex changing section LMA
1270 Set or change the LMA address of the named @var{section}. The LMA
1271 address is the address where the section will be loaded into memory at
1272 program load time. Normally this is the same as the VMA address, which
1273 is the address of the section at program run time, but on some systems,
1274 especially those where a program is held in ROM, the two can be
1275 different. If @samp{=} is used, the section address is set to
1276 @var{val}. Otherwise, @var{val} is added to or subtracted from the
1277 section address. See the comments under @option{--change-addresses},
1278 above. If @var{section} does not exist in the input file, a warning
1279 will be issued, unless @option{--no-change-warnings} is used.
1281 @item --change-section-vma @var{section}@{=,+,-@}@var{val}
1282 @cindex changing section VMA
1283 Set or change the VMA address of the named @var{section}. The VMA
1284 address is the address where the section will be located once the
1285 program has started executing. Normally this is the same as the LMA
1286 address, which is the address where the section will be loaded into
1287 memory, but on some systems, especially those where a program is held in
1288 ROM, the two can be different. If @samp{=} is used, the section address
1289 is set to @var{val}. Otherwise, @var{val} is added to or subtracted
1290 from the section address. See the comments under
1291 @option{--change-addresses}, above. If @var{section} does not exist in
1292 the input file, a warning will be issued, unless
1293 @option{--no-change-warnings} is used.
1295 @item --change-warnings
1296 @itemx --adjust-warnings
1297 If @option{--change-section-address} or @option{--change-section-lma} or
1298 @option{--change-section-vma} is used, and the named section does not
1299 exist, issue a warning. This is the default.
1301 @item --no-change-warnings
1302 @itemx --no-adjust-warnings
1303 Do not issue a warning if @option{--change-section-address} or
1304 @option{--adjust-section-lma} or @option{--adjust-section-vma} is used, even
1305 if the named section does not exist.
1307 @item --set-section-flags @var{section}=@var{flags}
1308 Set the flags for the named section. The @var{flags} argument is a
1309 comma separated string of flag names. The recognized names are
1310 @samp{alloc}, @samp{contents}, @samp{load}, @samp{noload},
1311 @samp{readonly}, @samp{code}, @samp{data}, @samp{rom}, @samp{share}, and
1312 @samp{debug}. You can set the @samp{contents} flag for a section which
1313 does not have contents, but it is not meaningful to clear the
1314 @samp{contents} flag of a section which does have contents--just remove
1315 the section instead. Not all flags are meaningful for all object file
1318 @item --add-section @var{sectionname}=@var{filename}
1319 Add a new section named @var{sectionname} while copying the file. The
1320 contents of the new section are taken from the file @var{filename}. The
1321 size of the section will be the size of the file. This option only
1322 works on file formats which can support sections with arbitrary names.
1324 @item --rename-section @var{oldname}=@var{newname}[,@var{flags}]
1325 Rename a section from @var{oldname} to @var{newname}, optionally
1326 changing the section's flags to @var{flags} in the process. This has
1327 the advantage over usng a linker script to perform the rename in that
1328 the output stays as an object file and does not become a linked
1331 This option is particularly helpful when the input format is binary,
1332 since this will always create a section called .data. If for example,
1333 you wanted instead to create a section called .rodata containing binary
1334 data you could use the following command line to achieve it:
1337 objcopy -I binary -O <output_format> -B <architecture> \
1338 --rename-section .data=.rodata,alloc,load,readonly,data,contents \
1339 <input_binary_file> <output_object_file>
1342 @item --long-section-names @{enable,disable,keep@}
1343 Controls the handling of long section names when processing @code{COFF}
1344 and @code{PE-COFF} object formats. The default behaviour, @samp{keep},
1345 is to preserve long section names if any are present in the input file.
1346 The @samp{enable} and @samp{disable} options forcibly enable or disable
1347 the use of long section names in the output object; when @samp{disable}
1348 is in effect, any long section names in the input object will be truncated.
1349 The @samp{enable} option will only emit long section names if any are
1350 present in the inputs; this is mostly the same as @samp{keep}, but it
1351 is left undefined whether the @samp{enable} option might force the
1352 creation of an empty string table in the output file.
1354 @item --change-leading-char
1355 Some object file formats use special characters at the start of
1356 symbols. The most common such character is underscore, which compilers
1357 often add before every symbol. This option tells @command{objcopy} to
1358 change the leading character of every symbol when it converts between
1359 object file formats. If the object file formats use the same leading
1360 character, this option has no effect. Otherwise, it will add a
1361 character, or remove a character, or change a character, as
1364 @item --remove-leading-char
1365 If the first character of a global symbol is a special symbol leading
1366 character used by the object file format, remove the character. The
1367 most common symbol leading character is underscore. This option will
1368 remove a leading underscore from all global symbols. This can be useful
1369 if you want to link together objects of different file formats with
1370 different conventions for symbol names. This is different from
1371 @option{--change-leading-char} because it always changes the symbol name
1372 when appropriate, regardless of the object file format of the output
1375 @item --reverse-bytes=@var{num}
1376 Reverse the bytes in a section with output contents. A section length must
1377 be evenly divisible by the value given in order for the swap to be able to
1378 take place. Reversing takes place before the interleaving is performed.
1380 This option is used typically in generating ROM images for problematic
1381 target systems. For example, on some target boards, the 32-bit words
1382 fetched from 8-bit ROMs are re-assembled in little-endian byte order
1383 regardless of the CPU byte order. Depending on the programming model, the
1384 endianness of the ROM may need to be modified.
1386 Consider a simple file with a section containing the following eight
1387 bytes: @code{12345678}.
1389 Using @samp{--reverse-bytes=2} for the above example, the bytes in the
1390 output file would be ordered @code{21436587}.
1392 Using @samp{--reverse-bytes=4} for the above example, the bytes in the
1393 output file would be ordered @code{43218765}.
1395 By using @samp{--reverse-bytes=2} for the above example, followed by
1396 @samp{--reverse-bytes=4} on the output file, the bytes in the second
1397 output file would be ordered @code{34127856}.
1399 @item --srec-len=@var{ival}
1400 Meaningful only for srec output. Set the maximum length of the Srecords
1401 being produced to @var{ival}. This length covers both address, data and
1404 @item --srec-forceS3
1405 Meaningful only for srec output. Avoid generation of S1/S2 records,
1406 creating S3-only record format.
1408 @item --redefine-sym @var{old}=@var{new}
1409 Change the name of a symbol @var{old}, to @var{new}. This can be useful
1410 when one is trying link two things together for which you have no
1411 source, and there are name collisions.
1413 @item --redefine-syms=@var{filename}
1414 Apply @option{--redefine-sym} to each symbol pair "@var{old} @var{new}"
1415 listed in the file @var{filename}. @var{filename} is simply a flat file,
1416 with one symbol pair per line. Line comments may be introduced by the hash
1417 character. This option may be given more than once.
1420 Change all global symbols in the file to be weak. This can be useful
1421 when building an object which will be linked against other objects using
1422 the @option{-R} option to the linker. This option is only effective when
1423 using an object file format which supports weak symbols.
1425 @item --keep-symbols=@var{filename}
1426 Apply @option{--keep-symbol} option to each symbol listed in the file
1427 @var{filename}. @var{filename} is simply a flat file, with one symbol
1428 name per line. Line comments may be introduced by the hash character.
1429 This option may be given more than once.
1431 @item --strip-symbols=@var{filename}
1432 Apply @option{--strip-symbol} option to each symbol listed in the file
1433 @var{filename}. @var{filename} is simply a flat file, with one symbol
1434 name per line. Line comments may be introduced by the hash character.
1435 This option may be given more than once.
1437 @item --strip-unneeded-symbols=@var{filename}
1438 Apply @option{--strip-unneeded-symbol} option to each symbol listed in
1439 the file @var{filename}. @var{filename} is simply a flat file, with one
1440 symbol name per line. Line comments may be introduced by the hash
1441 character. This option may be given more than once.
1443 @item --keep-global-symbols=@var{filename}
1444 Apply @option{--keep-global-symbol} option to each symbol listed in the
1445 file @var{filename}. @var{filename} is simply a flat file, with one
1446 symbol name per line. Line comments may be introduced by the hash
1447 character. This option may be given more than once.
1449 @item --localize-symbols=@var{filename}
1450 Apply @option{--localize-symbol} option to each symbol listed in the file
1451 @var{filename}. @var{filename} is simply a flat file, with one symbol
1452 name per line. Line comments may be introduced by the hash character.
1453 This option may be given more than once.
1455 @item --globalize-symbols=@var{filename}
1456 Apply @option{--globalize-symbol} option to each symbol listed in the file
1457 @var{filename}. @var{filename} is simply a flat file, with one symbol
1458 name per line. Line comments may be introduced by the hash character.
1459 This option may be given more than once.
1461 @item --weaken-symbols=@var{filename}
1462 Apply @option{--weaken-symbol} option to each symbol listed in the file
1463 @var{filename}. @var{filename} is simply a flat file, with one symbol
1464 name per line. Line comments may be introduced by the hash character.
1465 This option may be given more than once.
1467 @item --alt-machine-code=@var{index}
1468 If the output architecture has alternate machine codes, use the
1469 @var{index}th code instead of the default one. This is useful in case
1470 a machine is assigned an official code and the tool-chain adopts the
1471 new code, but other applications still depend on the original code
1472 being used. For ELF based architectures if the @var{index}
1473 alternative does not exist then the value is treated as an absolute
1474 number to be stored in the e_machine field of the ELF header.
1476 @item --writable-text
1477 Mark the output text as writable. This option isn't meaningful for all
1478 object file formats.
1480 @item --readonly-text
1481 Make the output text write protected. This option isn't meaningful for all
1482 object file formats.
1485 Mark the output file as demand paged. This option isn't meaningful for all
1486 object file formats.
1489 Mark the output file as impure. This option isn't meaningful for all
1490 object file formats.
1492 @item --prefix-symbols=@var{string}
1493 Prefix all symbols in the output file with @var{string}.
1495 @item --prefix-sections=@var{string}
1496 Prefix all section names in the output file with @var{string}.
1498 @item --prefix-alloc-sections=@var{string}
1499 Prefix all the names of all allocated sections in the output file with
1502 @item --add-gnu-debuglink=@var{path-to-file}
1503 Creates a .gnu_debuglink section which contains a reference to @var{path-to-file}
1504 and adds it to the output file.
1506 @item --keep-file-symbols
1507 When stripping a file, perhaps with @option{--strip-debug} or
1508 @option{--strip-unneeded}, retain any symbols specifying source file names,
1509 which would otherwise get stripped.
1511 @item --only-keep-debug
1512 Strip a file, removing contents of any sections that would not be
1513 stripped by @option{--strip-debug} and leaving the debugging sections
1514 intact. In ELF files, this preserves all note sections in the output.
1516 The intention is that this option will be used in conjunction with
1517 @option{--add-gnu-debuglink} to create a two part executable. One a
1518 stripped binary which will occupy less space in RAM and in a
1519 distribution and the second a debugging information file which is only
1520 needed if debugging abilities are required. The suggested procedure
1521 to create these files is as follows:
1524 @item Link the executable as normal. Assuming that is is called
1526 @item Run @code{objcopy --only-keep-debug foo foo.dbg} to
1527 create a file containing the debugging info.
1528 @item Run @code{objcopy --strip-debug foo} to create a
1529 stripped executable.
1530 @item Run @code{objcopy --add-gnu-debuglink=foo.dbg foo}
1531 to add a link to the debugging info into the stripped executable.
1534 Note---the choice of @code{.dbg} as an extension for the debug info
1535 file is arbitrary. Also the @code{--only-keep-debug} step is
1536 optional. You could instead do this:
1539 @item Link the executable as normal.
1540 @item Copy @code{foo} to @code{foo.full}
1541 @item Run @code{objcopy --strip-debug foo}
1542 @item Run @code{objcopy --add-gnu-debuglink=foo.full foo}
1545 i.e., the file pointed to by the @option{--add-gnu-debuglink} can be the
1546 full executable. It does not have to be a file created by the
1547 @option{--only-keep-debug} switch.
1549 Note---this switch is only intended for use on fully linked files. It
1550 does not make sense to use it on object files where the debugging
1551 information may be incomplete. Besides the gnu_debuglink feature
1552 currently only supports the presence of one filename containing
1553 debugging information, not multiple filenames on a one-per-object-file
1556 @item --extract-symbol
1557 Keep the file's section flags and symbols but remove all section data.
1558 Specifically, the option:
1561 @item removes the contents of all sections;
1562 @item sets the size of every section to zero; and
1563 @item sets the file's start address to zero.
1566 This option is used to build a @file{.sym} file for a VxWorks kernel.
1567 It can also be a useful way of reducing the size of a @option{--just-symbols}
1572 Show the version number of @command{objcopy}.
1576 Verbose output: list all object files modified. In the case of
1577 archives, @samp{objcopy -V} lists all members of the archive.
1580 Show a summary of the options to @command{objcopy}.
1583 Display a list showing all architectures and object formats available.
1589 @c man begin SEEALSO objcopy
1590 ld(1), objdump(1), and the Info entries for @file{binutils}.
1597 @cindex object file information
1600 @c man title objdump display information from object files.
1603 @c man begin SYNOPSIS objdump
1604 objdump [@option{-a}|@option{--archive-headers}]
1605 [@option{-b} @var{bfdname}|@option{--target=@var{bfdname}}]
1606 [@option{-C}|@option{--demangle}[=@var{style}] ]
1607 [@option{-d}|@option{--disassemble}]
1608 [@option{-D}|@option{--disassemble-all}]
1609 [@option{-z}|@option{--disassemble-zeroes}]
1610 [@option{-EB}|@option{-EL}|@option{--endian=}@{big | little @}]
1611 [@option{-f}|@option{--file-headers}]
1612 [@option{-F}|@option{--file-offsets}]
1613 [@option{--file-start-context}]
1614 [@option{-g}|@option{--debugging}]
1615 [@option{-e}|@option{--debugging-tags}]
1616 [@option{-h}|@option{--section-headers}|@option{--headers}]
1617 [@option{-i}|@option{--info}]
1618 [@option{-j} @var{section}|@option{--section=}@var{section}]
1619 [@option{-l}|@option{--line-numbers}]
1620 [@option{-S}|@option{--source}]
1621 [@option{-m} @var{machine}|@option{--architecture=}@var{machine}]
1622 [@option{-M} @var{options}|@option{--disassembler-options=}@var{options}]
1623 [@option{-p}|@option{--private-headers}]
1624 [@option{-r}|@option{--reloc}]
1625 [@option{-R}|@option{--dynamic-reloc}]
1626 [@option{-s}|@option{--full-contents}]
1627 [@option{-W[lLiaprmfFsoR]}|
1628 @option{--dwarf}[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges]]
1629 [@option{-G}|@option{--stabs}]
1630 [@option{-t}|@option{--syms}]
1631 [@option{-T}|@option{--dynamic-syms}]
1632 [@option{-x}|@option{--all-headers}]
1633 [@option{-w}|@option{--wide}]
1634 [@option{--start-address=}@var{address}]
1635 [@option{--stop-address=}@var{address}]
1636 [@option{--prefix-addresses}]
1637 [@option{--[no-]show-raw-insn}]
1638 [@option{--adjust-vma=}@var{offset}]
1639 [@option{--special-syms}]
1640 [@option{--prefix=}@var{prefix}]
1641 [@option{--prefix-strip=}@var{level}]
1642 [@option{-V}|@option{--version}]
1643 [@option{-H}|@option{--help}]
1644 @var{objfile}@dots{}
1648 @c man begin DESCRIPTION objdump
1650 @command{objdump} displays information about one or more object files.
1651 The options control what particular information to display. This
1652 information is mostly useful to programmers who are working on the
1653 compilation tools, as opposed to programmers who just want their
1654 program to compile and work.
1656 @var{objfile}@dots{} are the object files to be examined. When you
1657 specify archives, @command{objdump} shows information on each of the member
1662 @c man begin OPTIONS objdump
1664 The long and short forms of options, shown here as alternatives, are
1665 equivalent. At least one option from the list
1666 @option{-a,-d,-D,-e,-f,-g,-G,-h,-H,-p,-r,-R,-s,-S,-t,-T,-V,-x} must be given.
1670 @itemx --archive-header
1671 @cindex archive headers
1672 If any of the @var{objfile} files are archives, display the archive
1673 header information (in a format similar to @samp{ls -l}). Besides the
1674 information you could list with @samp{ar tv}, @samp{objdump -a} shows
1675 the object file format of each archive member.
1677 @item --adjust-vma=@var{offset}
1678 @cindex section addresses in objdump
1679 @cindex VMA in objdump
1680 When dumping information, first add @var{offset} to all the section
1681 addresses. This is useful if the section addresses do not correspond to
1682 the symbol table, which can happen when putting sections at particular
1683 addresses when using a format which can not represent section addresses,
1686 @item -b @var{bfdname}
1687 @itemx --target=@var{bfdname}
1688 @cindex object code format
1689 Specify that the object-code format for the object files is
1690 @var{bfdname}. This option may not be necessary; @var{objdump} can
1691 automatically recognize many formats.
1695 objdump -b oasys -m vax -h fu.o
1698 displays summary information from the section headers (@option{-h}) of
1699 @file{fu.o}, which is explicitly identified (@option{-m}) as a VAX object
1700 file in the format produced by Oasys compilers. You can list the
1701 formats available with the @option{-i} option.
1702 @xref{Target Selection}, for more information.
1705 @itemx --demangle[=@var{style}]
1706 @cindex demangling in objdump
1707 Decode (@dfn{demangle}) low-level symbol names into user-level names.
1708 Besides removing any initial underscore prepended by the system, this
1709 makes C++ function names readable. Different compilers have different
1710 mangling styles. The optional demangling style argument can be used to
1711 choose an appropriate demangling style for your compiler. @xref{c++filt},
1712 for more information on demangling.
1716 Display debugging information. This attempts to parse STABS and IEEE
1717 debugging format information stored in the file and print it out using
1718 a C like syntax. If neither of these formats are found this option
1719 falls back on the @option{-W} option to print any DWARF information in
1723 @itemx --debugging-tags
1724 Like @option{-g}, but the information is generated in a format compatible
1728 @itemx --disassemble
1729 @cindex disassembling object code
1730 @cindex machine instructions
1731 Display the assembler mnemonics for the machine instructions from
1732 @var{objfile}. This option only disassembles those sections which are
1733 expected to contain instructions.
1736 @itemx --disassemble-all
1737 Like @option{-d}, but disassemble the contents of all sections, not just
1738 those expected to contain instructions.
1740 @item --prefix-addresses
1741 When disassembling, print the complete address on each line. This is
1742 the older disassembly format.
1746 @itemx --endian=@{big|little@}
1748 @cindex disassembly endianness
1749 Specify the endianness of the object files. This only affects
1750 disassembly. This can be useful when disassembling a file format which
1751 does not describe endianness information, such as S-records.
1754 @itemx --file-headers
1755 @cindex object file header
1756 Display summary information from the overall header of
1757 each of the @var{objfile} files.
1760 @itemx --file-offsets
1761 @cindex object file offsets
1762 When disassembling sections, whenever a symbol is displayed, also
1763 display the file offset of the region of data that is about to be
1764 dumped. If zeroes are being skipped, then when disassembly resumes,
1765 tell the user how many zeroes were skipped and the file offset of the
1766 location from where the disassembly resumes. When dumping sections,
1767 display the file offset of the location from where the dump starts.
1769 @item --file-start-context
1770 @cindex source code context
1771 Specify that when displaying interlisted source code/disassembly
1772 (assumes @option{-S}) from a file that has not yet been displayed, extend the
1773 context to the start of the file.
1776 @itemx --section-headers
1778 @cindex section headers
1779 Display summary information from the section headers of the
1782 File segments may be relocated to nonstandard addresses, for example by
1783 using the @option{-Ttext}, @option{-Tdata}, or @option{-Tbss} options to
1784 @command{ld}. However, some object file formats, such as a.out, do not
1785 store the starting address of the file segments. In those situations,
1786 although @command{ld} relocates the sections correctly, using @samp{objdump
1787 -h} to list the file section headers cannot show the correct addresses.
1788 Instead, it shows the usual addresses, which are implicit for the
1793 Print a summary of the options to @command{objdump} and exit.
1797 @cindex architectures available
1798 @cindex object formats available
1799 Display a list showing all architectures and object formats available
1800 for specification with @option{-b} or @option{-m}.
1803 @itemx --section=@var{name}
1804 @cindex section information
1805 Display information only for section @var{name}.
1808 @itemx --line-numbers
1809 @cindex source filenames for object files
1810 Label the display (using debugging information) with the filename and
1811 source line numbers corresponding to the object code or relocs shown.
1812 Only useful with @option{-d}, @option{-D}, or @option{-r}.
1814 @item -m @var{machine}
1815 @itemx --architecture=@var{machine}
1816 @cindex architecture
1817 @cindex disassembly architecture
1818 Specify the architecture to use when disassembling object files. This
1819 can be useful when disassembling object files which do not describe
1820 architecture information, such as S-records. You can list the available
1821 architectures with the @option{-i} option.
1823 @item -M @var{options}
1824 @itemx --disassembler-options=@var{options}
1825 Pass target specific information to the disassembler. Only supported on
1826 some targets. If it is necessary to specify more than one
1827 disassembler option then multiple @option{-M} options can be used or
1828 can be placed together into a comma separated list.
1830 If the target is an ARM architecture then this switch can be used to
1831 select which register name set is used during disassembler. Specifying
1832 @option{-M reg-names-std} (the default) will select the register names as
1833 used in ARM's instruction set documentation, but with register 13 called
1834 'sp', register 14 called 'lr' and register 15 called 'pc'. Specifying
1835 @option{-M reg-names-apcs} will select the name set used by the ARM
1836 Procedure Call Standard, whilst specifying @option{-M reg-names-raw} will
1837 just use @samp{r} followed by the register number.
1839 There are also two variants on the APCS register naming scheme enabled
1840 by @option{-M reg-names-atpcs} and @option{-M reg-names-special-atpcs} which
1841 use the ARM/Thumb Procedure Call Standard naming conventions. (Either
1842 with the normal register names or the special register names).
1844 This option can also be used for ARM architectures to force the
1845 disassembler to interpret all instructions as Thumb instructions by
1846 using the switch @option{--disassembler-options=force-thumb}. This can be
1847 useful when attempting to disassemble thumb code produced by other
1850 For the x86, some of the options duplicate functions of the @option{-m}
1851 switch, but allow finer grained control. Multiple selections from the
1852 following may be specified as a comma separated string.
1853 @option{x86-64}, @option{i386} and @option{i8086} select disassembly for
1854 the given architecture. @option{intel} and @option{att} select between
1855 intel syntax mode and AT&T syntax mode.
1856 @option{intel-mnemonic} and @option{att-mnemonic} select between
1857 intel mnemonic mode and AT&T mnemonic mode. @option{intel-mnemonic}
1858 implies @option{intel} and @option{att-mnemonic} implies @option{att}.
1859 @option{addr64}, @option{addr32},
1860 @option{addr16}, @option{data32} and @option{data16} specify the default
1861 address size and operand size. These four options will be overridden if
1862 @option{x86-64}, @option{i386} or @option{i8086} appear later in the
1863 option string. Lastly, @option{suffix}, when in AT&T mode,
1864 instructs the disassembler to print a mnemonic suffix even when the
1865 suffix could be inferred by the operands.
1867 For PowerPC, @option{booke} controls the disassembly of BookE
1868 instructions. @option{32} and @option{64} select PowerPC and
1869 PowerPC64 disassembly, respectively. @option{e300} selects
1870 disassembly for the e300 family. @option{440} selects disassembly for
1871 the PowerPC 440. @option{ppcps} selects disassembly for the paired
1872 single instructions of the PPC750CL.
1874 For MIPS, this option controls the printing of instruction mnemonic
1875 names and register names in disassembled instructions. Multiple
1876 selections from the following may be specified as a comma separated
1877 string, and invalid options are ignored:
1881 Print the 'raw' instruction mnemonic instead of some pseudo
1882 instruction mnemonic. I.e., print 'daddu' or 'or' instead of 'move',
1883 'sll' instead of 'nop', etc.
1885 @item gpr-names=@var{ABI}
1886 Print GPR (general-purpose register) names as appropriate
1887 for the specified ABI. By default, GPR names are selected according to
1888 the ABI of the binary being disassembled.
1890 @item fpr-names=@var{ABI}
1891 Print FPR (floating-point register) names as
1892 appropriate for the specified ABI. By default, FPR numbers are printed
1895 @item cp0-names=@var{ARCH}
1896 Print CP0 (system control coprocessor; coprocessor 0) register names
1897 as appropriate for the CPU or architecture specified by
1898 @var{ARCH}. By default, CP0 register names are selected according to
1899 the architecture and CPU of the binary being disassembled.
1901 @item hwr-names=@var{ARCH}
1902 Print HWR (hardware register, used by the @code{rdhwr} instruction) names
1903 as appropriate for the CPU or architecture specified by
1904 @var{ARCH}. By default, HWR names are selected according to
1905 the architecture and CPU of the binary being disassembled.
1907 @item reg-names=@var{ABI}
1908 Print GPR and FPR names as appropriate for the selected ABI.
1910 @item reg-names=@var{ARCH}
1911 Print CPU-specific register names (CP0 register and HWR names)
1912 as appropriate for the selected CPU or architecture.
1915 For any of the options listed above, @var{ABI} or
1916 @var{ARCH} may be specified as @samp{numeric} to have numbers printed
1917 rather than names, for the selected types of registers.
1918 You can list the available values of @var{ABI} and @var{ARCH} using
1919 the @option{--help} option.
1921 For VAX, you can specify function entry addresses with @option{-M
1922 entry:0xf00ba}. You can use this multiple times to properly
1923 disassemble VAX binary files that don't contain symbol tables (like
1924 ROM dumps). In these cases, the function entry mask would otherwise
1925 be decoded as VAX instructions, which would probably lead the rest
1926 of the function being wrongly disassembled.
1929 @itemx --private-headers
1930 Print information that is specific to the object file format. The exact
1931 information printed depends upon the object file format. For some
1932 object file formats, no additional information is printed.
1936 @cindex relocation entries, in object file
1937 Print the relocation entries of the file. If used with @option{-d} or
1938 @option{-D}, the relocations are printed interspersed with the
1942 @itemx --dynamic-reloc
1943 @cindex dynamic relocation entries, in object file
1944 Print the dynamic relocation entries of the file. This is only
1945 meaningful for dynamic objects, such as certain types of shared
1946 libraries. As for @option{-r}, if used with @option{-d} or
1947 @option{-D}, the relocations are printed interspersed with the
1951 @itemx --full-contents
1952 @cindex sections, full contents
1953 @cindex object file sections
1954 Display the full contents of any sections requested. By default all
1955 non-empty sections are displayed.
1959 @cindex source disassembly
1960 @cindex disassembly, with source
1961 Display source code intermixed with disassembly, if possible. Implies
1964 @item --prefix=@var{prefix}
1965 @cindex Add prefix to absolute paths
1966 Specify @var{prefix} to add to the absolute paths when used with
1969 @item --prefix-strip=@var{level}
1970 @cindex Strip absolute paths
1971 Indicate how many initial directory names to strip off the hardwired
1972 absolute paths. It has no effect without @option{--prefix=}@var{prefix}.
1974 @item --show-raw-insn
1975 When disassembling instructions, print the instruction in hex as well as
1976 in symbolic form. This is the default except when
1977 @option{--prefix-addresses} is used.
1979 @item --no-show-raw-insn
1980 When disassembling instructions, do not print the instruction bytes.
1981 This is the default when @option{--prefix-addresses} is used.
1983 @item -W[lLiaprmfFsoR]
1984 @itemx --dwarf[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges]
1986 @cindex debug symbols
1987 Displays the contents of the debug sections in the file, if any are
1988 present. If one of the optional letters or words follows the switch
1989 then only data found in those specific sections will be dumped.
1995 @cindex debug symbols
1996 @cindex ELF object file format
1997 Display the full contents of any sections requested. Display the
1998 contents of the .stab and .stab.index and .stab.excl sections from an
1999 ELF file. This is only useful on systems (such as Solaris 2.0) in which
2000 @code{.stab} debugging symbol-table entries are carried in an ELF
2001 section. In most other file formats, debugging symbol-table entries are
2002 interleaved with linkage symbols, and are visible in the @option{--syms}
2005 For more information on stabs symbols, see @ref{Top,Stabs,Stabs
2006 Overview,stabs.info, The ``stabs'' debug format}.
2009 @item --start-address=@var{address}
2010 @cindex start-address
2011 Start displaying data at the specified address. This affects the output
2012 of the @option{-d}, @option{-r} and @option{-s} options.
2014 @item --stop-address=@var{address}
2015 @cindex stop-address
2016 Stop displaying data at the specified address. This affects the output
2017 of the @option{-d}, @option{-r} and @option{-s} options.
2021 @cindex symbol table entries, printing
2022 Print the symbol table entries of the file.
2023 This is similar to the information provided by the @samp{nm} program,
2024 although the display format is different. The format of the output
2025 depends upon the format of the file being dumped, but there are two main
2026 types. One looks like this:
2029 [ 4](sec 3)(fl 0x00)(ty 0)(scl 3) (nx 1) 0x00000000 .bss
2030 [ 6](sec 1)(fl 0x00)(ty 0)(scl 2) (nx 0) 0x00000000 fred
2033 where the number inside the square brackets is the number of the entry
2034 in the symbol table, the @var{sec} number is the section number, the
2035 @var{fl} value are the symbol's flag bits, the @var{ty} number is the
2036 symbol's type, the @var{scl} number is the symbol's storage class and
2037 the @var{nx} value is the number of auxilary entries associated with
2038 the symbol. The last two fields are the symbol's value and its name.
2040 The other common output format, usually seen with ELF based files,
2044 00000000 l d .bss 00000000 .bss
2045 00000000 g .text 00000000 fred
2048 Here the first number is the symbol's value (sometimes refered to as
2049 its address). The next field is actually a set of characters and
2050 spaces indicating the flag bits that are set on the symbol. These
2051 characters are described below. Next is the section with which the
2052 symbol is associated or @emph{*ABS*} if the section is absolute (ie
2053 not connected with any section), or @emph{*UND*} if the section is
2054 referenced in the file being dumped, but not defined there.
2056 After the section name comes another field, a number, which for common
2057 symbols is the alignment and for other symbol is the size. Finally
2058 the symbol's name is displayed.
2060 The flag characters are divided into 7 groups as follows:
2065 The symbol is local (l), global (g), neither (a space) or both (!). A
2066 symbol can be neither local or global for a variety of reasons, e.g.,
2067 because it is used for debugging, but it is probably an indication of
2068 a bug if it is ever both local and global.
2071 The symbol is weak (w) or strong (a space).
2074 The symbol denotes a constructor (C) or an ordinary symbol (a space).
2077 The symbol is a warning (W) or a normal symbol (a space). A warning
2078 symbol's name is a message to be displayed if the symbol following the
2079 warning symbol is ever referenced.
2083 The symbol is an indirect reference to another symbol (I), a function
2084 to be evaluated during reloc processing (i) or a normal symbol (a
2089 The symbol is a debugging symbol (d) or a dynamic symbol (D) or a
2090 normal symbol (a space).
2095 The symbol is the name of a function (F) or a file (f) or an object
2096 (O) or just a normal symbol (a space).
2100 @itemx --dynamic-syms
2101 @cindex dynamic symbol table entries, printing
2102 Print the dynamic symbol table entries of the file. This is only
2103 meaningful for dynamic objects, such as certain types of shared
2104 libraries. This is similar to the information provided by the @samp{nm}
2105 program when given the @option{-D} (@option{--dynamic}) option.
2107 @item --special-syms
2108 When displaying symbols include those which the target considers to be
2109 special in some way and which would not normally be of interest to the
2114 Print the version number of @command{objdump} and exit.
2117 @itemx --all-headers
2118 @cindex all header information, object file
2119 @cindex header information, all
2120 Display all available header information, including the symbol table and
2121 relocation entries. Using @option{-x} is equivalent to specifying all of
2122 @option{-a -f -h -p -r -t}.
2126 @cindex wide output, printing
2127 Format some lines for output devices that have more than 80 columns.
2128 Also do not truncate symbol names when they are displayed.
2131 @itemx --disassemble-zeroes
2132 Normally the disassembly output will skip blocks of zeroes. This
2133 option directs the disassembler to disassemble those blocks, just like
2140 @c man begin SEEALSO objdump
2141 nm(1), readelf(1), and the Info entries for @file{binutils}.
2149 @cindex archive contents
2150 @cindex symbol index
2152 @c man title ranlib generate index to archive.
2155 @c man begin SYNOPSIS ranlib
2156 ranlib [@option{-vVt}] @var{archive}
2160 @c man begin DESCRIPTION ranlib
2162 @command{ranlib} generates an index to the contents of an archive and
2163 stores it in the archive. The index lists each symbol defined by a
2164 member of an archive that is a relocatable object file.
2166 You may use @samp{nm -s} or @samp{nm --print-armap} to list this index.
2168 An archive with such an index speeds up linking to the library and
2169 allows routines in the library to call each other without regard to
2170 their placement in the archive.
2172 The @sc{gnu} @command{ranlib} program is another form of @sc{gnu} @command{ar}; running
2173 @command{ranlib} is completely equivalent to executing @samp{ar -s}.
2178 @c man begin OPTIONS ranlib
2184 Show the version number of @command{ranlib}.
2187 Update the timestamp of the symbol map of an archive.
2193 @c man begin SEEALSO ranlib
2194 ar(1), nm(1), and the Info entries for @file{binutils}.
2202 @cindex section sizes
2204 @c man title size list section sizes and total size.
2207 @c man begin SYNOPSIS size
2208 size [@option{-A}|@option{-B}|@option{--format=}@var{compatibility}]
2210 [@option{-d}|@option{-o}|@option{-x}|@option{--radix=}@var{number}]
2212 [@option{-t}|@option{--totals}]
2213 [@option{--target=}@var{bfdname}] [@option{-V}|@option{--version}]
2214 [@var{objfile}@dots{}]
2218 @c man begin DESCRIPTION size
2220 The @sc{gnu} @command{size} utility lists the section sizes---and the total
2221 size---for each of the object or archive files @var{objfile} in its
2222 argument list. By default, one line of output is generated for each
2223 object file or each module in an archive.
2225 @var{objfile}@dots{} are the object files to be examined.
2226 If none are specified, the file @code{a.out} will be used.
2230 @c man begin OPTIONS size
2232 The command line options have the following meanings:
2237 @itemx --format=@var{compatibility}
2238 @cindex @command{size} display format
2239 Using one of these options, you can choose whether the output from @sc{gnu}
2240 @command{size} resembles output from System V @command{size} (using @option{-A},
2241 or @option{--format=sysv}), or Berkeley @command{size} (using @option{-B}, or
2242 @option{--format=berkeley}). The default is the one-line format similar to
2244 @c Bonus for doc-source readers: you can also say --format=strange (or
2245 @c anything else that starts with 's') for sysv, and --format=boring (or
2246 @c anything else that starts with 'b') for Berkeley.
2248 Here is an example of the Berkeley (default) format of output from
2251 $ size --format=Berkeley ranlib size
2252 text data bss dec hex filename
2253 294880 81920 11592 388392 5ed28 ranlib
2254 294880 81920 11888 388688 5ee50 size
2258 This is the same data, but displayed closer to System V conventions:
2261 $ size --format=SysV ranlib size
2279 Show a summary of acceptable arguments and options.
2284 @itemx --radix=@var{number}
2285 @cindex @command{size} number format
2286 @cindex radix for section sizes
2287 Using one of these options, you can control whether the size of each
2288 section is given in decimal (@option{-d}, or @option{--radix=10}); octal
2289 (@option{-o}, or @option{--radix=8}); or hexadecimal (@option{-x}, or
2290 @option{--radix=16}). In @option{--radix=@var{number}}, only the three
2291 values (8, 10, 16) are supported. The total size is always given in two
2292 radices; decimal and hexadecimal for @option{-d} or @option{-x} output, or
2293 octal and hexadecimal if you're using @option{-o}.
2296 Print total size of common symbols in each file. When using Berkeley
2297 format these are included in the bss size.
2301 Show totals of all objects listed (Berkeley format listing mode only).
2303 @item --target=@var{bfdname}
2304 @cindex object code format
2305 Specify that the object-code format for @var{objfile} is
2306 @var{bfdname}. This option may not be necessary; @command{size} can
2307 automatically recognize many formats.
2308 @xref{Target Selection}, for more information.
2312 Display the version number of @command{size}.
2318 @c man begin SEEALSO size
2319 ar(1), objdump(1), readelf(1), and the Info entries for @file{binutils}.
2326 @cindex listings strings
2327 @cindex printing strings
2328 @cindex strings, printing
2330 @c man title strings print the strings of printable characters in files.
2333 @c man begin SYNOPSIS strings
2334 strings [@option{-afovV}] [@option{-}@var{min-len}]
2335 [@option{-n} @var{min-len}] [@option{--bytes=}@var{min-len}]
2336 [@option{-t} @var{radix}] [@option{--radix=}@var{radix}]
2337 [@option{-e} @var{encoding}] [@option{--encoding=}@var{encoding}]
2338 [@option{-}] [@option{--all}] [@option{--print-file-name}]
2339 [@option{-T} @var{bfdname}] [@option{--target=}@var{bfdname}]
2340 [@option{--help}] [@option{--version}] @var{file}@dots{}
2344 @c man begin DESCRIPTION strings
2346 For each @var{file} given, @sc{gnu} @command{strings} prints the printable
2347 character sequences that are at least 4 characters long (or the number
2348 given with the options below) and are followed by an unprintable
2349 character. By default, it only prints the strings from the initialized
2350 and loaded sections of object files; for other types of files, it prints
2351 the strings from the whole file.
2353 @command{strings} is mainly useful for determining the contents of non-text
2358 @c man begin OPTIONS strings
2364 Do not scan only the initialized and loaded sections of object files;
2365 scan the whole files.
2368 @itemx --print-file-name
2369 Print the name of the file before each string.
2372 Print a summary of the program usage on the standard output and exit.
2374 @item -@var{min-len}
2375 @itemx -n @var{min-len}
2376 @itemx --bytes=@var{min-len}
2377 Print sequences of characters that are at least @var{min-len} characters
2378 long, instead of the default 4.
2381 Like @samp{-t o}. Some other versions of @command{strings} have @option{-o}
2382 act like @samp{-t d} instead. Since we can not be compatible with both
2383 ways, we simply chose one.
2385 @item -t @var{radix}
2386 @itemx --radix=@var{radix}
2387 Print the offset within the file before each string. The single
2388 character argument specifies the radix of the offset---@samp{o} for
2389 octal, @samp{x} for hexadecimal, or @samp{d} for decimal.
2391 @item -e @var{encoding}
2392 @itemx --encoding=@var{encoding}
2393 Select the character encoding of the strings that are to be found.
2394 Possible values for @var{encoding} are: @samp{s} = single-7-bit-byte
2395 characters (ASCII, ISO 8859, etc., default), @samp{S} =
2396 single-8-bit-byte characters, @samp{b} = 16-bit bigendian, @samp{l} =
2397 16-bit littleendian, @samp{B} = 32-bit bigendian, @samp{L} = 32-bit
2398 littleendian. Useful for finding wide character strings. (@samp{l}
2399 and @samp{b} apply to, for example, Unicode UTF-16/UCS-2 encodings).
2401 @item -T @var{bfdname}
2402 @itemx --target=@var{bfdname}
2403 @cindex object code format
2404 Specify an object code format other than your system's default format.
2405 @xref{Target Selection}, for more information.
2410 Print the program version number on the standard output and exit.
2416 @c man begin SEEALSO strings
2417 ar(1), nm(1), objdump(1), ranlib(1), readelf(1)
2418 and the Info entries for @file{binutils}.
2426 @cindex removing symbols
2427 @cindex discarding symbols
2428 @cindex symbols, discarding
2430 @c man title strip Discard symbols from object files.
2433 @c man begin SYNOPSIS strip
2434 strip [@option{-F} @var{bfdname} |@option{--target=}@var{bfdname}]
2435 [@option{-I} @var{bfdname} |@option{--input-target=}@var{bfdname}]
2436 [@option{-O} @var{bfdname} |@option{--output-target=}@var{bfdname}]
2437 [@option{-s}|@option{--strip-all}]
2438 [@option{-S}|@option{-g}|@option{-d}|@option{--strip-debug}]
2439 [@option{-K} @var{symbolname} |@option{--keep-symbol=}@var{symbolname}]
2440 [@option{-N} @var{symbolname} |@option{--strip-symbol=}@var{symbolname}]
2441 [@option{-w}|@option{--wildcard}]
2442 [@option{-x}|@option{--discard-all}] [@option{-X} |@option{--discard-locals}]
2443 [@option{-R} @var{sectionname} |@option{--remove-section=}@var{sectionname}]
2444 [@option{-o} @var{file}] [@option{-p}|@option{--preserve-dates}]
2445 [@option{--keep-file-symbols}]
2446 [@option{--only-keep-debug}]
2447 [@option{-v} |@option{--verbose}] [@option{-V}|@option{--version}]
2448 [@option{--help}] [@option{--info}]
2449 @var{objfile}@dots{}
2453 @c man begin DESCRIPTION strip
2455 @sc{gnu} @command{strip} discards all symbols from object files
2456 @var{objfile}. The list of object files may include archives.
2457 At least one object file must be given.
2459 @command{strip} modifies the files named in its argument,
2460 rather than writing modified copies under different names.
2464 @c man begin OPTIONS strip
2467 @item -F @var{bfdname}
2468 @itemx --target=@var{bfdname}
2469 Treat the original @var{objfile} as a file with the object
2470 code format @var{bfdname}, and rewrite it in the same format.
2471 @xref{Target Selection}, for more information.
2474 Show a summary of the options to @command{strip} and exit.
2477 Display a list showing all architectures and object formats available.
2479 @item -I @var{bfdname}
2480 @itemx --input-target=@var{bfdname}
2481 Treat the original @var{objfile} as a file with the object
2482 code format @var{bfdname}.
2483 @xref{Target Selection}, for more information.
2485 @item -O @var{bfdname}
2486 @itemx --output-target=@var{bfdname}
2487 Replace @var{objfile} with a file in the output format @var{bfdname}.
2488 @xref{Target Selection}, for more information.
2490 @item -R @var{sectionname}
2491 @itemx --remove-section=@var{sectionname}
2492 Remove any section named @var{sectionname} from the output file. This
2493 option may be given more than once. Note that using this option
2494 inappropriately may make the output file unusable.
2503 @itemx --strip-debug
2504 Remove debugging symbols only.
2506 @item --strip-unneeded
2507 Remove all symbols that are not needed for relocation processing.
2509 @item -K @var{symbolname}
2510 @itemx --keep-symbol=@var{symbolname}
2511 When stripping symbols, keep symbol @var{symbolname} even if it would
2512 normally be stripped. This option may be given more than once.
2514 @item -N @var{symbolname}
2515 @itemx --strip-symbol=@var{symbolname}
2516 Remove symbol @var{symbolname} from the source file. This option may be
2517 given more than once, and may be combined with strip options other than
2521 Put the stripped output in @var{file}, rather than replacing the
2522 existing file. When this argument is used, only one @var{objfile}
2523 argument may be specified.
2526 @itemx --preserve-dates
2527 Preserve the access and modification dates of the file.
2531 Permit regular expressions in @var{symbolname}s used in other command
2532 line options. The question mark (?), asterisk (*), backslash (\) and
2533 square brackets ([]) operators can be used anywhere in the symbol
2534 name. If the first character of the symbol name is the exclamation
2535 point (!) then the sense of the switch is reversed for that symbol.
2542 would cause strip to only keep symbols that start with the letters
2543 ``fo'', but to discard the symbol ``foo''.
2546 @itemx --discard-all
2547 Remove non-global symbols.
2550 @itemx --discard-locals
2551 Remove compiler-generated local symbols.
2552 (These usually start with @samp{L} or @samp{.}.)
2554 @item --keep-file-symbols
2555 When stripping a file, perhaps with @option{--strip-debug} or
2556 @option{--strip-unneeded}, retain any symbols specifying source file names,
2557 which would otherwise get stripped.
2559 @item --only-keep-debug
2560 Strip a file, removing contents of any sections that would not be
2561 stripped by @option{--strip-debug} and leaving the debugging sections
2562 intact. In ELF files, this preserves all note sections in the output.
2564 The intention is that this option will be used in conjunction with
2565 @option{--add-gnu-debuglink} to create a two part executable. One a
2566 stripped binary which will occupy less space in RAM and in a
2567 distribution and the second a debugging information file which is only
2568 needed if debugging abilities are required. The suggested procedure
2569 to create these files is as follows:
2572 @item Link the executable as normal. Assuming that is is called
2574 @item Run @code{objcopy --only-keep-debug foo foo.dbg} to
2575 create a file containing the debugging info.
2576 @item Run @code{objcopy --strip-debug foo} to create a
2577 stripped executable.
2578 @item Run @code{objcopy --add-gnu-debuglink=foo.dbg foo}
2579 to add a link to the debugging info into the stripped executable.
2582 Note---the choice of @code{.dbg} as an extension for the debug info
2583 file is arbitrary. Also the @code{--only-keep-debug} step is
2584 optional. You could instead do this:
2587 @item Link the executable as normal.
2588 @item Copy @code{foo} to @code{foo.full}
2589 @item Run @code{strip --strip-debug foo}
2590 @item Run @code{objcopy --add-gnu-debuglink=foo.full foo}
2593 i.e., the file pointed to by the @option{--add-gnu-debuglink} can be the
2594 full executable. It does not have to be a file created by the
2595 @option{--only-keep-debug} switch.
2597 Note---this switch is only intended for use on fully linked files. It
2598 does not make sense to use it on object files where the debugging
2599 information may be incomplete. Besides the gnu_debuglink feature
2600 currently only supports the presence of one filename containing
2601 debugging information, not multiple filenames on a one-per-object-file
2606 Show the version number for @command{strip}.
2610 Verbose output: list all object files modified. In the case of
2611 archives, @samp{strip -v} lists all members of the archive.
2617 @c man begin SEEALSO strip
2618 the Info entries for @file{binutils}.
2622 @node c++filt, addr2line, strip, Top
2626 @cindex demangling C++ symbols
2628 @c man title cxxfilt Demangle C++ and Java symbols.
2631 @c man begin SYNOPSIS cxxfilt
2632 c++filt [@option{-_}|@option{--strip-underscores}]
2633 [@option{-n}|@option{--no-strip-underscores}]
2634 [@option{-p}|@option{--no-params}]
2635 [@option{-t}|@option{--types}]
2636 [@option{-i}|@option{--no-verbose}]
2637 [@option{-s} @var{format}|@option{--format=}@var{format}]
2638 [@option{--help}] [@option{--version}] [@var{symbol}@dots{}]
2642 @c man begin DESCRIPTION cxxfilt
2645 The C++ and Java languages provide function overloading, which means
2646 that you can write many functions with the same name, providing that
2647 each function takes parameters of different types. In order to be
2648 able to distinguish these similarly named functions C++ and Java
2649 encode them into a low-level assembler name which uniquely identifies
2650 each different version. This process is known as @dfn{mangling}. The
2652 @footnote{MS-DOS does not allow @kbd{+} characters in file names, so on
2653 MS-DOS this program is named @command{CXXFILT}.}
2654 program does the inverse mapping: it decodes (@dfn{demangles}) low-level
2655 names into user-level names so that they can be read.
2657 Every alphanumeric word (consisting of letters, digits, underscores,
2658 dollars, or periods) seen in the input is a potential mangled name.
2659 If the name decodes into a C++ name, the C++ name replaces the
2660 low-level name in the output, otherwise the original word is output.
2661 In this way you can pass an entire assembler source file, containing
2662 mangled names, through @command{c++filt} and see the same source file
2663 containing demangled names.
2665 You can also use @command{c++filt} to decipher individual symbols by
2666 passing them on the command line:
2669 c++filt @var{symbol}
2672 If no @var{symbol} arguments are given, @command{c++filt} reads symbol
2673 names from the standard input instead. All the results are printed on
2674 the standard output. The difference between reading names from the
2675 command line versus reading names from the standard input is that
2676 command line arguments are expected to be just mangled names and no
2677 checking is performed to separate them from surrounding text. Thus
2684 will work and demangle the name to ``f()'' whereas:
2690 will not work. (Note the extra comma at the end of the mangled
2691 name which makes it invalid). This command however will work:
2694 echo _Z1fv, | c++filt -n
2697 and will display ``f(),'', i.e., the demangled name followed by a
2698 trailing comma. This behaviour is because when the names are read
2699 from the standard input it is expected that they might be part of an
2700 assembler source file where there might be extra, extraneous
2701 characters trailing after a mangled name. For example:
2704 .type _Z1fv, @@function
2709 @c man begin OPTIONS cxxfilt
2713 @itemx --strip-underscores
2714 On some systems, both the C and C++ compilers put an underscore in front
2715 of every name. For example, the C name @code{foo} gets the low-level
2716 name @code{_foo}. This option removes the initial underscore. Whether
2717 @command{c++filt} removes the underscore by default is target dependent.
2721 Prints demangled names using Java syntax. The default is to use C++
2725 @itemx --no-strip-underscores
2726 Do not remove the initial underscore.
2730 When demangling the name of a function, do not display the types of
2731 the function's parameters.
2735 Attempt to demangle types as well as function names. This is disabled
2736 by default since mangled types are normally only used internally in
2737 the compiler, and they can be confused with non-mangled names. For example,
2738 a function called ``a'' treated as a mangled type name would be
2739 demangled to ``signed char''.
2743 Do not include implementation details (if any) in the demangled
2746 @item -s @var{format}
2747 @itemx --format=@var{format}
2748 @command{c++filt} can decode various methods of mangling, used by
2749 different compilers. The argument to this option selects which
2754 Automatic selection based on executable (the default method)
2756 the one used by the @sc{gnu} C++ compiler (g++)
2758 the one used by the Lucid compiler (lcc)
2760 the one specified by the C++ Annotated Reference Manual
2762 the one used by the HP compiler (aCC)
2764 the one used by the EDG compiler
2766 the one used by the @sc{gnu} C++ compiler (g++) with the V3 ABI.
2768 the one used by the @sc{gnu} Java compiler (gcj)
2770 the one used by the @sc{gnu} Ada compiler (GNAT).
2774 Print a summary of the options to @command{c++filt} and exit.
2777 Print the version number of @command{c++filt} and exit.
2783 @c man begin SEEALSO cxxfilt
2784 the Info entries for @file{binutils}.
2789 @emph{Warning:} @command{c++filt} is a new utility, and the details of its
2790 user interface are subject to change in future releases. In particular,
2791 a command-line option may be required in the future to decode a name
2792 passed as an argument on the command line; in other words,
2795 c++filt @var{symbol}
2799 may in a future release become
2802 c++filt @var{option} @var{symbol}
2810 @cindex address to file name and line number
2812 @c man title addr2line convert addresses into file names and line numbers.
2815 @c man begin SYNOPSIS addr2line
2816 addr2line [@option{-b} @var{bfdname}|@option{--target=}@var{bfdname}]
2817 [@option{-C}|@option{--demangle}[=@var{style}]]
2818 [@option{-e} @var{filename}|@option{--exe=}@var{filename}]
2819 [@option{-f}|@option{--functions}] [@option{-s}|@option{--basename}]
2820 [@option{-i}|@option{--inlines}]
2821 [@option{-j}|@option{--section=}@var{name}]
2822 [@option{-H}|@option{--help}] [@option{-V}|@option{--version}]
2827 @c man begin DESCRIPTION addr2line
2829 @command{addr2line} translates addresses into file names and line numbers.
2830 Given an address in an executable or an offset in a section of a relocatable
2831 object, it uses the debugging information to figure out which file name and
2832 line number are associated with it.
2834 The executable or relocatable object to use is specified with the @option{-e}
2835 option. The default is the file @file{a.out}. The section in the relocatable
2836 object to use is specified with the @option{-j} option.
2838 @command{addr2line} has two modes of operation.
2840 In the first, hexadecimal addresses are specified on the command line,
2841 and @command{addr2line} displays the file name and line number for each
2844 In the second, @command{addr2line} reads hexadecimal addresses from
2845 standard input, and prints the file name and line number for each
2846 address on standard output. In this mode, @command{addr2line} may be used
2847 in a pipe to convert dynamically chosen addresses.
2849 The format of the output is @samp{FILENAME:LINENO}. The file name and
2850 line number for each address is printed on a separate line. If the
2851 @command{-f} option is used, then each @samp{FILENAME:LINENO} line is
2852 preceded by a @samp{FUNCTIONNAME} line which is the name of the function
2853 containing the address.
2855 If the file name or function name can not be determined,
2856 @command{addr2line} will print two question marks in their place. If the
2857 line number can not be determined, @command{addr2line} will print 0.
2861 @c man begin OPTIONS addr2line
2863 The long and short forms of options, shown here as alternatives, are
2867 @item -b @var{bfdname}
2868 @itemx --target=@var{bfdname}
2869 @cindex object code format
2870 Specify that the object-code format for the object files is
2874 @itemx --demangle[=@var{style}]
2875 @cindex demangling in objdump
2876 Decode (@dfn{demangle}) low-level symbol names into user-level names.
2877 Besides removing any initial underscore prepended by the system, this
2878 makes C++ function names readable. Different compilers have different
2879 mangling styles. The optional demangling style argument can be used to
2880 choose an appropriate demangling style for your compiler. @xref{c++filt},
2881 for more information on demangling.
2883 @item -e @var{filename}
2884 @itemx --exe=@var{filename}
2885 Specify the name of the executable for which addresses should be
2886 translated. The default file is @file{a.out}.
2890 Display function names as well as file and line number information.
2894 Display only the base of each file name.
2898 If the address belongs to a function that was inlined, the source
2899 information for all enclosing scopes back to the first non-inlined
2900 function will also be printed. For example, if @code{main} inlines
2901 @code{callee1} which inlines @code{callee2}, and address is from
2902 @code{callee2}, the source information for @code{callee1} and @code{main}
2903 will also be printed.
2907 Read offsets relative to the specified section instead of absolute addresses.
2913 @c man begin SEEALSO addr2line
2914 Info entries for @file{binutils}.
2921 @command{nlmconv} converts a relocatable object file into a NetWare
2925 @command{nlmconv} currently works with @samp{i386} object
2926 files in @code{coff}, @sc{elf}, or @code{a.out} format, and @sc{SPARC}
2927 object files in @sc{elf}, or @code{a.out} format@footnote{
2928 @command{nlmconv} should work with any @samp{i386} or @sc{sparc} object
2929 format in the Binary File Descriptor library. It has only been tested
2930 with the above formats.}.
2934 @emph{Warning:} @command{nlmconv} is not always built as part of the binary
2935 utilities, since it is only useful for NLM targets.
2938 @c man title nlmconv converts object code into an NLM.
2941 @c man begin SYNOPSIS nlmconv
2942 nlmconv [@option{-I} @var{bfdname}|@option{--input-target=}@var{bfdname}]
2943 [@option{-O} @var{bfdname}|@option{--output-target=}@var{bfdname}]
2944 [@option{-T} @var{headerfile}|@option{--header-file=}@var{headerfile}]
2945 [@option{-d}|@option{--debug}] [@option{-l} @var{linker}|@option{--linker=}@var{linker}]
2946 [@option{-h}|@option{--help}] [@option{-V}|@option{--version}]
2947 @var{infile} @var{outfile}
2951 @c man begin DESCRIPTION nlmconv
2953 @command{nlmconv} converts the relocatable @samp{i386} object file
2954 @var{infile} into the NetWare Loadable Module @var{outfile}, optionally
2955 reading @var{headerfile} for NLM header information. For instructions
2956 on writing the NLM command file language used in header files, see the
2957 @samp{linkers} section, @samp{NLMLINK} in particular, of the @cite{NLM
2958 Development and Tools Overview}, which is part of the NLM Software
2959 Developer's Kit (``NLM SDK''), available from Novell, Inc.
2960 @command{nlmconv} uses the @sc{gnu} Binary File Descriptor library to read
2963 see @ref{BFD,,BFD,ld.info,Using LD}, for more information.
2966 @command{nlmconv} can perform a link step. In other words, you can list
2967 more than one object file for input if you list them in the definitions
2968 file (rather than simply specifying one input file on the command line).
2969 In this case, @command{nlmconv} calls the linker for you.
2973 @c man begin OPTIONS nlmconv
2976 @item -I @var{bfdname}
2977 @itemx --input-target=@var{bfdname}
2978 Object format of the input file. @command{nlmconv} can usually determine
2979 the format of a given file (so no default is necessary).
2980 @xref{Target Selection}, for more information.
2982 @item -O @var{bfdname}
2983 @itemx --output-target=@var{bfdname}
2984 Object format of the output file. @command{nlmconv} infers the output
2985 format based on the input format, e.g. for a @samp{i386} input file the
2986 output format is @samp{nlm32-i386}.
2987 @xref{Target Selection}, for more information.
2989 @item -T @var{headerfile}
2990 @itemx --header-file=@var{headerfile}
2991 Reads @var{headerfile} for NLM header information. For instructions on
2992 writing the NLM command file language used in header files, see@ see the
2993 @samp{linkers} section, of the @cite{NLM Development and Tools
2994 Overview}, which is part of the NLM Software Developer's Kit, available
2999 Displays (on standard error) the linker command line used by @command{nlmconv}.
3001 @item -l @var{linker}
3002 @itemx --linker=@var{linker}
3003 Use @var{linker} for any linking. @var{linker} can be an absolute or a
3008 Prints a usage summary.
3012 Prints the version number for @command{nlmconv}.
3018 @c man begin SEEALSO nlmconv
3019 the Info entries for @file{binutils}.
3026 @command{windmc} may be used to generator Windows message resources.
3029 @emph{Warning:} @command{windmc} is not always built as part of the binary
3030 utilities, since it is only useful for Windows targets.
3033 @c man title windmc generates Windows message resources.
3036 @c man begin SYNOPSIS windres
3037 windmc [options] input-file
3041 @c man begin DESCRIPTION windmc
3043 @command{windmc} reads message definitions from an input file (.mc) and
3044 translate them into a set of output files. The output files may be of
3049 A C header file containing the message definitions.
3052 A resource file compilable by the @command{windres} tool.
3055 One or more binary files containing the resource data for a specific
3059 A C include file that maps message id's to their symbolic name.
3062 The exact description of these different formats is available in
3063 documentation from Microsoft.
3065 When @command{windmc} converts from the @code{mc} format to the @code{bin}
3066 format, @code{rc}, @code{h}, and optional @code{dbg} it is acting like the
3067 Windows Message Compiler.
3071 @c man begin OPTIONS windmc
3076 Specifies that the input file specified is ANSI. This is the default
3081 Specifies that messages in the output @code{bin} files should be in ANSI
3086 Specifies that @code{bin} filenames should have to be prefixed by the
3087 basename of the source file.
3091 Sets the customer bit in all message id's.
3093 @item -C @var{codepage}
3094 @itemx --codepage_in @var{codepage}
3095 Sets the default codepage to be used to convert input file to UTF16. The
3096 default is ocdepage 1252.
3099 @itemx --decimal_values
3100 Outputs the constants in the header file in decimal. Default is using
3104 @itemx --extension @var{ext}
3105 The extension for the header file. The default is .h extension.
3107 @item -F @var{target}
3108 @itemx --target @var{target}
3109 Specify the BFD format to use for a bin file as output. This
3110 is a BFD target name; you can use the @option{--help} option to see a list
3111 of supported targets. Normally @command{windmc} will use the default
3112 format, which is the first one listed by the @option{--help} option.
3114 @ref{Target Selection}.
3118 @itemx --headerdir @var{path}
3119 The target directory of the generated header file. The default is the
3124 Displays a list of command line options and then exits.
3126 @item -m @var{characters}
3127 @itemx --maxlength @var{characters}
3128 Instructs @command{windmc} to generate a warning if the length
3129 of any message exceeds the number specified.
3132 @itemx --nullterminate
3133 Terminate message text in @code{bin} files by zero. By default they are
3134 terminated by CR/LF.
3137 @itemx --hresult_use
3138 Not yet implemented. Instructs @code{windmc} to generate an OLE2 header
3139 file, using HRESULT definitions. Status codes are used if the flag is not
3142 @item -O @var{codepage}
3143 @itemx --codepage_out @var{codepage}
3144 Sets the default codepage to be used to output text files. The default
3148 @itemx --rcdir @var{path}
3149 The target directory for the generated @code{rc} script and the generated
3150 @code{bin} files that the resource compiler script includes. The default
3151 is the current directory.
3155 Specifies that the input file is UTF16.
3158 @itemx --unicode_out
3159 Specifies that messages in the output @code{bin} file should be in UTF16
3160 format. This is the default behaviour.
3164 Enable verbose mode.
3168 Prints the version number for @command{windmc}.
3171 @itemx --xdgb @var{path}
3172 The path of the @code{dbg} C include file that maps message id's to the
3173 symbolic name. No such file is generated without specifying the switch.
3179 @c man begin SEEALSO windmc
3180 the Info entries for @file{binutils}.
3187 @command{windres} may be used to manipulate Windows resources.
3190 @emph{Warning:} @command{windres} is not always built as part of the binary
3191 utilities, since it is only useful for Windows targets.
3194 @c man title windres manipulate Windows resources.
3197 @c man begin SYNOPSIS windres
3198 windres [options] [input-file] [output-file]
3202 @c man begin DESCRIPTION windres
3204 @command{windres} reads resources from an input file and copies them into
3205 an output file. Either file may be in one of three formats:
3209 A text format read by the Resource Compiler.
3212 A binary format generated by the Resource Compiler.
3215 A COFF object or executable.
3218 The exact description of these different formats is available in
3219 documentation from Microsoft.
3221 When @command{windres} converts from the @code{rc} format to the @code{res}
3222 format, it is acting like the Windows Resource Compiler. When
3223 @command{windres} converts from the @code{res} format to the @code{coff}
3224 format, it is acting like the Windows @code{CVTRES} program.
3226 When @command{windres} generates an @code{rc} file, the output is similar
3227 but not identical to the format expected for the input. When an input
3228 @code{rc} file refers to an external filename, an output @code{rc} file
3229 will instead include the file contents.
3231 If the input or output format is not specified, @command{windres} will
3232 guess based on the file name, or, for the input file, the file contents.
3233 A file with an extension of @file{.rc} will be treated as an @code{rc}
3234 file, a file with an extension of @file{.res} will be treated as a
3235 @code{res} file, and a file with an extension of @file{.o} or
3236 @file{.exe} will be treated as a @code{coff} file.
3238 If no output file is specified, @command{windres} will print the resources
3239 in @code{rc} format to standard output.
3241 The normal use is for you to write an @code{rc} file, use @command{windres}
3242 to convert it to a COFF object file, and then link the COFF file into
3243 your application. This will make the resources described in the
3244 @code{rc} file available to Windows.
3248 @c man begin OPTIONS windres
3251 @item -i @var{filename}
3252 @itemx --input @var{filename}
3253 The name of the input file. If this option is not used, then
3254 @command{windres} will use the first non-option argument as the input file
3255 name. If there are no non-option arguments, then @command{windres} will
3256 read from standard input. @command{windres} can not read a COFF file from
3259 @item -o @var{filename}
3260 @itemx --output @var{filename}
3261 The name of the output file. If this option is not used, then
3262 @command{windres} will use the first non-option argument, after any used
3263 for the input file name, as the output file name. If there is no
3264 non-option argument, then @command{windres} will write to standard output.
3265 @command{windres} can not write a COFF file to standard output. Note,
3266 for compatibility with @command{rc} the option @option{-fo} is also
3267 accepted, but its use is not recommended.
3269 @item -J @var{format}
3270 @itemx --input-format @var{format}
3271 The input format to read. @var{format} may be @samp{res}, @samp{rc}, or
3272 @samp{coff}. If no input format is specified, @command{windres} will
3273 guess, as described above.
3275 @item -O @var{format}
3276 @itemx --output-format @var{format}
3277 The output format to generate. @var{format} may be @samp{res},
3278 @samp{rc}, or @samp{coff}. If no output format is specified,
3279 @command{windres} will guess, as described above.
3281 @item -F @var{target}
3282 @itemx --target @var{target}
3283 Specify the BFD format to use for a COFF file as input or output. This
3284 is a BFD target name; you can use the @option{--help} option to see a list
3285 of supported targets. Normally @command{windres} will use the default
3286 format, which is the first one listed by the @option{--help} option.
3288 @ref{Target Selection}.
3291 @item --preprocessor @var{program}
3292 When @command{windres} reads an @code{rc} file, it runs it through the C
3293 preprocessor first. This option may be used to specify the preprocessor
3294 to use, including any leading arguments. The default preprocessor
3295 argument is @code{gcc -E -xc-header -DRC_INVOKED}.
3297 @item -I @var{directory}
3298 @itemx --include-dir @var{directory}
3299 Specify an include directory to use when reading an @code{rc} file.
3300 @command{windres} will pass this to the preprocessor as an @option{-I}
3301 option. @command{windres} will also search this directory when looking for
3302 files named in the @code{rc} file. If the argument passed to this command
3303 matches any of the supported @var{formats} (as described in the @option{-J}
3304 option), it will issue a deprecation warning, and behave just like the
3305 @option{-J} option. New programs should not use this behaviour. If a
3306 directory happens to match a @var{format}, simple prefix it with @samp{./}
3307 to disable the backward compatibility.
3309 @item -D @var{target}
3310 @itemx --define @var{sym}[=@var{val}]
3311 Specify a @option{-D} option to pass to the preprocessor when reading an
3314 @item -U @var{target}
3315 @itemx --undefine @var{sym}
3316 Specify a @option{-U} option to pass to the preprocessor when reading an
3320 Ignored for compatibility with rc.
3323 Enable verbose mode. This tells you what the preprocessor is if you
3327 @item --codepage @var{val}
3328 Specify the default codepage to use when reading an @code{rc} file.
3329 @var{val} should be a hexadecimal prefixed by @samp{0x} or decimal
3330 codepage code. The valid range is from zero up to 0xffff, but the
3331 validity of the codepage is host and configuration dependent.
3334 @item --language @var{val}
3335 Specify the default language to use when reading an @code{rc} file.
3336 @var{val} should be a hexadecimal language code. The low eight bits are
3337 the language, and the high eight bits are the sublanguage.
3339 @item --use-temp-file
3340 Use a temporary file to instead of using popen to read the output of
3341 the preprocessor. Use this option if the popen implementation is buggy
3342 on the host (eg., certain non-English language versions of Windows 95 and
3343 Windows 98 are known to have buggy popen where the output will instead
3346 @item --no-use-temp-file
3347 Use popen, not a temporary file, to read the output of the preprocessor.
3348 This is the default behaviour.
3352 Prints a usage summary.
3356 Prints the version number for @command{windres}.
3359 If @command{windres} is compiled with @code{YYDEBUG} defined as @code{1},
3360 this will turn on parser debugging.
3366 @c man begin SEEALSO windres
3367 the Info entries for @file{binutils}.
3376 @command{dlltool} is used to create the files needed to create dynamic
3377 link libraries (DLLs) on systems which understand PE format image
3378 files such as Windows. A DLL contains an export table which contains
3379 information that the runtime loader needs to resolve references from a
3380 referencing program.
3382 The export table is generated by this program by reading in a
3383 @file{.def} file or scanning the @file{.a} and @file{.o} files which
3384 will be in the DLL. A @file{.o} file can contain information in
3385 special @samp{.drectve} sections with export information.
3388 @emph{Note:} @command{dlltool} is not always built as part of the
3389 binary utilities, since it is only useful for those targets which
3393 @c man title dlltool Create files needed to build and use DLLs.
3396 @c man begin SYNOPSIS dlltool
3397 dlltool [@option{-d}|@option{--input-def} @var{def-file-name}]
3398 [@option{-b}|@option{--base-file} @var{base-file-name}]
3399 [@option{-e}|@option{--output-exp} @var{exports-file-name}]
3400 [@option{-z}|@option{--output-def} @var{def-file-name}]
3401 [@option{-l}|@option{--output-lib} @var{library-file-name}]
3402 [@option{--export-all-symbols}] [@option{--no-export-all-symbols}]
3403 [@option{--exclude-symbols} @var{list}]
3404 [@option{--no-default-excludes}]
3405 [@option{-S}|@option{--as} @var{path-to-assembler}] [@option{-f}|@option{--as-flags} @var{options}]
3406 [@option{-D}|@option{--dllname} @var{name}] [@option{-m}|@option{--machine} @var{machine}]
3407 [@option{-a}|@option{--add-indirect}]
3408 [@option{-U}|@option{--add-underscore}] [@option{--add-stdcall-underscore}]
3409 [@option{-k}|@option{--kill-at}] [@option{-A}|@option{--add-stdcall-alias}]
3410 [@option{-p}|@option{--ext-prefix-alias} @var{prefix}]
3411 [@option{-x}|@option{--no-idata4}] [@option{-c}|@option{--no-idata5}]
3412 [@option{--use-nul-prefixed-import-tables}]
3413 [@option{-I}|@option{--identify} @var{library-file-name}] [@option{--identify-strict}]
3414 [@option{-i}|@option{--interwork}]
3415 [@option{-n}|@option{--nodelete}] [@option{-t}|@option{--temp-prefix} @var{prefix}]
3416 [@option{-v}|@option{--verbose}]
3417 [@option{-h}|@option{--help}] [@option{-V}|@option{--version}]
3418 [object-file @dots{}]
3422 @c man begin DESCRIPTION dlltool
3424 @command{dlltool} reads its inputs, which can come from the @option{-d} and
3425 @option{-b} options as well as object files specified on the command
3426 line. It then processes these inputs and if the @option{-e} option has
3427 been specified it creates a exports file. If the @option{-l} option
3428 has been specified it creates a library file and if the @option{-z} option
3429 has been specified it creates a def file. Any or all of the @option{-e},
3430 @option{-l} and @option{-z} options can be present in one invocation of
3433 When creating a DLL, along with the source for the DLL, it is necessary
3434 to have three other files. @command{dlltool} can help with the creation of
3437 The first file is a @file{.def} file which specifies which functions are
3438 exported from the DLL, which functions the DLL imports, and so on. This
3439 is a text file and can be created by hand, or @command{dlltool} can be used
3440 to create it using the @option{-z} option. In this case @command{dlltool}
3441 will scan the object files specified on its command line looking for
3442 those functions which have been specially marked as being exported and
3443 put entries for them in the @file{.def} file it creates.
3445 In order to mark a function as being exported from a DLL, it needs to
3446 have an @option{-export:<name_of_function>} entry in the @samp{.drectve}
3447 section of the object file. This can be done in C by using the
3451 asm (".section .drectve");
3452 asm (".ascii \"-export:my_func\"");
3454 int my_func (void) @{ @dots{} @}
3457 The second file needed for DLL creation is an exports file. This file
3458 is linked with the object files that make up the body of the DLL and it
3459 handles the interface between the DLL and the outside world. This is a
3460 binary file and it can be created by giving the @option{-e} option to
3461 @command{dlltool} when it is creating or reading in a @file{.def} file.
3463 The third file needed for DLL creation is the library file that programs
3464 will link with in order to access the functions in the DLL (an `import
3465 library'). This file can be created by giving the @option{-l} option to
3466 dlltool when it is creating or reading in a @file{.def} file.
3468 @command{dlltool} builds the library file by hand, but it builds the
3469 exports file by creating temporary files containing assembler statements
3470 and then assembling these. The @option{-S} command line option can be
3471 used to specify the path to the assembler that dlltool will use,
3472 and the @option{-f} option can be used to pass specific flags to that
3473 assembler. The @option{-n} can be used to prevent dlltool from deleting
3474 these temporary assembler files when it is done, and if @option{-n} is
3475 specified twice then this will prevent dlltool from deleting the
3476 temporary object files it used to build the library.
3478 Here is an example of creating a DLL from a source file @samp{dll.c} and
3479 also creating a program (from an object file called @samp{program.o})
3484 dlltool -e exports.o -l dll.lib dll.o
3485 gcc dll.o exports.o -o dll.dll
3486 gcc program.o dll.lib -o program
3490 @command{dlltool} may also be used to query an existing import library
3491 to determine the name of the DLL to which it is associated. See the
3492 description of the @option{-I} or @option{--identify} option.
3496 @c man begin OPTIONS dlltool
3498 The command line options have the following meanings:
3502 @item -d @var{filename}
3503 @itemx --input-def @var{filename}
3504 @cindex input .def file
3505 Specifies the name of a @file{.def} file to be read in and processed.
3507 @item -b @var{filename}
3508 @itemx --base-file @var{filename}
3510 Specifies the name of a base file to be read in and processed. The
3511 contents of this file will be added to the relocation section in the
3512 exports file generated by dlltool.
3514 @item -e @var{filename}
3515 @itemx --output-exp @var{filename}
3516 Specifies the name of the export file to be created by dlltool.
3518 @item -z @var{filename}
3519 @itemx --output-def @var{filename}
3520 Specifies the name of the @file{.def} file to be created by dlltool.
3522 @item -l @var{filename}
3523 @itemx --output-lib @var{filename}
3524 Specifies the name of the library file to be created by dlltool.
3526 @item --export-all-symbols
3527 Treat all global and weak defined symbols found in the input object
3528 files as symbols to be exported. There is a small list of symbols which
3529 are not exported by default; see the @option{--no-default-excludes}
3530 option. You may add to the list of symbols to not export by using the
3531 @option{--exclude-symbols} option.
3533 @item --no-export-all-symbols
3534 Only export symbols explicitly listed in an input @file{.def} file or in
3535 @samp{.drectve} sections in the input object files. This is the default
3536 behaviour. The @samp{.drectve} sections are created by @samp{dllexport}
3537 attributes in the source code.
3539 @item --exclude-symbols @var{list}
3540 Do not export the symbols in @var{list}. This is a list of symbol names
3541 separated by comma or colon characters. The symbol names should not
3542 contain a leading underscore. This is only meaningful when
3543 @option{--export-all-symbols} is used.
3545 @item --no-default-excludes
3546 When @option{--export-all-symbols} is used, it will by default avoid
3547 exporting certain special symbols. The current list of symbols to avoid
3548 exporting is @samp{DllMain@@12}, @samp{DllEntryPoint@@0},
3549 @samp{impure_ptr}. You may use the @option{--no-default-excludes} option
3550 to go ahead and export these special symbols. This is only meaningful
3551 when @option{--export-all-symbols} is used.
3554 @itemx --as @var{path}
3555 Specifies the path, including the filename, of the assembler to be used
3556 to create the exports file.
3558 @item -f @var{options}
3559 @itemx --as-flags @var{options}
3560 Specifies any specific command line options to be passed to the
3561 assembler when building the exports file. This option will work even if
3562 the @option{-S} option is not used. This option only takes one argument,
3563 and if it occurs more than once on the command line, then later
3564 occurrences will override earlier occurrences. So if it is necessary to
3565 pass multiple options to the assembler they should be enclosed in
3569 @itemx --dll-name @var{name}
3570 Specifies the name to be stored in the @file{.def} file as the name of
3571 the DLL when the @option{-e} option is used. If this option is not
3572 present, then the filename given to the @option{-e} option will be
3573 used as the name of the DLL.
3575 @item -m @var{machine}
3576 @itemx -machine @var{machine}
3577 Specifies the type of machine for which the library file should be
3578 built. @command{dlltool} has a built in default type, depending upon how
3579 it was created, but this option can be used to override that. This is
3580 normally only useful when creating DLLs for an ARM processor, when the
3581 contents of the DLL are actually encode using Thumb instructions.
3584 @itemx --add-indirect
3585 Specifies that when @command{dlltool} is creating the exports file it
3586 should add a section which allows the exported functions to be
3587 referenced without using the import library. Whatever the hell that
3591 @itemx --add-underscore
3592 Specifies that when @command{dlltool} is creating the exports file it
3593 should prepend an underscore to the names of @emph{all} exported symbols.
3595 @item --add-stdcall-underscore
3596 Specifies that when @command{dlltool} is creating the exports file it
3597 should prepend an underscore to the names of exported @emph{stdcall}
3598 functions. Variable names and non-stdcall function names are not modified.
3599 This option is useful when creating GNU-compatible import libs for third
3600 party DLLs that were built with MS-Windows tools.
3604 Specifies that when @command{dlltool} is creating the exports file it
3605 should not append the string @samp{@@ <number>}. These numbers are
3606 called ordinal numbers and they represent another way of accessing the
3607 function in a DLL, other than by name.
3610 @itemx --add-stdcall-alias
3611 Specifies that when @command{dlltool} is creating the exports file it
3612 should add aliases for stdcall symbols without @samp{@@ <number>}
3613 in addition to the symbols with @samp{@@ <number>}.
3616 @itemx --ext-prefix-alias @var{prefix}
3617 Causes @command{dlltool} to create external aliases for all DLL
3618 imports with the specified prefix. The aliases are created for both
3619 external and import symbols with no leading underscore.
3623 Specifies that when @command{dlltool} is creating the exports and library
3624 files it should omit the @code{.idata4} section. This is for compatibility
3625 with certain operating systems.
3627 @item --use-nul-prefixed-import-tables
3628 Specifies that when @command{dlltool} is creating the exports and library
3629 files it should prefix the @code{.idata4} and @code{.idata5} by zero an
3630 element. This emulates old gnu import library generation of
3631 @code{dlltool}. By default this option is turned off.
3635 Specifies that when @command{dlltool} is creating the exports and library
3636 files it should omit the @code{.idata5} section. This is for compatibility
3637 with certain operating systems.
3639 @item -I @var{filename}
3640 @itemx --identify @var{filename}
3641 Specifies that @command{dlltool} should inspect the import library
3642 indicated by @var{filename} and report, on @code{stdout}, the name(s)
3643 of the associated DLL(s). This can be performed in addition to any
3644 other operations indicated by the other options and arguments.
3645 @command{dlltool} fails if the import library does not exist or is not
3646 actually an import library. See also @option{--identify-strict}.
3648 @item --identify-strict
3649 Modifies the behavior of the @option{--identify} option, such
3650 that an error is reported if @var{filename} is associated with
3655 Specifies that @command{dlltool} should mark the objects in the library
3656 file and exports file that it produces as supporting interworking
3657 between ARM and Thumb code.
3661 Makes @command{dlltool} preserve the temporary assembler files it used to
3662 create the exports file. If this option is repeated then dlltool will
3663 also preserve the temporary object files it uses to create the library
3666 @item -t @var{prefix}
3667 @itemx --temp-prefix @var{prefix}
3668 Makes @command{dlltool} use @var{prefix} when constructing the names of
3669 temporary assembler and object files. By default, the temp file prefix
3670 is generated from the pid.
3674 Make dlltool describe what it is doing.
3678 Displays a list of command line options and then exits.
3682 Displays dlltool's version number and then exits.
3689 * def file format:: The format of the dlltool @file{.def} file
3692 @node def file format
3693 @section The format of the @command{dlltool} @file{.def} file
3695 A @file{.def} file contains any number of the following commands:
3699 @item @code{NAME} @var{name} @code{[ ,} @var{base} @code{]}
3700 The result is going to be named @var{name}@code{.exe}.
3702 @item @code{LIBRARY} @var{name} @code{[ ,} @var{base} @code{]}
3703 The result is going to be named @var{name}@code{.dll}.
3705 @item @code{EXPORTS ( ( (} @var{name1} @code{[ = } @var{name2} @code{] ) | ( } @var{name1} @code{=} @var{module-name} @code{.} @var{external-name} @code{) )}
3706 @item @code{[} @var{integer} @code{] [ NONAME ] [ CONSTANT ] [ DATA ] [ PRIVATE ] ) *}
3707 Declares @var{name1} as an exported symbol from the DLL, with optional
3708 ordinal number @var{integer}, or declares @var{name1} as an alias
3709 (forward) of the function @var{external-name} in the DLL
3712 @item @code{IMPORTS ( (} @var{internal-name} @code{=} @var{module-name} @code{.} @var{integer} @code{) | [} @var{internal-name} @code{= ]} @var{module-name} @code{.} @var{external-name} @code{) ) *}
3713 Declares that @var{external-name} or the exported function whose
3714 ordinal number is @var{integer} is to be imported from the file
3715 @var{module-name}. If @var{internal-name} is specified then this is
3716 the name that the imported function will be referred to in the body of
3719 @item @code{DESCRIPTION} @var{string}
3720 Puts @var{string} into the output @file{.exp} file in the
3721 @code{.rdata} section.
3723 @item @code{STACKSIZE} @var{number-reserve} @code{[, } @var{number-commit} @code{]}
3724 @item @code{HEAPSIZE} @var{number-reserve} @code{[, } @var{number-commit} @code{]}
3725 Generates @code{--stack} or @code{--heap}
3726 @var{number-reserve},@var{number-commit} in the output @code{.drectve}
3727 section. The linker will see this and act upon it.
3729 @item @code{CODE} @var{attr} @code{+}
3730 @item @code{DATA} @var{attr} @code{+}
3731 @item @code{SECTIONS (} @var{section-name} @var{attr}@code{ + ) *}
3732 Generates @code{--attr} @var{section-name} @var{attr} in the output
3733 @code{.drectve} section, where @var{attr} is one of @code{READ},
3734 @code{WRITE}, @code{EXECUTE} or @code{SHARED}. The linker will see
3735 this and act upon it.
3740 @c man begin SEEALSO dlltool
3741 The Info pages for @file{binutils}.
3748 @cindex ELF file information
3751 @c man title readelf Displays information about ELF files.
3754 @c man begin SYNOPSIS readelf
3755 readelf [@option{-a}|@option{--all}]
3756 [@option{-h}|@option{--file-header}]
3757 [@option{-l}|@option{--program-headers}|@option{--segments}]
3758 [@option{-S}|@option{--section-headers}|@option{--sections}]
3759 [@option{-g}|@option{--section-groups}]
3760 [@option{-t}|@option{--section-details}]
3761 [@option{-e}|@option{--headers}]
3762 [@option{-s}|@option{--syms}|@option{--symbols}]
3763 [@option{-n}|@option{--notes}]
3764 [@option{-r}|@option{--relocs}]
3765 [@option{-u}|@option{--unwind}]
3766 [@option{-d}|@option{--dynamic}]
3767 [@option{-V}|@option{--version-info}]
3768 [@option{-A}|@option{--arch-specific}]
3769 [@option{-D}|@option{--use-dynamic}]
3770 [@option{-x} <number or name>|@option{--hex-dump=}<number or name>]
3771 [@option{-p} <number or name>|@option{--string-dump=}<number or name>]
3772 [@option{-c}|@option{--archive-index}]
3773 [@option{-w[lLiaprmfFsoR]}|
3774 @option{--debug-dump}[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges]]
3775 [@option{-I}|@option{-histogram}]
3776 [@option{-v}|@option{--version}]
3777 [@option{-W}|@option{--wide}]
3778 [@option{-H}|@option{--help}]
3779 @var{elffile}@dots{}
3783 @c man begin DESCRIPTION readelf
3785 @command{readelf} displays information about one or more ELF format object
3786 files. The options control what particular information to display.
3788 @var{elffile}@dots{} are the object files to be examined. 32-bit and
3789 64-bit ELF files are supported, as are archives containing ELF files.
3791 This program performs a similar function to @command{objdump} but it
3792 goes into more detail and it exists independently of the @sc{bfd}
3793 library, so if there is a bug in @sc{bfd} then readelf will not be
3798 @c man begin OPTIONS readelf
3800 The long and short forms of options, shown here as alternatives, are
3801 equivalent. At least one option besides @samp{-v} or @samp{-H} must be
3807 Equivalent to specifying @option{--file-header},
3808 @option{--program-headers}, @option{--sections}, @option{--symbols},
3809 @option{--relocs}, @option{--dynamic}, @option{--notes} and
3810 @option{--version-info}.
3813 @itemx --file-header
3814 @cindex ELF file header information
3815 Displays the information contained in the ELF header at the start of the
3819 @itemx --program-headers
3821 @cindex ELF program header information
3822 @cindex ELF segment information
3823 Displays the information contained in the file's segment headers, if it
3828 @itemx --section-headers
3829 @cindex ELF section information
3830 Displays the information contained in the file's section headers, if it
3834 @itemx --section-groups
3835 @cindex ELF section group information
3836 Displays the information contained in the file's section groups, if it
3840 @itemx --section-details
3841 @cindex ELF section information
3842 Displays the detailed section information. Implies @option{-S}.
3847 @cindex ELF symbol table information
3848 Displays the entries in symbol table section of the file, if it has one.
3852 Display all the headers in the file. Equivalent to @option{-h -l -S}.
3857 Displays the contents of the NOTE segments and/or sections, if any.
3861 @cindex ELF reloc information
3862 Displays the contents of the file's relocation section, if it has one.
3866 @cindex unwind information
3867 Displays the contents of the file's unwind section, if it has one. Only
3868 the unwind sections for IA64 ELF files are currently supported.
3872 @cindex ELF dynamic section information
3873 Displays the contents of the file's dynamic section, if it has one.
3876 @itemx --version-info
3877 @cindex ELF version sections informations
3878 Displays the contents of the version sections in the file, it they
3882 @itemx --arch-specific
3883 Displays architecture-specific information in the file, if there
3887 @itemx --use-dynamic
3888 When displaying symbols, this option makes @command{readelf} use the
3889 symbol table in the file's dynamic section, rather than the one in the
3892 @item -x <number or name>
3893 @itemx --hex-dump=<number or name>
3894 Displays the contents of the indicated section as a hexadecimal dump.
3895 A number identifies a particular section by index in the section table;
3896 any other string identifies all sections with that name in the object file.
3898 @item -p <number or name>
3899 @itemx --string-dump=<number or name>
3900 Displays the contents of the indicated section as printable strings.
3901 A number identifies a particular section by index in the section table;
3902 any other string identifies all sections with that name in the object file.
3905 @itemx --archive-index
3906 @cindex Archive file symbol index information
3907 Displays the file symbol index infomation contained in the header part
3908 of binary archives. Performs the same function as the @option{t}
3909 command to @command{ar}, but without using the BFD library. @xref{ar}.
3911 @item -w[lLiaprmfFsoR]
3912 @itemx --debug-dump[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges]
3913 Displays the contents of the debug sections in the file, if any are
3914 present. If one of the optional letters or words follows the switch
3915 then only data found in those specific sections will be dumped.
3917 Note: the @option{=decodedline} option will display the interpreted
3918 contents of a .debug_line section whereas the @option{=rawline} option
3919 dumps the contents in a raw format.
3923 Display a histogram of bucket list lengths when displaying the contents
3924 of the symbol tables.
3928 Display the version number of readelf.
3932 Don't break output lines to fit into 80 columns. By default
3933 @command{readelf} breaks section header and segment listing lines for
3934 64-bit ELF files, so that they fit into 80 columns. This option causes
3935 @command{readelf} to print each section header resp. each segment one a
3936 single line, which is far more readable on terminals wider than 80 columns.
3940 Display the command line options understood by @command{readelf}.
3947 @c man begin SEEALSO readelf
3948 objdump(1), and the Info entries for @file{binutils}.
3952 @node Common Options
3953 @chapter Common Options
3955 The following command-line options are supported by all of the
3956 programs described in this manual.
3958 @c man begin OPTIONS
3960 @include at-file.texi
3964 Display the command-line options supported by the program.
3967 Display the version number of the program.
3969 @c man begin OPTIONS
3973 @node Selecting the Target System
3974 @chapter Selecting the Target System
3976 You can specify two aspects of the target system to the @sc{gnu}
3977 binary file utilities, each in several ways:
3987 In the following summaries, the lists of ways to specify values are in
3988 order of decreasing precedence. The ways listed first override those
3991 The commands to list valid values only list the values for which the
3992 programs you are running were configured. If they were configured with
3993 @option{--enable-targets=all}, the commands list most of the available
3994 values, but a few are left out; not all targets can be configured in at
3995 once because some of them can only be configured @dfn{native} (on hosts
3996 with the same type as the target system).
3999 * Target Selection::
4000 * Architecture Selection::
4003 @node Target Selection
4004 @section Target Selection
4006 A @dfn{target} is an object file format. A given target may be
4007 supported for multiple architectures (@pxref{Architecture Selection}).
4008 A target selection may also have variations for different operating
4009 systems or architectures.
4011 The command to list valid target values is @samp{objdump -i}
4012 (the first column of output contains the relevant information).
4014 Some sample values are: @samp{a.out-hp300bsd}, @samp{ecoff-littlemips},
4015 @samp{a.out-sunos-big}.
4017 You can also specify a target using a configuration triplet. This is
4018 the same sort of name that is passed to @file{configure} to specify a
4019 target. When you use a configuration triplet as an argument, it must be
4020 fully canonicalized. You can see the canonical version of a triplet by
4021 running the shell script @file{config.sub} which is included with the
4024 Some sample configuration triplets are: @samp{m68k-hp-bsd},
4025 @samp{mips-dec-ultrix}, @samp{sparc-sun-sunos}.
4027 @subheading @command{objdump} Target
4033 command line option: @option{-b} or @option{--target}
4036 environment variable @code{GNUTARGET}
4039 deduced from the input file
4042 @subheading @command{objcopy} and @command{strip} Input Target
4048 command line options: @option{-I} or @option{--input-target}, or @option{-F} or @option{--target}
4051 environment variable @code{GNUTARGET}
4054 deduced from the input file
4057 @subheading @command{objcopy} and @command{strip} Output Target
4063 command line options: @option{-O} or @option{--output-target}, or @option{-F} or @option{--target}
4066 the input target (see ``@command{objcopy} and @command{strip} Input Target'' above)
4069 environment variable @code{GNUTARGET}
4072 deduced from the input file
4075 @subheading @command{nm}, @command{size}, and @command{strings} Target
4081 command line option: @option{--target}
4084 environment variable @code{GNUTARGET}
4087 deduced from the input file
4090 @node Architecture Selection
4091 @section Architecture Selection
4093 An @dfn{architecture} is a type of @sc{cpu} on which an object file is
4094 to run. Its name may contain a colon, separating the name of the
4095 processor family from the name of the particular @sc{cpu}.
4097 The command to list valid architecture values is @samp{objdump -i} (the
4098 second column contains the relevant information).
4100 Sample values: @samp{m68k:68020}, @samp{mips:3000}, @samp{sparc}.
4102 @subheading @command{objdump} Architecture
4108 command line option: @option{-m} or @option{--architecture}
4111 deduced from the input file
4114 @subheading @command{objcopy}, @command{nm}, @command{size}, @command{strings} Architecture
4120 deduced from the input file
4123 @node Reporting Bugs
4124 @chapter Reporting Bugs
4126 @cindex reporting bugs
4128 Your bug reports play an essential role in making the binary utilities
4131 Reporting a bug may help you by bringing a solution to your problem, or
4132 it may not. But in any case the principal function of a bug report is
4133 to help the entire community by making the next version of the binary
4134 utilities work better. Bug reports are your contribution to their
4137 In order for a bug report to serve its purpose, you must include the
4138 information that enables us to fix the bug.
4141 * Bug Criteria:: Have you found a bug?
4142 * Bug Reporting:: How to report bugs
4146 @section Have You Found a Bug?
4147 @cindex bug criteria
4149 If you are not sure whether you have found a bug, here are some guidelines:
4152 @cindex fatal signal
4155 If a binary utility gets a fatal signal, for any input whatever, that is
4156 a bug. Reliable utilities never crash.
4158 @cindex error on valid input
4160 If a binary utility produces an error message for valid input, that is a
4164 If you are an experienced user of binary utilities, your suggestions for
4165 improvement are welcome in any case.
4169 @section How to Report Bugs
4171 @cindex bugs, reporting
4173 A number of companies and individuals offer support for @sc{gnu}
4174 products. If you obtained the binary utilities from a support
4175 organization, we recommend you contact that organization first.
4177 You can find contact information for many support companies and
4178 individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs
4182 In any event, we also recommend that you send bug reports for the binary
4183 utilities to @value{BUGURL}.
4186 The fundamental principle of reporting bugs usefully is this:
4187 @strong{report all the facts}. If you are not sure whether to state a
4188 fact or leave it out, state it!
4190 Often people omit facts because they think they know what causes the
4191 problem and assume that some details do not matter. Thus, you might
4192 assume that the name of a file you use in an example does not matter.
4193 Well, probably it does not, but one cannot be sure. Perhaps the bug is
4194 a stray memory reference which happens to fetch from the location where
4195 that pathname is stored in memory; perhaps, if the pathname were
4196 different, the contents of that location would fool the utility into
4197 doing the right thing despite the bug. Play it safe and give a
4198 specific, complete example. That is the easiest thing for you to do,
4199 and the most helpful.
4201 Keep in mind that the purpose of a bug report is to enable us to fix the bug if
4202 it is new to us. Therefore, always write your bug reports on the assumption
4203 that the bug has not been reported previously.
4205 Sometimes people give a few sketchy facts and ask, ``Does this ring a
4206 bell?'' This cannot help us fix a bug, so it is basically useless. We
4207 respond by asking for enough details to enable us to investigate.
4208 You might as well expedite matters by sending them to begin with.
4210 To enable us to fix the bug, you should include all these things:
4214 The version of the utility. Each utility announces it if you start it
4215 with the @option{--version} argument.
4217 Without this, we will not know whether there is any point in looking for
4218 the bug in the current version of the binary utilities.
4221 Any patches you may have applied to the source, including any patches
4222 made to the @code{BFD} library.
4225 The type of machine you are using, and the operating system name and
4229 What compiler (and its version) was used to compile the utilities---e.g.
4233 The command arguments you gave the utility to observe the bug. To
4234 guarantee you will not omit something important, list them all. A copy
4235 of the Makefile (or the output from make) is sufficient.
4237 If we were to try to guess the arguments, we would probably guess wrong
4238 and then we might not encounter the bug.
4241 A complete input file, or set of input files, that will reproduce the
4242 bug. If the utility is reading an object file or files, then it is
4243 generally most helpful to send the actual object files.
4245 If the source files were produced exclusively using @sc{gnu} programs
4246 (e.g., @command{gcc}, @command{gas}, and/or the @sc{gnu} @command{ld}), then it
4247 may be OK to send the source files rather than the object files. In
4248 this case, be sure to say exactly what version of @command{gcc}, or
4249 whatever, was used to produce the object files. Also say how
4250 @command{gcc}, or whatever, was configured.
4253 A description of what behavior you observe that you believe is
4254 incorrect. For example, ``It gets a fatal signal.''
4256 Of course, if the bug is that the utility gets a fatal signal, then we
4257 will certainly notice it. But if the bug is incorrect output, we might
4258 not notice unless it is glaringly wrong. You might as well not give us
4259 a chance to make a mistake.
4261 Even if the problem you experience is a fatal signal, you should still
4262 say so explicitly. Suppose something strange is going on, such as your
4263 copy of the utility is out of sync, or you have encountered a bug in
4264 the C library on your system. (This has happened!) Your copy might
4265 crash and ours would not. If you told us to expect a crash, then when
4266 ours fails to crash, we would know that the bug was not happening for
4267 us. If you had not told us to expect a crash, then we would not be able
4268 to draw any conclusion from our observations.
4271 If you wish to suggest changes to the source, send us context diffs, as
4272 generated by @command{diff} with the @option{-u}, @option{-c}, or @option{-p}
4273 option. Always send diffs from the old file to the new file. If you
4274 wish to discuss something in the @command{ld} source, refer to it by
4275 context, not by line number.
4277 The line numbers in our development sources will not match those in your
4278 sources. Your line numbers would convey no useful information to us.
4281 Here are some things that are not necessary:
4285 A description of the envelope of the bug.
4287 Often people who encounter a bug spend a lot of time investigating
4288 which changes to the input file will make the bug go away and which
4289 changes will not affect it.
4291 This is often time consuming and not very useful, because the way we
4292 will find the bug is by running a single example under the debugger
4293 with breakpoints, not by pure deduction from a series of examples.
4294 We recommend that you save your time for something else.
4296 Of course, if you can find a simpler example to report @emph{instead}
4297 of the original one, that is a convenience for us. Errors in the
4298 output will be easier to spot, running under the debugger will take
4299 less time, and so on.
4301 However, simplification is not vital; if you do not want to do this,
4302 report the bug anyway and send us the entire test case you used.
4305 A patch for the bug.
4307 A patch for the bug does help us if it is a good one. But do not omit
4308 the necessary information, such as the test case, on the assumption that
4309 a patch is all we need. We might see problems with your patch and decide
4310 to fix the problem another way, or we might not understand it at all.
4312 Sometimes with programs as complicated as the binary utilities it is
4313 very hard to construct an example that will make the program follow a
4314 certain path through the code. If you do not send us the example, we
4315 will not be able to construct one, so we will not be able to verify that
4318 And if we cannot understand what bug you are trying to fix, or why your
4319 patch should be an improvement, we will not install it. A test case will
4320 help us to understand.
4323 A guess about what the bug is or what it depends on.
4325 Such guesses are usually wrong. Even we cannot guess right about such
4326 things without first using the debugger to find the facts.
4329 @node GNU Free Documentation License
4330 @appendix GNU Free Documentation License
4334 @node Binutils Index
4335 @unnumbered Binutils Index