1 \input texinfo @c -*- Texinfo -*-
2 @setfilename binutils.info
3 @settitle @sc{gnu} Binary Utilities
12 @c man begin COPYRIGHT
13 Copyright @copyright{} 1991-2018 Free Software Foundation, Inc.
15 Permission is granted to copy, distribute and/or modify this document
16 under the terms of the GNU Free Documentation License, Version 1.3
17 or any later version published by the Free Software Foundation;
18 with no Invariant Sections, with no Front-Cover Texts, and with no
19 Back-Cover Texts. A copy of the license is included in the
20 section entitled ``GNU Free Documentation License''.
25 @dircategory Software development
27 * Binutils: (binutils). The GNU binary utilities.
30 @dircategory Individual utilities
32 * addr2line: (binutils)addr2line. Convert addresses to file and line.
33 * ar: (binutils)ar. Create, modify, and extract from archives.
34 * c++filt: (binutils)c++filt. Filter to demangle encoded C++ symbols.
35 * cxxfilt: (binutils)c++filt. MS-DOS name for c++filt.
36 * dlltool: (binutils)dlltool. Create files needed to build and use DLLs.
37 * nlmconv: (binutils)nlmconv. Converts object code into an NLM.
38 * nm: (binutils)nm. List symbols from object files.
39 * objcopy: (binutils)objcopy. Copy and translate object files.
40 * objdump: (binutils)objdump. Display information from object files.
41 * ranlib: (binutils)ranlib. Generate index to archive contents.
42 * readelf: (binutils)readelf. Display the contents of ELF format files.
43 * size: (binutils)size. List section sizes and total size.
44 * strings: (binutils)strings. List printable strings from files.
45 * strip: (binutils)strip. Discard symbols.
46 * elfedit: (binutils)elfedit. Update the ELF header of ELF files.
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 Update the ELF header of ELF files.
118 Demangle encoded C++ symbols (on MS-DOS, this program is named
122 Convert addresses into file names and line numbers
125 Convert object code into a Netware Loadable Module
128 Manipulate Windows resources
131 Generator for Windows message resources
134 Create the files needed to build and use Dynamic Link Libraries
138 This document is distributed under the terms of the GNU Free
139 Documentation License version 1.3. A copy of the license is included
140 in the section entitled ``GNU Free Documentation License''.
143 * ar:: Create, modify, and extract from archives
144 * nm:: List symbols from object files
145 * objcopy:: Copy and translate object files
146 * objdump:: Display information from object files
147 * ranlib:: Generate index to archive contents
148 * size:: List section sizes and total size
149 * strings:: List printable strings from files
150 * strip:: Discard symbols
151 * c++filt:: Filter to demangle encoded C++ symbols
152 * cxxfilt: c++filt. MS-DOS name for c++filt
153 * addr2line:: Convert addresses to file and line
154 * nlmconv:: Converts object code into an NLM
155 * windmc:: Generator for Windows message resources
156 * windres:: Manipulate Windows resources
157 * dlltool:: Create files needed to build and use DLLs
158 * readelf:: Display the contents of ELF format files
159 * elfedit:: Update the ELF header of ELF files
160 * Common Options:: Command-line options for all utilities
161 * Selecting the Target System:: How these utilities determine the target
162 * Reporting Bugs:: Reporting Bugs
163 * GNU Free Documentation License:: GNU Free Documentation License
164 * Binutils Index:: Binutils Index
172 @cindex collections of files
174 @c man title ar create, modify, and extract from archives
177 ar [-]@var{p}[@var{mod}] [@option{--plugin} @var{name}] [@option{--target} @var{bfdname}] [@var{relpos}] [@var{count}] @var{archive} [@var{member}@dots{}]
178 ar -M [ <mri-script ]
181 @c man begin DESCRIPTION ar
183 The @sc{gnu} @command{ar} program creates, modifies, and extracts from
184 archives. An @dfn{archive} is a single file holding a collection of
185 other files in a structure that makes it possible to retrieve
186 the original individual files (called @dfn{members} of the archive).
188 The original files' contents, mode (permissions), timestamp, owner, and
189 group are preserved in the archive, and can be restored on
193 @sc{gnu} @command{ar} can maintain archives whose members have names of any
194 length; however, depending on how @command{ar} is configured on your
195 system, a limit on member-name length may be imposed for compatibility
196 with archive formats maintained with other tools. If it exists, the
197 limit is often 15 characters (typical of formats related to a.out) or 16
198 characters (typical of formats related to coff).
201 @command{ar} is considered a binary utility because archives of this sort
202 are most often used as @dfn{libraries} holding commonly needed
206 @command{ar} creates an index to the symbols defined in relocatable
207 object modules in the archive when you specify the modifier @samp{s}.
208 Once created, this index is updated in the archive whenever @command{ar}
209 makes a change to its contents (save for the @samp{q} update operation).
210 An archive with such an index speeds up linking to the library, and
211 allows routines in the library to call each other without regard to
212 their placement in the archive.
214 You may use @samp{nm -s} or @samp{nm --print-armap} to list this index
215 table. If an archive lacks the table, another form of @command{ar} called
216 @command{ranlib} can be used to add just the table.
218 @cindex thin archives
219 @sc{gnu} @command{ar} can optionally create a @emph{thin} archive,
220 which contains a symbol index and references to the original copies
221 of the member files of the archive. This is useful for building
222 libraries for use within a local build tree, where the relocatable
223 objects are expected to remain available, and copying the contents of
224 each object would only waste time and space.
226 An archive can either be @emph{thin} or it can be normal. It cannot
227 be both at the same time. Once an archive is created its format
228 cannot be changed without first deleting it and then creating a new
229 archive in its place.
231 Thin archives are also @emph{flattened}, so that adding one thin
232 archive to another thin archive does not nest it, as would happen with
233 a normal archive. Instead the elements of the first archive are added
234 individually to the second archive.
236 The paths to the elements of the archive are stored relative to the
239 @cindex compatibility, @command{ar}
240 @cindex @command{ar} compatibility
241 @sc{gnu} @command{ar} is designed to be compatible with two different
242 facilities. You can control its activity using command-line options,
243 like the different varieties of @command{ar} on Unix systems; or, if you
244 specify the single command-line option @option{-M}, you can control it
245 with a script supplied via standard input, like the MRI ``librarian''
251 * ar cmdline:: Controlling @command{ar} on the command line
252 * ar scripts:: Controlling @command{ar} with a script
257 @section Controlling @command{ar} on the Command Line
260 @c man begin SYNOPSIS ar
261 ar [@option{-X32_64}] [@option{-}]@var{p}[@var{mod}] [@option{--plugin} @var{name}] [@option{--target} @var{bfdname}] [@var{relpos}] [@var{count}] @var{archive} [@var{member}@dots{}]
265 @cindex Unix compatibility, @command{ar}
266 When you use @command{ar} in the Unix style, @command{ar} insists on at least two
267 arguments to execute: one keyletter specifying the @emph{operation}
268 (optionally accompanied by other keyletters specifying
269 @emph{modifiers}), and the archive name to act on.
271 Most operations can also accept further @var{member} arguments,
272 specifying particular files to operate on.
274 @c man begin OPTIONS ar
276 @sc{gnu} @command{ar} allows you to mix the operation code @var{p} and modifier
277 flags @var{mod} in any order, within the first command-line argument.
279 If you wish, you may begin the first command-line argument with a
282 @cindex operations on archive
283 The @var{p} keyletter specifies what operation to execute; it may be
284 any of the following, but you must specify only one of them:
288 @cindex deleting from archive
289 @emph{Delete} modules from the archive. Specify the names of modules to
290 be deleted as @var{member}@dots{}; the archive is untouched if you
291 specify no files to delete.
293 If you specify the @samp{v} modifier, @command{ar} lists each module
297 @cindex moving in archive
298 Use this operation to @emph{move} members in an archive.
300 The ordering of members in an archive can make a difference in how
301 programs are linked using the library, if a symbol is defined in more
304 If no modifiers are used with @code{m}, any members you name in the
305 @var{member} arguments are moved to the @emph{end} of the archive;
306 you can use the @samp{a}, @samp{b}, or @samp{i} modifiers to move them to a
307 specified place instead.
310 @cindex printing from archive
311 @emph{Print} the specified members of the archive, to the standard
312 output file. If the @samp{v} modifier is specified, show the member
313 name before copying its contents to standard output.
315 If you specify no @var{member} arguments, all the files in the archive are
319 @cindex quick append to archive
320 @emph{Quick append}; Historically, add the files @var{member}@dots{} to the end of
321 @var{archive}, without checking for replacement.
323 The modifiers @samp{a}, @samp{b}, and @samp{i} do @emph{not} affect this
324 operation; new members are always placed at the end of the archive.
326 The modifier @samp{v} makes @command{ar} list each file as it is appended.
328 Since the point of this operation is speed, implementations of
329 @command{ar} have the option of not updating the archive's symbol
330 table if one exists. Too many different systems however assume that
331 symbol tables are always up-to-date, so @sc{gnu} @command{ar} will
332 rebuild the table even with a quick append.
334 Note - @sc{gnu} @command{ar} treats the command @samp{qs} as a
335 synonym for @samp{r} - replacing already existing files in the
336 archive and appending new ones at the end.
339 @cindex replacement in archive
340 Insert the files @var{member}@dots{} into @var{archive} (with
341 @emph{replacement}). This operation differs from @samp{q} in that any
342 previously existing members are deleted if their names match those being
345 If one of the files named in @var{member}@dots{} does not exist, @command{ar}
346 displays an error message, and leaves undisturbed any existing members
347 of the archive matching that name.
349 By default, new members are added at the end of the file; but you may
350 use one of the modifiers @samp{a}, @samp{b}, or @samp{i} to request
351 placement relative to some existing member.
353 The modifier @samp{v} used with this operation elicits a line of
354 output for each file inserted, along with one of the letters @samp{a} or
355 @samp{r} to indicate whether the file was appended (no old member
356 deleted) or replaced.
360 Add an index to the archive, or update it if it already exists. Note
361 this command is an exception to the rule that there can only be one
362 command letter, as it is possible to use it as either a command or a
363 modifier. In either case it does the same thing.
366 @cindex contents of archive
367 Display a @emph{table} listing the contents of @var{archive}, or those
368 of the files listed in @var{member}@dots{} that are present in the
369 archive. Normally only the member name is shown; if you also want to
370 see the modes (permissions), timestamp, owner, group, and size, you can
371 request that by also specifying the @samp{v} modifier.
373 If you do not specify a @var{member}, all files in the archive
376 @cindex repeated names in archive
377 @cindex name duplication in archive
378 If there is more than one file with the same name (say, @samp{fie}) in
379 an archive (say @samp{b.a}), @samp{ar t b.a fie} lists only the
380 first instance; to see them all, you must ask for a complete
381 listing---in our example, @samp{ar t b.a}.
382 @c WRS only; per Gumby, this is implementation-dependent, and in a more
383 @c recent case in fact works the other way.
386 @cindex extract from archive
387 @emph{Extract} members (named @var{member}) from the archive. You can
388 use the @samp{v} modifier with this operation, to request that
389 @command{ar} list each name as it extracts it.
391 If you do not specify a @var{member}, all files in the archive
394 Files cannot be extracted from a thin archive.
397 A number of modifiers (@var{mod}) may immediately follow the @var{p}
398 keyletter, to specify variations on an operation's behavior:
402 @cindex relative placement in archive
403 Add new files @emph{after} an existing member of the
404 archive. If you use the modifier @samp{a}, the name of an existing archive
405 member must be present as the @var{relpos} argument, before the
406 @var{archive} specification.
409 Add new files @emph{before} an existing member of the
410 archive. If you use the modifier @samp{b}, the name of an existing archive
411 member must be present as the @var{relpos} argument, before the
412 @var{archive} specification. (same as @samp{i}).
415 @cindex creating archives
416 @emph{Create} the archive. The specified @var{archive} is always
417 created if it did not exist, when you request an update. But a warning is
418 issued unless you specify in advance that you expect to create it, by
422 @cindex deterministic archives
423 @kindex --enable-deterministic-archives
424 Operate in @emph{deterministic} mode. When adding files and the archive
425 index use zero for UIDs, GIDs, timestamps, and use consistent file modes
426 for all files. When this option is used, if @command{ar} is used with
427 identical options and identical input files, multiple runs will create
428 identical output files regardless of the input files' owners, groups,
429 file modes, or modification times.
431 If @file{binutils} was configured with
432 @option{--enable-deterministic-archives}, then this mode is on by default.
433 It can be disabled with the @samp{U} modifier, below.
436 Truncate names in the archive. @sc{gnu} @command{ar} will normally permit file
437 names of any length. This will cause it to create archives which are
438 not compatible with the native @command{ar} program on some systems. If
439 this is a concern, the @samp{f} modifier may be used to truncate file
440 names when putting them in the archive.
443 Insert new files @emph{before} an existing member of the
444 archive. If you use the modifier @samp{i}, the name of an existing archive
445 member must be present as the @var{relpos} argument, before the
446 @var{archive} specification. (same as @samp{b}).
449 This modifier is accepted but not used.
450 @c whaffor ar l modifier??? presumably compat; with
451 @c what???---doc@@cygnus.com, 25jan91
454 Uses the @var{count} parameter. This is used if there are multiple
455 entries in the archive with the same name. Extract or delete instance
456 @var{count} of the given name from the archive.
459 @cindex dates in archive
460 Preserve the @emph{original} dates of members when extracting them. If
461 you do not specify this modifier, files extracted from the archive
462 are stamped with the time of extraction.
465 Use the full path name when matching names in the archive. @sc{gnu}
466 @command{ar} can not create an archive with a full path name (such archives
467 are not POSIX complaint), but other archive creators can. This option
468 will cause @sc{gnu} @command{ar} to match file names using a complete path
469 name, which can be convenient when extracting a single file from an
470 archive created by another tool.
473 @cindex writing archive index
474 Write an object-file index into the archive, or update an existing one,
475 even if no other change is made to the archive. You may use this modifier
476 flag either with any operation, or alone. Running @samp{ar s} on an
477 archive is equivalent to running @samp{ranlib} on it.
480 @cindex not writing archive index
481 Do not generate an archive symbol table. This can speed up building a
482 large library in several steps. The resulting archive can not be used
483 with the linker. In order to build a symbol table, you must omit the
484 @samp{S} modifier on the last execution of @samp{ar}, or you must run
485 @samp{ranlib} on the archive.
488 @cindex creating thin archive
489 Make the specified @var{archive} a @emph{thin} archive. If it already
490 exists and is a regular archive, the existing members must be present
491 in the same directory as @var{archive}.
494 @cindex updating an archive
495 Normally, @samp{ar r}@dots{} inserts all files
496 listed into the archive. If you would like to insert @emph{only} those
497 of the files you list that are newer than existing members of the same
498 names, use this modifier. The @samp{u} modifier is allowed only for the
499 operation @samp{r} (replace). In particular, the combination @samp{qu} is
500 not allowed, since checking the timestamps would lose any speed
501 advantage from the operation @samp{q}.
504 @cindex deterministic archives
505 @kindex --enable-deterministic-archives
506 Do @emph{not} operate in @emph{deterministic} mode. This is the inverse
507 of the @samp{D} modifier, above: added files and the archive index will
508 get their actual UID, GID, timestamp, and file mode values.
510 This is the default unless @file{binutils} was configured with
511 @option{--enable-deterministic-archives}.
514 This modifier requests the @emph{verbose} version of an operation. Many
515 operations display additional information, such as filenames processed,
516 when the modifier @samp{v} is appended.
519 This modifier shows the version number of @command{ar}.
522 The @command{ar} program also supports some command line options which
523 are neither modifiers nor actions, but which do change its behaviour
528 Displays the list of command line options supported by @command{ar}
532 Displays the version information of @command{ar} and then exits.
535 @command{ar} ignores an initial option spelt @samp{-X32_64}, for
536 compatibility with AIX. The behaviour produced by this option is the
537 default for @sc{gnu} @command{ar}. @command{ar} does not support any
538 of the other @samp{-X} options; in particular, it does not support
539 @option{-X32} which is the default for AIX @command{ar}.
541 @item --plugin @var{name}
543 The optional command line switch @option{--plugin @var{name}} causes
544 @command{ar} to load the plugin called @var{name} which adds support
545 for more file formats, including object files with link-time
546 optimization information.
548 This option is only available if the toolchain has been built with
549 plugin support enabled.
551 If @option{--plugin} is not provided, but plugin support has been
552 enabled then @command{ar} iterates over the files in
553 @file{$@{libdir@}/bfd-plugins} in alphabetic order and the first
554 plugin that claims the object in question is used.
556 Please note that this plugin search directory is @emph{not} the one
557 used by @command{ld}'s @option{-plugin} option. In order to make
558 @command{ar} use the linker plugin it must be copied into the
559 @file{$@{libdir@}/bfd-plugins} directory. For GCC based compilations
560 the linker plugin is called @file{liblto_plugin.so.0.0.0}. For Clang
561 based compilations it is called @file{LLVMgold.so}. The GCC plugin
562 is always backwards compatible with earlier versions, so it is
563 sufficient to just copy the newest one.
565 @item --target @var{target}
566 The optional command line switch @option{--target @var{bfdname}}
567 specifies that the archive members are in an object code format
568 different from your system's default format. See
569 @xref{Target Selection}, for more information.
574 @c man begin SEEALSO ar
575 nm(1), ranlib(1), and the Info entries for @file{binutils}.
580 @section Controlling @command{ar} with a Script
583 ar -M [ <@var{script} ]
586 @cindex MRI compatibility, @command{ar}
587 @cindex scripts, @command{ar}
588 If you use the single command-line option @samp{-M} with @command{ar}, you
589 can control its operation with a rudimentary command language. This
590 form of @command{ar} operates interactively if standard input is coming
591 directly from a terminal. During interactive use, @command{ar} prompts for
592 input (the prompt is @samp{AR >}), and continues executing even after
593 errors. If you redirect standard input to a script file, no prompts are
594 issued, and @command{ar} abandons execution (with a nonzero exit code)
597 The @command{ar} command language is @emph{not} designed to be equivalent
598 to the command-line options; in fact, it provides somewhat less control
599 over archives. The only purpose of the command language is to ease the
600 transition to @sc{gnu} @command{ar} for developers who already have scripts
601 written for the MRI ``librarian'' program.
603 The syntax for the @command{ar} command language is straightforward:
606 commands are recognized in upper or lower case; for example, @code{LIST}
607 is the same as @code{list}. In the following descriptions, commands are
608 shown in upper case for clarity.
611 a single command may appear on each line; it is the first word on the
615 empty lines are allowed, and have no effect.
618 comments are allowed; text after either of the characters @samp{*}
619 or @samp{;} is ignored.
622 Whenever you use a list of names as part of the argument to an @command{ar}
623 command, you can separate the individual names with either commas or
624 blanks. Commas are shown in the explanations below, for clarity.
627 @samp{+} is used as a line continuation character; if @samp{+} appears
628 at the end of a line, the text on the following line is considered part
629 of the current command.
632 Here are the commands you can use in @command{ar} scripts, or when using
633 @command{ar} interactively. Three of them have special significance:
635 @code{OPEN} or @code{CREATE} specify a @dfn{current archive}, which is
636 a temporary file required for most of the other commands.
638 @code{SAVE} commits the changes so far specified by the script. Prior
639 to @code{SAVE}, commands affect only the temporary copy of the current
643 @item ADDLIB @var{archive}
644 @itemx ADDLIB @var{archive} (@var{module}, @var{module}, @dots{} @var{module})
645 Add all the contents of @var{archive} (or, if specified, each named
646 @var{module} from @var{archive}) to the current archive.
648 Requires prior use of @code{OPEN} or @code{CREATE}.
650 @item ADDMOD @var{member}, @var{member}, @dots{} @var{member}
651 @c FIXME! w/Replacement?? If so, like "ar r @var{archive} @var{names}"
652 @c else like "ar q..."
653 Add each named @var{member} as a module in the current archive.
655 Requires prior use of @code{OPEN} or @code{CREATE}.
658 Discard the contents of the current archive, canceling the effect of
659 any operations since the last @code{SAVE}. May be executed (with no
660 effect) even if no current archive is specified.
662 @item CREATE @var{archive}
663 Creates an archive, and makes it the current archive (required for many
664 other commands). The new archive is created with a temporary name; it
665 is not actually saved as @var{archive} until you use @code{SAVE}.
666 You can overwrite existing archives; similarly, the contents of any
667 existing file named @var{archive} will not be destroyed until @code{SAVE}.
669 @item DELETE @var{module}, @var{module}, @dots{} @var{module}
670 Delete each listed @var{module} from the current archive; equivalent to
671 @samp{ar -d @var{archive} @var{module} @dots{} @var{module}}.
673 Requires prior use of @code{OPEN} or @code{CREATE}.
675 @item DIRECTORY @var{archive} (@var{module}, @dots{} @var{module})
676 @itemx DIRECTORY @var{archive} (@var{module}, @dots{} @var{module}) @var{outputfile}
677 List each named @var{module} present in @var{archive}. The separate
678 command @code{VERBOSE} specifies the form of the output: when verbose
679 output is off, output is like that of @samp{ar -t @var{archive}
680 @var{module}@dots{}}. When verbose output is on, the listing is like
681 @samp{ar -tv @var{archive} @var{module}@dots{}}.
683 Output normally goes to the standard output stream; however, if you
684 specify @var{outputfile} as a final argument, @command{ar} directs the
688 Exit from @command{ar}, with a @code{0} exit code to indicate successful
689 completion. This command does not save the output file; if you have
690 changed the current archive since the last @code{SAVE} command, those
693 @item EXTRACT @var{module}, @var{module}, @dots{} @var{module}
694 Extract each named @var{module} from the current archive, writing them
695 into the current directory as separate files. Equivalent to @samp{ar -x
696 @var{archive} @var{module}@dots{}}.
698 Requires prior use of @code{OPEN} or @code{CREATE}.
701 @c FIXME Tokens but no commands???
708 Display full contents of the current archive, in ``verbose'' style
709 regardless of the state of @code{VERBOSE}. The effect is like @samp{ar
710 tv @var{archive}}. (This single command is a @sc{gnu} @command{ar}
711 enhancement, rather than present for MRI compatibility.)
713 Requires prior use of @code{OPEN} or @code{CREATE}.
715 @item OPEN @var{archive}
716 Opens an existing archive for use as the current archive (required for
717 many other commands). Any changes as the result of subsequent commands
718 will not actually affect @var{archive} until you next use @code{SAVE}.
720 @item REPLACE @var{module}, @var{module}, @dots{} @var{module}
721 In the current archive, replace each existing @var{module} (named in
722 the @code{REPLACE} arguments) from files in the current working directory.
723 To execute this command without errors, both the file, and the module in
724 the current archive, must exist.
726 Requires prior use of @code{OPEN} or @code{CREATE}.
729 Toggle an internal flag governing the output from @code{DIRECTORY}.
730 When the flag is on, @code{DIRECTORY} output matches output from
731 @samp{ar -tv }@dots{}.
734 Commit your changes to the current archive, and actually save it as a
735 file with the name specified in the last @code{CREATE} or @code{OPEN}
738 Requires prior use of @code{OPEN} or @code{CREATE}.
747 The @sc{gnu} linker @command{ld} is now described in a separate manual.
748 @xref{Top,, Overview,, Using LD: the @sc{gnu} linker}.
756 @c man title nm list symbols from object files
759 @c man begin SYNOPSIS nm
760 nm [@option{-A}|@option{-o}|@option{--print-file-name}] [@option{-a}|@option{--debug-syms}]
761 [@option{-B}|@option{--format=bsd}] [@option{-C}|@option{--demangle}[=@var{style}]]
762 [@option{-D}|@option{--dynamic}] [@option{-f}@var{format}|@option{--format=}@var{format}]
763 [@option{-g}|@option{--extern-only}] [@option{-h}|@option{--help}]
764 [@option{-l}|@option{--line-numbers}] [@option{--inlines}]
765 [@option{-n}|@option{-v}|@option{--numeric-sort}]
766 [@option{-P}|@option{--portability}] [@option{-p}|@option{--no-sort}]
767 [@option{-r}|@option{--reverse-sort}] [@option{-S}|@option{--print-size}]
768 [@option{-s}|@option{--print-armap}] [@option{-t} @var{radix}|@option{--radix=}@var{radix}]
769 [@option{-u}|@option{--undefined-only}] [@option{-V}|@option{--version}]
770 [@option{-X 32_64}] [@option{--defined-only}] [@option{--no-demangle}]
771 [@option{--plugin} @var{name}] [@option{--size-sort}] [@option{--special-syms}]
772 [@option{--synthetic}] [@option{--with-symbol-versions}] [@option{--target=}@var{bfdname}]
773 [@var{objfile}@dots{}]
777 @c man begin DESCRIPTION nm
778 @sc{gnu} @command{nm} lists the symbols from object files @var{objfile}@dots{}.
779 If no object files are listed as arguments, @command{nm} assumes the file
782 For each symbol, @command{nm} shows:
786 The symbol value, in the radix selected by options (see below), or
787 hexadecimal by default.
790 The symbol type. At least the following types are used; others are, as
791 well, depending on the object file format. If lowercase, the symbol is
792 usually local; if uppercase, the symbol is global (external). There
793 are however a few lowercase symbols that are shown for special global
794 symbols (@code{u}, @code{v} and @code{w}).
796 @c Some more detail on exactly what these symbol types are used for
800 The symbol's value is absolute, and will not be changed by further
805 The symbol is in the uninitialized data section (known as BSS).
808 The symbol is common. Common symbols are uninitialized data. When
809 linking, multiple common symbols may appear with the same name. If the
810 symbol is defined anywhere, the common symbols are treated as undefined
813 For more details on common symbols, see the discussion of
814 --warn-common in @ref{Options,,Linker options,ld.info,The GNU linker}.
819 The symbol is in the initialized data section.
823 The symbol is in an initialized data section for small objects. Some
824 object file formats permit more efficient access to small data objects,
825 such as a global int variable as opposed to a large global array.
828 For PE format files this indicates that the symbol is in a section
829 specific to the implementation of DLLs. For ELF format files this
830 indicates that the symbol is an indirect function. This is a GNU
831 extension to the standard set of ELF symbol types. It indicates a
832 symbol which if referenced by a relocation does not evaluate to its
833 address, but instead must be invoked at runtime. The runtime
834 execution will then return the value to be used in the relocation.
837 The symbol is an indirect reference to another symbol.
840 The symbol is a debugging symbol.
843 The symbols is in a stack unwind section.
847 The symbol is in a read only data section.
851 The symbol is in an uninitialized data section for small objects.
855 The symbol is in the text (code) section.
858 The symbol is undefined.
861 The symbol is a unique global symbol. This is a GNU extension to the
862 standard set of ELF symbol bindings. For such a symbol the dynamic linker
863 will make sure that in the entire process there is just one symbol with
864 this name and type in use.
868 The symbol is a weak object. When a weak defined symbol is linked with
869 a normal defined symbol, the normal defined symbol is used with no error.
870 When a weak undefined symbol is linked and the symbol is not defined,
871 the value of the weak symbol becomes zero with no error. On some
872 systems, uppercase indicates that a default value has been specified.
876 The symbol is a weak symbol that has not been specifically tagged as a
877 weak object symbol. When a weak defined symbol is linked with a normal
878 defined symbol, the normal defined symbol is used with no error.
879 When a weak undefined symbol is linked and the symbol is not defined,
880 the value of the symbol is determined in a system-specific manner without
881 error. On some systems, uppercase indicates that a default value has been
885 The symbol is a stabs symbol in an a.out object file. In this case, the
886 next values printed are the stabs other field, the stabs desc field, and
887 the stab type. Stabs symbols are used to hold debugging information.
890 The symbol type is unknown, or object file format specific.
899 @c man begin OPTIONS nm
900 The long and short forms of options, shown here as alternatives, are
906 @itemx --print-file-name
907 @cindex input file name
909 @cindex source file name
910 Precede each symbol by the name of the input file (or archive member)
911 in which it was found, rather than identifying the input file once only,
912 before all of its symbols.
916 @cindex debugging symbols
917 Display all symbols, even debugger-only symbols; normally these are not
921 @cindex @command{nm} format
922 @cindex @command{nm} compatibility
923 The same as @option{--format=bsd} (for compatibility with the MIPS @command{nm}).
926 @itemx --demangle[=@var{style}]
927 @cindex demangling in nm
928 Decode (@dfn{demangle}) low-level symbol names into user-level names.
929 Besides removing any initial underscore prepended by the system, this
930 makes C++ function names readable. Different compilers have different
931 mangling styles. The optional demangling style argument can be used to
932 choose an appropriate demangling style for your compiler. @xref{c++filt},
933 for more information on demangling.
936 Do not demangle low-level symbol names. This is the default.
940 @cindex dynamic symbols
941 Display the dynamic symbols rather than the normal symbols. This is
942 only meaningful for dynamic objects, such as certain types of shared
945 @item -f @var{format}
946 @itemx --format=@var{format}
947 @cindex @command{nm} format
948 @cindex @command{nm} compatibility
949 Use the output format @var{format}, which can be @code{bsd},
950 @code{sysv}, or @code{posix}. The default is @code{bsd}.
951 Only the first character of @var{format} is significant; it can be
952 either upper or lower case.
956 @cindex external symbols
957 Display only external symbols.
961 Show a summary of the options to @command{nm} and exit.
964 @itemx --line-numbers
965 @cindex symbol line numbers
966 For each symbol, use debugging information to try to find a filename and
967 line number. For a defined symbol, look for the line number of the
968 address of the symbol. For an undefined symbol, look for the line
969 number of a relocation entry which refers to the symbol. If line number
970 information can be found, print it after the other symbol information.
973 @cindex objdump inlines
974 When option @option{-l} is active, if the address belongs to a
975 function that was inlined, then this option causes the source
976 information for all enclosing scopes back to the first non-inlined
977 function to be printed as well. For example, if @code{main} inlines
978 @code{callee1} which inlines @code{callee2}, and address is from
979 @code{callee2}, the source information for @code{callee1} and @code{main}
980 will also be printed.
984 @itemx --numeric-sort
985 Sort symbols numerically by their addresses, rather than alphabetically
990 @cindex sorting symbols
991 Do not bother to sort the symbols in any order; print them in the order
996 Use the POSIX.2 standard output format instead of the default format.
997 Equivalent to @samp{-f posix}.
1000 @itemx --reverse-sort
1001 Reverse the order of the sort (whether numeric or alphabetic); let the
1006 Print both value and size of defined symbols for the @code{bsd} output style.
1007 This option has no effect for object formats that do not record symbol
1008 sizes, unless @samp{--size-sort} is also used in which case a
1009 calculated size is displayed.
1012 @itemx --print-armap
1013 @cindex symbol index, listing
1014 When listing symbols from archive members, include the index: a mapping
1015 (stored in the archive by @command{ar} or @command{ranlib}) of which modules
1016 contain definitions for which names.
1018 @item -t @var{radix}
1019 @itemx --radix=@var{radix}
1020 Use @var{radix} as the radix for printing the symbol values. It must be
1021 @samp{d} for decimal, @samp{o} for octal, or @samp{x} for hexadecimal.
1024 @itemx --undefined-only
1025 @cindex external symbols
1026 @cindex undefined symbols
1027 Display only undefined symbols (those external to each object file).
1031 Show the version number of @command{nm} and exit.
1034 This option is ignored for compatibility with the AIX version of
1035 @command{nm}. It takes one parameter which must be the string
1036 @option{32_64}. The default mode of AIX @command{nm} corresponds
1037 to @option{-X 32}, which is not supported by @sc{gnu} @command{nm}.
1039 @item --defined-only
1040 @cindex external symbols
1041 @cindex undefined symbols
1042 Display only defined symbols for each object file.
1044 @item --plugin @var{name}
1046 Load the plugin called @var{name} to add support for extra target
1047 types. This option is only available if the toolchain has been built
1048 with plugin support enabled.
1050 If @option{--plugin} is not provided, but plugin support has been
1051 enabled then @command{nm} iterates over the files in
1052 @file{$@{libdir@}/bfd-plugins} in alphabetic order and the first
1053 plugin that claims the object in question is used.
1055 Please note that this plugin search directory is @emph{not} the one
1056 used by @command{ld}'s @option{-plugin} option. In order to make
1057 @command{nm} use the linker plugin it must be copied into the
1058 @file{$@{libdir@}/bfd-plugins} directory. For GCC based compilations
1059 the linker plugin is called @file{liblto_plugin.so.0.0.0}. For Clang
1060 based compilations it is called @file{LLVMgold.so}. The GCC plugin
1061 is always backwards compatible with earlier versions, so it is
1062 sufficient to just copy the newest one.
1065 Sort symbols by size. For ELF objects symbol sizes are read from the
1066 ELF, for other object types the symbol sizes are computed as the
1067 difference between the value of the symbol and the value of the symbol
1068 with the next higher value. If the @code{bsd} output format is used
1069 the size of the symbol is printed, rather than the value, and
1070 @samp{-S} must be used in order both size and value to be printed.
1072 @item --special-syms
1073 Display symbols which have a target-specific special meaning. These
1074 symbols are usually used by the target for some special processing and
1075 are not normally helpful when included in the normal symbol lists.
1076 For example for ARM targets this option would skip the mapping symbols
1077 used to mark transitions between ARM code, THUMB code and data.
1080 Include synthetic symbols in the output. These are special symbols
1081 created by the linker for various purposes. They are not shown by
1082 default since they are not part of the binary's original source code.
1084 @item --with-symbol-versions
1085 Enables the display of symbol version information if any exists. The
1086 version string is displayed as a suffix to the symbol name, preceeded by
1087 an @@ character. For example @samp{foo@@VER_1}. If the version is
1088 the default version to be used when resolving unversioned references
1089 to the symbol then it is displayed as a suffix preceeded by two @@
1090 characters. For example @samp{foo@@@@VER_2}.
1092 @item --target=@var{bfdname}
1093 @cindex object code format
1094 Specify an object code format other than your system's default format.
1095 @xref{Target Selection}, for more information.
1102 @c man begin SEEALSO nm
1103 ar(1), objdump(1), ranlib(1), and the Info entries for @file{binutils}.
1110 @c man title objcopy copy and translate object files
1113 @c man begin SYNOPSIS objcopy
1114 objcopy [@option{-F} @var{bfdname}|@option{--target=}@var{bfdname}]
1115 [@option{-I} @var{bfdname}|@option{--input-target=}@var{bfdname}]
1116 [@option{-O} @var{bfdname}|@option{--output-target=}@var{bfdname}]
1117 [@option{-B} @var{bfdarch}|@option{--binary-architecture=}@var{bfdarch}]
1118 [@option{-S}|@option{--strip-all}]
1119 [@option{-g}|@option{--strip-debug}]
1120 [@option{--strip-unneeded}]
1121 [@option{-K} @var{symbolname}|@option{--keep-symbol=}@var{symbolname}]
1122 [@option{-N} @var{symbolname}|@option{--strip-symbol=}@var{symbolname}]
1123 [@option{--strip-unneeded-symbol=}@var{symbolname}]
1124 [@option{-G} @var{symbolname}|@option{--keep-global-symbol=}@var{symbolname}]
1125 [@option{--localize-hidden}]
1126 [@option{-L} @var{symbolname}|@option{--localize-symbol=}@var{symbolname}]
1127 [@option{--globalize-symbol=}@var{symbolname}]
1128 [@option{-W} @var{symbolname}|@option{--weaken-symbol=}@var{symbolname}]
1129 [@option{-w}|@option{--wildcard}]
1130 [@option{-x}|@option{--discard-all}]
1131 [@option{-X}|@option{--discard-locals}]
1132 [@option{-b} @var{byte}|@option{--byte=}@var{byte}]
1133 [@option{-i} [@var{breadth}]|@option{--interleave}[=@var{breadth}]]
1134 [@option{--interleave-width=}@var{width}]
1135 [@option{-j} @var{sectionpattern}|@option{--only-section=}@var{sectionpattern}]
1136 [@option{-R} @var{sectionpattern}|@option{--remove-section=}@var{sectionpattern}]
1137 [@option{--remove-relocations=}@var{sectionpattern}]
1138 [@option{-p}|@option{--preserve-dates}]
1139 [@option{-D}|@option{--enable-deterministic-archives}]
1140 [@option{-U}|@option{--disable-deterministic-archives}]
1141 [@option{--debugging}]
1142 [@option{--gap-fill=}@var{val}]
1143 [@option{--pad-to=}@var{address}]
1144 [@option{--set-start=}@var{val}]
1145 [@option{--adjust-start=}@var{incr}]
1146 [@option{--change-addresses=}@var{incr}]
1147 [@option{--change-section-address} @var{sectionpattern}@{=,+,-@}@var{val}]
1148 [@option{--change-section-lma} @var{sectionpattern}@{=,+,-@}@var{val}]
1149 [@option{--change-section-vma} @var{sectionpattern}@{=,+,-@}@var{val}]
1150 [@option{--change-warnings}] [@option{--no-change-warnings}]
1151 [@option{--set-section-flags} @var{sectionpattern}=@var{flags}]
1152 [@option{--add-section} @var{sectionname}=@var{filename}]
1153 [@option{--dump-section} @var{sectionname}=@var{filename}]
1154 [@option{--update-section} @var{sectionname}=@var{filename}]
1155 [@option{--rename-section} @var{oldname}=@var{newname}[,@var{flags}]]
1156 [@option{--long-section-names} @{enable,disable,keep@}]
1157 [@option{--change-leading-char}] [@option{--remove-leading-char}]
1158 [@option{--reverse-bytes=}@var{num}]
1159 [@option{--srec-len=}@var{ival}] [@option{--srec-forceS3}]
1160 [@option{--redefine-sym} @var{old}=@var{new}]
1161 [@option{--redefine-syms=}@var{filename}]
1163 [@option{--keep-symbols=}@var{filename}]
1164 [@option{--strip-symbols=}@var{filename}]
1165 [@option{--strip-unneeded-symbols=}@var{filename}]
1166 [@option{--keep-global-symbols=}@var{filename}]
1167 [@option{--localize-symbols=}@var{filename}]
1168 [@option{--globalize-symbols=}@var{filename}]
1169 [@option{--weaken-symbols=}@var{filename}]
1170 [@option{--add-symbol} @var{name}=[@var{section}:]@var{value}[,@var{flags}]
1171 [@option{--alt-machine-code=}@var{index}]
1172 [@option{--prefix-symbols=}@var{string}]
1173 [@option{--prefix-sections=}@var{string}]
1174 [@option{--prefix-alloc-sections=}@var{string}]
1175 [@option{--add-gnu-debuglink=}@var{path-to-file}]
1176 [@option{--keep-file-symbols}]
1177 [@option{--only-keep-debug}]
1178 [@option{--strip-dwo}]
1179 [@option{--extract-dwo}]
1180 [@option{--extract-symbol}]
1181 [@option{--writable-text}]
1182 [@option{--readonly-text}]
1185 [@option{--file-alignment=}@var{num}]
1186 [@option{--heap=}@var{size}]
1187 [@option{--image-base=}@var{address}]
1188 [@option{--section-alignment=}@var{num}]
1189 [@option{--stack=}@var{size}]
1190 [@option{--subsystem=}@var{which}:@var{major}.@var{minor}]
1191 [@option{--compress-debug-sections}]
1192 [@option{--decompress-debug-sections}]
1193 [@option{--elf-stt-common=@var{val}}]
1194 [@option{--merge-notes}]
1195 [@option{--no-merge-notes}]
1196 [@option{-v}|@option{--verbose}]
1197 [@option{-V}|@option{--version}]
1198 [@option{--help}] [@option{--info}]
1199 @var{infile} [@var{outfile}]
1203 @c man begin DESCRIPTION objcopy
1204 The @sc{gnu} @command{objcopy} utility copies the contents of an object
1205 file to another. @command{objcopy} uses the @sc{gnu} @sc{bfd} Library to
1206 read and write the object files. It can write the destination object
1207 file in a format different from that of the source object file. The
1208 exact behavior of @command{objcopy} is controlled by command-line options.
1209 Note that @command{objcopy} should be able to copy a fully linked file
1210 between any two formats. However, copying a relocatable object file
1211 between any two formats may not work as expected.
1213 @command{objcopy} creates temporary files to do its translations and
1214 deletes them afterward. @command{objcopy} uses @sc{bfd} to do all its
1215 translation work; it has access to all the formats described in @sc{bfd}
1216 and thus is able to recognize most formats without being told
1217 explicitly. @xref{BFD,,BFD,ld.info,Using LD}.
1219 @command{objcopy} can be used to generate S-records by using an output
1220 target of @samp{srec} (e.g., use @samp{-O srec}).
1222 @command{objcopy} can be used to generate a raw binary file by using an
1223 output target of @samp{binary} (e.g., use @option{-O binary}). When
1224 @command{objcopy} generates a raw binary file, it will essentially produce
1225 a memory dump of the contents of the input object file. All symbols and
1226 relocation information will be discarded. The memory dump will start at
1227 the load address of the lowest section copied into the output file.
1229 When generating an S-record or a raw binary file, it may be helpful to
1230 use @option{-S} to remove sections containing debugging information. In
1231 some cases @option{-R} will be useful to remove sections which contain
1232 information that is not needed by the binary file.
1234 Note---@command{objcopy} is not able to change the endianness of its input
1235 files. If the input format has an endianness (some formats do not),
1236 @command{objcopy} can only copy the inputs into file formats that have the
1237 same endianness or which have no endianness (e.g., @samp{srec}).
1238 (However, see the @option{--reverse-bytes} option.)
1242 @c man begin OPTIONS objcopy
1246 @itemx @var{outfile}
1247 The input and output files, respectively.
1248 If you do not specify @var{outfile}, @command{objcopy} creates a
1249 temporary file and destructively renames the result with
1250 the name of @var{infile}.
1252 @item -I @var{bfdname}
1253 @itemx --input-target=@var{bfdname}
1254 Consider the source file's object format to be @var{bfdname}, rather than
1255 attempting to deduce it. @xref{Target Selection}, for more information.
1257 @item -O @var{bfdname}
1258 @itemx --output-target=@var{bfdname}
1259 Write the output file using the object format @var{bfdname}.
1260 @xref{Target Selection}, for more information.
1262 @item -F @var{bfdname}
1263 @itemx --target=@var{bfdname}
1264 Use @var{bfdname} as the object format for both the input and the output
1265 file; i.e., simply transfer data from source to destination with no
1266 translation. @xref{Target Selection}, for more information.
1268 @item -B @var{bfdarch}
1269 @itemx --binary-architecture=@var{bfdarch}
1270 Useful when transforming a architecture-less input file into an object file.
1271 In this case the output architecture can be set to @var{bfdarch}. This
1272 option will be ignored if the input file has a known @var{bfdarch}. You
1273 can access this binary data inside a program by referencing the special
1274 symbols that are created by the conversion process. These symbols are
1275 called _binary_@var{objfile}_start, _binary_@var{objfile}_end and
1276 _binary_@var{objfile}_size. e.g. you can transform a picture file into
1277 an object file and then access it in your code using these symbols.
1279 @item -j @var{sectionpattern}
1280 @itemx --only-section=@var{sectionpattern}
1281 Copy only the indicated sections from the input file to the output file.
1282 This option may be given more than once. Note that using this option
1283 inappropriately may make the output file unusable. Wildcard
1284 characters are accepted in @var{sectionpattern}.
1286 If the first character of @var{sectionpattern} is the exclamation
1287 point (!) then matching sections will not be copied, even if earlier
1288 use of @option{--only-section} on the same command line would
1289 otherwise copy it. For example:
1292 --only-section=.text.* --only-section=!.text.foo
1295 will copy all sectinos maching '.text.*' but not the section
1298 @item -R @var{sectionpattern}
1299 @itemx --remove-section=@var{sectionpattern}
1300 Remove any section matching @var{sectionpattern} from the output file.
1301 This option may be given more than once. Note that using this option
1302 inappropriately may make the output file unusable. Wildcard
1303 characters are accepted in @var{sectionpattern}. Using both the
1304 @option{-j} and @option{-R} options together results in undefined
1307 If the first character of @var{sectionpattern} is the exclamation
1308 point (!) then matching sections will not be removed even if an
1309 earlier use of @option{--remove-section} on the same command line
1310 would otherwise remove it. For example:
1313 --remove-section=.text.* --remove-section=!.text.foo
1316 will remove all sections matching the pattern '.text.*', but will not
1317 remove the section '.text.foo'.
1319 @item --remove-relocations=@var{sectionpattern}
1320 Remove relocations from the output file for any section matching
1321 @var{sectionpattern}. This option may be given more than once. Note
1322 that using this option inappropriately may make the output file
1323 unusable. Wildcard characters are accepted in @var{sectionpattern}.
1327 --remove-relocations=.text.*
1330 will remove the relocations for all sections matching the patter
1333 If the first character of @var{sectionpattern} is the exclamation
1334 point (!) then matching sections will not have their relocation
1335 removed even if an earlier use of @option{--remove-relocations} on the
1336 same command line would otherwise cause the relocations to be removed.
1340 --remove-relocations=.text.* --remove-relocations=!.text.foo
1343 will remove all relocations for sections matching the pattern
1344 '.text.*', but will not remove relocations for the section
1349 Do not copy relocation and symbol information from the source file.
1352 @itemx --strip-debug
1353 Do not copy debugging symbols or sections from the source file.
1355 @item --strip-unneeded
1356 Strip all symbols that are not needed for relocation processing.
1358 @item -K @var{symbolname}
1359 @itemx --keep-symbol=@var{symbolname}
1360 When stripping symbols, keep symbol @var{symbolname} even if it would
1361 normally be stripped. This option may be given more than once.
1363 @item -N @var{symbolname}
1364 @itemx --strip-symbol=@var{symbolname}
1365 Do not copy symbol @var{symbolname} from the source file. This option
1366 may be given more than once.
1368 @item --strip-unneeded-symbol=@var{symbolname}
1369 Do not copy symbol @var{symbolname} from the source file unless it is needed
1370 by a relocation. This option may be given more than once.
1372 @item -G @var{symbolname}
1373 @itemx --keep-global-symbol=@var{symbolname}
1374 Keep only symbol @var{symbolname} global. Make all other symbols local
1375 to the file, so that they are not visible externally. This option may
1376 be given more than once.
1378 @item --localize-hidden
1379 In an ELF object, mark all symbols that have hidden or internal visibility
1380 as local. This option applies on top of symbol-specific localization options
1381 such as @option{-L}.
1383 @item -L @var{symbolname}
1384 @itemx --localize-symbol=@var{symbolname}
1385 Convert a global or weak symbol called @var{symbolname} into a local
1386 symbol, so that it is not visible externally. This option may be
1387 given more than once. Note - unique symbols are not converted.
1389 @item -W @var{symbolname}
1390 @itemx --weaken-symbol=@var{symbolname}
1391 Make symbol @var{symbolname} weak. This option may be given more than once.
1393 @item --globalize-symbol=@var{symbolname}
1394 Give symbol @var{symbolname} global scoping so that it is visible
1395 outside of the file in which it is defined. This option may be given
1400 Permit regular expressions in @var{symbolname}s used in other command
1401 line options. The question mark (?), asterisk (*), backslash (\) and
1402 square brackets ([]) operators can be used anywhere in the symbol
1403 name. If the first character of the symbol name is the exclamation
1404 point (!) then the sense of the switch is reversed for that symbol.
1411 would cause objcopy to weaken all symbols that start with ``fo''
1412 except for the symbol ``foo''.
1415 @itemx --discard-all
1416 Do not copy non-global symbols from the source file.
1417 @c FIXME any reason to prefer "non-global" to "local" here?
1420 @itemx --discard-locals
1421 Do not copy compiler-generated local symbols.
1422 (These usually start with @samp{L} or @samp{.}.)
1425 @itemx --byte=@var{byte}
1426 If interleaving has been enabled via the @option{--interleave} option
1427 then start the range of bytes to keep at the @var{byte}th byte.
1428 @var{byte} can be in the range from 0 to @var{breadth}-1, where
1429 @var{breadth} is the value given by the @option{--interleave} option.
1431 @item -i [@var{breadth}]
1432 @itemx --interleave[=@var{breadth}]
1433 Only copy a range out of every @var{breadth} bytes. (Header data is
1434 not affected). Select which byte in the range begins the copy with
1435 the @option{--byte} option. Select the width of the range with the
1436 @option{--interleave-width} option.
1438 This option is useful for creating files to program @sc{rom}. It is
1439 typically used with an @code{srec} output target. Note that
1440 @command{objcopy} will complain if you do not specify the
1441 @option{--byte} option as well.
1443 The default interleave breadth is 4, so with @option{--byte} set to 0,
1444 @command{objcopy} would copy the first byte out of every four bytes
1445 from the input to the output.
1447 @item --interleave-width=@var{width}
1448 When used with the @option{--interleave} option, copy @var{width}
1449 bytes at a time. The start of the range of bytes to be copied is set
1450 by the @option{--byte} option, and the extent of the range is set with
1451 the @option{--interleave} option.
1453 The default value for this option is 1. The value of @var{width} plus
1454 the @var{byte} value set by the @option{--byte} option must not exceed
1455 the interleave breadth set by the @option{--interleave} option.
1457 This option can be used to create images for two 16-bit flashes interleaved
1458 in a 32-bit bus by passing @option{-b 0 -i 4 --interleave-width=2}
1459 and @option{-b 2 -i 4 --interleave-width=2} to two @command{objcopy}
1460 commands. If the input was '12345678' then the outputs would be
1461 '1256' and '3478' respectively.
1464 @itemx --preserve-dates
1465 Set the access and modification dates of the output file to be the same
1466 as those of the input file.
1469 @itemx --enable-deterministic-archives
1470 @cindex deterministic archives
1471 @kindex --enable-deterministic-archives
1472 Operate in @emph{deterministic} mode. When copying archive members
1473 and writing the archive index, use zero for UIDs, GIDs, timestamps,
1474 and use consistent file modes for all files.
1476 If @file{binutils} was configured with
1477 @option{--enable-deterministic-archives}, then this mode is on by default.
1478 It can be disabled with the @samp{-U} option, below.
1481 @itemx --disable-deterministic-archives
1482 @cindex deterministic archives
1483 @kindex --enable-deterministic-archives
1484 Do @emph{not} operate in @emph{deterministic} mode. This is the
1485 inverse of the @option{-D} option, above: when copying archive members
1486 and writing the archive index, use their actual UID, GID, timestamp,
1487 and file mode values.
1489 This is the default unless @file{binutils} was configured with
1490 @option{--enable-deterministic-archives}.
1493 Convert debugging information, if possible. This is not the default
1494 because only certain debugging formats are supported, and the
1495 conversion process can be time consuming.
1497 @item --gap-fill @var{val}
1498 Fill gaps between sections with @var{val}. This operation applies to
1499 the @emph{load address} (LMA) of the sections. It is done by increasing
1500 the size of the section with the lower address, and filling in the extra
1501 space created with @var{val}.
1503 @item --pad-to @var{address}
1504 Pad the output file up to the load address @var{address}. This is
1505 done by increasing the size of the last section. The extra space is
1506 filled in with the value specified by @option{--gap-fill} (default zero).
1508 @item --set-start @var{val}
1509 Set the start address of the new file to @var{val}. Not all object file
1510 formats support setting the start address.
1512 @item --change-start @var{incr}
1513 @itemx --adjust-start @var{incr}
1514 @cindex changing start address
1515 Change the start address by adding @var{incr}. Not all object file
1516 formats support setting the start address.
1518 @item --change-addresses @var{incr}
1519 @itemx --adjust-vma @var{incr}
1520 @cindex changing object addresses
1521 Change the VMA and LMA addresses of all sections, as well as the start
1522 address, by adding @var{incr}. Some object file formats do not permit
1523 section addresses to be changed arbitrarily. Note that this does not
1524 relocate the sections; if the program expects sections to be loaded at a
1525 certain address, and this option is used to change the sections such
1526 that they are loaded at a different address, the program may fail.
1528 @item --change-section-address @var{sectionpattern}@{=,+,-@}@var{val}
1529 @itemx --adjust-section-vma @var{sectionpattern}@{=,+,-@}@var{val}
1530 @cindex changing section address
1531 Set or change both the VMA address and the LMA address of any section
1532 matching @var{sectionpattern}. If @samp{=} is used, the section
1533 address is set to @var{val}. Otherwise, @var{val} is added to or
1534 subtracted from the section address. See the comments under
1535 @option{--change-addresses}, above. If @var{sectionpattern} does not
1536 match any sections in the input file, a warning will be issued, unless
1537 @option{--no-change-warnings} is used.
1539 @item --change-section-lma @var{sectionpattern}@{=,+,-@}@var{val}
1540 @cindex changing section LMA
1541 Set or change the LMA address of any sections matching
1542 @var{sectionpattern}. The LMA address is the address where the
1543 section will be loaded into memory at program load time. Normally
1544 this is the same as the VMA address, which is the address of the
1545 section at program run time, but on some systems, especially those
1546 where a program is held in ROM, the two can be different. If @samp{=}
1547 is used, the section address is set to @var{val}. Otherwise,
1548 @var{val} is added to or subtracted from the section address. See the
1549 comments under @option{--change-addresses}, above. If
1550 @var{sectionpattern} does not match any sections in the input file, a
1551 warning will be issued, unless @option{--no-change-warnings} is used.
1553 @item --change-section-vma @var{sectionpattern}@{=,+,-@}@var{val}
1554 @cindex changing section VMA
1555 Set or change the VMA address of any section matching
1556 @var{sectionpattern}. The VMA address is the address where the
1557 section will be located once the program has started executing.
1558 Normally this is the same as the LMA address, which is the address
1559 where the section will be loaded into memory, but on some systems,
1560 especially those where a program is held in ROM, the two can be
1561 different. If @samp{=} is used, the section address is set to
1562 @var{val}. Otherwise, @var{val} is added to or subtracted from the
1563 section address. See the comments under @option{--change-addresses},
1564 above. If @var{sectionpattern} does not match any sections in the
1565 input file, a warning will be issued, unless
1566 @option{--no-change-warnings} is used.
1568 @item --change-warnings
1569 @itemx --adjust-warnings
1570 If @option{--change-section-address} or @option{--change-section-lma} or
1571 @option{--change-section-vma} is used, and the section pattern does not
1572 match any sections, issue a warning. This is the default.
1574 @item --no-change-warnings
1575 @itemx --no-adjust-warnings
1576 Do not issue a warning if @option{--change-section-address} or
1577 @option{--adjust-section-lma} or @option{--adjust-section-vma} is used, even
1578 if the section pattern does not match any sections.
1580 @item --set-section-flags @var{sectionpattern}=@var{flags}
1581 Set the flags for any sections matching @var{sectionpattern}. The
1582 @var{flags} argument is a comma separated string of flag names. The
1583 recognized names are @samp{alloc}, @samp{contents}, @samp{load},
1584 @samp{noload}, @samp{readonly}, @samp{code}, @samp{data}, @samp{rom},
1585 @samp{share}, and @samp{debug}. You can set the @samp{contents} flag
1586 for a section which does not have contents, but it is not meaningful
1587 to clear the @samp{contents} flag of a section which does have
1588 contents--just remove the section instead. Not all flags are
1589 meaningful for all object file formats.
1591 @item --add-section @var{sectionname}=@var{filename}
1592 Add a new section named @var{sectionname} while copying the file. The
1593 contents of the new section are taken from the file @var{filename}. The
1594 size of the section will be the size of the file. This option only
1595 works on file formats which can support sections with arbitrary names.
1596 Note - it may be necessary to use the @option{--set-section-flags}
1597 option to set the attributes of the newly created section.
1599 @item --dump-section @var{sectionname}=@var{filename}
1600 Place the contents of section named @var{sectionname} into the file
1601 @var{filename}, overwriting any contents that may have been there
1602 previously. This option is the inverse of @option{--add-section}.
1603 This option is similar to the @option{--only-section} option except
1604 that it does not create a formatted file, it just dumps the contents
1605 as raw binary data, without applying any relocations. The option can
1606 be specified more than once.
1608 @item --update-section @var{sectionname}=@var{filename}
1609 Replace the existing contents of a section named @var{sectionname}
1610 with the contents of file @var{filename}. The size of the section
1611 will be adjusted to the size of the file. The section flags for
1612 @var{sectionname} will be unchanged. For ELF format files the section
1613 to segment mapping will also remain unchanged, something which is not
1614 possible using @option{--remove-section} followed by
1615 @option{--add-section}. The option can be specified more than once.
1617 Note - it is possible to use @option{--rename-section} and
1618 @option{--update-section} to both update and rename a section from one
1619 command line. In this case, pass the original section name to
1620 @option{--update-section}, and the original and new section names to
1621 @option{--rename-section}.
1623 @item --add-symbol @var{name}=[@var{section}:]@var{value}[,@var{flags}]
1624 Add a new symbol named @var{name} while copying the file. This option may be
1625 specified multiple times. If the @var{section} is given, the symbol will be
1626 associated with and relative to that section, otherwise it will be an ABS
1627 symbol. Specifying an undefined section will result in a fatal error. There
1628 is no check for the value, it will be taken as specified. Symbol flags can
1629 be specified and not all flags will be meaningful for all object file
1630 formats. By default, the symbol will be global. The special flag
1631 'before=@var{othersym}' will insert the new symbol in front of the specified
1632 @var{othersym}, otherwise the symbol(s) will be added at the end of the
1633 symbol table in the order they appear.
1635 @item --rename-section @var{oldname}=@var{newname}[,@var{flags}]
1636 Rename a section from @var{oldname} to @var{newname}, optionally
1637 changing the section's flags to @var{flags} in the process. This has
1638 the advantage over using a linker script to perform the rename in that
1639 the output stays as an object file and does not become a linked
1642 This option is particularly helpful when the input format is binary,
1643 since this will always create a section called .data. If for example,
1644 you wanted instead to create a section called .rodata containing binary
1645 data you could use the following command line to achieve it:
1648 objcopy -I binary -O <output_format> -B <architecture> \
1649 --rename-section .data=.rodata,alloc,load,readonly,data,contents \
1650 <input_binary_file> <output_object_file>
1653 @item --long-section-names @{enable,disable,keep@}
1654 Controls the handling of long section names when processing @code{COFF}
1655 and @code{PE-COFF} object formats. The default behaviour, @samp{keep},
1656 is to preserve long section names if any are present in the input file.
1657 The @samp{enable} and @samp{disable} options forcibly enable or disable
1658 the use of long section names in the output object; when @samp{disable}
1659 is in effect, any long section names in the input object will be truncated.
1660 The @samp{enable} option will only emit long section names if any are
1661 present in the inputs; this is mostly the same as @samp{keep}, but it
1662 is left undefined whether the @samp{enable} option might force the
1663 creation of an empty string table in the output file.
1665 @item --change-leading-char
1666 Some object file formats use special characters at the start of
1667 symbols. The most common such character is underscore, which compilers
1668 often add before every symbol. This option tells @command{objcopy} to
1669 change the leading character of every symbol when it converts between
1670 object file formats. If the object file formats use the same leading
1671 character, this option has no effect. Otherwise, it will add a
1672 character, or remove a character, or change a character, as
1675 @item --remove-leading-char
1676 If the first character of a global symbol is a special symbol leading
1677 character used by the object file format, remove the character. The
1678 most common symbol leading character is underscore. This option will
1679 remove a leading underscore from all global symbols. This can be useful
1680 if you want to link together objects of different file formats with
1681 different conventions for symbol names. This is different from
1682 @option{--change-leading-char} because it always changes the symbol name
1683 when appropriate, regardless of the object file format of the output
1686 @item --reverse-bytes=@var{num}
1687 Reverse the bytes in a section with output contents. A section length must
1688 be evenly divisible by the value given in order for the swap to be able to
1689 take place. Reversing takes place before the interleaving is performed.
1691 This option is used typically in generating ROM images for problematic
1692 target systems. For example, on some target boards, the 32-bit words
1693 fetched from 8-bit ROMs are re-assembled in little-endian byte order
1694 regardless of the CPU byte order. Depending on the programming model, the
1695 endianness of the ROM may need to be modified.
1697 Consider a simple file with a section containing the following eight
1698 bytes: @code{12345678}.
1700 Using @samp{--reverse-bytes=2} for the above example, the bytes in the
1701 output file would be ordered @code{21436587}.
1703 Using @samp{--reverse-bytes=4} for the above example, the bytes in the
1704 output file would be ordered @code{43218765}.
1706 By using @samp{--reverse-bytes=2} for the above example, followed by
1707 @samp{--reverse-bytes=4} on the output file, the bytes in the second
1708 output file would be ordered @code{34127856}.
1710 @item --srec-len=@var{ival}
1711 Meaningful only for srec output. Set the maximum length of the Srecords
1712 being produced to @var{ival}. This length covers both address, data and
1715 @item --srec-forceS3
1716 Meaningful only for srec output. Avoid generation of S1/S2 records,
1717 creating S3-only record format.
1719 @item --redefine-sym @var{old}=@var{new}
1720 Change the name of a symbol @var{old}, to @var{new}. This can be useful
1721 when one is trying link two things together for which you have no
1722 source, and there are name collisions.
1724 @item --redefine-syms=@var{filename}
1725 Apply @option{--redefine-sym} to each symbol pair "@var{old} @var{new}"
1726 listed in the file @var{filename}. @var{filename} is simply a flat file,
1727 with one symbol pair per line. Line comments may be introduced by the hash
1728 character. This option may be given more than once.
1731 Change all global symbols in the file to be weak. This can be useful
1732 when building an object which will be linked against other objects using
1733 the @option{-R} option to the linker. This option is only effective when
1734 using an object file format which supports weak symbols.
1736 @item --keep-symbols=@var{filename}
1737 Apply @option{--keep-symbol} option to each symbol listed in the file
1738 @var{filename}. @var{filename} is simply a flat file, with one symbol
1739 name per line. Line comments may be introduced by the hash character.
1740 This option may be given more than once.
1742 @item --strip-symbols=@var{filename}
1743 Apply @option{--strip-symbol} option to each symbol listed in the file
1744 @var{filename}. @var{filename} is simply a flat file, with one symbol
1745 name per line. Line comments may be introduced by the hash character.
1746 This option may be given more than once.
1748 @item --strip-unneeded-symbols=@var{filename}
1749 Apply @option{--strip-unneeded-symbol} option to each symbol listed in
1750 the file @var{filename}. @var{filename} is simply a flat file, with one
1751 symbol name per line. Line comments may be introduced by the hash
1752 character. This option may be given more than once.
1754 @item --keep-global-symbols=@var{filename}
1755 Apply @option{--keep-global-symbol} option to each symbol listed in the
1756 file @var{filename}. @var{filename} is simply a flat file, with one
1757 symbol name per line. Line comments may be introduced by the hash
1758 character. This option may be given more than once.
1760 @item --localize-symbols=@var{filename}
1761 Apply @option{--localize-symbol} option to each symbol listed in the file
1762 @var{filename}. @var{filename} is simply a flat file, with one symbol
1763 name per line. Line comments may be introduced by the hash character.
1764 This option may be given more than once.
1766 @item --globalize-symbols=@var{filename}
1767 Apply @option{--globalize-symbol} option to each symbol listed in the file
1768 @var{filename}. @var{filename} is simply a flat file, with one symbol
1769 name per line. Line comments may be introduced by the hash character.
1770 This option may be given more than once.
1772 @item --weaken-symbols=@var{filename}
1773 Apply @option{--weaken-symbol} option to each symbol listed in the file
1774 @var{filename}. @var{filename} is simply a flat file, with one symbol
1775 name per line. Line comments may be introduced by the hash character.
1776 This option may be given more than once.
1778 @item --alt-machine-code=@var{index}
1779 If the output architecture has alternate machine codes, use the
1780 @var{index}th code instead of the default one. This is useful in case
1781 a machine is assigned an official code and the tool-chain adopts the
1782 new code, but other applications still depend on the original code
1783 being used. For ELF based architectures if the @var{index}
1784 alternative does not exist then the value is treated as an absolute
1785 number to be stored in the e_machine field of the ELF header.
1787 @item --writable-text
1788 Mark the output text as writable. This option isn't meaningful for all
1789 object file formats.
1791 @item --readonly-text
1792 Make the output text write protected. This option isn't meaningful for all
1793 object file formats.
1796 Mark the output file as demand paged. This option isn't meaningful for all
1797 object file formats.
1800 Mark the output file as impure. This option isn't meaningful for all
1801 object file formats.
1803 @item --prefix-symbols=@var{string}
1804 Prefix all symbols in the output file with @var{string}.
1806 @item --prefix-sections=@var{string}
1807 Prefix all section names in the output file with @var{string}.
1809 @item --prefix-alloc-sections=@var{string}
1810 Prefix all the names of all allocated sections in the output file with
1813 @item --add-gnu-debuglink=@var{path-to-file}
1814 Creates a .gnu_debuglink section which contains a reference to
1815 @var{path-to-file} and adds it to the output file. Note: the file at
1816 @var{path-to-file} must exist. Part of the process of adding the
1817 .gnu_debuglink section involves embedding a checksum of the contents
1818 of the debug info file into the section.
1820 If the debug info file is built in one location but it is going to be
1821 installed at a later time into a different location then do not use
1822 the path to the installed location. The @option{--add-gnu-debuglink}
1823 option will fail because the installed file does not exist yet.
1824 Instead put the debug info file in the current directory and use the
1825 @option{--add-gnu-debuglink} option without any directory components,
1829 objcopy --add-gnu-debuglink=foo.debug
1832 At debug time the debugger will attempt to look for the separate debug
1833 info file in a set of known locations. The exact set of these
1834 locations varies depending upon the distribution being used, but it
1839 @item * The same directory as the executable.
1841 @item * A sub-directory of the directory containing the executable
1844 @item * A global debug directory such as /usr/lib/debug.
1847 As long as the debug info file has been installed into one of these
1848 locations before the debugger is run everything should work
1851 @item --keep-file-symbols
1852 When stripping a file, perhaps with @option{--strip-debug} or
1853 @option{--strip-unneeded}, retain any symbols specifying source file names,
1854 which would otherwise get stripped.
1856 @item --only-keep-debug
1857 Strip a file, removing contents of any sections that would not be
1858 stripped by @option{--strip-debug} and leaving the debugging sections
1859 intact. In ELF files, this preserves all note sections in the output.
1861 Note - the section headers of the stripped sections are preserved,
1862 including their sizes, but the contents of the section are discarded.
1863 The section headers are preserved so that other tools can match up the
1864 debuginfo file with the real executable, even if that executable has
1865 been relocated to a different address space.
1867 The intention is that this option will be used in conjunction with
1868 @option{--add-gnu-debuglink} to create a two part executable. One a
1869 stripped binary which will occupy less space in RAM and in a
1870 distribution and the second a debugging information file which is only
1871 needed if debugging abilities are required. The suggested procedure
1872 to create these files is as follows:
1875 @item Link the executable as normal. Assuming that is is called
1877 @item Run @code{objcopy --only-keep-debug foo foo.dbg} to
1878 create a file containing the debugging info.
1879 @item Run @code{objcopy --strip-debug foo} to create a
1880 stripped executable.
1881 @item Run @code{objcopy --add-gnu-debuglink=foo.dbg foo}
1882 to add a link to the debugging info into the stripped executable.
1885 Note---the choice of @code{.dbg} as an extension for the debug info
1886 file is arbitrary. Also the @code{--only-keep-debug} step is
1887 optional. You could instead do this:
1890 @item Link the executable as normal.
1891 @item Copy @code{foo} to @code{foo.full}
1892 @item Run @code{objcopy --strip-debug foo}
1893 @item Run @code{objcopy --add-gnu-debuglink=foo.full foo}
1896 i.e., the file pointed to by the @option{--add-gnu-debuglink} can be the
1897 full executable. It does not have to be a file created by the
1898 @option{--only-keep-debug} switch.
1900 Note---this switch is only intended for use on fully linked files. It
1901 does not make sense to use it on object files where the debugging
1902 information may be incomplete. Besides the gnu_debuglink feature
1903 currently only supports the presence of one filename containing
1904 debugging information, not multiple filenames on a one-per-object-file
1908 Remove the contents of all DWARF .dwo sections, leaving the
1909 remaining debugging sections and all symbols intact.
1910 This option is intended for use by the compiler as part of
1911 the @option{-gsplit-dwarf} option, which splits debug information
1912 between the .o file and a separate .dwo file. The compiler
1913 generates all debug information in the same file, then uses
1914 the @option{--extract-dwo} option to copy the .dwo sections to
1915 the .dwo file, then the @option{--strip-dwo} option to remove
1916 those sections from the original .o file.
1919 Extract the contents of all DWARF .dwo sections. See the
1920 @option{--strip-dwo} option for more information.
1922 @item --file-alignment @var{num}
1923 Specify the file alignment. Sections in the file will always begin at
1924 file offsets which are multiples of this number. This defaults to
1926 [This option is specific to PE targets.]
1928 @item --heap @var{reserve}
1929 @itemx --heap @var{reserve},@var{commit}
1930 Specify the number of bytes of memory to reserve (and optionally commit)
1931 to be used as heap for this program.
1932 [This option is specific to PE targets.]
1934 @item --image-base @var{value}
1935 Use @var{value} as the base address of your program or dll. This is
1936 the lowest memory location that will be used when your program or dll
1937 is loaded. To reduce the need to relocate and improve performance of
1938 your dlls, each should have a unique base address and not overlap any
1939 other dlls. The default is 0x400000 for executables, and 0x10000000
1941 [This option is specific to PE targets.]
1943 @item --section-alignment @var{num}
1944 Sets the section alignment. Sections in memory will always begin at
1945 addresses which are a multiple of this number. Defaults to 0x1000.
1946 [This option is specific to PE targets.]
1948 @item --stack @var{reserve}
1949 @itemx --stack @var{reserve},@var{commit}
1950 Specify the number of bytes of memory to reserve (and optionally commit)
1951 to be used as stack for this program.
1952 [This option is specific to PE targets.]
1954 @item --subsystem @var{which}
1955 @itemx --subsystem @var{which}:@var{major}
1956 @itemx --subsystem @var{which}:@var{major}.@var{minor}
1957 Specifies the subsystem under which your program will execute. The
1958 legal values for @var{which} are @code{native}, @code{windows},
1959 @code{console}, @code{posix}, @code{efi-app}, @code{efi-bsd},
1960 @code{efi-rtd}, @code{sal-rtd}, and @code{xbox}. You may optionally set
1961 the subsystem version also. Numeric values are also accepted for
1963 [This option is specific to PE targets.]
1965 @item --extract-symbol
1966 Keep the file's section flags and symbols but remove all section data.
1967 Specifically, the option:
1970 @item removes the contents of all sections;
1971 @item sets the size of every section to zero; and
1972 @item sets the file's start address to zero.
1975 This option is used to build a @file{.sym} file for a VxWorks kernel.
1976 It can also be a useful way of reducing the size of a @option{--just-symbols}
1979 @item --compress-debug-sections
1980 Compress DWARF debug sections using zlib with SHF_COMPRESSED from the
1981 ELF ABI. Note - if compression would actually make a section
1982 @emph{larger}, then it is not compressed.
1984 @item --compress-debug-sections=none
1985 @itemx --compress-debug-sections=zlib
1986 @itemx --compress-debug-sections=zlib-gnu
1987 @itemx --compress-debug-sections=zlib-gabi
1988 For ELF files, these options control how DWARF debug sections are
1989 compressed. @option{--compress-debug-sections=none} is equivalent
1990 to @option{--decompress-debug-sections}.
1991 @option{--compress-debug-sections=zlib} and
1992 @option{--compress-debug-sections=zlib-gabi} are equivalent to
1993 @option{--compress-debug-sections}.
1994 @option{--compress-debug-sections=zlib-gnu} compresses DWARF debug
1995 sections using zlib. The debug sections are renamed to begin with
1996 @samp{.zdebug} instead of @samp{.debug}. Note - if compression would
1997 actually make a section @emph{larger}, then it is not compressed nor
2000 @item --decompress-debug-sections
2001 Decompress DWARF debug sections using zlib. The original section
2002 names of the compressed sections are restored.
2004 @item --elf-stt-common=yes
2005 @itemx --elf-stt-common=no
2006 For ELF files, these options control whether common symbols should be
2007 converted to the @code{STT_COMMON} or @code{STT_OBJECT} type.
2008 @option{--elf-stt-common=yes} converts common symbol type to
2009 @code{STT_COMMON}. @option{--elf-stt-common=no} converts common symbol
2010 type to @code{STT_OBJECT}.
2013 @itemx --no-merge-notes
2014 For ELF files, attempt (or do not attempt) to reduce the size of any
2015 SHT_NOTE type sections by removing duplicate notes.
2019 Show the version number of @command{objcopy}.
2023 Verbose output: list all object files modified. In the case of
2024 archives, @samp{objcopy -V} lists all members of the archive.
2027 Show a summary of the options to @command{objcopy}.
2030 Display a list showing all architectures and object formats available.
2036 @c man begin SEEALSO objcopy
2037 ld(1), objdump(1), and the Info entries for @file{binutils}.
2044 @cindex object file information
2047 @c man title objdump display information from object files.
2050 @c man begin SYNOPSIS objdump
2051 objdump [@option{-a}|@option{--archive-headers}]
2052 [@option{-b} @var{bfdname}|@option{--target=@var{bfdname}}]
2053 [@option{-C}|@option{--demangle}[=@var{style}] ]
2054 [@option{-d}|@option{--disassemble}]
2055 [@option{-D}|@option{--disassemble-all}]
2056 [@option{-z}|@option{--disassemble-zeroes}]
2057 [@option{-EB}|@option{-EL}|@option{--endian=}@{big | little @}]
2058 [@option{-f}|@option{--file-headers}]
2059 [@option{-F}|@option{--file-offsets}]
2060 [@option{--file-start-context}]
2061 [@option{-g}|@option{--debugging}]
2062 [@option{-e}|@option{--debugging-tags}]
2063 [@option{-h}|@option{--section-headers}|@option{--headers}]
2064 [@option{-i}|@option{--info}]
2065 [@option{-j} @var{section}|@option{--section=}@var{section}]
2066 [@option{-l}|@option{--line-numbers}]
2067 [@option{-S}|@option{--source}]
2068 [@option{-m} @var{machine}|@option{--architecture=}@var{machine}]
2069 [@option{-M} @var{options}|@option{--disassembler-options=}@var{options}]
2070 [@option{-p}|@option{--private-headers}]
2071 [@option{-P} @var{options}|@option{--private=}@var{options}]
2072 [@option{-r}|@option{--reloc}]
2073 [@option{-R}|@option{--dynamic-reloc}]
2074 [@option{-s}|@option{--full-contents}]
2075 [@option{-W[lLiaprmfFsoRtUuTgAckK]}|
2076 @option{--dwarf}[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links]
2077 [@option{-G}|@option{--stabs}]
2078 [@option{-t}|@option{--syms}]
2079 [@option{-T}|@option{--dynamic-syms}]
2080 [@option{-x}|@option{--all-headers}]
2081 [@option{-w}|@option{--wide}]
2082 [@option{--start-address=}@var{address}]
2083 [@option{--stop-address=}@var{address}]
2084 [@option{--prefix-addresses}]
2085 [@option{--[no-]show-raw-insn}]
2086 [@option{--adjust-vma=}@var{offset}]
2087 [@option{--dwarf-depth=@var{n}}]
2088 [@option{--dwarf-start=@var{n}}]
2089 [@option{--special-syms}]
2090 [@option{--prefix=}@var{prefix}]
2091 [@option{--prefix-strip=}@var{level}]
2092 [@option{--insn-width=}@var{width}]
2093 [@option{-V}|@option{--version}]
2094 [@option{-H}|@option{--help}]
2095 @var{objfile}@dots{}
2099 @c man begin DESCRIPTION objdump
2101 @command{objdump} displays information about one or more object files.
2102 The options control what particular information to display. This
2103 information is mostly useful to programmers who are working on the
2104 compilation tools, as opposed to programmers who just want their
2105 program to compile and work.
2107 @var{objfile}@dots{} are the object files to be examined. When you
2108 specify archives, @command{objdump} shows information on each of the member
2113 @c man begin OPTIONS objdump
2115 The long and short forms of options, shown here as alternatives, are
2116 equivalent. At least one option from the list
2117 @option{-a,-d,-D,-e,-f,-g,-G,-h,-H,-p,-P,-r,-R,-s,-S,-t,-T,-V,-x} must be given.
2121 @itemx --archive-header
2122 @cindex archive headers
2123 If any of the @var{objfile} files are archives, display the archive
2124 header information (in a format similar to @samp{ls -l}). Besides the
2125 information you could list with @samp{ar tv}, @samp{objdump -a} shows
2126 the object file format of each archive member.
2128 @item --adjust-vma=@var{offset}
2129 @cindex section addresses in objdump
2130 @cindex VMA in objdump
2131 When dumping information, first add @var{offset} to all the section
2132 addresses. This is useful if the section addresses do not correspond to
2133 the symbol table, which can happen when putting sections at particular
2134 addresses when using a format which can not represent section addresses,
2137 @item -b @var{bfdname}
2138 @itemx --target=@var{bfdname}
2139 @cindex object code format
2140 Specify that the object-code format for the object files is
2141 @var{bfdname}. This option may not be necessary; @var{objdump} can
2142 automatically recognize many formats.
2146 objdump -b oasys -m vax -h fu.o
2149 displays summary information from the section headers (@option{-h}) of
2150 @file{fu.o}, which is explicitly identified (@option{-m}) as a VAX object
2151 file in the format produced by Oasys compilers. You can list the
2152 formats available with the @option{-i} option.
2153 @xref{Target Selection}, for more information.
2156 @itemx --demangle[=@var{style}]
2157 @cindex demangling in objdump
2158 Decode (@dfn{demangle}) low-level symbol names into user-level names.
2159 Besides removing any initial underscore prepended by the system, this
2160 makes C++ function names readable. Different compilers have different
2161 mangling styles. The optional demangling style argument can be used to
2162 choose an appropriate demangling style for your compiler. @xref{c++filt},
2163 for more information on demangling.
2167 Display debugging information. This attempts to parse STABS and IEEE
2168 debugging format information stored in the file and print it out using
2169 a C like syntax. If neither of these formats are found this option
2170 falls back on the @option{-W} option to print any DWARF information in
2174 @itemx --debugging-tags
2175 Like @option{-g}, but the information is generated in a format compatible
2179 @itemx --disassemble
2180 @cindex disassembling object code
2181 @cindex machine instructions
2182 Display the assembler mnemonics for the machine instructions from
2183 @var{objfile}. This option only disassembles those sections which are
2184 expected to contain instructions.
2187 @itemx --disassemble-all
2188 Like @option{-d}, but disassemble the contents of all sections, not just
2189 those expected to contain instructions.
2191 This option also has a subtle effect on the disassembly of
2192 instructions in code sections. When option @option{-d} is in effect
2193 objdump will assume that any symbols present in a code section occur
2194 on the boundary between instructions and it will refuse to disassemble
2195 across such a boundary. When option @option{-D} is in effect however
2196 this assumption is supressed. This means that it is possible for the
2197 output of @option{-d} and @option{-D} to differ if, for example, data
2198 is stored in code sections.
2200 If the target is an ARM architecture this switch also has the effect
2201 of forcing the disassembler to decode pieces of data found in code
2202 sections as if they were instructions.
2204 @item --prefix-addresses
2205 When disassembling, print the complete address on each line. This is
2206 the older disassembly format.
2210 @itemx --endian=@{big|little@}
2212 @cindex disassembly endianness
2213 Specify the endianness of the object files. This only affects
2214 disassembly. This can be useful when disassembling a file format which
2215 does not describe endianness information, such as S-records.
2218 @itemx --file-headers
2219 @cindex object file header
2220 Display summary information from the overall header of
2221 each of the @var{objfile} files.
2224 @itemx --file-offsets
2225 @cindex object file offsets
2226 When disassembling sections, whenever a symbol is displayed, also
2227 display the file offset of the region of data that is about to be
2228 dumped. If zeroes are being skipped, then when disassembly resumes,
2229 tell the user how many zeroes were skipped and the file offset of the
2230 location from where the disassembly resumes. When dumping sections,
2231 display the file offset of the location from where the dump starts.
2233 @item --file-start-context
2234 @cindex source code context
2235 Specify that when displaying interlisted source code/disassembly
2236 (assumes @option{-S}) from a file that has not yet been displayed, extend the
2237 context to the start of the file.
2240 @itemx --section-headers
2242 @cindex section headers
2243 Display summary information from the section headers of the
2246 File segments may be relocated to nonstandard addresses, for example by
2247 using the @option{-Ttext}, @option{-Tdata}, or @option{-Tbss} options to
2248 @command{ld}. However, some object file formats, such as a.out, do not
2249 store the starting address of the file segments. In those situations,
2250 although @command{ld} relocates the sections correctly, using @samp{objdump
2251 -h} to list the file section headers cannot show the correct addresses.
2252 Instead, it shows the usual addresses, which are implicit for the
2255 Note, in some cases it is possible for a section to have both the
2256 READONLY and the NOREAD attributes set. In such cases the NOREAD
2257 attribute takes precedence, but @command{objdump} will report both
2258 since the exact setting of the flag bits might be important.
2262 Print a summary of the options to @command{objdump} and exit.
2266 @cindex architectures available
2267 @cindex object formats available
2268 Display a list showing all architectures and object formats available
2269 for specification with @option{-b} or @option{-m}.
2272 @itemx --section=@var{name}
2273 @cindex section information
2274 Display information only for section @var{name}.
2277 @itemx --line-numbers
2278 @cindex source filenames for object files
2279 Label the display (using debugging information) with the filename and
2280 source line numbers corresponding to the object code or relocs shown.
2281 Only useful with @option{-d}, @option{-D}, or @option{-r}.
2283 @item -m @var{machine}
2284 @itemx --architecture=@var{machine}
2285 @cindex architecture
2286 @cindex disassembly architecture
2287 Specify the architecture to use when disassembling object files. This
2288 can be useful when disassembling object files which do not describe
2289 architecture information, such as S-records. You can list the available
2290 architectures with the @option{-i} option.
2292 If the target is an ARM architecture then this switch has an
2293 additional effect. It restricts the disassembly to only those
2294 instructions supported by the architecture specified by @var{machine}.
2295 If it is necessary to use this switch because the input file does not
2296 contain any architecture information, but it is also desired to
2297 disassemble all the instructions use @option{-marm}.
2299 @item -M @var{options}
2300 @itemx --disassembler-options=@var{options}
2301 Pass target specific information to the disassembler. Only supported on
2302 some targets. If it is necessary to specify more than one
2303 disassembler option then multiple @option{-M} options can be used or
2304 can be placed together into a comma separated list.
2306 For ARC, @option{dsp} controls the printing of DSP instructions,
2307 @option{spfp} selects the printing of FPX single precision FP
2308 instructions, @option{dpfp} selects the printing of FPX double
2309 precision FP instructions, @option{quarkse_em} selects the printing of
2310 special QuarkSE-EM instructions, @option{fpuda} selects the printing
2311 of double precision assist instructions, @option{fpus} selects the
2312 printing of FPU single precision FP instructions, while @option{fpud}
2313 selects the printing of FPU souble precision FP instructions.
2314 Additionally, one can choose to have all the immediates printed in
2315 hexadecimal using @option{hex}. By default, the short immediates are
2316 printed using the decimal representation, while the long immediate
2317 values are printed as hexadecimal.
2319 @option{cpu=...} allows to enforce a particular ISA when disassembling
2320 instructions, overriding the @option{-m} value or whatever is in the ELF file.
2321 This might be useful to select ARC EM or HS ISA, because architecture is same
2322 for those and disassembler relies on private ELF header data to decide if code
2323 is for EM or HS. This option might be specified multiple times - only the
2324 latest value will be used. Valid values are same as for the assembler
2325 @option{-mcpu=...} option.
2327 If the target is an ARM architecture then this switch can be used to
2328 select which register name set is used during disassembler. Specifying
2329 @option{-M reg-names-std} (the default) will select the register names as
2330 used in ARM's instruction set documentation, but with register 13 called
2331 'sp', register 14 called 'lr' and register 15 called 'pc'. Specifying
2332 @option{-M reg-names-apcs} will select the name set used by the ARM
2333 Procedure Call Standard, whilst specifying @option{-M reg-names-raw} will
2334 just use @samp{r} followed by the register number.
2336 There are also two variants on the APCS register naming scheme enabled
2337 by @option{-M reg-names-atpcs} and @option{-M reg-names-special-atpcs} which
2338 use the ARM/Thumb Procedure Call Standard naming conventions. (Either
2339 with the normal register names or the special register names).
2341 This option can also be used for ARM architectures to force the
2342 disassembler to interpret all instructions as Thumb instructions by
2343 using the switch @option{--disassembler-options=force-thumb}. This can be
2344 useful when attempting to disassemble thumb code produced by other
2347 For the x86, some of the options duplicate functions of the @option{-m}
2348 switch, but allow finer grained control. Multiple selections from the
2349 following may be specified as a comma separated string.
2354 Select disassembly for the given architecture.
2358 Select between intel syntax mode and AT&T syntax mode.
2362 Select between AMD64 ISA and Intel64 ISA.
2364 @item intel-mnemonic
2366 Select between intel mnemonic mode and AT&T mnemonic mode.
2367 Note: @code{intel-mnemonic} implies @code{intel} and
2368 @code{att-mnemonic} implies @code{att}.
2375 Specify the default address size and operand size. These four options
2376 will be overridden if @code{x86-64}, @code{i386} or @code{i8086}
2377 appear later in the option string.
2380 When in AT&T mode, instructs the disassembler to print a mnemonic
2381 suffix even when the suffix could be inferred by the operands.
2384 For PowerPC, the @option{-M} argument @option{raw} selects
2385 disasssembly of hardware insns rather than aliases. For example, you
2386 will see @code{rlwinm} rather than @code{clrlwi}, and @code{addi}
2387 rather than @code{li}. All of the @option{-m} arguments for
2388 @command{gas} that select a CPU are supported. These are:
2389 @option{403}, @option{405}, @option{440}, @option{464}, @option{476},
2390 @option{601}, @option{603}, @option{604}, @option{620}, @option{7400},
2391 @option{7410}, @option{7450}, @option{7455}, @option{750cl},
2392 @option{821}, @option{850}, @option{860}, @option{a2}, @option{booke},
2393 @option{booke32}, @option{cell}, @option{com}, @option{e200z4},
2394 @option{e300}, @option{e500}, @option{e500mc}, @option{e500mc64},
2395 @option{e500x2}, @option{e5500}, @option{e6500}, @option{efs},
2396 @option{power4}, @option{power5}, @option{power6}, @option{power7},
2397 @option{power8}, @option{power9}, @option{ppc}, @option{ppc32},
2398 @option{ppc64}, @option{ppc64bridge}, @option{ppcps}, @option{pwr},
2399 @option{pwr2}, @option{pwr4}, @option{pwr5}, @option{pwr5x},
2400 @option{pwr6}, @option{pwr7}, @option{pwr8}, @option{pwr9},
2401 @option{pwrx}, @option{titan}, and @option{vle}.
2402 @option{32} and @option{64} modify the default or a prior CPU
2403 selection, disabling and enabling 64-bit insns respectively. In
2404 addition, @option{altivec}, @option{any}, @option{htm}, @option{vsx},
2405 and @option{spe} add capabilities to a previous @emph{or later} CPU
2406 selection. @option{any} will disassemble any opcode known to
2407 binutils, but in cases where an opcode has two different meanings or
2408 different arguments, you may not see the disassembly you expect.
2409 If you disassemble without giving a CPU selection, a default will be
2410 chosen from information gleaned by BFD from the object files headers,
2411 but the result again may not be as you expect.
2413 For MIPS, this option controls the printing of instruction mnemonic
2414 names and register names in disassembled instructions. Multiple
2415 selections from the following may be specified as a comma separated
2416 string, and invalid options are ignored:
2420 Print the 'raw' instruction mnemonic instead of some pseudo
2421 instruction mnemonic. I.e., print 'daddu' or 'or' instead of 'move',
2422 'sll' instead of 'nop', etc.
2425 Disassemble MSA instructions.
2428 Disassemble the virtualization ASE instructions.
2431 Disassemble the eXtended Physical Address (XPA) ASE instructions.
2433 @item gpr-names=@var{ABI}
2434 Print GPR (general-purpose register) names as appropriate
2435 for the specified ABI. By default, GPR names are selected according to
2436 the ABI of the binary being disassembled.
2438 @item fpr-names=@var{ABI}
2439 Print FPR (floating-point register) names as
2440 appropriate for the specified ABI. By default, FPR numbers are printed
2443 @item cp0-names=@var{ARCH}
2444 Print CP0 (system control coprocessor; coprocessor 0) register names
2445 as appropriate for the CPU or architecture specified by
2446 @var{ARCH}. By default, CP0 register names are selected according to
2447 the architecture and CPU of the binary being disassembled.
2449 @item hwr-names=@var{ARCH}
2450 Print HWR (hardware register, used by the @code{rdhwr} instruction) names
2451 as appropriate for the CPU or architecture specified by
2452 @var{ARCH}. By default, HWR names are selected according to
2453 the architecture and CPU of the binary being disassembled.
2455 @item reg-names=@var{ABI}
2456 Print GPR and FPR names as appropriate for the selected ABI.
2458 @item reg-names=@var{ARCH}
2459 Print CPU-specific register names (CP0 register and HWR names)
2460 as appropriate for the selected CPU or architecture.
2463 For any of the options listed above, @var{ABI} or
2464 @var{ARCH} may be specified as @samp{numeric} to have numbers printed
2465 rather than names, for the selected types of registers.
2466 You can list the available values of @var{ABI} and @var{ARCH} using
2467 the @option{--help} option.
2469 For VAX, you can specify function entry addresses with @option{-M
2470 entry:0xf00ba}. You can use this multiple times to properly
2471 disassemble VAX binary files that don't contain symbol tables (like
2472 ROM dumps). In these cases, the function entry mask would otherwise
2473 be decoded as VAX instructions, which would probably lead the rest
2474 of the function being wrongly disassembled.
2477 @itemx --private-headers
2478 Print information that is specific to the object file format. The exact
2479 information printed depends upon the object file format. For some
2480 object file formats, no additional information is printed.
2482 @item -P @var{options}
2483 @itemx --private=@var{options}
2484 Print information that is specific to the object file format. The
2485 argument @var{options} is a comma separated list that depends on the
2486 format (the lists of options is displayed with the help).
2488 For XCOFF, the available options are:
2504 Not all object formats support this option. In particular the ELF
2505 format does not use it.
2509 @cindex relocation entries, in object file
2510 Print the relocation entries of the file. If used with @option{-d} or
2511 @option{-D}, the relocations are printed interspersed with the
2515 @itemx --dynamic-reloc
2516 @cindex dynamic relocation entries, in object file
2517 Print the dynamic relocation entries of the file. This is only
2518 meaningful for dynamic objects, such as certain types of shared
2519 libraries. As for @option{-r}, if used with @option{-d} or
2520 @option{-D}, the relocations are printed interspersed with the
2524 @itemx --full-contents
2525 @cindex sections, full contents
2526 @cindex object file sections
2527 Display the full contents of any sections requested. By default all
2528 non-empty sections are displayed.
2532 @cindex source disassembly
2533 @cindex disassembly, with source
2534 Display source code intermixed with disassembly, if possible. Implies
2537 @item --prefix=@var{prefix}
2538 @cindex Add prefix to absolute paths
2539 Specify @var{prefix} to add to the absolute paths when used with
2542 @item --prefix-strip=@var{level}
2543 @cindex Strip absolute paths
2544 Indicate how many initial directory names to strip off the hardwired
2545 absolute paths. It has no effect without @option{--prefix=}@var{prefix}.
2547 @item --show-raw-insn
2548 When disassembling instructions, print the instruction in hex as well as
2549 in symbolic form. This is the default except when
2550 @option{--prefix-addresses} is used.
2552 @item --no-show-raw-insn
2553 When disassembling instructions, do not print the instruction bytes.
2554 This is the default when @option{--prefix-addresses} is used.
2556 @item --insn-width=@var{width}
2557 @cindex Instruction width
2558 Display @var{width} bytes on a single line when disassembling
2561 @item -W[lLiaprmfFsoRtUuTgAckK]
2562 @itemx --dwarf[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links]
2563 @include debug.options.texi
2566 Enable additional checks for consistency of Dwarf information.
2572 @cindex debug symbols
2573 @cindex ELF object file format
2574 Display the full contents of any sections requested. Display the
2575 contents of the .stab and .stab.index and .stab.excl sections from an
2576 ELF file. This is only useful on systems (such as Solaris 2.0) in which
2577 @code{.stab} debugging symbol-table entries are carried in an ELF
2578 section. In most other file formats, debugging symbol-table entries are
2579 interleaved with linkage symbols, and are visible in the @option{--syms}
2582 @item --start-address=@var{address}
2583 @cindex start-address
2584 Start displaying data at the specified address. This affects the output
2585 of the @option{-d}, @option{-r} and @option{-s} options.
2587 @item --stop-address=@var{address}
2588 @cindex stop-address
2589 Stop displaying data at the specified address. This affects the output
2590 of the @option{-d}, @option{-r} and @option{-s} options.
2594 @cindex symbol table entries, printing
2595 Print the symbol table entries of the file.
2596 This is similar to the information provided by the @samp{nm} program,
2597 although the display format is different. The format of the output
2598 depends upon the format of the file being dumped, but there are two main
2599 types. One looks like this:
2602 [ 4](sec 3)(fl 0x00)(ty 0)(scl 3) (nx 1) 0x00000000 .bss
2603 [ 6](sec 1)(fl 0x00)(ty 0)(scl 2) (nx 0) 0x00000000 fred
2606 where the number inside the square brackets is the number of the entry
2607 in the symbol table, the @var{sec} number is the section number, the
2608 @var{fl} value are the symbol's flag bits, the @var{ty} number is the
2609 symbol's type, the @var{scl} number is the symbol's storage class and
2610 the @var{nx} value is the number of auxilary entries associated with
2611 the symbol. The last two fields are the symbol's value and its name.
2613 The other common output format, usually seen with ELF based files,
2617 00000000 l d .bss 00000000 .bss
2618 00000000 g .text 00000000 fred
2621 Here the first number is the symbol's value (sometimes refered to as
2622 its address). The next field is actually a set of characters and
2623 spaces indicating the flag bits that are set on the symbol. These
2624 characters are described below. Next is the section with which the
2625 symbol is associated or @emph{*ABS*} if the section is absolute (ie
2626 not connected with any section), or @emph{*UND*} if the section is
2627 referenced in the file being dumped, but not defined there.
2629 After the section name comes another field, a number, which for common
2630 symbols is the alignment and for other symbol is the size. Finally
2631 the symbol's name is displayed.
2633 The flag characters are divided into 7 groups as follows:
2639 The symbol is a local (l), global (g), unique global (u), neither
2640 global nor local (a space) or both global and local (!). A
2641 symbol can be neither local or global for a variety of reasons, e.g.,
2642 because it is used for debugging, but it is probably an indication of
2643 a bug if it is ever both local and global. Unique global symbols are
2644 a GNU extension to the standard set of ELF symbol bindings. For such
2645 a symbol the dynamic linker will make sure that in the entire process
2646 there is just one symbol with this name and type in use.
2649 The symbol is weak (w) or strong (a space).
2652 The symbol denotes a constructor (C) or an ordinary symbol (a space).
2655 The symbol is a warning (W) or a normal symbol (a space). A warning
2656 symbol's name is a message to be displayed if the symbol following the
2657 warning symbol is ever referenced.
2661 The symbol is an indirect reference to another symbol (I), a function
2662 to be evaluated during reloc processing (i) or a normal symbol (a
2667 The symbol is a debugging symbol (d) or a dynamic symbol (D) or a
2668 normal symbol (a space).
2673 The symbol is the name of a function (F) or a file (f) or an object
2674 (O) or just a normal symbol (a space).
2678 @itemx --dynamic-syms
2679 @cindex dynamic symbol table entries, printing
2680 Print the dynamic symbol table entries of the file. This is only
2681 meaningful for dynamic objects, such as certain types of shared
2682 libraries. This is similar to the information provided by the @samp{nm}
2683 program when given the @option{-D} (@option{--dynamic}) option.
2685 The output format is similar to that produced by the @option{--syms}
2686 option, except that an extra field is inserted before the symbol's
2687 name, giving the version information associated with the symbol.
2688 If the version is the default version to be used when resolving
2689 unversioned references to the symbol then it's displayed as is,
2690 otherwise it's put into parentheses.
2692 @item --special-syms
2693 When displaying symbols include those which the target considers to be
2694 special in some way and which would not normally be of interest to the
2699 Print the version number of @command{objdump} and exit.
2702 @itemx --all-headers
2703 @cindex all header information, object file
2704 @cindex header information, all
2705 Display all available header information, including the symbol table and
2706 relocation entries. Using @option{-x} is equivalent to specifying all of
2707 @option{-a -f -h -p -r -t}.
2711 @cindex wide output, printing
2712 Format some lines for output devices that have more than 80 columns.
2713 Also do not truncate symbol names when they are displayed.
2716 @itemx --disassemble-zeroes
2717 Normally the disassembly output will skip blocks of zeroes. This
2718 option directs the disassembler to disassemble those blocks, just like
2725 @c man begin SEEALSO objdump
2726 nm(1), readelf(1), and the Info entries for @file{binutils}.
2734 @cindex archive contents
2735 @cindex symbol index
2737 @c man title ranlib generate index to archive.
2740 @c man begin SYNOPSIS ranlib
2741 ranlib [@option{--plugin} @var{name}] [@option{-DhHvVt}] @var{archive}
2745 @c man begin DESCRIPTION ranlib
2747 @command{ranlib} generates an index to the contents of an archive and
2748 stores it in the archive. The index lists each symbol defined by a
2749 member of an archive that is a relocatable object file.
2751 You may use @samp{nm -s} or @samp{nm --print-armap} to list this index.
2753 An archive with such an index speeds up linking to the library and
2754 allows routines in the library to call each other without regard to
2755 their placement in the archive.
2757 The @sc{gnu} @command{ranlib} program is another form of @sc{gnu} @command{ar}; running
2758 @command{ranlib} is completely equivalent to executing @samp{ar -s}.
2763 @c man begin OPTIONS ranlib
2769 Show usage information for @command{ranlib}.
2774 Show the version number of @command{ranlib}.
2777 @cindex deterministic archives
2778 @kindex --enable-deterministic-archives
2779 Operate in @emph{deterministic} mode. The symbol map archive member's
2780 header will show zero for the UID, GID, and timestamp. When this
2781 option is used, multiple runs will produce identical output files.
2783 If @file{binutils} was configured with
2784 @option{--enable-deterministic-archives}, then this mode is on by
2785 default. It can be disabled with the @samp{-U} option, described
2789 Update the timestamp of the symbol map of an archive.
2792 @cindex deterministic archives
2793 @kindex --enable-deterministic-archives
2794 Do @emph{not} operate in @emph{deterministic} mode. This is the
2795 inverse of the @samp{-D} option, above: the archive index will get
2796 actual UID, GID, timestamp, and file mode values.
2798 If @file{binutils} was configured @emph{without}
2799 @option{--enable-deterministic-archives}, then this mode is on by
2807 @c man begin SEEALSO ranlib
2808 ar(1), nm(1), and the Info entries for @file{binutils}.
2816 @cindex section sizes
2818 @c man title size list section sizes and total size.
2821 @c man begin SYNOPSIS size
2822 size [@option{-A}|@option{-B}|@option{--format=}@var{compatibility}]
2824 [@option{-d}|@option{-o}|@option{-x}|@option{--radix=}@var{number}]
2826 [@option{-t}|@option{--totals}]
2827 [@option{--target=}@var{bfdname}] [@option{-V}|@option{--version}]
2828 [@var{objfile}@dots{}]
2832 @c man begin DESCRIPTION size
2834 The @sc{gnu} @command{size} utility lists the section sizes---and the total
2835 size---for each of the object or archive files @var{objfile} in its
2836 argument list. By default, one line of output is generated for each
2837 object file or each module in an archive.
2839 @var{objfile}@dots{} are the object files to be examined.
2840 If none are specified, the file @code{a.out} will be used.
2844 @c man begin OPTIONS size
2846 The command line options have the following meanings:
2851 @itemx --format=@var{compatibility}
2852 @cindex @command{size} display format
2853 Using one of these options, you can choose whether the output from @sc{gnu}
2854 @command{size} resembles output from System V @command{size} (using @option{-A},
2855 or @option{--format=sysv}), or Berkeley @command{size} (using @option{-B}, or
2856 @option{--format=berkeley}). The default is the one-line format similar to
2858 @c Bonus for doc-source readers: you can also say --format=strange (or
2859 @c anything else that starts with 's') for sysv, and --format=boring (or
2860 @c anything else that starts with 'b') for Berkeley.
2862 Here is an example of the Berkeley (default) format of output from
2865 $ size --format=Berkeley ranlib size
2866 text data bss dec hex filename
2867 294880 81920 11592 388392 5ed28 ranlib
2868 294880 81920 11888 388688 5ee50 size
2872 This is the same data, but displayed closer to System V conventions:
2875 $ size --format=SysV ranlib size
2893 Show a summary of acceptable arguments and options.
2898 @itemx --radix=@var{number}
2899 @cindex @command{size} number format
2900 @cindex radix for section sizes
2901 Using one of these options, you can control whether the size of each
2902 section is given in decimal (@option{-d}, or @option{--radix=10}); octal
2903 (@option{-o}, or @option{--radix=8}); or hexadecimal (@option{-x}, or
2904 @option{--radix=16}). In @option{--radix=@var{number}}, only the three
2905 values (8, 10, 16) are supported. The total size is always given in two
2906 radices; decimal and hexadecimal for @option{-d} or @option{-x} output, or
2907 octal and hexadecimal if you're using @option{-o}.
2910 Print total size of common symbols in each file. When using Berkeley
2911 format these are included in the bss size.
2915 Show totals of all objects listed (Berkeley format listing mode only).
2917 @item --target=@var{bfdname}
2918 @cindex object code format
2919 Specify that the object-code format for @var{objfile} is
2920 @var{bfdname}. This option may not be necessary; @command{size} can
2921 automatically recognize many formats.
2922 @xref{Target Selection}, for more information.
2926 Display the version number of @command{size}.
2932 @c man begin SEEALSO size
2933 ar(1), objdump(1), readelf(1), and the Info entries for @file{binutils}.
2940 @cindex listings strings
2941 @cindex printing strings
2942 @cindex strings, printing
2944 @c man title strings print the strings of printable characters in files.
2947 @c man begin SYNOPSIS strings
2948 strings [@option{-afovV}] [@option{-}@var{min-len}]
2949 [@option{-n} @var{min-len}] [@option{--bytes=}@var{min-len}]
2950 [@option{-t} @var{radix}] [@option{--radix=}@var{radix}]
2951 [@option{-e} @var{encoding}] [@option{--encoding=}@var{encoding}]
2952 [@option{-}] [@option{--all}] [@option{--print-file-name}]
2953 [@option{-T} @var{bfdname}] [@option{--target=}@var{bfdname}]
2954 [@option{-w}] [@option{--include-all-whitespace}]
2955 [@option{-s}] [@option{--output-separator}@var{sep_string}]
2956 [@option{--help}] [@option{--version}] @var{file}@dots{}
2960 @c man begin DESCRIPTION strings
2962 For each @var{file} given, @sc{gnu} @command{strings} prints the
2963 printable character sequences that are at least 4 characters long (or
2964 the number given with the options below) and are followed by an
2965 unprintable character.
2967 Depending upon how the strings program was configured it will default
2968 to either displaying all the printable sequences that it can find in
2969 each file, or only those sequences that are in loadable, initialized
2970 data sections. If the file type in unrecognizable, or if strings is
2971 reading from stdin then it will always display all of the printable
2972 sequences that it can find.
2974 For backwards compatibility any file that occurs after a command line
2975 option of just @option{-} will also be scanned in full, regardless of
2976 the presence of any @option{-d} option.
2978 @command{strings} is mainly useful for determining the contents of
2983 @c man begin OPTIONS strings
2989 Scan the whole file, regardless of what sections it contains or
2990 whether those sections are loaded or initialized. Normally this is
2991 the default behaviour, but strings can be configured so that the
2992 @option{-d} is the default instead.
2994 The @option{-} option is position dependent and forces strings to
2995 perform full scans of any file that is mentioned after the @option{-}
2996 on the command line, even if the @option{-d} option has been
3001 Only print strings from initialized, loaded data sections in the
3002 file. This may reduce the amount of garbage in the output, but it
3003 also exposes the strings program to any security flaws that may be
3004 present in the BFD library used to scan and load sections. Strings
3005 can be configured so that this option is the default behaviour. In
3006 such cases the @option{-a} option can be used to avoid using the BFD
3007 library and instead just print all of the strings found in the file.
3010 @itemx --print-file-name
3011 Print the name of the file before each string.
3014 Print a summary of the program usage on the standard output and exit.
3016 @item -@var{min-len}
3017 @itemx -n @var{min-len}
3018 @itemx --bytes=@var{min-len}
3019 Print sequences of characters that are at least @var{min-len} characters
3020 long, instead of the default 4.
3023 Like @samp{-t o}. Some other versions of @command{strings} have @option{-o}
3024 act like @samp{-t d} instead. Since we can not be compatible with both
3025 ways, we simply chose one.
3027 @item -t @var{radix}
3028 @itemx --radix=@var{radix}
3029 Print the offset within the file before each string. The single
3030 character argument specifies the radix of the offset---@samp{o} for
3031 octal, @samp{x} for hexadecimal, or @samp{d} for decimal.
3033 @item -e @var{encoding}
3034 @itemx --encoding=@var{encoding}
3035 Select the character encoding of the strings that are to be found.
3036 Possible values for @var{encoding} are: @samp{s} = single-7-bit-byte
3037 characters (ASCII, ISO 8859, etc., default), @samp{S} =
3038 single-8-bit-byte characters, @samp{b} = 16-bit bigendian, @samp{l} =
3039 16-bit littleendian, @samp{B} = 32-bit bigendian, @samp{L} = 32-bit
3040 littleendian. Useful for finding wide character strings. (@samp{l}
3041 and @samp{b} apply to, for example, Unicode UTF-16/UCS-2 encodings).
3043 @item -T @var{bfdname}
3044 @itemx --target=@var{bfdname}
3045 @cindex object code format
3046 Specify an object code format other than your system's default format.
3047 @xref{Target Selection}, for more information.
3052 Print the program version number on the standard output and exit.
3055 @itemx --include-all-whitespace
3056 By default tab and space characters are included in the strings that
3057 are displayed, but other whitespace characters, such a newlines and
3058 carriage returns, are not. The @option{-w} option changes this so
3059 that all whitespace characters are considered to be part of a string.
3062 @itemx --output-separator
3063 By default, output strings are delimited by a new-line. This option
3064 allows you to supply any string to be used as the output record
3065 separator. Useful with --include-all-whitespace where strings
3066 may contain new-lines internally.
3072 @c man begin SEEALSO strings
3073 ar(1), nm(1), objdump(1), ranlib(1), readelf(1)
3074 and the Info entries for @file{binutils}.
3082 @cindex removing symbols
3083 @cindex discarding symbols
3084 @cindex symbols, discarding
3086 @c man title strip Discard symbols from object files.
3089 @c man begin SYNOPSIS strip
3090 strip [@option{-F} @var{bfdname} |@option{--target=}@var{bfdname}]
3091 [@option{-I} @var{bfdname} |@option{--input-target=}@var{bfdname}]
3092 [@option{-O} @var{bfdname} |@option{--output-target=}@var{bfdname}]
3093 [@option{-s}|@option{--strip-all}]
3094 [@option{-S}|@option{-g}|@option{-d}|@option{--strip-debug}]
3095 [@option{--strip-dwo}]
3096 [@option{-K} @var{symbolname}|@option{--keep-symbol=}@var{symbolname}]
3097 [@option{-M}|@option{--merge-notes}][@option{--no-merge-notes}]
3098 [@option{-N} @var{symbolname} |@option{--strip-symbol=}@var{symbolname}]
3099 [@option{-w}|@option{--wildcard}]
3100 [@option{-x}|@option{--discard-all}] [@option{-X} |@option{--discard-locals}]
3101 [@option{-R} @var{sectionname} |@option{--remove-section=}@var{sectionname}]
3102 [@option{--remove-relocations=}@var{sectionpattern}]
3103 [@option{-o} @var{file}] [@option{-p}|@option{--preserve-dates}]
3104 [@option{-D}|@option{--enable-deterministic-archives}]
3105 [@option{-U}|@option{--disable-deterministic-archives}]
3106 [@option{--keep-file-symbols}]
3107 [@option{--only-keep-debug}]
3108 [@option{-v} |@option{--verbose}] [@option{-V}|@option{--version}]
3109 [@option{--help}] [@option{--info}]
3110 @var{objfile}@dots{}
3114 @c man begin DESCRIPTION strip
3116 @sc{gnu} @command{strip} discards all symbols from object files
3117 @var{objfile}. The list of object files may include archives.
3118 At least one object file must be given.
3120 @command{strip} modifies the files named in its argument,
3121 rather than writing modified copies under different names.
3125 @c man begin OPTIONS strip
3128 @item -F @var{bfdname}
3129 @itemx --target=@var{bfdname}
3130 Treat the original @var{objfile} as a file with the object
3131 code format @var{bfdname}, and rewrite it in the same format.
3132 @xref{Target Selection}, for more information.
3135 Show a summary of the options to @command{strip} and exit.
3138 Display a list showing all architectures and object formats available.
3140 @item -I @var{bfdname}
3141 @itemx --input-target=@var{bfdname}
3142 Treat the original @var{objfile} as a file with the object
3143 code format @var{bfdname}.
3144 @xref{Target Selection}, for more information.
3146 @item -O @var{bfdname}
3147 @itemx --output-target=@var{bfdname}
3148 Replace @var{objfile} with a file in the output format @var{bfdname}.
3149 @xref{Target Selection}, for more information.
3151 @item -R @var{sectionname}
3152 @itemx --remove-section=@var{sectionname}
3153 Remove any section named @var{sectionname} from the output file, in
3154 addition to whatever sections would otherwise be removed. This
3155 option may be given more than once. Note that using this option
3156 inappropriately may make the output file unusable. The wildcard
3157 character @samp{*} may be given at the end of @var{sectionname}. If
3158 so, then any section starting with @var{sectionname} will be removed.
3160 If the first character of @var{sectionpattern} is the exclamation
3161 point (!) then matching sections will not be removed even if an
3162 earlier use of @option{--remove-section} on the same command line
3163 would otherwise remove it. For example:
3166 --remove-section=.text.* --remove-section=!.text.foo
3169 will remove all sections matching the pattern '.text.*', but will not
3170 remove the section '.text.foo'.
3172 @item --remove-relocations=@var{sectionpattern}
3173 Remove relocations from the output file for any section matching
3174 @var{sectionpattern}. This option may be given more than once. Note
3175 that using this option inappropriately may make the output file
3176 unusable. Wildcard characters are accepted in @var{sectionpattern}.
3180 --remove-relocations=.text.*
3183 will remove the relocations for all sections matching the patter
3186 If the first character of @var{sectionpattern} is the exclamation
3187 point (!) then matching sections will not have their relocation
3188 removed even if an earlier use of @option{--remove-relocations} on the
3189 same command line would otherwise cause the relocations to be removed.
3193 --remove-relocations=.text.* --remove-relocations=!.text.foo
3196 will remove all relocations for sections matching the pattern
3197 '.text.*', but will not remove relocations for the section
3207 @itemx --strip-debug
3208 Remove debugging symbols only.
3211 Remove the contents of all DWARF .dwo sections, leaving the
3212 remaining debugging sections and all symbols intact.
3213 See the description of this option in the @command{objcopy} section
3214 for more information.
3216 @item --strip-unneeded
3217 Remove all symbols that are not needed for relocation processing.
3219 @item -K @var{symbolname}
3220 @itemx --keep-symbol=@var{symbolname}
3221 When stripping symbols, keep symbol @var{symbolname} even if it would
3222 normally be stripped. This option may be given more than once.
3225 @itemx --merge-notes
3226 @itemx --no-merge-notes
3227 For ELF files, attempt (or do not attempt) to reduce the size of any
3228 SHT_NOTE type sections by removing duplicate notes. The default is to
3229 attempt this reduction.
3231 @item -N @var{symbolname}
3232 @itemx --strip-symbol=@var{symbolname}
3233 Remove symbol @var{symbolname} from the source file. This option may be
3234 given more than once, and may be combined with strip options other than
3238 Put the stripped output in @var{file}, rather than replacing the
3239 existing file. When this argument is used, only one @var{objfile}
3240 argument may be specified.
3243 @itemx --preserve-dates
3244 Preserve the access and modification dates of the file.
3247 @itemx --enable-deterministic-archives
3248 @cindex deterministic archives
3249 @kindex --enable-deterministic-archives
3250 Operate in @emph{deterministic} mode. When copying archive members
3251 and writing the archive index, use zero for UIDs, GIDs, timestamps,
3252 and use consistent file modes for all files.
3254 If @file{binutils} was configured with
3255 @option{--enable-deterministic-archives}, then this mode is on by default.
3256 It can be disabled with the @samp{-U} option, below.
3259 @itemx --disable-deterministic-archives
3260 @cindex deterministic archives
3261 @kindex --enable-deterministic-archives
3262 Do @emph{not} operate in @emph{deterministic} mode. This is the
3263 inverse of the @option{-D} option, above: when copying archive members
3264 and writing the archive index, use their actual UID, GID, timestamp,
3265 and file mode values.
3267 This is the default unless @file{binutils} was configured with
3268 @option{--enable-deterministic-archives}.
3272 Permit regular expressions in @var{symbolname}s used in other command
3273 line options. The question mark (?), asterisk (*), backslash (\) and
3274 square brackets ([]) operators can be used anywhere in the symbol
3275 name. If the first character of the symbol name is the exclamation
3276 point (!) then the sense of the switch is reversed for that symbol.
3283 would cause strip to only keep symbols that start with the letters
3284 ``fo'', but to discard the symbol ``foo''.
3287 @itemx --discard-all
3288 Remove non-global symbols.
3291 @itemx --discard-locals
3292 Remove compiler-generated local symbols.
3293 (These usually start with @samp{L} or @samp{.}.)
3295 @item --keep-file-symbols
3296 When stripping a file, perhaps with @option{--strip-debug} or
3297 @option{--strip-unneeded}, retain any symbols specifying source file names,
3298 which would otherwise get stripped.
3300 @item --only-keep-debug
3301 Strip a file, emptying the contents of any sections that would not be
3302 stripped by @option{--strip-debug} and leaving the debugging sections
3303 intact. In ELF files, this preserves all the note sections in the
3306 Note - the section headers of the stripped sections are preserved,
3307 including their sizes, but the contents of the section are discarded.
3308 The section headers are preserved so that other tools can match up the
3309 debuginfo file with the real executable, even if that executable has
3310 been relocated to a different address space.
3312 The intention is that this option will be used in conjunction with
3313 @option{--add-gnu-debuglink} to create a two part executable. One a
3314 stripped binary which will occupy less space in RAM and in a
3315 distribution and the second a debugging information file which is only
3316 needed if debugging abilities are required. The suggested procedure
3317 to create these files is as follows:
3320 @item Link the executable as normal. Assuming that is is called
3322 @item Run @code{objcopy --only-keep-debug foo foo.dbg} to
3323 create a file containing the debugging info.
3324 @item Run @code{objcopy --strip-debug foo} to create a
3325 stripped executable.
3326 @item Run @code{objcopy --add-gnu-debuglink=foo.dbg foo}
3327 to add a link to the debugging info into the stripped executable.
3330 Note---the choice of @code{.dbg} as an extension for the debug info
3331 file is arbitrary. Also the @code{--only-keep-debug} step is
3332 optional. You could instead do this:
3335 @item Link the executable as normal.
3336 @item Copy @code{foo} to @code{foo.full}
3337 @item Run @code{strip --strip-debug foo}
3338 @item Run @code{objcopy --add-gnu-debuglink=foo.full foo}
3341 i.e., the file pointed to by the @option{--add-gnu-debuglink} can be the
3342 full executable. It does not have to be a file created by the
3343 @option{--only-keep-debug} switch.
3345 Note---this switch is only intended for use on fully linked files. It
3346 does not make sense to use it on object files where the debugging
3347 information may be incomplete. Besides the gnu_debuglink feature
3348 currently only supports the presence of one filename containing
3349 debugging information, not multiple filenames on a one-per-object-file
3354 Show the version number for @command{strip}.
3358 Verbose output: list all object files modified. In the case of
3359 archives, @samp{strip -v} lists all members of the archive.
3365 @c man begin SEEALSO strip
3366 the Info entries for @file{binutils}.
3370 @node c++filt, addr2line, strip, Top
3374 @cindex demangling C++ symbols
3376 @c man title cxxfilt Demangle C++ and Java symbols.
3379 @c man begin SYNOPSIS cxxfilt
3380 c++filt [@option{-_}|@option{--strip-underscore}]
3381 [@option{-n}|@option{--no-strip-underscore}]
3382 [@option{-p}|@option{--no-params}]
3383 [@option{-t}|@option{--types}]
3384 [@option{-i}|@option{--no-verbose}]
3385 [@option{-s} @var{format}|@option{--format=}@var{format}]
3386 [@option{--help}] [@option{--version}] [@var{symbol}@dots{}]
3390 @c man begin DESCRIPTION cxxfilt
3393 The C++ and Java languages provide function overloading, which means
3394 that you can write many functions with the same name, providing that
3395 each function takes parameters of different types. In order to be
3396 able to distinguish these similarly named functions C++ and Java
3397 encode them into a low-level assembler name which uniquely identifies
3398 each different version. This process is known as @dfn{mangling}. The
3400 @footnote{MS-DOS does not allow @kbd{+} characters in file names, so on
3401 MS-DOS this program is named @command{CXXFILT}.}
3402 program does the inverse mapping: it decodes (@dfn{demangles}) low-level
3403 names into user-level names so that they can be read.
3405 Every alphanumeric word (consisting of letters, digits, underscores,
3406 dollars, or periods) seen in the input is a potential mangled name.
3407 If the name decodes into a C++ name, the C++ name replaces the
3408 low-level name in the output, otherwise the original word is output.
3409 In this way you can pass an entire assembler source file, containing
3410 mangled names, through @command{c++filt} and see the same source file
3411 containing demangled names.
3413 You can also use @command{c++filt} to decipher individual symbols by
3414 passing them on the command line:
3417 c++filt @var{symbol}
3420 If no @var{symbol} arguments are given, @command{c++filt} reads symbol
3421 names from the standard input instead. All the results are printed on
3422 the standard output. The difference between reading names from the
3423 command line versus reading names from the standard input is that
3424 command line arguments are expected to be just mangled names and no
3425 checking is performed to separate them from surrounding text. Thus
3432 will work and demangle the name to ``f()'' whereas:
3438 will not work. (Note the extra comma at the end of the mangled
3439 name which makes it invalid). This command however will work:
3442 echo _Z1fv, | c++filt -n
3445 and will display ``f(),'', i.e., the demangled name followed by a
3446 trailing comma. This behaviour is because when the names are read
3447 from the standard input it is expected that they might be part of an
3448 assembler source file where there might be extra, extraneous
3449 characters trailing after a mangled name. For example:
3452 .type _Z1fv, @@function
3457 @c man begin OPTIONS cxxfilt
3461 @itemx --strip-underscore
3462 On some systems, both the C and C++ compilers put an underscore in front
3463 of every name. For example, the C name @code{foo} gets the low-level
3464 name @code{_foo}. This option removes the initial underscore. Whether
3465 @command{c++filt} removes the underscore by default is target dependent.
3468 @itemx --no-strip-underscore
3469 Do not remove the initial underscore.
3473 When demangling the name of a function, do not display the types of
3474 the function's parameters.
3478 Attempt to demangle types as well as function names. This is disabled
3479 by default since mangled types are normally only used internally in
3480 the compiler, and they can be confused with non-mangled names. For example,
3481 a function called ``a'' treated as a mangled type name would be
3482 demangled to ``signed char''.
3486 Do not include implementation details (if any) in the demangled
3489 @item -s @var{format}
3490 @itemx --format=@var{format}
3491 @command{c++filt} can decode various methods of mangling, used by
3492 different compilers. The argument to this option selects which
3497 Automatic selection based on executable (the default method)
3499 the one used by the @sc{gnu} C++ compiler (g++)
3501 the one used by the Lucid compiler (lcc)
3503 the one specified by the C++ Annotated Reference Manual
3505 the one used by the HP compiler (aCC)
3507 the one used by the EDG compiler
3509 the one used by the @sc{gnu} C++ compiler (g++) with the V3 ABI.
3511 the one used by the @sc{gnu} Java compiler (gcj)
3513 the one used by the @sc{gnu} Ada compiler (GNAT).
3517 Print a summary of the options to @command{c++filt} and exit.
3520 Print the version number of @command{c++filt} and exit.
3526 @c man begin SEEALSO cxxfilt
3527 the Info entries for @file{binutils}.
3532 @emph{Warning:} @command{c++filt} is a new utility, and the details of its
3533 user interface are subject to change in future releases. In particular,
3534 a command-line option may be required in the future to decode a name
3535 passed as an argument on the command line; in other words,
3538 c++filt @var{symbol}
3542 may in a future release become
3545 c++filt @var{option} @var{symbol}
3553 @cindex address to file name and line number
3555 @c man title addr2line convert addresses into file names and line numbers.
3558 @c man begin SYNOPSIS addr2line
3559 addr2line [@option{-a}|@option{--addresses}]
3560 [@option{-b} @var{bfdname}|@option{--target=}@var{bfdname}]
3561 [@option{-C}|@option{--demangle}[=@var{style}]]
3562 [@option{-e} @var{filename}|@option{--exe=}@var{filename}]
3563 [@option{-f}|@option{--functions}] [@option{-s}|@option{--basename}]
3564 [@option{-i}|@option{--inlines}]
3565 [@option{-p}|@option{--pretty-print}]
3566 [@option{-j}|@option{--section=}@var{name}]
3567 [@option{-H}|@option{--help}] [@option{-V}|@option{--version}]
3572 @c man begin DESCRIPTION addr2line
3574 @command{addr2line} translates addresses into file names and line numbers.
3575 Given an address in an executable or an offset in a section of a relocatable
3576 object, it uses the debugging information to figure out which file name and
3577 line number are associated with it.
3579 The executable or relocatable object to use is specified with the @option{-e}
3580 option. The default is the file @file{a.out}. The section in the relocatable
3581 object to use is specified with the @option{-j} option.
3583 @command{addr2line} has two modes of operation.
3585 In the first, hexadecimal addresses are specified on the command line,
3586 and @command{addr2line} displays the file name and line number for each
3589 In the second, @command{addr2line} reads hexadecimal addresses from
3590 standard input, and prints the file name and line number for each
3591 address on standard output. In this mode, @command{addr2line} may be used
3592 in a pipe to convert dynamically chosen addresses.
3594 The format of the output is @samp{FILENAME:LINENO}. By default
3595 each input address generates one line of output.
3597 Two options can generate additional lines before each
3598 @samp{FILENAME:LINENO} line (in that order).
3600 If the @option{-a} option is used then a line with the input address
3603 If the @option{-f} option is used, then a line with the
3604 @samp{FUNCTIONNAME} is displayed. This is the name of the function
3605 containing the address.
3607 One option can generate additional lines after the
3608 @samp{FILENAME:LINENO} line.
3610 If the @option{-i} option is used and the code at the given address is
3611 present there because of inlining by the compiler then additional
3612 lines are displayed afterwards. One or two extra lines (if the
3613 @option{-f} option is used) are displayed for each inlined function.
3615 Alternatively if the @option{-p} option is used then each input
3616 address generates a single, long, output line containing the address,
3617 the function name, the file name and the line number. If the
3618 @option{-i} option has also been used then any inlined functions will
3619 be displayed in the same manner, but on separate lines, and prefixed
3620 by the text @samp{(inlined by)}.
3622 If the file name or function name can not be determined,
3623 @command{addr2line} will print two question marks in their place. If the
3624 line number can not be determined, @command{addr2line} will print 0.
3628 @c man begin OPTIONS addr2line
3630 The long and short forms of options, shown here as alternatives, are
3636 Display the address before the function name, file and line number
3637 information. The address is printed with a @samp{0x} prefix to easily
3640 @item -b @var{bfdname}
3641 @itemx --target=@var{bfdname}
3642 @cindex object code format
3643 Specify that the object-code format for the object files is
3647 @itemx --demangle[=@var{style}]
3648 @cindex demangling in objdump
3649 Decode (@dfn{demangle}) low-level symbol names into user-level names.
3650 Besides removing any initial underscore prepended by the system, this
3651 makes C++ function names readable. Different compilers have different
3652 mangling styles. The optional demangling style argument can be used to
3653 choose an appropriate demangling style for your compiler. @xref{c++filt},
3654 for more information on demangling.
3656 @item -e @var{filename}
3657 @itemx --exe=@var{filename}
3658 Specify the name of the executable for which addresses should be
3659 translated. The default file is @file{a.out}.
3663 Display function names as well as file and line number information.
3667 Display only the base of each file name.
3671 If the address belongs to a function that was inlined, the source
3672 information for all enclosing scopes back to the first non-inlined
3673 function will also be printed. For example, if @code{main} inlines
3674 @code{callee1} which inlines @code{callee2}, and address is from
3675 @code{callee2}, the source information for @code{callee1} and @code{main}
3676 will also be printed.
3680 Read offsets relative to the specified section instead of absolute addresses.
3683 @itemx --pretty-print
3684 Make the output more human friendly: each location are printed on one line.
3685 If option @option{-i} is specified, lines for all enclosing scopes are
3686 prefixed with @samp{(inlined by)}.
3692 @c man begin SEEALSO addr2line
3693 Info entries for @file{binutils}.
3700 @command{nlmconv} converts a relocatable object file into a NetWare
3704 @command{nlmconv} currently works with @samp{i386} object
3705 files in @code{coff}, @sc{elf}, or @code{a.out} format, and @sc{SPARC}
3706 object files in @sc{elf}, or @code{a.out} format@footnote{
3707 @command{nlmconv} should work with any @samp{i386} or @sc{sparc} object
3708 format in the Binary File Descriptor library. It has only been tested
3709 with the above formats.}.
3713 @emph{Warning:} @command{nlmconv} is not always built as part of the binary
3714 utilities, since it is only useful for NLM targets.
3717 @c man title nlmconv converts object code into an NLM.
3720 @c man begin SYNOPSIS nlmconv
3721 nlmconv [@option{-I} @var{bfdname}|@option{--input-target=}@var{bfdname}]
3722 [@option{-O} @var{bfdname}|@option{--output-target=}@var{bfdname}]
3723 [@option{-T} @var{headerfile}|@option{--header-file=}@var{headerfile}]
3724 [@option{-d}|@option{--debug}] [@option{-l} @var{linker}|@option{--linker=}@var{linker}]
3725 [@option{-h}|@option{--help}] [@option{-V}|@option{--version}]
3726 @var{infile} @var{outfile}
3730 @c man begin DESCRIPTION nlmconv
3732 @command{nlmconv} converts the relocatable @samp{i386} object file
3733 @var{infile} into the NetWare Loadable Module @var{outfile}, optionally
3734 reading @var{headerfile} for NLM header information. For instructions
3735 on writing the NLM command file language used in header files, see the
3736 @samp{linkers} section, @samp{NLMLINK} in particular, of the @cite{NLM
3737 Development and Tools Overview}, which is part of the NLM Software
3738 Developer's Kit (``NLM SDK''), available from Novell, Inc.
3739 @command{nlmconv} uses the @sc{gnu} Binary File Descriptor library to read
3742 see @ref{BFD,,BFD,ld.info,Using LD}, for more information.
3745 @command{nlmconv} can perform a link step. In other words, you can list
3746 more than one object file for input if you list them in the definitions
3747 file (rather than simply specifying one input file on the command line).
3748 In this case, @command{nlmconv} calls the linker for you.
3752 @c man begin OPTIONS nlmconv
3755 @item -I @var{bfdname}
3756 @itemx --input-target=@var{bfdname}
3757 Object format of the input file. @command{nlmconv} can usually determine
3758 the format of a given file (so no default is necessary).
3759 @xref{Target Selection}, for more information.
3761 @item -O @var{bfdname}
3762 @itemx --output-target=@var{bfdname}
3763 Object format of the output file. @command{nlmconv} infers the output
3764 format based on the input format, e.g. for a @samp{i386} input file the
3765 output format is @samp{nlm32-i386}.
3766 @xref{Target Selection}, for more information.
3768 @item -T @var{headerfile}
3769 @itemx --header-file=@var{headerfile}
3770 Reads @var{headerfile} for NLM header information. For instructions on
3771 writing the NLM command file language used in header files, see@ see the
3772 @samp{linkers} section, of the @cite{NLM Development and Tools
3773 Overview}, which is part of the NLM Software Developer's Kit, available
3778 Displays (on standard error) the linker command line used by @command{nlmconv}.
3780 @item -l @var{linker}
3781 @itemx --linker=@var{linker}
3782 Use @var{linker} for any linking. @var{linker} can be an absolute or a
3787 Prints a usage summary.
3791 Prints the version number for @command{nlmconv}.
3797 @c man begin SEEALSO nlmconv
3798 the Info entries for @file{binutils}.
3805 @command{windmc} may be used to generator Windows message resources.
3808 @emph{Warning:} @command{windmc} is not always built as part of the binary
3809 utilities, since it is only useful for Windows targets.
3812 @c man title windmc generates Windows message resources.
3815 @c man begin SYNOPSIS windmc
3816 windmc [options] input-file
3820 @c man begin DESCRIPTION windmc
3822 @command{windmc} reads message definitions from an input file (.mc) and
3823 translate them into a set of output files. The output files may be of
3828 A C header file containing the message definitions.
3831 A resource file compilable by the @command{windres} tool.
3834 One or more binary files containing the resource data for a specific
3838 A C include file that maps message id's to their symbolic name.
3841 The exact description of these different formats is available in
3842 documentation from Microsoft.
3844 When @command{windmc} converts from the @code{mc} format to the @code{bin}
3845 format, @code{rc}, @code{h}, and optional @code{dbg} it is acting like the
3846 Windows Message Compiler.
3850 @c man begin OPTIONS windmc
3855 Specifies that the input file specified is ASCII. This is the default
3860 Specifies that messages in the output @code{bin} files should be in ASCII
3865 Specifies that @code{bin} filenames should have to be prefixed by the
3866 basename of the source file.
3870 Sets the customer bit in all message id's.
3872 @item -C @var{codepage}
3873 @itemx --codepage_in @var{codepage}
3874 Sets the default codepage to be used to convert input file to UTF16. The
3875 default is ocdepage 1252.
3878 @itemx --decimal_values
3879 Outputs the constants in the header file in decimal. Default is using
3883 @itemx --extension @var{ext}
3884 The extension for the header file. The default is .h extension.
3886 @item -F @var{target}
3887 @itemx --target @var{target}
3888 Specify the BFD format to use for a bin file as output. This
3889 is a BFD target name; you can use the @option{--help} option to see a list
3890 of supported targets. Normally @command{windmc} will use the default
3891 format, which is the first one listed by the @option{--help} option.
3893 @ref{Target Selection}.
3897 @itemx --headerdir @var{path}
3898 The target directory of the generated header file. The default is the
3903 Displays a list of command line options and then exits.
3905 @item -m @var{characters}
3906 @itemx --maxlength @var{characters}
3907 Instructs @command{windmc} to generate a warning if the length
3908 of any message exceeds the number specified.
3911 @itemx --nullterminate
3912 Terminate message text in @code{bin} files by zero. By default they are
3913 terminated by CR/LF.
3916 @itemx --hresult_use
3917 Not yet implemented. Instructs @code{windmc} to generate an OLE2 header
3918 file, using HRESULT definitions. Status codes are used if the flag is not
3921 @item -O @var{codepage}
3922 @itemx --codepage_out @var{codepage}
3923 Sets the default codepage to be used to output text files. The default
3927 @itemx --rcdir @var{path}
3928 The target directory for the generated @code{rc} script and the generated
3929 @code{bin} files that the resource compiler script includes. The default
3930 is the current directory.
3934 Specifies that the input file is UTF16.
3937 @itemx --unicode_out
3938 Specifies that messages in the output @code{bin} file should be in UTF16
3939 format. This is the default behaviour.
3943 Enable verbose mode.
3947 Prints the version number for @command{windmc}.
3950 @itemx --xdgb @var{path}
3951 The path of the @code{dbg} C include file that maps message id's to the
3952 symbolic name. No such file is generated without specifying the switch.
3958 @c man begin SEEALSO windmc
3959 the Info entries for @file{binutils}.
3966 @command{windres} may be used to manipulate Windows resources.
3969 @emph{Warning:} @command{windres} is not always built as part of the binary
3970 utilities, since it is only useful for Windows targets.
3973 @c man title windres manipulate Windows resources.
3976 @c man begin SYNOPSIS windres
3977 windres [options] [input-file] [output-file]
3981 @c man begin DESCRIPTION windres
3983 @command{windres} reads resources from an input file and copies them into
3984 an output file. Either file may be in one of three formats:
3988 A text format read by the Resource Compiler.
3991 A binary format generated by the Resource Compiler.
3994 A COFF object or executable.
3997 The exact description of these different formats is available in
3998 documentation from Microsoft.
4000 When @command{windres} converts from the @code{rc} format to the @code{res}
4001 format, it is acting like the Windows Resource Compiler. When
4002 @command{windres} converts from the @code{res} format to the @code{coff}
4003 format, it is acting like the Windows @code{CVTRES} program.
4005 When @command{windres} generates an @code{rc} file, the output is similar
4006 but not identical to the format expected for the input. When an input
4007 @code{rc} file refers to an external filename, an output @code{rc} file
4008 will instead include the file contents.
4010 If the input or output format is not specified, @command{windres} will
4011 guess based on the file name, or, for the input file, the file contents.
4012 A file with an extension of @file{.rc} will be treated as an @code{rc}
4013 file, a file with an extension of @file{.res} will be treated as a
4014 @code{res} file, and a file with an extension of @file{.o} or
4015 @file{.exe} will be treated as a @code{coff} file.
4017 If no output file is specified, @command{windres} will print the resources
4018 in @code{rc} format to standard output.
4020 The normal use is for you to write an @code{rc} file, use @command{windres}
4021 to convert it to a COFF object file, and then link the COFF file into
4022 your application. This will make the resources described in the
4023 @code{rc} file available to Windows.
4027 @c man begin OPTIONS windres
4030 @item -i @var{filename}
4031 @itemx --input @var{filename}
4032 The name of the input file. If this option is not used, then
4033 @command{windres} will use the first non-option argument as the input file
4034 name. If there are no non-option arguments, then @command{windres} will
4035 read from standard input. @command{windres} can not read a COFF file from
4038 @item -o @var{filename}
4039 @itemx --output @var{filename}
4040 The name of the output file. If this option is not used, then
4041 @command{windres} will use the first non-option argument, after any used
4042 for the input file name, as the output file name. If there is no
4043 non-option argument, then @command{windres} will write to standard output.
4044 @command{windres} can not write a COFF file to standard output. Note,
4045 for compatibility with @command{rc} the option @option{-fo} is also
4046 accepted, but its use is not recommended.
4048 @item -J @var{format}
4049 @itemx --input-format @var{format}
4050 The input format to read. @var{format} may be @samp{res}, @samp{rc}, or
4051 @samp{coff}. If no input format is specified, @command{windres} will
4052 guess, as described above.
4054 @item -O @var{format}
4055 @itemx --output-format @var{format}
4056 The output format to generate. @var{format} may be @samp{res},
4057 @samp{rc}, or @samp{coff}. If no output format is specified,
4058 @command{windres} will guess, as described above.
4060 @item -F @var{target}
4061 @itemx --target @var{target}
4062 Specify the BFD format to use for a COFF file as input or output. This
4063 is a BFD target name; you can use the @option{--help} option to see a list
4064 of supported targets. Normally @command{windres} will use the default
4065 format, which is the first one listed by the @option{--help} option.
4067 @ref{Target Selection}.
4070 @item --preprocessor @var{program}
4071 When @command{windres} reads an @code{rc} file, it runs it through the C
4072 preprocessor first. This option may be used to specify the preprocessor
4073 to use, including any leading arguments. The default preprocessor
4074 argument is @code{gcc -E -xc-header -DRC_INVOKED}.
4076 @item --preprocessor-arg @var{option}
4077 When @command{windres} reads an @code{rc} file, it runs it through
4078 the C preprocessor first. This option may be used to specify additional
4079 text to be passed to preprocessor on its command line.
4080 This option can be used multiple times to add multiple options to the
4081 preprocessor command line.
4083 @item -I @var{directory}
4084 @itemx --include-dir @var{directory}
4085 Specify an include directory to use when reading an @code{rc} file.
4086 @command{windres} will pass this to the preprocessor as an @option{-I}
4087 option. @command{windres} will also search this directory when looking for
4088 files named in the @code{rc} file. If the argument passed to this command
4089 matches any of the supported @var{formats} (as described in the @option{-J}
4090 option), it will issue a deprecation warning, and behave just like the
4091 @option{-J} option. New programs should not use this behaviour. If a
4092 directory happens to match a @var{format}, simple prefix it with @samp{./}
4093 to disable the backward compatibility.
4095 @item -D @var{target}
4096 @itemx --define @var{sym}[=@var{val}]
4097 Specify a @option{-D} option to pass to the preprocessor when reading an
4100 @item -U @var{target}
4101 @itemx --undefine @var{sym}
4102 Specify a @option{-U} option to pass to the preprocessor when reading an
4106 Ignored for compatibility with rc.
4109 Enable verbose mode. This tells you what the preprocessor is if you
4113 @item --codepage @var{val}
4114 Specify the default codepage to use when reading an @code{rc} file.
4115 @var{val} should be a hexadecimal prefixed by @samp{0x} or decimal
4116 codepage code. The valid range is from zero up to 0xffff, but the
4117 validity of the codepage is host and configuration dependent.
4120 @item --language @var{val}
4121 Specify the default language to use when reading an @code{rc} file.
4122 @var{val} should be a hexadecimal language code. The low eight bits are
4123 the language, and the high eight bits are the sublanguage.
4125 @item --use-temp-file
4126 Use a temporary file to instead of using popen to read the output of
4127 the preprocessor. Use this option if the popen implementation is buggy
4128 on the host (eg., certain non-English language versions of Windows 95 and
4129 Windows 98 are known to have buggy popen where the output will instead
4132 @item --no-use-temp-file
4133 Use popen, not a temporary file, to read the output of the preprocessor.
4134 This is the default behaviour.
4138 Prints a usage summary.
4142 Prints the version number for @command{windres}.
4145 If @command{windres} is compiled with @code{YYDEBUG} defined as @code{1},
4146 this will turn on parser debugging.
4152 @c man begin SEEALSO windres
4153 the Info entries for @file{binutils}.
4162 @command{dlltool} is used to create the files needed to create dynamic
4163 link libraries (DLLs) on systems which understand PE format image
4164 files such as Windows. A DLL contains an export table which contains
4165 information that the runtime loader needs to resolve references from a
4166 referencing program.
4168 The export table is generated by this program by reading in a
4169 @file{.def} file or scanning the @file{.a} and @file{.o} files which
4170 will be in the DLL. A @file{.o} file can contain information in
4171 special @samp{.drectve} sections with export information.
4174 @emph{Note:} @command{dlltool} is not always built as part of the
4175 binary utilities, since it is only useful for those targets which
4179 @c man title dlltool Create files needed to build and use DLLs.
4182 @c man begin SYNOPSIS dlltool
4183 dlltool [@option{-d}|@option{--input-def} @var{def-file-name}]
4184 [@option{-b}|@option{--base-file} @var{base-file-name}]
4185 [@option{-e}|@option{--output-exp} @var{exports-file-name}]
4186 [@option{-z}|@option{--output-def} @var{def-file-name}]
4187 [@option{-l}|@option{--output-lib} @var{library-file-name}]
4188 [@option{-y}|@option{--output-delaylib} @var{library-file-name}]
4189 [@option{--export-all-symbols}] [@option{--no-export-all-symbols}]
4190 [@option{--exclude-symbols} @var{list}]
4191 [@option{--no-default-excludes}]
4192 [@option{-S}|@option{--as} @var{path-to-assembler}] [@option{-f}|@option{--as-flags} @var{options}]
4193 [@option{-D}|@option{--dllname} @var{name}] [@option{-m}|@option{--machine} @var{machine}]
4194 [@option{-a}|@option{--add-indirect}]
4195 [@option{-U}|@option{--add-underscore}] [@option{--add-stdcall-underscore}]
4196 [@option{-k}|@option{--kill-at}] [@option{-A}|@option{--add-stdcall-alias}]
4197 [@option{-p}|@option{--ext-prefix-alias} @var{prefix}]
4198 [@option{-x}|@option{--no-idata4}] [@option{-c}|@option{--no-idata5}]
4199 [@option{--use-nul-prefixed-import-tables}]
4200 [@option{-I}|@option{--identify} @var{library-file-name}] [@option{--identify-strict}]
4201 [@option{-i}|@option{--interwork}]
4202 [@option{-n}|@option{--nodelete}] [@option{-t}|@option{--temp-prefix} @var{prefix}]
4203 [@option{-v}|@option{--verbose}]
4204 [@option{-h}|@option{--help}] [@option{-V}|@option{--version}]
4205 [@option{--no-leading-underscore}] [@option{--leading-underscore}]
4206 [object-file @dots{}]
4210 @c man begin DESCRIPTION dlltool
4212 @command{dlltool} reads its inputs, which can come from the @option{-d} and
4213 @option{-b} options as well as object files specified on the command
4214 line. It then processes these inputs and if the @option{-e} option has
4215 been specified it creates a exports file. If the @option{-l} option
4216 has been specified it creates a library file and if the @option{-z} option
4217 has been specified it creates a def file. Any or all of the @option{-e},
4218 @option{-l} and @option{-z} options can be present in one invocation of
4221 When creating a DLL, along with the source for the DLL, it is necessary
4222 to have three other files. @command{dlltool} can help with the creation of
4225 The first file is a @file{.def} file which specifies which functions are
4226 exported from the DLL, which functions the DLL imports, and so on. This
4227 is a text file and can be created by hand, or @command{dlltool} can be used
4228 to create it using the @option{-z} option. In this case @command{dlltool}
4229 will scan the object files specified on its command line looking for
4230 those functions which have been specially marked as being exported and
4231 put entries for them in the @file{.def} file it creates.
4233 In order to mark a function as being exported from a DLL, it needs to
4234 have an @option{-export:<name_of_function>} entry in the @samp{.drectve}
4235 section of the object file. This can be done in C by using the
4239 asm (".section .drectve");
4240 asm (".ascii \"-export:my_func\"");
4242 int my_func (void) @{ @dots{} @}
4245 The second file needed for DLL creation is an exports file. This file
4246 is linked with the object files that make up the body of the DLL and it
4247 handles the interface between the DLL and the outside world. This is a
4248 binary file and it can be created by giving the @option{-e} option to
4249 @command{dlltool} when it is creating or reading in a @file{.def} file.
4251 The third file needed for DLL creation is the library file that programs
4252 will link with in order to access the functions in the DLL (an `import
4253 library'). This file can be created by giving the @option{-l} option to
4254 dlltool when it is creating or reading in a @file{.def} file.
4256 If the @option{-y} option is specified, dlltool generates a delay-import
4257 library that can be used instead of the normal import library to allow
4258 a program to link to the dll only as soon as an imported function is
4259 called for the first time. The resulting executable will need to be
4260 linked to the static delayimp library containing __delayLoadHelper2(),
4261 which in turn will import LoadLibraryA and GetProcAddress from kernel32.
4263 @command{dlltool} builds the library file by hand, but it builds the
4264 exports file by creating temporary files containing assembler statements
4265 and then assembling these. The @option{-S} command line option can be
4266 used to specify the path to the assembler that dlltool will use,
4267 and the @option{-f} option can be used to pass specific flags to that
4268 assembler. The @option{-n} can be used to prevent dlltool from deleting
4269 these temporary assembler files when it is done, and if @option{-n} is
4270 specified twice then this will prevent dlltool from deleting the
4271 temporary object files it used to build the library.
4273 Here is an example of creating a DLL from a source file @samp{dll.c} and
4274 also creating a program (from an object file called @samp{program.o})
4279 dlltool -e exports.o -l dll.lib dll.o
4280 gcc dll.o exports.o -o dll.dll
4281 gcc program.o dll.lib -o program
4285 @command{dlltool} may also be used to query an existing import library
4286 to determine the name of the DLL to which it is associated. See the
4287 description of the @option{-I} or @option{--identify} option.
4291 @c man begin OPTIONS dlltool
4293 The command line options have the following meanings:
4297 @item -d @var{filename}
4298 @itemx --input-def @var{filename}
4299 @cindex input .def file
4300 Specifies the name of a @file{.def} file to be read in and processed.
4302 @item -b @var{filename}
4303 @itemx --base-file @var{filename}
4305 Specifies the name of a base file to be read in and processed. The
4306 contents of this file will be added to the relocation section in the
4307 exports file generated by dlltool.
4309 @item -e @var{filename}
4310 @itemx --output-exp @var{filename}
4311 Specifies the name of the export file to be created by dlltool.
4313 @item -z @var{filename}
4314 @itemx --output-def @var{filename}
4315 Specifies the name of the @file{.def} file to be created by dlltool.
4317 @item -l @var{filename}
4318 @itemx --output-lib @var{filename}
4319 Specifies the name of the library file to be created by dlltool.
4321 @item -y @var{filename}
4322 @itemx --output-delaylib @var{filename}
4323 Specifies the name of the delay-import library file to be created by dlltool.
4325 @item --export-all-symbols
4326 Treat all global and weak defined symbols found in the input object
4327 files as symbols to be exported. There is a small list of symbols which
4328 are not exported by default; see the @option{--no-default-excludes}
4329 option. You may add to the list of symbols to not export by using the
4330 @option{--exclude-symbols} option.
4332 @item --no-export-all-symbols
4333 Only export symbols explicitly listed in an input @file{.def} file or in
4334 @samp{.drectve} sections in the input object files. This is the default
4335 behaviour. The @samp{.drectve} sections are created by @samp{dllexport}
4336 attributes in the source code.
4338 @item --exclude-symbols @var{list}
4339 Do not export the symbols in @var{list}. This is a list of symbol names
4340 separated by comma or colon characters. The symbol names should not
4341 contain a leading underscore. This is only meaningful when
4342 @option{--export-all-symbols} is used.
4344 @item --no-default-excludes
4345 When @option{--export-all-symbols} is used, it will by default avoid
4346 exporting certain special symbols. The current list of symbols to avoid
4347 exporting is @samp{DllMain@@12}, @samp{DllEntryPoint@@0},
4348 @samp{impure_ptr}. You may use the @option{--no-default-excludes} option
4349 to go ahead and export these special symbols. This is only meaningful
4350 when @option{--export-all-symbols} is used.
4353 @itemx --as @var{path}
4354 Specifies the path, including the filename, of the assembler to be used
4355 to create the exports file.
4357 @item -f @var{options}
4358 @itemx --as-flags @var{options}
4359 Specifies any specific command line options to be passed to the
4360 assembler when building the exports file. This option will work even if
4361 the @option{-S} option is not used. This option only takes one argument,
4362 and if it occurs more than once on the command line, then later
4363 occurrences will override earlier occurrences. So if it is necessary to
4364 pass multiple options to the assembler they should be enclosed in
4368 @itemx --dll-name @var{name}
4369 Specifies the name to be stored in the @file{.def} file as the name of
4370 the DLL when the @option{-e} option is used. If this option is not
4371 present, then the filename given to the @option{-e} option will be
4372 used as the name of the DLL.
4374 @item -m @var{machine}
4375 @itemx -machine @var{machine}
4376 Specifies the type of machine for which the library file should be
4377 built. @command{dlltool} has a built in default type, depending upon how
4378 it was created, but this option can be used to override that. This is
4379 normally only useful when creating DLLs for an ARM processor, when the
4380 contents of the DLL are actually encode using Thumb instructions.
4383 @itemx --add-indirect
4384 Specifies that when @command{dlltool} is creating the exports file it
4385 should add a section which allows the exported functions to be
4386 referenced without using the import library. Whatever the hell that
4390 @itemx --add-underscore
4391 Specifies that when @command{dlltool} is creating the exports file it
4392 should prepend an underscore to the names of @emph{all} exported symbols.
4394 @item --no-leading-underscore
4395 @item --leading-underscore
4396 Specifies whether standard symbol should be forced to be prefixed, or
4399 @item --add-stdcall-underscore
4400 Specifies that when @command{dlltool} is creating the exports file it
4401 should prepend an underscore to the names of exported @emph{stdcall}
4402 functions. Variable names and non-stdcall function names are not modified.
4403 This option is useful when creating GNU-compatible import libs for third
4404 party DLLs that were built with MS-Windows tools.
4408 Specifies that @samp{@@<number>} suffixes should be omitted from the names
4409 of stdcall functions that will be imported from the DLL. This is
4410 useful when creating an import library for a DLL which exports stdcall
4411 functions but without the usual @samp{@@<number>} symbol name suffix.
4413 This does not change the naming of symbols provided by the import library
4414 to programs linked against it, but only the entries in the import table
4415 (ie the .idata section).
4418 @itemx --add-stdcall-alias
4419 Specifies that when @command{dlltool} is creating the exports file it
4420 should add aliases for stdcall symbols without @samp{@@ <number>}
4421 in addition to the symbols with @samp{@@ <number>}.
4424 @itemx --ext-prefix-alias @var{prefix}
4425 Causes @command{dlltool} to create external aliases for all DLL
4426 imports with the specified prefix. The aliases are created for both
4427 external and import symbols with no leading underscore.
4431 Specifies that when @command{dlltool} is creating the exports and library
4432 files it should omit the @code{.idata4} section. This is for compatibility
4433 with certain operating systems.
4435 @item --use-nul-prefixed-import-tables
4436 Specifies that when @command{dlltool} is creating the exports and library
4437 files it should prefix the @code{.idata4} and @code{.idata5} by zero an
4438 element. This emulates old gnu import library generation of
4439 @code{dlltool}. By default this option is turned off.
4443 Specifies that when @command{dlltool} is creating the exports and library
4444 files it should omit the @code{.idata5} section. This is for compatibility
4445 with certain operating systems.
4447 @item -I @var{filename}
4448 @itemx --identify @var{filename}
4449 Specifies that @command{dlltool} should inspect the import library
4450 indicated by @var{filename} and report, on @code{stdout}, the name(s)
4451 of the associated DLL(s). This can be performed in addition to any
4452 other operations indicated by the other options and arguments.
4453 @command{dlltool} fails if the import library does not exist or is not
4454 actually an import library. See also @option{--identify-strict}.
4456 @item --identify-strict
4457 Modifies the behavior of the @option{--identify} option, such
4458 that an error is reported if @var{filename} is associated with
4463 Specifies that @command{dlltool} should mark the objects in the library
4464 file and exports file that it produces as supporting interworking
4465 between ARM and Thumb code.
4469 Makes @command{dlltool} preserve the temporary assembler files it used to
4470 create the exports file. If this option is repeated then dlltool will
4471 also preserve the temporary object files it uses to create the library
4474 @item -t @var{prefix}
4475 @itemx --temp-prefix @var{prefix}
4476 Makes @command{dlltool} use @var{prefix} when constructing the names of
4477 temporary assembler and object files. By default, the temp file prefix
4478 is generated from the pid.
4482 Make dlltool describe what it is doing.
4486 Displays a list of command line options and then exits.
4490 Displays dlltool's version number and then exits.
4497 * def file format:: The format of the dlltool @file{.def} file
4500 @node def file format
4501 @section The format of the @command{dlltool} @file{.def} file
4503 A @file{.def} file contains any number of the following commands:
4507 @item @code{NAME} @var{name} @code{[ ,} @var{base} @code{]}
4508 The result is going to be named @var{name}@code{.exe}.
4510 @item @code{LIBRARY} @var{name} @code{[ ,} @var{base} @code{]}
4511 The result is going to be named @var{name}@code{.dll}.
4512 Note: If you want to use LIBRARY as name then you need to quote. Otherwise
4513 this will fail due a necessary hack for libtool (see PR binutils/13710 for more
4516 @item @code{EXPORTS ( ( (} @var{name1} @code{[ = } @var{name2} @code{] ) | ( } @var{name1} @code{=} @var{module-name} @code{.} @var{external-name} @code{) ) [ == } @var{its_name} @code{]}
4517 @item @code{[} @var{integer} @code{] [ NONAME ] [ CONSTANT ] [ DATA ] [ PRIVATE ] ) *}
4518 Declares @var{name1} as an exported symbol from the DLL, with optional
4519 ordinal number @var{integer}, or declares @var{name1} as an alias
4520 (forward) of the function @var{external-name} in the DLL.
4521 If @var{its_name} is specified, this name is used as string in export table.
4523 Note: The @code{EXPORTS} has to be the last command in .def file, as keywords
4524 are treated - beside @code{LIBRARY} - as simple name-identifiers.
4525 If you want to use LIBRARY as name then you need to quote it.
4527 @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{) [ == ) @var{its_name} @code{]} *}
4528 Declares that @var{external-name} or the exported function whose
4529 ordinal number is @var{integer} is to be imported from the file
4530 @var{module-name}. If @var{internal-name} is specified then this is
4531 the name that the imported function will be referred to in the body of
4533 If @var{its_name} is specified, this name is used as string in import table.
4534 Note: The @code{IMPORTS} has to be the last command in .def file, as keywords
4535 are treated - beside @code{LIBRARY} - as simple name-identifiers.
4536 If you want to use LIBRARY as name then you need to quote it.
4538 @item @code{DESCRIPTION} @var{string}
4539 Puts @var{string} into the output @file{.exp} file in the
4540 @code{.rdata} section.
4542 @item @code{STACKSIZE} @var{number-reserve} @code{[, } @var{number-commit} @code{]}
4543 @item @code{HEAPSIZE} @var{number-reserve} @code{[, } @var{number-commit} @code{]}
4544 Generates @code{--stack} or @code{--heap}
4545 @var{number-reserve},@var{number-commit} in the output @code{.drectve}
4546 section. The linker will see this and act upon it.
4548 @item @code{CODE} @var{attr} @code{+}
4549 @item @code{DATA} @var{attr} @code{+}
4550 @item @code{SECTIONS (} @var{section-name} @var{attr}@code{ + ) *}
4551 Generates @code{--attr} @var{section-name} @var{attr} in the output
4552 @code{.drectve} section, where @var{attr} is one of @code{READ},
4553 @code{WRITE}, @code{EXECUTE} or @code{SHARED}. The linker will see
4554 this and act upon it.
4559 @c man begin SEEALSO dlltool
4560 The Info pages for @file{binutils}.
4567 @cindex ELF file information
4570 @c man title readelf Displays information about ELF files.
4573 @c man begin SYNOPSIS readelf
4574 readelf [@option{-a}|@option{--all}]
4575 [@option{-h}|@option{--file-header}]
4576 [@option{-l}|@option{--program-headers}|@option{--segments}]
4577 [@option{-S}|@option{--section-headers}|@option{--sections}]
4578 [@option{-g}|@option{--section-groups}]
4579 [@option{-t}|@option{--section-details}]
4580 [@option{-e}|@option{--headers}]
4581 [@option{-s}|@option{--syms}|@option{--symbols}]
4582 [@option{--dyn-syms}]
4583 [@option{-n}|@option{--notes}]
4584 [@option{-r}|@option{--relocs}]
4585 [@option{-u}|@option{--unwind}]
4586 [@option{-d}|@option{--dynamic}]
4587 [@option{-V}|@option{--version-info}]
4588 [@option{-A}|@option{--arch-specific}]
4589 [@option{-D}|@option{--use-dynamic}]
4590 [@option{-x} <number or name>|@option{--hex-dump=}<number or name>]
4591 [@option{-p} <number or name>|@option{--string-dump=}<number or name>]
4592 [@option{-R} <number or name>|@option{--relocated-dump=}<number or name>]
4593 [@option{-z}|@option{--decompress}]
4594 [@option{-c}|@option{--archive-index}]
4595 [@option{-w[lLiaprmfFsoRtUuTgAckK]}|
4596 @option{--debug-dump}[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links]]
4597 [@option{--dwarf-depth=@var{n}}]
4598 [@option{--dwarf-start=@var{n}}]
4599 [@option{-I}|@option{--histogram}]
4600 [@option{-v}|@option{--version}]
4601 [@option{-W}|@option{--wide}]
4602 [@option{-H}|@option{--help}]
4603 @var{elffile}@dots{}
4607 @c man begin DESCRIPTION readelf
4609 @command{readelf} displays information about one or more ELF format object
4610 files. The options control what particular information to display.
4612 @var{elffile}@dots{} are the object files to be examined. 32-bit and
4613 64-bit ELF files are supported, as are archives containing ELF files.
4615 This program performs a similar function to @command{objdump} but it
4616 goes into more detail and it exists independently of the @sc{bfd}
4617 library, so if there is a bug in @sc{bfd} then readelf will not be
4622 @c man begin OPTIONS readelf
4624 The long and short forms of options, shown here as alternatives, are
4625 equivalent. At least one option besides @samp{-v} or @samp{-H} must be
4631 Equivalent to specifying @option{--file-header},
4632 @option{--program-headers}, @option{--sections}, @option{--symbols},
4633 @option{--relocs}, @option{--dynamic}, @option{--notes},
4634 @option{--version-info}, @option{--arch-specific}, @option{--unwind},
4635 @option{--section-groups} and @option{--histogram}.
4637 Note - this option does not enable @option{--use-dynamic} itself, so
4638 if that option is not present on the command line then dynamic symbols
4639 and dynamic relocs will not be displayed.
4642 @itemx --file-header
4643 @cindex ELF file header information
4644 Displays the information contained in the ELF header at the start of the
4648 @itemx --program-headers
4650 @cindex ELF program header information
4651 @cindex ELF segment information
4652 Displays the information contained in the file's segment headers, if it
4657 @itemx --section-headers
4658 @cindex ELF section information
4659 Displays the information contained in the file's section headers, if it
4663 @itemx --section-groups
4664 @cindex ELF section group information
4665 Displays the information contained in the file's section groups, if it
4669 @itemx --section-details
4670 @cindex ELF section information
4671 Displays the detailed section information. Implies @option{-S}.
4676 @cindex ELF symbol table information
4677 Displays the entries in symbol table section of the file, if it has one.
4678 If a symbol has version information associated with it then this is
4679 displayed as well. The version string is displayed as a suffix to the
4680 symbol name, preceeded by an @@ character. For example
4681 @samp{foo@@VER_1}. If the version is the default version to be used
4682 when resolving unversioned references to the symbol then it is
4683 displayed as a suffix preceeded by two @@ characters. For example
4684 @samp{foo@@@@VER_2}.
4687 @cindex ELF dynamic symbol table information
4688 Displays the entries in dynamic symbol table section of the file, if it
4689 has one. The output format is the same as the format used by the
4690 @option{--syms} option.
4694 Display all the headers in the file. Equivalent to @option{-h -l -S}.
4699 Displays the contents of the NOTE segments and/or sections, if any.
4703 @cindex ELF reloc information
4704 Displays the contents of the file's relocation section, if it has one.
4708 @cindex unwind information
4709 Displays the contents of the file's unwind section, if it has one. Only
4710 the unwind sections for IA64 ELF files, as well as ARM unwind tables
4711 (@code{.ARM.exidx} / @code{.ARM.extab}) are currently supported.
4715 @cindex ELF dynamic section information
4716 Displays the contents of the file's dynamic section, if it has one.
4719 @itemx --version-info
4720 @cindex ELF version sections information
4721 Displays the contents of the version sections in the file, it they
4725 @itemx --arch-specific
4726 Displays architecture-specific information in the file, if there
4730 @itemx --use-dynamic
4731 When displaying symbols, this option makes @command{readelf} use the
4732 symbol hash tables in the file's dynamic section, rather than the
4733 symbol table sections.
4735 When displaying relocations, this option makes @command{readelf}
4736 display the dynamic relocations rather than the static relocations.
4738 @item -x <number or name>
4739 @itemx --hex-dump=<number or name>
4740 Displays the contents of the indicated section as a hexadecimal bytes.
4741 A number identifies a particular section by index in the section table;
4742 any other string identifies all sections with that name in the object file.
4744 @item -R <number or name>
4745 @itemx --relocated-dump=<number or name>
4746 Displays the contents of the indicated section as a hexadecimal
4747 bytes. A number identifies a particular section by index in the
4748 section table; any other string identifies all sections with that name
4749 in the object file. The contents of the section will be relocated
4750 before they are displayed.
4752 @item -p <number or name>
4753 @itemx --string-dump=<number or name>
4754 Displays the contents of the indicated section as printable strings.
4755 A number identifies a particular section by index in the section table;
4756 any other string identifies all sections with that name in the object file.
4760 Requests that the section(s) being dumped by @option{x}, @option{R} or
4761 @option{p} options are decompressed before being displayed. If the
4762 section(s) are not compressed then they are displayed as is.
4765 @itemx --archive-index
4766 @cindex Archive file symbol index information
4767 Displays the file symbol index information contained in the header part
4768 of binary archives. Performs the same function as the @option{t}
4769 command to @command{ar}, but without using the BFD library. @xref{ar}.
4771 @item -w[lLiaprmfFsoRtUuTgAckK]
4772 @itemx --debug-dump[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links]
4773 @include debug.options.texi
4777 Display a histogram of bucket list lengths when displaying the contents
4778 of the symbol tables.
4782 Display the version number of readelf.
4786 Don't break output lines to fit into 80 columns. By default
4787 @command{readelf} breaks section header and segment listing lines for
4788 64-bit ELF files, so that they fit into 80 columns. This option causes
4789 @command{readelf} to print each section header resp. each segment one a
4790 single line, which is far more readable on terminals wider than 80 columns.
4794 Display the command line options understood by @command{readelf}.
4801 @c man begin SEEALSO readelf
4802 objdump(1), and the Info entries for @file{binutils}.
4809 @cindex Update ELF header
4812 @c man title elfedit Update the ELF header of ELF files.
4815 @c man begin SYNOPSIS elfedit
4816 elfedit [@option{--input-mach=}@var{machine}]
4817 [@option{--input-type=}@var{type}]
4818 [@option{--input-osabi=}@var{osabi}]
4819 @option{--output-mach=}@var{machine}
4820 @option{--output-type=}@var{type}
4821 @option{--output-osabi=}@var{osabi}
4822 [@option{-v}|@option{--version}]
4823 [@option{-h}|@option{--help}]
4824 @var{elffile}@dots{}
4828 @c man begin DESCRIPTION elfedit
4830 @command{elfedit} updates the ELF header of ELF files which have
4831 the matching ELF machine and file types. The options control how and
4832 which fields in the ELF header should be updated.
4834 @var{elffile}@dots{} are the ELF files to be updated. 32-bit and
4835 64-bit ELF files are supported, as are archives containing ELF files.
4838 @c man begin OPTIONS elfedit
4840 The long and short forms of options, shown here as alternatives, are
4841 equivalent. At least one of the @option{--output-mach},
4842 @option{--output-type} and @option{--output-osabi} options must be given.
4846 @item --input-mach=@var{machine}
4847 Set the matching input ELF machine type to @var{machine}. If
4848 @option{--input-mach} isn't specified, it will match any ELF
4851 The supported ELF machine types are, @var{i386}, @var{IAMCU}, @var{L1OM},
4852 @var{K1OM} and @var{x86-64}.
4854 @item --output-mach=@var{machine}
4855 Change the ELF machine type in the ELF header to @var{machine}. The
4856 supported ELF machine types are the same as @option{--input-mach}.
4858 @item --input-type=@var{type}
4859 Set the matching input ELF file type to @var{type}. If
4860 @option{--input-type} isn't specified, it will match any ELF file types.
4862 The supported ELF file types are, @var{rel}, @var{exec} and @var{dyn}.
4864 @item --output-type=@var{type}
4865 Change the ELF file type in the ELF header to @var{type}. The
4866 supported ELF types are the same as @option{--input-type}.
4868 @item --input-osabi=@var{osabi}
4869 Set the matching input ELF file OSABI to @var{osabi}. If
4870 @option{--input-osabi} isn't specified, it will match any ELF OSABIs.
4872 The supported ELF OSABIs are, @var{none}, @var{HPUX}, @var{NetBSD},
4873 @var{GNU}, @var{Linux} (alias for @var{GNU}),
4874 @var{Solaris}, @var{AIX}, @var{Irix},
4875 @var{FreeBSD}, @var{TRU64}, @var{Modesto}, @var{OpenBSD}, @var{OpenVMS},
4876 @var{NSK}, @var{AROS} and @var{FenixOS}.
4878 @item --output-osabi=@var{osabi}
4879 Change the ELF OSABI in the ELF header to @var{osabi}. The
4880 supported ELF OSABI are the same as @option{--input-osabi}.
4884 Display the version number of @command{elfedit}.
4888 Display the command line options understood by @command{elfedit}.
4895 @c man begin SEEALSO elfedit
4896 readelf(1), and the Info entries for @file{binutils}.
4900 @node Common Options
4901 @chapter Common Options
4903 The following command-line options are supported by all of the
4904 programs described in this manual.
4906 @c man begin OPTIONS
4908 @include at-file.texi
4912 Display the command-line options supported by the program.
4915 Display the version number of the program.
4917 @c man begin OPTIONS
4921 @node Selecting the Target System
4922 @chapter Selecting the Target System
4924 You can specify two aspects of the target system to the @sc{gnu}
4925 binary file utilities, each in several ways:
4935 In the following summaries, the lists of ways to specify values are in
4936 order of decreasing precedence. The ways listed first override those
4939 The commands to list valid values only list the values for which the
4940 programs you are running were configured. If they were configured with
4941 @option{--enable-targets=all}, the commands list most of the available
4942 values, but a few are left out; not all targets can be configured in at
4943 once because some of them can only be configured @dfn{native} (on hosts
4944 with the same type as the target system).
4947 * Target Selection::
4948 * Architecture Selection::
4951 @node Target Selection
4952 @section Target Selection
4954 A @dfn{target} is an object file format. A given target may be
4955 supported for multiple architectures (@pxref{Architecture Selection}).
4956 A target selection may also have variations for different operating
4957 systems or architectures.
4959 The command to list valid target values is @samp{objdump -i}
4960 (the first column of output contains the relevant information).
4962 Some sample values are: @samp{a.out-hp300bsd}, @samp{ecoff-littlemips},
4963 @samp{a.out-sunos-big}.
4965 You can also specify a target using a configuration triplet. This is
4966 the same sort of name that is passed to @file{configure} to specify a
4967 target. When you use a configuration triplet as an argument, it must be
4968 fully canonicalized. You can see the canonical version of a triplet by
4969 running the shell script @file{config.sub} which is included with the
4972 Some sample configuration triplets are: @samp{m68k-hp-bsd},
4973 @samp{mips-dec-ultrix}, @samp{sparc-sun-sunos}.
4975 @subheading @command{objdump} Target
4981 command line option: @option{-b} or @option{--target}
4984 environment variable @code{GNUTARGET}
4987 deduced from the input file
4990 @subheading @command{objcopy} and @command{strip} Input Target
4996 command line options: @option{-I} or @option{--input-target}, or @option{-F} or @option{--target}
4999 environment variable @code{GNUTARGET}
5002 deduced from the input file
5005 @subheading @command{objcopy} and @command{strip} Output Target
5011 command line options: @option{-O} or @option{--output-target}, or @option{-F} or @option{--target}
5014 the input target (see ``@command{objcopy} and @command{strip} Input Target'' above)
5017 environment variable @code{GNUTARGET}
5020 deduced from the input file
5023 @subheading @command{nm}, @command{size}, and @command{strings} Target
5029 command line option: @option{--target}
5032 environment variable @code{GNUTARGET}
5035 deduced from the input file
5038 @node Architecture Selection
5039 @section Architecture Selection
5041 An @dfn{architecture} is a type of @sc{cpu} on which an object file is
5042 to run. Its name may contain a colon, separating the name of the
5043 processor family from the name of the particular @sc{cpu}.
5045 The command to list valid architecture values is @samp{objdump -i} (the
5046 second column contains the relevant information).
5048 Sample values: @samp{m68k:68020}, @samp{mips:3000}, @samp{sparc}.
5050 @subheading @command{objdump} Architecture
5056 command line option: @option{-m} or @option{--architecture}
5059 deduced from the input file
5062 @subheading @command{objcopy}, @command{nm}, @command{size}, @command{strings} Architecture
5068 deduced from the input file
5071 @node Reporting Bugs
5072 @chapter Reporting Bugs
5074 @cindex reporting bugs
5076 Your bug reports play an essential role in making the binary utilities
5079 Reporting a bug may help you by bringing a solution to your problem, or
5080 it may not. But in any case the principal function of a bug report is
5081 to help the entire community by making the next version of the binary
5082 utilities work better. Bug reports are your contribution to their
5085 In order for a bug report to serve its purpose, you must include the
5086 information that enables us to fix the bug.
5089 * Bug Criteria:: Have you found a bug?
5090 * Bug Reporting:: How to report bugs
5094 @section Have You Found a Bug?
5095 @cindex bug criteria
5097 If you are not sure whether you have found a bug, here are some guidelines:
5100 @cindex fatal signal
5103 If a binary utility gets a fatal signal, for any input whatever, that is
5104 a bug. Reliable utilities never crash.
5106 @cindex error on valid input
5108 If a binary utility produces an error message for valid input, that is a
5112 If you are an experienced user of binary utilities, your suggestions for
5113 improvement are welcome in any case.
5117 @section How to Report Bugs
5119 @cindex bugs, reporting
5121 A number of companies and individuals offer support for @sc{gnu}
5122 products. If you obtained the binary utilities from a support
5123 organization, we recommend you contact that organization first.
5125 You can find contact information for many support companies and
5126 individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs
5130 In any event, we also recommend that you send bug reports for the binary
5131 utilities to @value{BUGURL}.
5134 The fundamental principle of reporting bugs usefully is this:
5135 @strong{report all the facts}. If you are not sure whether to state a
5136 fact or leave it out, state it!
5138 Often people omit facts because they think they know what causes the
5139 problem and assume that some details do not matter. Thus, you might
5140 assume that the name of a file you use in an example does not matter.
5141 Well, probably it does not, but one cannot be sure. Perhaps the bug is
5142 a stray memory reference which happens to fetch from the location where
5143 that pathname is stored in memory; perhaps, if the pathname were
5144 different, the contents of that location would fool the utility into
5145 doing the right thing despite the bug. Play it safe and give a
5146 specific, complete example. That is the easiest thing for you to do,
5147 and the most helpful.
5149 Keep in mind that the purpose of a bug report is to enable us to fix the bug if
5150 it is new to us. Therefore, always write your bug reports on the assumption
5151 that the bug has not been reported previously.
5153 Sometimes people give a few sketchy facts and ask, ``Does this ring a
5154 bell?'' This cannot help us fix a bug, so it is basically useless. We
5155 respond by asking for enough details to enable us to investigate.
5156 You might as well expedite matters by sending them to begin with.
5158 To enable us to fix the bug, you should include all these things:
5162 The version of the utility. Each utility announces it if you start it
5163 with the @option{--version} argument.
5165 Without this, we will not know whether there is any point in looking for
5166 the bug in the current version of the binary utilities.
5169 Any patches you may have applied to the source, including any patches
5170 made to the @code{BFD} library.
5173 The type of machine you are using, and the operating system name and
5177 What compiler (and its version) was used to compile the utilities---e.g.
5181 The command arguments you gave the utility to observe the bug. To
5182 guarantee you will not omit something important, list them all. A copy
5183 of the Makefile (or the output from make) is sufficient.
5185 If we were to try to guess the arguments, we would probably guess wrong
5186 and then we might not encounter the bug.
5189 A complete input file, or set of input files, that will reproduce the
5190 bug. If the utility is reading an object file or files, then it is
5191 generally most helpful to send the actual object files.
5193 If the source files were produced exclusively using @sc{gnu} programs
5194 (e.g., @command{gcc}, @command{gas}, and/or the @sc{gnu} @command{ld}), then it
5195 may be OK to send the source files rather than the object files. In
5196 this case, be sure to say exactly what version of @command{gcc}, or
5197 whatever, was used to produce the object files. Also say how
5198 @command{gcc}, or whatever, was configured.
5201 A description of what behavior you observe that you believe is
5202 incorrect. For example, ``It gets a fatal signal.''
5204 Of course, if the bug is that the utility gets a fatal signal, then we
5205 will certainly notice it. But if the bug is incorrect output, we might
5206 not notice unless it is glaringly wrong. You might as well not give us
5207 a chance to make a mistake.
5209 Even if the problem you experience is a fatal signal, you should still
5210 say so explicitly. Suppose something strange is going on, such as your
5211 copy of the utility is out of sync, or you have encountered a bug in
5212 the C library on your system. (This has happened!) Your copy might
5213 crash and ours would not. If you told us to expect a crash, then when
5214 ours fails to crash, we would know that the bug was not happening for
5215 us. If you had not told us to expect a crash, then we would not be able
5216 to draw any conclusion from our observations.
5219 If you wish to suggest changes to the source, send us context diffs, as
5220 generated by @command{diff} with the @option{-u}, @option{-c}, or @option{-p}
5221 option. Always send diffs from the old file to the new file. If you
5222 wish to discuss something in the @command{ld} source, refer to it by
5223 context, not by line number.
5225 The line numbers in our development sources will not match those in your
5226 sources. Your line numbers would convey no useful information to us.
5229 Here are some things that are not necessary:
5233 A description of the envelope of the bug.
5235 Often people who encounter a bug spend a lot of time investigating
5236 which changes to the input file will make the bug go away and which
5237 changes will not affect it.
5239 This is often time consuming and not very useful, because the way we
5240 will find the bug is by running a single example under the debugger
5241 with breakpoints, not by pure deduction from a series of examples.
5242 We recommend that you save your time for something else.
5244 Of course, if you can find a simpler example to report @emph{instead}
5245 of the original one, that is a convenience for us. Errors in the
5246 output will be easier to spot, running under the debugger will take
5247 less time, and so on.
5249 However, simplification is not vital; if you do not want to do this,
5250 report the bug anyway and send us the entire test case you used.
5253 A patch for the bug.
5255 A patch for the bug does help us if it is a good one. But do not omit
5256 the necessary information, such as the test case, on the assumption that
5257 a patch is all we need. We might see problems with your patch and decide
5258 to fix the problem another way, or we might not understand it at all.
5260 Sometimes with programs as complicated as the binary utilities it is
5261 very hard to construct an example that will make the program follow a
5262 certain path through the code. If you do not send us the example, we
5263 will not be able to construct one, so we will not be able to verify that
5266 And if we cannot understand what bug you are trying to fix, or why your
5267 patch should be an improvement, we will not install it. A test case will
5268 help us to understand.
5271 A guess about what the bug is or what it depends on.
5273 Such guesses are usually wrong. Even we cannot guess right about such
5274 things without first using the debugger to find the facts.
5277 @node GNU Free Documentation License
5278 @appendix GNU Free Documentation License
5282 @node Binutils Index
5283 @unnumbered Binutils Index