1 \input texinfo @c -*- Texinfo -*-
2 @setfilename binutils.info
3 @settitle @sc{gnu} Binary Utilities
12 @c man begin COPYRIGHT
13 Copyright @copyright{} 1991-2020 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 * nm: (binutils)nm. List symbols from object files.
38 * objcopy: (binutils)objcopy. Copy and translate object files.
39 * objdump: (binutils)objdump. Display information from object files.
40 * ranlib: (binutils)ranlib. Generate index to archive contents.
41 * readelf: (binutils)readelf. Display the contents of ELF format files.
42 * size: (binutils)size. List section sizes and total size.
43 * strings: (binutils)strings. List printable strings from files.
44 * strip: (binutils)strip. Discard symbols.
45 * elfedit: (binutils)elfedit. Update ELF header and property of ELF files.
46 * windmc: (binutils)windmc. Generator for Windows message resources.
47 * windres: (binutils)windres. Manipulate Windows resources.
51 @title The @sc{gnu} Binary Utilities
52 @ifset VERSION_PACKAGE
53 @subtitle @value{VERSION_PACKAGE}
55 @subtitle Version @value{VERSION}
57 @subtitle @value{UPDATED}
58 @author Roland H. Pesch
59 @author Jeffrey M. Osier
60 @author Cygnus Support
64 {\parskip=0pt \hfill Cygnus Support\par \hfill
65 Texinfo \texinfoversion\par }
68 @vskip 0pt plus 1filll
77 This brief manual contains documentation for the @sc{gnu} binary
79 @ifset VERSION_PACKAGE
80 @value{VERSION_PACKAGE}
82 version @value{VERSION}:
87 Create, modify, and extract from archives
90 List symbols from object files
93 Copy and translate object files
96 Display information from object files
99 Generate index to archive contents
102 Display the contents of ELF format files.
105 List file section sizes and total size
108 List printable strings from files
114 Update the ELF header and program property of ELF files.
117 Demangle encoded C++ symbols (on MS-DOS, this program is named
121 Convert addresses into file names and line numbers
124 Manipulate Windows resources
127 Generator for Windows message resources
130 Create the files needed to build and use Dynamic Link Libraries
134 This document is distributed under the terms of the GNU Free
135 Documentation License version 1.3. A copy of the license is included
136 in the section entitled ``GNU Free Documentation License''.
139 * ar:: Create, modify, and extract from archives
140 * nm:: List symbols from object files
141 * objcopy:: Copy and translate object files
142 * objdump:: Display information from object files
143 * ranlib:: Generate index to archive contents
144 * size:: List section sizes and total size
145 * strings:: List printable strings from files
146 * strip:: Discard symbols
147 * c++filt:: Filter to demangle encoded C++ symbols
148 * cxxfilt: c++filt. MS-DOS name for c++filt
149 * addr2line:: Convert addresses to file and line
150 * windmc:: Generator for Windows message resources
151 * windres:: Manipulate Windows resources
152 * dlltool:: Create files needed to build and use DLLs
153 * readelf:: Display the contents of ELF format files
154 * elfedit:: Update ELF header and property of ELF files
155 * Common Options:: Command-line options for all utilities
156 * Selecting the Target System:: How these utilities determine the target
157 * debuginfod:: Using binutils with debuginfod
158 * Reporting Bugs:: Reporting Bugs
159 * GNU Free Documentation License:: GNU Free Documentation License
160 * Binutils Index:: Binutils Index
168 @cindex collections of files
170 @c man title ar create, modify, and extract from archives
173 ar [-]@var{p}[@var{mod}] [@option{--plugin} @var{name}] [@option{--target} @var{bfdname}] [@option{--output} @var{dirname}] [@var{relpos}] [@var{count}] @var{archive} [@var{member}@dots{}]
174 ar -M [ <mri-script ]
177 @c man begin DESCRIPTION ar
179 The @sc{gnu} @command{ar} program creates, modifies, and extracts from
180 archives. An @dfn{archive} is a single file holding a collection of
181 other files in a structure that makes it possible to retrieve
182 the original individual files (called @dfn{members} of the archive).
184 The original files' contents, mode (permissions), timestamp, owner, and
185 group are preserved in the archive, and can be restored on
189 @sc{gnu} @command{ar} can maintain archives whose members have names of any
190 length; however, depending on how @command{ar} is configured on your
191 system, a limit on member-name length may be imposed for compatibility
192 with archive formats maintained with other tools. If it exists, the
193 limit is often 15 characters (typical of formats related to a.out) or 16
194 characters (typical of formats related to coff).
197 @command{ar} is considered a binary utility because archives of this sort
198 are most often used as @dfn{libraries} holding commonly needed
202 @command{ar} creates an index to the symbols defined in relocatable
203 object modules in the archive when you specify the modifier @samp{s}.
204 Once created, this index is updated in the archive whenever @command{ar}
205 makes a change to its contents (save for the @samp{q} update operation).
206 An archive with such an index speeds up linking to the library, and
207 allows routines in the library to call each other without regard to
208 their placement in the archive.
210 You may use @samp{nm -s} or @samp{nm --print-armap} to list this index
211 table. If an archive lacks the table, another form of @command{ar} called
212 @command{ranlib} can be used to add just the table.
214 @cindex thin archives
215 @sc{gnu} @command{ar} can optionally create a @emph{thin} archive,
216 which contains a symbol index and references to the original copies
217 of the member files of the archive. This is useful for building
218 libraries for use within a local build tree, where the relocatable
219 objects are expected to remain available, and copying the contents of
220 each object would only waste time and space.
222 An archive can either be @emph{thin} or it can be normal. It cannot
223 be both at the same time. Once an archive is created its format
224 cannot be changed without first deleting it and then creating a new
225 archive in its place.
227 Thin archives are also @emph{flattened}, so that adding one thin
228 archive to another thin archive does not nest it, as would happen with
229 a normal archive. Instead the elements of the first archive are added
230 individually to the second archive.
232 The paths to the elements of the archive are stored relative to the
235 @cindex compatibility, @command{ar}
236 @cindex @command{ar} compatibility
237 @sc{gnu} @command{ar} is designed to be compatible with two different
238 facilities. You can control its activity using command-line options,
239 like the different varieties of @command{ar} on Unix systems; or, if you
240 specify the single command-line option @option{-M}, you can control it
241 with a script supplied via standard input, like the MRI ``librarian''
247 * ar cmdline:: Controlling @command{ar} on the command line
248 * ar scripts:: Controlling @command{ar} with a script
253 @section Controlling @command{ar} on the Command Line
256 @c man begin SYNOPSIS ar
257 ar [@option{-X32_64}] [@option{-}]@var{p}[@var{mod}] [@option{--plugin} @var{name}] [@option{--target} @var{bfdname}] [@option{--output} @var{dirname}] [@var{relpos}] [@var{count}] @var{archive} [@var{member}@dots{}]
261 @cindex Unix compatibility, @command{ar}
262 When you use @command{ar} in the Unix style, @command{ar} insists on at least two
263 arguments to execute: one keyletter specifying the @emph{operation}
264 (optionally accompanied by other keyletters specifying
265 @emph{modifiers}), and the archive name to act on.
267 Most operations can also accept further @var{member} arguments,
268 specifying particular files to operate on.
270 @c man begin OPTIONS ar
272 @sc{gnu} @command{ar} allows you to mix the operation code @var{p} and modifier
273 flags @var{mod} in any order, within the first command-line argument.
275 If you wish, you may begin the first command-line argument with a
278 @cindex operations on archive
279 The @var{p} keyletter specifies what operation to execute; it may be
280 any of the following, but you must specify only one of them:
284 @cindex deleting from archive
285 @emph{Delete} modules from the archive. Specify the names of modules to
286 be deleted as @var{member}@dots{}; the archive is untouched if you
287 specify no files to delete.
289 If you specify the @samp{v} modifier, @command{ar} lists each module
293 @cindex moving in archive
294 Use this operation to @emph{move} members in an archive.
296 The ordering of members in an archive can make a difference in how
297 programs are linked using the library, if a symbol is defined in more
300 If no modifiers are used with @code{m}, any members you name in the
301 @var{member} arguments are moved to the @emph{end} of the archive;
302 you can use the @samp{a}, @samp{b}, or @samp{i} modifiers to move them to a
303 specified place instead.
306 @cindex printing from archive
307 @emph{Print} the specified members of the archive, to the standard
308 output file. If the @samp{v} modifier is specified, show the member
309 name before copying its contents to standard output.
311 If you specify no @var{member} arguments, all the files in the archive are
315 @cindex quick append to archive
316 @emph{Quick append}; Historically, add the files @var{member}@dots{} to the end of
317 @var{archive}, without checking for replacement.
319 The modifiers @samp{a}, @samp{b}, and @samp{i} do @emph{not} affect this
320 operation; new members are always placed at the end of the archive.
322 The modifier @samp{v} makes @command{ar} list each file as it is appended.
324 Since the point of this operation is speed, implementations of
325 @command{ar} have the option of not updating the archive's symbol
326 table if one exists. Too many different systems however assume that
327 symbol tables are always up-to-date, so @sc{gnu} @command{ar} will
328 rebuild the table even with a quick append.
330 Note - @sc{gnu} @command{ar} treats the command @samp{qs} as a
331 synonym for @samp{r} - replacing already existing files in the
332 archive and appending new ones at the end.
335 @cindex replacement in archive
336 Insert the files @var{member}@dots{} into @var{archive} (with
337 @emph{replacement}). This operation differs from @samp{q} in that any
338 previously existing members are deleted if their names match those being
341 If one of the files named in @var{member}@dots{} does not exist, @command{ar}
342 displays an error message, and leaves undisturbed any existing members
343 of the archive matching that name.
345 By default, new members are added at the end of the file; but you may
346 use one of the modifiers @samp{a}, @samp{b}, or @samp{i} to request
347 placement relative to some existing member.
349 The modifier @samp{v} used with this operation elicits a line of
350 output for each file inserted, along with one of the letters @samp{a} or
351 @samp{r} to indicate whether the file was appended (no old member
352 deleted) or replaced.
356 Add an index to the archive, or update it if it already exists. Note
357 this command is an exception to the rule that there can only be one
358 command letter, as it is possible to use it as either a command or a
359 modifier. In either case it does the same thing.
362 @cindex contents of archive
363 Display a @emph{table} listing the contents of @var{archive}, or those
364 of the files listed in @var{member}@dots{} that are present in the
365 archive. Normally only the member name is shown, but if the modifier
366 @samp{O} is specified, then the corresponding offset of the member is also
367 displayed. Finally, in order to see the modes (permissions), timestamp,
368 owner, group, and size the @samp{v} modifier should be included.
370 If you do not specify a @var{member}, all files in the archive
373 @cindex repeated names in archive
374 @cindex name duplication in archive
375 If there is more than one file with the same name (say, @samp{fie}) in
376 an archive (say @samp{b.a}), @samp{ar t b.a fie} lists only the
377 first instance; to see them all, you must ask for a complete
378 listing---in our example, @samp{ar t b.a}.
379 @c WRS only; per Gumby, this is implementation-dependent, and in a more
380 @c recent case in fact works the other way.
383 @cindex extract from archive
384 @emph{Extract} members (named @var{member}) from the archive. You can
385 use the @samp{v} modifier with this operation, to request that
386 @command{ar} list each name as it extracts it.
388 If you do not specify a @var{member}, all files in the archive
391 Files cannot be extracted from a thin archive, and there are
392 restrictions on extracting from archives created with @option{P}: The
393 paths must not be absolute, may not contain @code{..}, and any
394 subdirectories in the paths must exist. If it is desired to avoid
395 these restrictions then used the @option{--output} option to specify
399 A number of modifiers (@var{mod}) may immediately follow the @var{p}
400 keyletter, to specify variations on an operation's behavior:
404 @cindex relative placement in archive
405 Add new files @emph{after} an existing member of the
406 archive. If you use the modifier @samp{a}, the name of an existing archive
407 member must be present as the @var{relpos} argument, before the
408 @var{archive} specification.
411 Add new files @emph{before} an existing member of the
412 archive. If you use the modifier @samp{b}, the name of an existing archive
413 member must be present as the @var{relpos} argument, before the
414 @var{archive} specification. (same as @samp{i}).
417 @cindex creating archives
418 @emph{Create} the archive. The specified @var{archive} is always
419 created if it did not exist, when you request an update. But a warning is
420 issued unless you specify in advance that you expect to create it, by
424 @cindex deterministic archives
425 @kindex --enable-deterministic-archives
426 Operate in @emph{deterministic} mode. When adding files and the archive
427 index use zero for UIDs, GIDs, timestamps, and use consistent file modes
428 for all files. When this option is used, if @command{ar} is used with
429 identical options and identical input files, multiple runs will create
430 identical output files regardless of the input files' owners, groups,
431 file modes, or modification times.
433 If @file{binutils} was configured with
434 @option{--enable-deterministic-archives}, then this mode is on by default.
435 It can be disabled with the @samp{U} modifier, below.
438 Truncate names in the archive. @sc{gnu} @command{ar} will normally permit file
439 names of any length. This will cause it to create archives which are
440 not compatible with the native @command{ar} program on some systems. If
441 this is a concern, the @samp{f} modifier may be used to truncate file
442 names when putting them in the archive.
445 Insert new files @emph{before} an existing member of the
446 archive. If you use the modifier @samp{i}, the name of an existing archive
447 member must be present as the @var{relpos} argument, before the
448 @var{archive} specification. (same as @samp{b}).
451 This modifier is accepted but not used.
452 @c whaffor ar l modifier??? presumably compat; with
453 @c what???---doc@@cygnus.com, 25jan91
456 Uses the @var{count} parameter. This is used if there are multiple
457 entries in the archive with the same name. Extract or delete instance
458 @var{count} of the given name from the archive.
461 @cindex dates in archive
462 Preserve the @emph{original} dates of members when extracting them. If
463 you do not specify this modifier, files extracted from the archive
464 are stamped with the time of extraction.
467 @cindex offsets of files
468 Display member offsets inside the archive. Use together with the @samp{t}
472 Use the full path name when matching or storing names in the archive.
473 Archives created with full path names are not POSIX compliant, and
474 thus may not work with tools other than up to date @sc{gnu} tools.
475 Modifying such archives with @sc{gnu} @command{ar} without using
476 @option{P} will remove the full path names unless the archive is a
477 thin archive. Note that @option{P} may be useful when adding files to
478 a thin archive since @option{r} without @option{P} ignores the path
479 when choosing which element to replace. Thus
481 ar rcST archive.a subdir/file1 subdir/file2 file1
483 will result in the first @code{subdir/file1} being replaced with
484 @code{file1} from the current directory. Adding @option{P} will
485 prevent this replacement.
488 @cindex writing archive index
489 Write an object-file index into the archive, or update an existing one,
490 even if no other change is made to the archive. You may use this modifier
491 flag either with any operation, or alone. Running @samp{ar s} on an
492 archive is equivalent to running @samp{ranlib} on it.
495 @cindex not writing archive index
496 Do not generate an archive symbol table. This can speed up building a
497 large library in several steps. The resulting archive can not be used
498 with the linker. In order to build a symbol table, you must omit the
499 @samp{S} modifier on the last execution of @samp{ar}, or you must run
500 @samp{ranlib} on the archive.
503 @cindex creating thin archive
504 Make the specified @var{archive} a @emph{thin} archive. If it already
505 exists and is a regular archive, the existing members must be present
506 in the same directory as @var{archive}.
509 @cindex updating an archive
510 Normally, @samp{ar r}@dots{} inserts all files
511 listed into the archive. If you would like to insert @emph{only} those
512 of the files you list that are newer than existing members of the same
513 names, use this modifier. The @samp{u} modifier is allowed only for the
514 operation @samp{r} (replace). In particular, the combination @samp{qu} is
515 not allowed, since checking the timestamps would lose any speed
516 advantage from the operation @samp{q}.
519 @cindex deterministic archives
520 @kindex --enable-deterministic-archives
521 Do @emph{not} operate in @emph{deterministic} mode. This is the inverse
522 of the @samp{D} modifier, above: added files and the archive index will
523 get their actual UID, GID, timestamp, and file mode values.
525 This is the default unless @file{binutils} was configured with
526 @option{--enable-deterministic-archives}.
529 This modifier requests the @emph{verbose} version of an operation. Many
530 operations display additional information, such as filenames processed,
531 when the modifier @samp{v} is appended.
534 This modifier shows the version number of @command{ar}.
537 The @command{ar} program also supports some command-line options which
538 are neither modifiers nor actions, but which do change its behaviour
543 Displays the list of command-line options supported by @command{ar}
547 Displays the version information of @command{ar} and then exits.
550 @command{ar} ignores an initial option spelled @samp{-X32_64}, for
551 compatibility with AIX. The behaviour produced by this option is the
552 default for @sc{gnu} @command{ar}. @command{ar} does not support any
553 of the other @samp{-X} options; in particular, it does not support
554 @option{-X32} which is the default for AIX @command{ar}.
556 @item --plugin @var{name}
558 The optional command-line switch @option{--plugin @var{name}} causes
559 @command{ar} to load the plugin called @var{name} which adds support
560 for more file formats, including object files with link-time
561 optimization information.
563 This option is only available if the toolchain has been built with
564 plugin support enabled.
566 If @option{--plugin} is not provided, but plugin support has been
567 enabled then @command{ar} iterates over the files in
568 @file{$@{libdir@}/bfd-plugins} in alphabetic order and the first
569 plugin that claims the object in question is used.
571 Please note that this plugin search directory is @emph{not} the one
572 used by @command{ld}'s @option{-plugin} option. In order to make
573 @command{ar} use the linker plugin it must be copied into the
574 @file{$@{libdir@}/bfd-plugins} directory. For GCC based compilations
575 the linker plugin is called @file{liblto_plugin.so.0.0.0}. For Clang
576 based compilations it is called @file{LLVMgold.so}. The GCC plugin
577 is always backwards compatible with earlier versions, so it is
578 sufficient to just copy the newest one.
580 @item --target @var{target}
581 The optional command-line switch @option{--target @var{bfdname}}
582 specifies that the archive members are in an object code format
583 different from your system's default format. See
584 @xref{Target Selection}, for more information.
586 @item --output @var{dirname}
587 The @option{--output} option can be used to specify a path to a
588 directory into which archive members should be extracted. If this
589 option is not specified then the current directory will be used.
591 Note - although the presence of this option does imply a @option{x}
592 extraction operation that option must still be included on the command
599 @c man begin SEEALSO ar
600 nm(1), ranlib(1), and the Info entries for @file{binutils}.
605 @section Controlling @command{ar} with a Script
608 ar -M [ <@var{script} ]
611 @cindex MRI compatibility, @command{ar}
612 @cindex scripts, @command{ar}
613 If you use the single command-line option @samp{-M} with @command{ar}, you
614 can control its operation with a rudimentary command language. This
615 form of @command{ar} operates interactively if standard input is coming
616 directly from a terminal. During interactive use, @command{ar} prompts for
617 input (the prompt is @samp{AR >}), and continues executing even after
618 errors. If you redirect standard input to a script file, no prompts are
619 issued, and @command{ar} abandons execution (with a nonzero exit code)
622 The @command{ar} command language is @emph{not} designed to be equivalent
623 to the command-line options; in fact, it provides somewhat less control
624 over archives. The only purpose of the command language is to ease the
625 transition to @sc{gnu} @command{ar} for developers who already have scripts
626 written for the MRI ``librarian'' program.
628 The syntax for the @command{ar} command language is straightforward:
631 commands are recognized in upper or lower case; for example, @code{LIST}
632 is the same as @code{list}. In the following descriptions, commands are
633 shown in upper case for clarity.
636 a single command may appear on each line; it is the first word on the
640 empty lines are allowed, and have no effect.
643 comments are allowed; text after either of the characters @samp{*}
644 or @samp{;} is ignored.
647 Whenever you use a list of names as part of the argument to an @command{ar}
648 command, you can separate the individual names with either commas or
649 blanks. Commas are shown in the explanations below, for clarity.
652 @samp{+} is used as a line continuation character; if @samp{+} appears
653 at the end of a line, the text on the following line is considered part
654 of the current command.
657 Here are the commands you can use in @command{ar} scripts, or when using
658 @command{ar} interactively. Three of them have special significance:
660 @code{OPEN} or @code{CREATE} specify a @dfn{current archive}, which is
661 a temporary file required for most of the other commands.
663 @code{SAVE} commits the changes so far specified by the script. Prior
664 to @code{SAVE}, commands affect only the temporary copy of the current
668 @item ADDLIB @var{archive}
669 @itemx ADDLIB @var{archive} (@var{module}, @var{module}, @dots{} @var{module})
670 Add all the contents of @var{archive} (or, if specified, each named
671 @var{module} from @var{archive}) to the current archive.
673 Requires prior use of @code{OPEN} or @code{CREATE}.
675 @item ADDMOD @var{member}, @var{member}, @dots{} @var{member}
676 @c FIXME! w/Replacement?? If so, like "ar r @var{archive} @var{names}"
677 @c else like "ar q..."
678 Add each named @var{member} as a module in the current archive.
680 Requires prior use of @code{OPEN} or @code{CREATE}.
683 Discard the contents of the current archive, canceling the effect of
684 any operations since the last @code{SAVE}. May be executed (with no
685 effect) even if no current archive is specified.
687 @item CREATE @var{archive}
688 Creates an archive, and makes it the current archive (required for many
689 other commands). The new archive is created with a temporary name; it
690 is not actually saved as @var{archive} until you use @code{SAVE}.
691 You can overwrite existing archives; similarly, the contents of any
692 existing file named @var{archive} will not be destroyed until @code{SAVE}.
694 @item DELETE @var{module}, @var{module}, @dots{} @var{module}
695 Delete each listed @var{module} from the current archive; equivalent to
696 @samp{ar -d @var{archive} @var{module} @dots{} @var{module}}.
698 Requires prior use of @code{OPEN} or @code{CREATE}.
700 @item DIRECTORY @var{archive} (@var{module}, @dots{} @var{module})
701 @itemx DIRECTORY @var{archive} (@var{module}, @dots{} @var{module}) @var{outputfile}
702 List each named @var{module} present in @var{archive}. The separate
703 command @code{VERBOSE} specifies the form of the output: when verbose
704 output is off, output is like that of @samp{ar -t @var{archive}
705 @var{module}@dots{}}. When verbose output is on, the listing is like
706 @samp{ar -tv @var{archive} @var{module}@dots{}}.
708 Output normally goes to the standard output stream; however, if you
709 specify @var{outputfile} as a final argument, @command{ar} directs the
713 Exit from @command{ar}, with a @code{0} exit code to indicate successful
714 completion. This command does not save the output file; if you have
715 changed the current archive since the last @code{SAVE} command, those
718 @item EXTRACT @var{module}, @var{module}, @dots{} @var{module}
719 Extract each named @var{module} from the current archive, writing them
720 into the current directory as separate files. Equivalent to @samp{ar -x
721 @var{archive} @var{module}@dots{}}.
723 Requires prior use of @code{OPEN} or @code{CREATE}.
726 @c FIXME Tokens but no commands???
733 Display full contents of the current archive, in ``verbose'' style
734 regardless of the state of @code{VERBOSE}. The effect is like @samp{ar
735 tv @var{archive}}. (This single command is a @sc{gnu} @command{ar}
736 enhancement, rather than present for MRI compatibility.)
738 Requires prior use of @code{OPEN} or @code{CREATE}.
740 @item OPEN @var{archive}
741 Opens an existing archive for use as the current archive (required for
742 many other commands). Any changes as the result of subsequent commands
743 will not actually affect @var{archive} until you next use @code{SAVE}.
745 @item REPLACE @var{module}, @var{module}, @dots{} @var{module}
746 In the current archive, replace each existing @var{module} (named in
747 the @code{REPLACE} arguments) from files in the current working directory.
748 To execute this command without errors, both the file, and the module in
749 the current archive, must exist.
751 Requires prior use of @code{OPEN} or @code{CREATE}.
754 Toggle an internal flag governing the output from @code{DIRECTORY}.
755 When the flag is on, @code{DIRECTORY} output matches output from
756 @samp{ar -tv }@dots{}.
759 Commit your changes to the current archive, and actually save it as a
760 file with the name specified in the last @code{CREATE} or @code{OPEN}
763 Requires prior use of @code{OPEN} or @code{CREATE}.
772 The @sc{gnu} linker @command{ld} is now described in a separate manual.
773 @xref{Top,, Overview,, Using LD: the @sc{gnu} linker}.
781 @c man title nm list symbols from object files
784 @c man begin SYNOPSIS nm
785 nm [@option{-A}|@option{-o}|@option{--print-file-name}] [@option{-a}|@option{--debug-syms}]
786 [@option{-B}|@option{--format=bsd}] [@option{-C}|@option{--demangle}[=@var{style}]]
787 [@option{-D}|@option{--dynamic}] [@option{-f}@var{format}|@option{--format=}@var{format}]
788 [@option{-g}|@option{--extern-only}] [@option{-h}|@option{--help}]
789 [@option{-l}|@option{--line-numbers}] [@option{--inlines}]
790 [@option{-n}|@option{-v}|@option{--numeric-sort}]
791 [@option{-P}|@option{--portability}] [@option{-p}|@option{--no-sort}]
792 [@option{-r}|@option{--reverse-sort}] [@option{-S}|@option{--print-size}]
793 [@option{-s}|@option{--print-armap}] [@option{-t} @var{radix}|@option{--radix=}@var{radix}]
794 [@option{-u}|@option{--undefined-only}] [@option{-V}|@option{--version}]
795 [@option{-X 32_64}] [@option{--defined-only}] [@option{--no-demangle}]
796 [@option{--plugin} @var{name}]
797 [@option{--no-recurse-limit}|@option{--recurse-limit}]]
798 [@option{--size-sort}] [@option{--special-syms}]
799 [@option{--synthetic}] [@option{--with-symbol-versions}] [@option{--target=}@var{bfdname}]
800 [@var{objfile}@dots{}]
804 @c man begin DESCRIPTION nm
805 @sc{gnu} @command{nm} lists the symbols from object files @var{objfile}@dots{}.
806 If no object files are listed as arguments, @command{nm} assumes the file
809 For each symbol, @command{nm} shows:
813 The symbol value, in the radix selected by options (see below), or
814 hexadecimal by default.
817 The symbol type. At least the following types are used; others are, as
818 well, depending on the object file format. If lowercase, the symbol is
819 usually local; if uppercase, the symbol is global (external). There
820 are however a few lowercase symbols that are shown for special global
821 symbols (@code{u}, @code{v} and @code{w}).
823 @c Some more detail on exactly what these symbol types are used for
827 The symbol's value is absolute, and will not be changed by further
832 The symbol is in the BSS data section. This section typically
833 contains zero-initialized or uninitialized data, although the exact
834 behavior is system dependent.
837 The symbol is common. Common symbols are uninitialized data. When
838 linking, multiple common symbols may appear with the same name. If the
839 symbol is defined anywhere, the common symbols are treated as undefined
842 For more details on common symbols, see the discussion of
843 --warn-common in @ref{Options,,Linker options,ld.info,The GNU linker}.
848 The symbol is in the initialized data section.
852 The symbol is in an initialized data section for small objects. Some
853 object file formats permit more efficient access to small data objects,
854 such as a global int variable as opposed to a large global array.
857 For PE format files this indicates that the symbol is in a section
858 specific to the implementation of DLLs. For ELF format files this
859 indicates that the symbol is an indirect function. This is a GNU
860 extension to the standard set of ELF symbol types. It indicates a
861 symbol which if referenced by a relocation does not evaluate to its
862 address, but instead must be invoked at runtime. The runtime
863 execution will then return the value to be used in the relocation.
866 The symbol is an indirect reference to another symbol.
869 The symbol is a debugging symbol.
872 The symbol is in the read-only data section.
875 The symbol is in a stack unwind section.
879 The symbol is in a read only data section.
883 The symbol is in an uninitialized or zero-initialized data section
888 The symbol is in the text (code) section.
891 The symbol is undefined.
894 The symbol is a unique global symbol. This is a GNU extension to the
895 standard set of ELF symbol bindings. For such a symbol the dynamic linker
896 will make sure that in the entire process there is just one symbol with
897 this name and type in use.
901 The symbol is a weak object. When a weak defined symbol is linked with
902 a normal defined symbol, the normal defined symbol is used with no error.
903 When a weak undefined symbol is linked and the symbol is not defined,
904 the value of the weak symbol becomes zero with no error. On some
905 systems, uppercase indicates that a default value has been specified.
909 The symbol is a weak symbol that has not been specifically tagged as a
910 weak object symbol. When a weak defined symbol is linked with a normal
911 defined symbol, the normal defined symbol is used with no error.
912 When a weak undefined symbol is linked and the symbol is not defined,
913 the value of the symbol is determined in a system-specific manner without
914 error. On some systems, uppercase indicates that a default value has been
918 The symbol is a stabs symbol in an a.out object file. In this case, the
919 next values printed are the stabs other field, the stabs desc field, and
920 the stab type. Stabs symbols are used to hold debugging information.
923 The symbol type is unknown, or object file format specific.
932 @c man begin OPTIONS nm
933 The long and short forms of options, shown here as alternatives, are
939 @itemx --print-file-name
940 @cindex input file name
942 @cindex source file name
943 Precede each symbol by the name of the input file (or archive member)
944 in which it was found, rather than identifying the input file once only,
945 before all of its symbols.
949 @cindex debugging symbols
950 Display all symbols, even debugger-only symbols; normally these are not
954 @cindex @command{nm} format
955 @cindex @command{nm} compatibility
956 The same as @option{--format=bsd} (for compatibility with the MIPS @command{nm}).
959 @itemx --demangle[=@var{style}]
960 @cindex demangling in nm
961 Decode (@dfn{demangle}) low-level symbol names into user-level names.
962 Besides removing any initial underscore prepended by the system, this
963 makes C++ function names readable. Different compilers have different
964 mangling styles. The optional demangling style argument can be used to
965 choose an appropriate demangling style for your compiler. @xref{c++filt},
966 for more information on demangling.
969 Do not demangle low-level symbol names. This is the default.
971 @item --recurse-limit
972 @itemx --no-recurse-limit
973 @itemx --recursion-limit
974 @itemx --no-recursion-limit
975 Enables or disables a limit on the amount of recursion performed
976 whilst demangling strings. Since the name mangling formats allow for
977 an inifinite level of recursion it is possible to create strings whose
978 decoding will exhaust the amount of stack space available on the host
979 machine, triggering a memory fault. The limit tries to prevent this
980 from happening by restricting recursion to 2048 levels of nesting.
982 The default is for this limit to be enabled, but disabling it may be
983 necessary in order to demangle truly complicated names. Note however
984 that if the recursion limit is disabled then stack exhaustion is
985 possible and any bug reports about such an event will be rejected.
989 @cindex dynamic symbols
990 Display the dynamic symbols rather than the normal symbols. This is
991 only meaningful for dynamic objects, such as certain types of shared
994 @item -f @var{format}
995 @itemx --format=@var{format}
996 @cindex @command{nm} format
997 @cindex @command{nm} compatibility
998 Use the output format @var{format}, which can be @code{bsd},
999 @code{sysv}, or @code{posix}. The default is @code{bsd}.
1000 Only the first character of @var{format} is significant; it can be
1001 either upper or lower case.
1004 @itemx --extern-only
1005 @cindex external symbols
1006 Display only external symbols.
1010 Show a summary of the options to @command{nm} and exit.
1013 @itemx --line-numbers
1014 @cindex symbol line numbers
1015 For each symbol, use debugging information to try to find a filename and
1016 line number. For a defined symbol, look for the line number of the
1017 address of the symbol. For an undefined symbol, look for the line
1018 number of a relocation entry which refers to the symbol. If line number
1019 information can be found, print it after the other symbol information.
1022 @cindex objdump inlines
1023 When option @option{-l} is active, if the address belongs to a
1024 function that was inlined, then this option causes the source
1025 information for all enclosing scopes back to the first non-inlined
1026 function to be printed as well. For example, if @code{main} inlines
1027 @code{callee1} which inlines @code{callee2}, and address is from
1028 @code{callee2}, the source information for @code{callee1} and @code{main}
1029 will also be printed.
1033 @itemx --numeric-sort
1034 Sort symbols numerically by their addresses, rather than alphabetically
1039 @cindex sorting symbols
1040 Do not bother to sort the symbols in any order; print them in the order
1044 @itemx --portability
1045 Use the POSIX.2 standard output format instead of the default format.
1046 Equivalent to @samp{-f posix}.
1049 @itemx --reverse-sort
1050 Reverse the order of the sort (whether numeric or alphabetic); let the
1055 Print both value and size of defined symbols for the @code{bsd} output style.
1056 This option has no effect for object formats that do not record symbol
1057 sizes, unless @samp{--size-sort} is also used in which case a
1058 calculated size is displayed.
1061 @itemx --print-armap
1062 @cindex symbol index, listing
1063 When listing symbols from archive members, include the index: a mapping
1064 (stored in the archive by @command{ar} or @command{ranlib}) of which modules
1065 contain definitions for which names.
1067 @item -t @var{radix}
1068 @itemx --radix=@var{radix}
1069 Use @var{radix} as the radix for printing the symbol values. It must be
1070 @samp{d} for decimal, @samp{o} for octal, or @samp{x} for hexadecimal.
1073 @itemx --undefined-only
1074 @cindex external symbols
1075 @cindex undefined symbols
1076 Display only undefined symbols (those external to each object file).
1080 Show the version number of @command{nm} and exit.
1083 This option is ignored for compatibility with the AIX version of
1084 @command{nm}. It takes one parameter which must be the string
1085 @option{32_64}. The default mode of AIX @command{nm} corresponds
1086 to @option{-X 32}, which is not supported by @sc{gnu} @command{nm}.
1088 @item --defined-only
1089 @cindex external symbols
1090 @cindex undefined symbols
1091 Display only defined symbols for each object file.
1093 @item --plugin @var{name}
1095 Load the plugin called @var{name} to add support for extra target
1096 types. This option is only available if the toolchain has been built
1097 with plugin support enabled.
1099 If @option{--plugin} is not provided, but plugin support has been
1100 enabled then @command{nm} iterates over the files in
1101 @file{$@{libdir@}/bfd-plugins} in alphabetic order and the first
1102 plugin that claims the object in question is used.
1104 Please note that this plugin search directory is @emph{not} the one
1105 used by @command{ld}'s @option{-plugin} option. In order to make
1106 @command{nm} use the linker plugin it must be copied into the
1107 @file{$@{libdir@}/bfd-plugins} directory. For GCC based compilations
1108 the linker plugin is called @file{liblto_plugin.so.0.0.0}. For Clang
1109 based compilations it is called @file{LLVMgold.so}. The GCC plugin
1110 is always backwards compatible with earlier versions, so it is
1111 sufficient to just copy the newest one.
1114 Sort symbols by size. For ELF objects symbol sizes are read from the
1115 ELF, for other object types the symbol sizes are computed as the
1116 difference between the value of the symbol and the value of the symbol
1117 with the next higher value. If the @code{bsd} output format is used
1118 the size of the symbol is printed, rather than the value, and
1119 @samp{-S} must be used in order both size and value to be printed.
1121 @item --special-syms
1122 Display symbols which have a target-specific special meaning. These
1123 symbols are usually used by the target for some special processing and
1124 are not normally helpful when included in the normal symbol lists.
1125 For example for ARM targets this option would skip the mapping symbols
1126 used to mark transitions between ARM code, THUMB code and data.
1129 Include synthetic symbols in the output. These are special symbols
1130 created by the linker for various purposes. They are not shown by
1131 default since they are not part of the binary's original source code.
1133 @item --with-symbol-versions
1134 Enables the display of symbol version information if any exists. The
1135 version string is displayed as a suffix to the symbol name, preceeded by
1136 an @@ character. For example @samp{foo@@VER_1}. If the version is
1137 the default version to be used when resolving unversioned references
1138 to the symbol then it is displayed as a suffix preceeded by two @@
1139 characters. For example @samp{foo@@@@VER_2}.
1141 @item --target=@var{bfdname}
1142 @cindex object code format
1143 Specify an object code format other than your system's default format.
1144 @xref{Target Selection}, for more information.
1151 @c man begin SEEALSO nm
1152 ar(1), objdump(1), ranlib(1), and the Info entries for @file{binutils}.
1159 @c man title objcopy copy and translate object files
1162 @c man begin SYNOPSIS objcopy
1163 objcopy [@option{-F} @var{bfdname}|@option{--target=}@var{bfdname}]
1164 [@option{-I} @var{bfdname}|@option{--input-target=}@var{bfdname}]
1165 [@option{-O} @var{bfdname}|@option{--output-target=}@var{bfdname}]
1166 [@option{-B} @var{bfdarch}|@option{--binary-architecture=}@var{bfdarch}]
1167 [@option{-S}|@option{--strip-all}]
1168 [@option{-g}|@option{--strip-debug}]
1169 [@option{--strip-unneeded}]
1170 [@option{-K} @var{symbolname}|@option{--keep-symbol=}@var{symbolname}]
1171 [@option{-N} @var{symbolname}|@option{--strip-symbol=}@var{symbolname}]
1172 [@option{--strip-unneeded-symbol=}@var{symbolname}]
1173 [@option{-G} @var{symbolname}|@option{--keep-global-symbol=}@var{symbolname}]
1174 [@option{--localize-hidden}]
1175 [@option{-L} @var{symbolname}|@option{--localize-symbol=}@var{symbolname}]
1176 [@option{--globalize-symbol=}@var{symbolname}]
1177 [@option{--globalize-symbols=}@var{filename}]
1178 [@option{-W} @var{symbolname}|@option{--weaken-symbol=}@var{symbolname}]
1179 [@option{-w}|@option{--wildcard}]
1180 [@option{-x}|@option{--discard-all}]
1181 [@option{-X}|@option{--discard-locals}]
1182 [@option{-b} @var{byte}|@option{--byte=}@var{byte}]
1183 [@option{-i} [@var{breadth}]|@option{--interleave}[=@var{breadth}]]
1184 [@option{--interleave-width=}@var{width}]
1185 [@option{-j} @var{sectionpattern}|@option{--only-section=}@var{sectionpattern}]
1186 [@option{-R} @var{sectionpattern}|@option{--remove-section=}@var{sectionpattern}]
1187 [@option{--keep-section=}@var{sectionpattern}]
1188 [@option{--remove-relocations=}@var{sectionpattern}]
1189 [@option{-p}|@option{--preserve-dates}]
1190 [@option{-D}|@option{--enable-deterministic-archives}]
1191 [@option{-U}|@option{--disable-deterministic-archives}]
1192 [@option{--debugging}]
1193 [@option{--gap-fill=}@var{val}]
1194 [@option{--pad-to=}@var{address}]
1195 [@option{--set-start=}@var{val}]
1196 [@option{--adjust-start=}@var{incr}]
1197 [@option{--change-addresses=}@var{incr}]
1198 [@option{--change-section-address} @var{sectionpattern}@{=,+,-@}@var{val}]
1199 [@option{--change-section-lma} @var{sectionpattern}@{=,+,-@}@var{val}]
1200 [@option{--change-section-vma} @var{sectionpattern}@{=,+,-@}@var{val}]
1201 [@option{--change-warnings}] [@option{--no-change-warnings}]
1202 [@option{--set-section-flags} @var{sectionpattern}=@var{flags}]
1203 [@option{--set-section-alignment} @var{sectionpattern}=@var{align}]
1204 [@option{--add-section} @var{sectionname}=@var{filename}]
1205 [@option{--dump-section} @var{sectionname}=@var{filename}]
1206 [@option{--update-section} @var{sectionname}=@var{filename}]
1207 [@option{--rename-section} @var{oldname}=@var{newname}[,@var{flags}]]
1208 [@option{--long-section-names} @{enable,disable,keep@}]
1209 [@option{--change-leading-char}] [@option{--remove-leading-char}]
1210 [@option{--reverse-bytes=}@var{num}]
1211 [@option{--srec-len=}@var{ival}] [@option{--srec-forceS3}]
1212 [@option{--redefine-sym} @var{old}=@var{new}]
1213 [@option{--redefine-syms=}@var{filename}]
1215 [@option{--keep-symbols=}@var{filename}]
1216 [@option{--strip-symbols=}@var{filename}]
1217 [@option{--strip-unneeded-symbols=}@var{filename}]
1218 [@option{--keep-global-symbols=}@var{filename}]
1219 [@option{--localize-symbols=}@var{filename}]
1220 [@option{--weaken-symbols=}@var{filename}]
1221 [@option{--add-symbol} @var{name}=[@var{section}:]@var{value}[,@var{flags}]]
1222 [@option{--alt-machine-code=}@var{index}]
1223 [@option{--prefix-symbols=}@var{string}]
1224 [@option{--prefix-sections=}@var{string}]
1225 [@option{--prefix-alloc-sections=}@var{string}]
1226 [@option{--add-gnu-debuglink=}@var{path-to-file}]
1227 [@option{--keep-file-symbols}]
1228 [@option{--only-keep-debug}]
1229 [@option{--strip-dwo}]
1230 [@option{--extract-dwo}]
1231 [@option{--extract-symbol}]
1232 [@option{--writable-text}]
1233 [@option{--readonly-text}]
1236 [@option{--file-alignment=}@var{num}]
1237 [@option{--heap=}@var{size}]
1238 [@option{--image-base=}@var{address}]
1239 [@option{--section-alignment=}@var{num}]
1240 [@option{--stack=}@var{size}]
1241 [@option{--subsystem=}@var{which}:@var{major}.@var{minor}]
1242 [@option{--compress-debug-sections}]
1243 [@option{--decompress-debug-sections}]
1244 [@option{--elf-stt-common=@var{val}}]
1245 [@option{--merge-notes}]
1246 [@option{--no-merge-notes}]
1247 [@option{--verilog-data-width=@var{val}}]
1248 [@option{-v}|@option{--verbose}]
1249 [@option{-V}|@option{--version}]
1250 [@option{--help}] [@option{--info}]
1251 @var{infile} [@var{outfile}]
1255 @c man begin DESCRIPTION objcopy
1256 The @sc{gnu} @command{objcopy} utility copies the contents of an object
1257 file to another. @command{objcopy} uses the @sc{gnu} @sc{bfd} Library to
1258 read and write the object files. It can write the destination object
1259 file in a format different from that of the source object file. The
1260 exact behavior of @command{objcopy} is controlled by command-line options.
1261 Note that @command{objcopy} should be able to copy a fully linked file
1262 between any two formats. However, copying a relocatable object file
1263 between any two formats may not work as expected.
1265 @command{objcopy} creates temporary files to do its translations and
1266 deletes them afterward. @command{objcopy} uses @sc{bfd} to do all its
1267 translation work; it has access to all the formats described in @sc{bfd}
1268 and thus is able to recognize most formats without being told
1269 explicitly. @xref{BFD,,BFD,ld.info,Using LD}.
1271 @command{objcopy} can be used to generate S-records by using an output
1272 target of @samp{srec} (e.g., use @samp{-O srec}).
1274 @command{objcopy} can be used to generate a raw binary file by using an
1275 output target of @samp{binary} (e.g., use @option{-O binary}). When
1276 @command{objcopy} generates a raw binary file, it will essentially produce
1277 a memory dump of the contents of the input object file. All symbols and
1278 relocation information will be discarded. The memory dump will start at
1279 the load address of the lowest section copied into the output file.
1281 When generating an S-record or a raw binary file, it may be helpful to
1282 use @option{-S} to remove sections containing debugging information. In
1283 some cases @option{-R} will be useful to remove sections which contain
1284 information that is not needed by the binary file.
1286 Note---@command{objcopy} is not able to change the endianness of its input
1287 files. If the input format has an endianness (some formats do not),
1288 @command{objcopy} can only copy the inputs into file formats that have the
1289 same endianness or which have no endianness (e.g., @samp{srec}).
1290 (However, see the @option{--reverse-bytes} option.)
1294 @c man begin OPTIONS objcopy
1298 @itemx @var{outfile}
1299 The input and output files, respectively.
1300 If you do not specify @var{outfile}, @command{objcopy} creates a
1301 temporary file and destructively renames the result with
1302 the name of @var{infile}.
1304 @item -I @var{bfdname}
1305 @itemx --input-target=@var{bfdname}
1306 Consider the source file's object format to be @var{bfdname}, rather than
1307 attempting to deduce it. @xref{Target Selection}, for more information.
1309 @item -O @var{bfdname}
1310 @itemx --output-target=@var{bfdname}
1311 Write the output file using the object format @var{bfdname}.
1312 @xref{Target Selection}, for more information.
1314 @item -F @var{bfdname}
1315 @itemx --target=@var{bfdname}
1316 Use @var{bfdname} as the object format for both the input and the output
1317 file; i.e., simply transfer data from source to destination with no
1318 translation. @xref{Target Selection}, for more information.
1320 @item -B @var{bfdarch}
1321 @itemx --binary-architecture=@var{bfdarch}
1322 Useful when transforming a architecture-less input file into an object file.
1323 In this case the output architecture can be set to @var{bfdarch}. This
1324 option will be ignored if the input file has a known @var{bfdarch}. You
1325 can access this binary data inside a program by referencing the special
1326 symbols that are created by the conversion process. These symbols are
1327 called _binary_@var{objfile}_start, _binary_@var{objfile}_end and
1328 _binary_@var{objfile}_size. e.g. you can transform a picture file into
1329 an object file and then access it in your code using these symbols.
1331 @item -j @var{sectionpattern}
1332 @itemx --only-section=@var{sectionpattern}
1333 Copy only the indicated sections from the input file to the output file.
1334 This option may be given more than once. Note that using this option
1335 inappropriately may make the output file unusable. Wildcard
1336 characters are accepted in @var{sectionpattern}.
1338 If the first character of @var{sectionpattern} is the exclamation
1339 point (!) then matching sections will not be copied, even if earlier
1340 use of @option{--only-section} on the same command line would
1341 otherwise copy it. For example:
1344 --only-section=.text.* --only-section=!.text.foo
1347 will copy all sectinos maching '.text.*' but not the section
1350 @item -R @var{sectionpattern}
1351 @itemx --remove-section=@var{sectionpattern}
1352 Remove any section matching @var{sectionpattern} from the output file.
1353 This option may be given more than once. Note that using this option
1354 inappropriately may make the output file unusable. Wildcard
1355 characters are accepted in @var{sectionpattern}. Using both the
1356 @option{-j} and @option{-R} options together results in undefined
1359 If the first character of @var{sectionpattern} is the exclamation
1360 point (!) then matching sections will not be removed even if an
1361 earlier use of @option{--remove-section} on the same command line
1362 would otherwise remove it. For example:
1365 --remove-section=.text.* --remove-section=!.text.foo
1368 will remove all sections matching the pattern '.text.*', but will not
1369 remove the section '.text.foo'.
1371 @item --keep-section=@var{sectionpattern}
1372 When removing sections from the output file, keep sections that match
1373 @var{sectionpattern}.
1375 @item --remove-relocations=@var{sectionpattern}
1376 Remove non-dynamic relocations from the output file for any section
1377 matching @var{sectionpattern}. This option may be given more than
1378 once. Note that using this option inappropriately may make the output
1379 file unusable, and attempting to remove a dynamic relocation section
1380 such as @samp{.rela.plt} from an executable or shared library with
1381 @option{--remove-relocations=.plt} will not work. Wildcard characters
1382 are accepted in @var{sectionpattern}.
1386 --remove-relocations=.text.*
1389 will remove the relocations for all sections matching the pattern
1392 If the first character of @var{sectionpattern} is the exclamation
1393 point (!) then matching sections will not have their relocation
1394 removed even if an earlier use of @option{--remove-relocations} on the
1395 same command line would otherwise cause the relocations to be removed.
1399 --remove-relocations=.text.* --remove-relocations=!.text.foo
1402 will remove all relocations for sections matching the pattern
1403 '.text.*', but will not remove relocations for the section
1408 Do not copy relocation and symbol information from the source file.
1411 @itemx --strip-debug
1412 Do not copy debugging symbols or sections from the source file.
1414 @item --strip-unneeded
1415 Strip all symbols that are not needed for relocation processing.
1417 @item -K @var{symbolname}
1418 @itemx --keep-symbol=@var{symbolname}
1419 When stripping symbols, keep symbol @var{symbolname} even if it would
1420 normally be stripped. This option may be given more than once.
1422 @item -N @var{symbolname}
1423 @itemx --strip-symbol=@var{symbolname}
1424 Do not copy symbol @var{symbolname} from the source file. This option
1425 may be given more than once.
1427 @item --strip-unneeded-symbol=@var{symbolname}
1428 Do not copy symbol @var{symbolname} from the source file unless it is needed
1429 by a relocation. This option may be given more than once.
1431 @item -G @var{symbolname}
1432 @itemx --keep-global-symbol=@var{symbolname}
1433 Keep only symbol @var{symbolname} global. Make all other symbols local
1434 to the file, so that they are not visible externally. This option may
1435 be given more than once. Note: this option cannot be used in
1436 conjunction with the @option{--globalize-symbol} or
1437 @option{--globalize-symbols} options.
1439 @item --localize-hidden
1440 In an ELF object, mark all symbols that have hidden or internal visibility
1441 as local. This option applies on top of symbol-specific localization options
1442 such as @option{-L}.
1444 @item -L @var{symbolname}
1445 @itemx --localize-symbol=@var{symbolname}
1446 Convert a global or weak symbol called @var{symbolname} into a local
1447 symbol, so that it is not visible externally. This option may be
1448 given more than once. Note - unique symbols are not converted.
1450 @item -W @var{symbolname}
1451 @itemx --weaken-symbol=@var{symbolname}
1452 Make symbol @var{symbolname} weak. This option may be given more than once.
1454 @item --globalize-symbol=@var{symbolname}
1455 Give symbol @var{symbolname} global scoping so that it is visible
1456 outside of the file in which it is defined. This option may be given
1457 more than once. Note: this option cannot be used in conjunction with
1458 the @option{-G} or @option{--keep-global-symbol} options.
1462 Permit regular expressions in @var{symbolname}s used in other command
1463 line options. The question mark (?), asterisk (*), backslash (\) and
1464 square brackets ([]) operators can be used anywhere in the symbol
1465 name. If the first character of the symbol name is the exclamation
1466 point (!) then the sense of the switch is reversed for that symbol.
1473 would cause objcopy to weaken all symbols that start with ``fo''
1474 except for the symbol ``foo''.
1477 @itemx --discard-all
1478 Do not copy non-global symbols from the source file.
1479 @c FIXME any reason to prefer "non-global" to "local" here?
1482 @itemx --discard-locals
1483 Do not copy compiler-generated local symbols.
1484 (These usually start with @samp{L} or @samp{.}.)
1487 @itemx --byte=@var{byte}
1488 If interleaving has been enabled via the @option{--interleave} option
1489 then start the range of bytes to keep at the @var{byte}th byte.
1490 @var{byte} can be in the range from 0 to @var{breadth}-1, where
1491 @var{breadth} is the value given by the @option{--interleave} option.
1493 @item -i [@var{breadth}]
1494 @itemx --interleave[=@var{breadth}]
1495 Only copy a range out of every @var{breadth} bytes. (Header data is
1496 not affected). Select which byte in the range begins the copy with
1497 the @option{--byte} option. Select the width of the range with the
1498 @option{--interleave-width} option.
1500 This option is useful for creating files to program @sc{rom}. It is
1501 typically used with an @code{srec} output target. Note that
1502 @command{objcopy} will complain if you do not specify the
1503 @option{--byte} option as well.
1505 The default interleave breadth is 4, so with @option{--byte} set to 0,
1506 @command{objcopy} would copy the first byte out of every four bytes
1507 from the input to the output.
1509 @item --interleave-width=@var{width}
1510 When used with the @option{--interleave} option, copy @var{width}
1511 bytes at a time. The start of the range of bytes to be copied is set
1512 by the @option{--byte} option, and the extent of the range is set with
1513 the @option{--interleave} option.
1515 The default value for this option is 1. The value of @var{width} plus
1516 the @var{byte} value set by the @option{--byte} option must not exceed
1517 the interleave breadth set by the @option{--interleave} option.
1519 This option can be used to create images for two 16-bit flashes interleaved
1520 in a 32-bit bus by passing @option{-b 0 -i 4 --interleave-width=2}
1521 and @option{-b 2 -i 4 --interleave-width=2} to two @command{objcopy}
1522 commands. If the input was '12345678' then the outputs would be
1523 '1256' and '3478' respectively.
1526 @itemx --preserve-dates
1527 Set the access and modification dates of the output file to be the same
1528 as those of the input file.
1531 @itemx --enable-deterministic-archives
1532 @cindex deterministic archives
1533 @kindex --enable-deterministic-archives
1534 Operate in @emph{deterministic} mode. When copying archive members
1535 and writing the archive index, use zero for UIDs, GIDs, timestamps,
1536 and use consistent file modes for all files.
1538 If @file{binutils} was configured with
1539 @option{--enable-deterministic-archives}, then this mode is on by default.
1540 It can be disabled with the @samp{-U} option, below.
1543 @itemx --disable-deterministic-archives
1544 @cindex deterministic archives
1545 @kindex --enable-deterministic-archives
1546 Do @emph{not} operate in @emph{deterministic} mode. This is the
1547 inverse of the @option{-D} option, above: when copying archive members
1548 and writing the archive index, use their actual UID, GID, timestamp,
1549 and file mode values.
1551 This is the default unless @file{binutils} was configured with
1552 @option{--enable-deterministic-archives}.
1555 Convert debugging information, if possible. This is not the default
1556 because only certain debugging formats are supported, and the
1557 conversion process can be time consuming.
1559 @item --gap-fill @var{val}
1560 Fill gaps between sections with @var{val}. This operation applies to
1561 the @emph{load address} (LMA) of the sections. It is done by increasing
1562 the size of the section with the lower address, and filling in the extra
1563 space created with @var{val}.
1565 @item --pad-to @var{address}
1566 Pad the output file up to the load address @var{address}. This is
1567 done by increasing the size of the last section. The extra space is
1568 filled in with the value specified by @option{--gap-fill} (default zero).
1570 @item --set-start @var{val}
1571 Set the start address of the new file to @var{val}. Not all object file
1572 formats support setting the start address.
1574 @item --change-start @var{incr}
1575 @itemx --adjust-start @var{incr}
1576 @cindex changing start address
1577 Change the start address by adding @var{incr}. Not all object file
1578 formats support setting the start address.
1580 @item --change-addresses @var{incr}
1581 @itemx --adjust-vma @var{incr}
1582 @cindex changing object addresses
1583 Change the VMA and LMA addresses of all sections, as well as the start
1584 address, by adding @var{incr}. Some object file formats do not permit
1585 section addresses to be changed arbitrarily. Note that this does not
1586 relocate the sections; if the program expects sections to be loaded at a
1587 certain address, and this option is used to change the sections such
1588 that they are loaded at a different address, the program may fail.
1590 @item --change-section-address @var{sectionpattern}@{=,+,-@}@var{val}
1591 @itemx --adjust-section-vma @var{sectionpattern}@{=,+,-@}@var{val}
1592 @cindex changing section address
1593 Set or change both the VMA address and the LMA address of any section
1594 matching @var{sectionpattern}. If @samp{=} is used, the section
1595 address is set to @var{val}. Otherwise, @var{val} is added to or
1596 subtracted from the section address. See the comments under
1597 @option{--change-addresses}, above. If @var{sectionpattern} does not
1598 match any sections in the input file, a warning will be issued, unless
1599 @option{--no-change-warnings} is used.
1601 @item --change-section-lma @var{sectionpattern}@{=,+,-@}@var{val}
1602 @cindex changing section LMA
1603 Set or change the LMA address of any sections matching
1604 @var{sectionpattern}. The LMA address is the address where the
1605 section will be loaded into memory at program load time. Normally
1606 this is the same as the VMA address, which is the address of the
1607 section at program run time, but on some systems, especially those
1608 where a program is held in ROM, the two can be different. If @samp{=}
1609 is used, the section address is set to @var{val}. Otherwise,
1610 @var{val} is added to or subtracted from the section address. See the
1611 comments under @option{--change-addresses}, above. If
1612 @var{sectionpattern} does not match any sections in the input file, a
1613 warning will be issued, unless @option{--no-change-warnings} is used.
1615 @item --change-section-vma @var{sectionpattern}@{=,+,-@}@var{val}
1616 @cindex changing section VMA
1617 Set or change the VMA address of any section matching
1618 @var{sectionpattern}. The VMA address is the address where the
1619 section will be located once the program has started executing.
1620 Normally this is the same as the LMA address, which is the address
1621 where the section will be loaded into memory, but on some systems,
1622 especially those where a program is held in ROM, the two can be
1623 different. If @samp{=} is used, the section address is set to
1624 @var{val}. Otherwise, @var{val} is added to or subtracted from the
1625 section address. See the comments under @option{--change-addresses},
1626 above. If @var{sectionpattern} does not match any sections in the
1627 input file, a warning will be issued, unless
1628 @option{--no-change-warnings} is used.
1630 @item --change-warnings
1631 @itemx --adjust-warnings
1632 If @option{--change-section-address} or @option{--change-section-lma} or
1633 @option{--change-section-vma} is used, and the section pattern does not
1634 match any sections, issue a warning. This is the default.
1636 @item --no-change-warnings
1637 @itemx --no-adjust-warnings
1638 Do not issue a warning if @option{--change-section-address} or
1639 @option{--adjust-section-lma} or @option{--adjust-section-vma} is used, even
1640 if the section pattern does not match any sections.
1642 @item --set-section-flags @var{sectionpattern}=@var{flags}
1643 Set the flags for any sections matching @var{sectionpattern}. The
1644 @var{flags} argument is a comma separated string of flag names. The
1645 recognized names are @samp{alloc}, @samp{contents}, @samp{load},
1646 @samp{noload}, @samp{readonly}, @samp{code}, @samp{data}, @samp{rom},
1647 @samp{share}, and @samp{debug}. You can set the @samp{contents} flag
1648 for a section which does not have contents, but it is not meaningful
1649 to clear the @samp{contents} flag of a section which does have
1650 contents--just remove the section instead. Not all flags are
1651 meaningful for all object file formats.
1653 @item --set-section-alignment @var{sectionpattern}=@var{align}
1654 Set the alignment for any sections matching @var{sectionpattern}.
1655 @var{align} specifies the alignment in bytes and must be a power of
1656 two, i.e. 1, 2, 4, 8@dots{}.
1658 @item --add-section @var{sectionname}=@var{filename}
1659 Add a new section named @var{sectionname} while copying the file. The
1660 contents of the new section are taken from the file @var{filename}. The
1661 size of the section will be the size of the file. This option only
1662 works on file formats which can support sections with arbitrary names.
1663 Note - it may be necessary to use the @option{--set-section-flags}
1664 option to set the attributes of the newly created section.
1666 @item --dump-section @var{sectionname}=@var{filename}
1667 Place the contents of section named @var{sectionname} into the file
1668 @var{filename}, overwriting any contents that may have been there
1669 previously. This option is the inverse of @option{--add-section}.
1670 This option is similar to the @option{--only-section} option except
1671 that it does not create a formatted file, it just dumps the contents
1672 as raw binary data, without applying any relocations. The option can
1673 be specified more than once.
1675 @item --update-section @var{sectionname}=@var{filename}
1676 Replace the existing contents of a section named @var{sectionname}
1677 with the contents of file @var{filename}. The size of the section
1678 will be adjusted to the size of the file. The section flags for
1679 @var{sectionname} will be unchanged. For ELF format files the section
1680 to segment mapping will also remain unchanged, something which is not
1681 possible using @option{--remove-section} followed by
1682 @option{--add-section}. The option can be specified more than once.
1684 Note - it is possible to use @option{--rename-section} and
1685 @option{--update-section} to both update and rename a section from one
1686 command line. In this case, pass the original section name to
1687 @option{--update-section}, and the original and new section names to
1688 @option{--rename-section}.
1690 @item --add-symbol @var{name}=[@var{section}:]@var{value}[,@var{flags}]
1691 Add a new symbol named @var{name} while copying the file. This option may be
1692 specified multiple times. If the @var{section} is given, the symbol will be
1693 associated with and relative to that section, otherwise it will be an ABS
1694 symbol. Specifying an undefined section will result in a fatal error. There
1695 is no check for the value, it will be taken as specified. Symbol flags can
1696 be specified and not all flags will be meaningful for all object file
1697 formats. By default, the symbol will be global. The special flag
1698 'before=@var{othersym}' will insert the new symbol in front of the specified
1699 @var{othersym}, otherwise the symbol(s) will be added at the end of the
1700 symbol table in the order they appear.
1702 @item --rename-section @var{oldname}=@var{newname}[,@var{flags}]
1703 Rename a section from @var{oldname} to @var{newname}, optionally
1704 changing the section's flags to @var{flags} in the process. This has
1705 the advantage over using a linker script to perform the rename in that
1706 the output stays as an object file and does not become a linked
1709 This option is particularly helpful when the input format is binary,
1710 since this will always create a section called .data. If for example,
1711 you wanted instead to create a section called .rodata containing binary
1712 data you could use the following command line to achieve it:
1715 objcopy -I binary -O <output_format> -B <architecture> \
1716 --rename-section .data=.rodata,alloc,load,readonly,data,contents \
1717 <input_binary_file> <output_object_file>
1720 @item --long-section-names @{enable,disable,keep@}
1721 Controls the handling of long section names when processing @code{COFF}
1722 and @code{PE-COFF} object formats. The default behaviour, @samp{keep},
1723 is to preserve long section names if any are present in the input file.
1724 The @samp{enable} and @samp{disable} options forcibly enable or disable
1725 the use of long section names in the output object; when @samp{disable}
1726 is in effect, any long section names in the input object will be truncated.
1727 The @samp{enable} option will only emit long section names if any are
1728 present in the inputs; this is mostly the same as @samp{keep}, but it
1729 is left undefined whether the @samp{enable} option might force the
1730 creation of an empty string table in the output file.
1732 @item --change-leading-char
1733 Some object file formats use special characters at the start of
1734 symbols. The most common such character is underscore, which compilers
1735 often add before every symbol. This option tells @command{objcopy} to
1736 change the leading character of every symbol when it converts between
1737 object file formats. If the object file formats use the same leading
1738 character, this option has no effect. Otherwise, it will add a
1739 character, or remove a character, or change a character, as
1742 @item --remove-leading-char
1743 If the first character of a global symbol is a special symbol leading
1744 character used by the object file format, remove the character. The
1745 most common symbol leading character is underscore. This option will
1746 remove a leading underscore from all global symbols. This can be useful
1747 if you want to link together objects of different file formats with
1748 different conventions for symbol names. This is different from
1749 @option{--change-leading-char} because it always changes the symbol name
1750 when appropriate, regardless of the object file format of the output
1753 @item --reverse-bytes=@var{num}
1754 Reverse the bytes in a section with output contents. A section length must
1755 be evenly divisible by the value given in order for the swap to be able to
1756 take place. Reversing takes place before the interleaving is performed.
1758 This option is used typically in generating ROM images for problematic
1759 target systems. For example, on some target boards, the 32-bit words
1760 fetched from 8-bit ROMs are re-assembled in little-endian byte order
1761 regardless of the CPU byte order. Depending on the programming model, the
1762 endianness of the ROM may need to be modified.
1764 Consider a simple file with a section containing the following eight
1765 bytes: @code{12345678}.
1767 Using @samp{--reverse-bytes=2} for the above example, the bytes in the
1768 output file would be ordered @code{21436587}.
1770 Using @samp{--reverse-bytes=4} for the above example, the bytes in the
1771 output file would be ordered @code{43218765}.
1773 By using @samp{--reverse-bytes=2} for the above example, followed by
1774 @samp{--reverse-bytes=4} on the output file, the bytes in the second
1775 output file would be ordered @code{34127856}.
1777 @item --srec-len=@var{ival}
1778 Meaningful only for srec output. Set the maximum length of the Srecords
1779 being produced to @var{ival}. This length covers both address, data and
1782 @item --srec-forceS3
1783 Meaningful only for srec output. Avoid generation of S1/S2 records,
1784 creating S3-only record format.
1786 @item --redefine-sym @var{old}=@var{new}
1787 Change the name of a symbol @var{old}, to @var{new}. This can be useful
1788 when one is trying link two things together for which you have no
1789 source, and there are name collisions.
1791 @item --redefine-syms=@var{filename}
1792 Apply @option{--redefine-sym} to each symbol pair "@var{old} @var{new}"
1793 listed in the file @var{filename}. @var{filename} is simply a flat file,
1794 with one symbol pair per line. Line comments may be introduced by the hash
1795 character. This option may be given more than once.
1798 Change all global symbols in the file to be weak. This can be useful
1799 when building an object which will be linked against other objects using
1800 the @option{-R} option to the linker. This option is only effective when
1801 using an object file format which supports weak symbols.
1803 @item --keep-symbols=@var{filename}
1804 Apply @option{--keep-symbol} option to each symbol listed in the file
1805 @var{filename}. @var{filename} is simply a flat file, with one symbol
1806 name per line. Line comments may be introduced by the hash character.
1807 This option may be given more than once.
1809 @item --strip-symbols=@var{filename}
1810 Apply @option{--strip-symbol} option to each symbol listed in the file
1811 @var{filename}. @var{filename} is simply a flat file, with one symbol
1812 name per line. Line comments may be introduced by the hash character.
1813 This option may be given more than once.
1815 @item --strip-unneeded-symbols=@var{filename}
1816 Apply @option{--strip-unneeded-symbol} option to each symbol listed in
1817 the file @var{filename}. @var{filename} is simply a flat file, with one
1818 symbol name per line. Line comments may be introduced by the hash
1819 character. This option may be given more than once.
1821 @item --keep-global-symbols=@var{filename}
1822 Apply @option{--keep-global-symbol} option to each symbol listed in the
1823 file @var{filename}. @var{filename} is simply a flat file, with one
1824 symbol name per line. Line comments may be introduced by the hash
1825 character. This option may be given more than once.
1827 @item --localize-symbols=@var{filename}
1828 Apply @option{--localize-symbol} option to each symbol listed in the file
1829 @var{filename}. @var{filename} is simply a flat file, with one symbol
1830 name per line. Line comments may be introduced by the hash character.
1831 This option may be given more than once.
1833 @item --globalize-symbols=@var{filename}
1834 Apply @option{--globalize-symbol} option to each symbol listed in the file
1835 @var{filename}. @var{filename} is simply a flat file, with one symbol
1836 name per line. Line comments may be introduced by the hash character.
1837 This option may be given more than once. Note: this option cannot be
1838 used in conjunction with the @option{-G} or @option{--keep-global-symbol}
1841 @item --weaken-symbols=@var{filename}
1842 Apply @option{--weaken-symbol} option to each symbol listed in the file
1843 @var{filename}. @var{filename} is simply a flat file, with one symbol
1844 name per line. Line comments may be introduced by the hash character.
1845 This option may be given more than once.
1847 @item --alt-machine-code=@var{index}
1848 If the output architecture has alternate machine codes, use the
1849 @var{index}th code instead of the default one. This is useful in case
1850 a machine is assigned an official code and the tool-chain adopts the
1851 new code, but other applications still depend on the original code
1852 being used. For ELF based architectures if the @var{index}
1853 alternative does not exist then the value is treated as an absolute
1854 number to be stored in the e_machine field of the ELF header.
1856 @item --writable-text
1857 Mark the output text as writable. This option isn't meaningful for all
1858 object file formats.
1860 @item --readonly-text
1861 Make the output text write protected. This option isn't meaningful for all
1862 object file formats.
1865 Mark the output file as demand paged. This option isn't meaningful for all
1866 object file formats.
1869 Mark the output file as impure. This option isn't meaningful for all
1870 object file formats.
1872 @item --prefix-symbols=@var{string}
1873 Prefix all symbols in the output file with @var{string}.
1875 @item --prefix-sections=@var{string}
1876 Prefix all section names in the output file with @var{string}.
1878 @item --prefix-alloc-sections=@var{string}
1879 Prefix all the names of all allocated sections in the output file with
1882 @item --add-gnu-debuglink=@var{path-to-file}
1883 Creates a .gnu_debuglink section which contains a reference to
1884 @var{path-to-file} and adds it to the output file. Note: the file at
1885 @var{path-to-file} must exist. Part of the process of adding the
1886 .gnu_debuglink section involves embedding a checksum of the contents
1887 of the debug info file into the section.
1889 If the debug info file is built in one location but it is going to be
1890 installed at a later time into a different location then do not use
1891 the path to the installed location. The @option{--add-gnu-debuglink}
1892 option will fail because the installed file does not exist yet.
1893 Instead put the debug info file in the current directory and use the
1894 @option{--add-gnu-debuglink} option without any directory components,
1898 objcopy --add-gnu-debuglink=foo.debug
1901 At debug time the debugger will attempt to look for the separate debug
1902 info file in a set of known locations. The exact set of these
1903 locations varies depending upon the distribution being used, but it
1908 @item * The same directory as the executable.
1910 @item * A sub-directory of the directory containing the executable
1913 @item * A global debug directory such as /usr/lib/debug.
1916 As long as the debug info file has been installed into one of these
1917 locations before the debugger is run everything should work
1920 @item --keep-file-symbols
1921 When stripping a file, perhaps with @option{--strip-debug} or
1922 @option{--strip-unneeded}, retain any symbols specifying source file names,
1923 which would otherwise get stripped.
1925 @item --only-keep-debug
1926 Strip a file, removing contents of any sections that would not be
1927 stripped by @option{--strip-debug} and leaving the debugging sections
1928 intact. In ELF files, this preserves all note sections in the output.
1930 Note - the section headers of the stripped sections are preserved,
1931 including their sizes, but the contents of the section are discarded.
1932 The section headers are preserved so that other tools can match up the
1933 debuginfo file with the real executable, even if that executable has
1934 been relocated to a different address space.
1936 The intention is that this option will be used in conjunction with
1937 @option{--add-gnu-debuglink} to create a two part executable. One a
1938 stripped binary which will occupy less space in RAM and in a
1939 distribution and the second a debugging information file which is only
1940 needed if debugging abilities are required. The suggested procedure
1941 to create these files is as follows:
1944 @item Link the executable as normal. Assuming that it is called
1946 @item Run @code{objcopy --only-keep-debug foo foo.dbg} to
1947 create a file containing the debugging info.
1948 @item Run @code{objcopy --strip-debug foo} to create a
1949 stripped executable.
1950 @item Run @code{objcopy --add-gnu-debuglink=foo.dbg foo}
1951 to add a link to the debugging info into the stripped executable.
1954 Note---the choice of @code{.dbg} as an extension for the debug info
1955 file is arbitrary. Also the @code{--only-keep-debug} step is
1956 optional. You could instead do this:
1959 @item Link the executable as normal.
1960 @item Copy @code{foo} to @code{foo.full}
1961 @item Run @code{objcopy --strip-debug foo}
1962 @item Run @code{objcopy --add-gnu-debuglink=foo.full foo}
1965 i.e., the file pointed to by the @option{--add-gnu-debuglink} can be the
1966 full executable. It does not have to be a file created by the
1967 @option{--only-keep-debug} switch.
1969 Note---this switch is only intended for use on fully linked files. It
1970 does not make sense to use it on object files where the debugging
1971 information may be incomplete. Besides the gnu_debuglink feature
1972 currently only supports the presence of one filename containing
1973 debugging information, not multiple filenames on a one-per-object-file
1977 Remove the contents of all DWARF .dwo sections, leaving the
1978 remaining debugging sections and all symbols intact.
1979 This option is intended for use by the compiler as part of
1980 the @option{-gsplit-dwarf} option, which splits debug information
1981 between the .o file and a separate .dwo file. The compiler
1982 generates all debug information in the same file, then uses
1983 the @option{--extract-dwo} option to copy the .dwo sections to
1984 the .dwo file, then the @option{--strip-dwo} option to remove
1985 those sections from the original .o file.
1988 Extract the contents of all DWARF .dwo sections. See the
1989 @option{--strip-dwo} option for more information.
1991 @item --file-alignment @var{num}
1992 Specify the file alignment. Sections in the file will always begin at
1993 file offsets which are multiples of this number. This defaults to
1995 [This option is specific to PE targets.]
1997 @item --heap @var{reserve}
1998 @itemx --heap @var{reserve},@var{commit}
1999 Specify the number of bytes of memory to reserve (and optionally commit)
2000 to be used as heap for this program.
2001 [This option is specific to PE targets.]
2003 @item --image-base @var{value}
2004 Use @var{value} as the base address of your program or dll. This is
2005 the lowest memory location that will be used when your program or dll
2006 is loaded. To reduce the need to relocate and improve performance of
2007 your dlls, each should have a unique base address and not overlap any
2008 other dlls. The default is 0x400000 for executables, and 0x10000000
2010 [This option is specific to PE targets.]
2012 @item --section-alignment @var{num}
2013 Sets the section alignment field in the PE header. Sections in memory
2014 will always begin at addresses which are a multiple of this number.
2016 [This option is specific to PE targets.]
2018 @item --stack @var{reserve}
2019 @itemx --stack @var{reserve},@var{commit}
2020 Specify the number of bytes of memory to reserve (and optionally commit)
2021 to be used as stack for this program.
2022 [This option is specific to PE targets.]
2024 @item --subsystem @var{which}
2025 @itemx --subsystem @var{which}:@var{major}
2026 @itemx --subsystem @var{which}:@var{major}.@var{minor}
2027 Specifies the subsystem under which your program will execute. The
2028 legal values for @var{which} are @code{native}, @code{windows},
2029 @code{console}, @code{posix}, @code{efi-app}, @code{efi-bsd},
2030 @code{efi-rtd}, @code{sal-rtd}, and @code{xbox}. You may optionally set
2031 the subsystem version also. Numeric values are also accepted for
2033 [This option is specific to PE targets.]
2035 @item --extract-symbol
2036 Keep the file's section flags and symbols but remove all section data.
2037 Specifically, the option:
2040 @item removes the contents of all sections;
2041 @item sets the size of every section to zero; and
2042 @item sets the file's start address to zero.
2045 This option is used to build a @file{.sym} file for a VxWorks kernel.
2046 It can also be a useful way of reducing the size of a @option{--just-symbols}
2049 @item --compress-debug-sections
2050 Compress DWARF debug sections using zlib with SHF_COMPRESSED from the
2051 ELF ABI. Note - if compression would actually make a section
2052 @emph{larger}, then it is not compressed.
2054 @item --compress-debug-sections=none
2055 @itemx --compress-debug-sections=zlib
2056 @itemx --compress-debug-sections=zlib-gnu
2057 @itemx --compress-debug-sections=zlib-gabi
2058 For ELF files, these options control how DWARF debug sections are
2059 compressed. @option{--compress-debug-sections=none} is equivalent
2060 to @option{--decompress-debug-sections}.
2061 @option{--compress-debug-sections=zlib} and
2062 @option{--compress-debug-sections=zlib-gabi} are equivalent to
2063 @option{--compress-debug-sections}.
2064 @option{--compress-debug-sections=zlib-gnu} compresses DWARF debug
2065 sections using zlib. The debug sections are renamed to begin with
2066 @samp{.zdebug} instead of @samp{.debug}. Note - if compression would
2067 actually make a section @emph{larger}, then it is not compressed nor
2070 @item --decompress-debug-sections
2071 Decompress DWARF debug sections using zlib. The original section
2072 names of the compressed sections are restored.
2074 @item --elf-stt-common=yes
2075 @itemx --elf-stt-common=no
2076 For ELF files, these options control whether common symbols should be
2077 converted to the @code{STT_COMMON} or @code{STT_OBJECT} type.
2078 @option{--elf-stt-common=yes} converts common symbol type to
2079 @code{STT_COMMON}. @option{--elf-stt-common=no} converts common symbol
2080 type to @code{STT_OBJECT}.
2083 @itemx --no-merge-notes
2084 For ELF files, attempt (or do not attempt) to reduce the size of any
2085 SHT_NOTE type sections by removing duplicate notes.
2089 Show the version number of @command{objcopy}.
2091 @item --verilog-data-width=@var{bytes}
2092 For Verilog output, this options controls the number of bytes
2093 converted for each output data element. The input target controls the
2094 endianness of the conversion.
2098 Verbose output: list all object files modified. In the case of
2099 archives, @samp{objcopy -V} lists all members of the archive.
2102 Show a summary of the options to @command{objcopy}.
2105 Display a list showing all architectures and object formats available.
2111 @c man begin SEEALSO objcopy
2112 ld(1), objdump(1), and the Info entries for @file{binutils}.
2119 @cindex object file information
2122 @c man title objdump display information from object files
2125 @c man begin SYNOPSIS objdump
2126 objdump [@option{-a}|@option{--archive-headers}]
2127 [@option{-b} @var{bfdname}|@option{--target=@var{bfdname}}]
2128 [@option{-C}|@option{--demangle}[=@var{style}] ]
2129 [@option{-d}|@option{--disassemble}[=@var{symbol}]]
2130 [@option{-D}|@option{--disassemble-all}]
2131 [@option{-z}|@option{--disassemble-zeroes}]
2132 [@option{-EB}|@option{-EL}|@option{--endian=}@{big | little @}]
2133 [@option{-f}|@option{--file-headers}]
2134 [@option{-F}|@option{--file-offsets}]
2135 [@option{--file-start-context}]
2136 [@option{-g}|@option{--debugging}]
2137 [@option{-e}|@option{--debugging-tags}]
2138 [@option{-h}|@option{--section-headers}|@option{--headers}]
2139 [@option{-i}|@option{--info}]
2140 [@option{-j} @var{section}|@option{--section=}@var{section}]
2141 [@option{-l}|@option{--line-numbers}]
2142 [@option{-S}|@option{--source}]
2143 [@option{--source-comment}[=@var{text}]]
2144 [@option{-m} @var{machine}|@option{--architecture=}@var{machine}]
2145 [@option{-M} @var{options}|@option{--disassembler-options=}@var{options}]
2146 [@option{-p}|@option{--private-headers}]
2147 [@option{-P} @var{options}|@option{--private=}@var{options}]
2148 [@option{-r}|@option{--reloc}]
2149 [@option{-R}|@option{--dynamic-reloc}]
2150 [@option{-s}|@option{--full-contents}]
2151 [@option{-W[lLiaprmfFsoRtUuTgAckK]}|
2152 @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]]
2153 [@option{--ctf=}@var{section}]
2154 [@option{-G}|@option{--stabs}]
2155 [@option{-t}|@option{--syms}]
2156 [@option{-T}|@option{--dynamic-syms}]
2157 [@option{-x}|@option{--all-headers}]
2158 [@option{-w}|@option{--wide}]
2159 [@option{--start-address=}@var{address}]
2160 [@option{--stop-address=}@var{address}]
2161 [@option{--prefix-addresses}]
2162 [@option{--[no-]show-raw-insn}]
2163 [@option{--adjust-vma=}@var{offset}]
2164 [@option{--dwarf-depth=@var{n}}]
2165 [@option{--dwarf-start=@var{n}}]
2166 [@option{--ctf-parent=}@var{section}]
2167 [@option{--no-recurse-limit}|@option{--recurse-limit}]
2168 [@option{--special-syms}]
2169 [@option{--prefix=}@var{prefix}]
2170 [@option{--prefix-strip=}@var{level}]
2171 [@option{--insn-width=}@var{width}]
2172 [@option{-V}|@option{--version}]
2173 [@option{-H}|@option{--help}]
2174 @var{objfile}@dots{}
2178 @c man begin DESCRIPTION objdump
2180 @command{objdump} displays information about one or more object files.
2181 The options control what particular information to display. This
2182 information is mostly useful to programmers who are working on the
2183 compilation tools, as opposed to programmers who just want their
2184 program to compile and work.
2186 @var{objfile}@dots{} are the object files to be examined. When you
2187 specify archives, @command{objdump} shows information on each of the member
2192 @c man begin OPTIONS objdump
2194 The long and short forms of options, shown here as alternatives, are
2195 equivalent. At least one option from the list
2196 @option{-a,-d,-D,-e,-f,-g,-G,-h,-H,-p,-P,-r,-R,-s,-S,-t,-T,-V,-x} must be given.
2200 @itemx --archive-header
2201 @cindex archive headers
2202 If any of the @var{objfile} files are archives, display the archive
2203 header information (in a format similar to @samp{ls -l}). Besides the
2204 information you could list with @samp{ar tv}, @samp{objdump -a} shows
2205 the object file format of each archive member.
2207 @item --adjust-vma=@var{offset}
2208 @cindex section addresses in objdump
2209 @cindex VMA in objdump
2210 When dumping information, first add @var{offset} to all the section
2211 addresses. This is useful if the section addresses do not correspond to
2212 the symbol table, which can happen when putting sections at particular
2213 addresses when using a format which can not represent section addresses,
2216 @item -b @var{bfdname}
2217 @itemx --target=@var{bfdname}
2218 @cindex object code format
2219 Specify that the object-code format for the object files is
2220 @var{bfdname}. This option may not be necessary; @var{objdump} can
2221 automatically recognize many formats.
2225 objdump -b oasys -m vax -h fu.o
2228 displays summary information from the section headers (@option{-h}) of
2229 @file{fu.o}, which is explicitly identified (@option{-m}) as a VAX object
2230 file in the format produced by Oasys compilers. You can list the
2231 formats available with the @option{-i} option.
2232 @xref{Target Selection}, for more information.
2235 @itemx --demangle[=@var{style}]
2236 @cindex demangling in objdump
2237 Decode (@dfn{demangle}) low-level symbol names into user-level names.
2238 Besides removing any initial underscore prepended by the system, this
2239 makes C++ function names readable. Different compilers have different
2240 mangling styles. The optional demangling style argument can be used to
2241 choose an appropriate demangling style for your compiler. @xref{c++filt},
2242 for more information on demangling.
2244 @item --recurse-limit
2245 @itemx --no-recurse-limit
2246 @itemx --recursion-limit
2247 @itemx --no-recursion-limit
2248 Enables or disables a limit on the amount of recursion performed
2249 whilst demangling strings. Since the name mangling formats allow for
2250 an inifinite level of recursion it is possible to create strings whose
2251 decoding will exhaust the amount of stack space available on the host
2252 machine, triggering a memory fault. The limit tries to prevent this
2253 from happening by restricting recursion to 2048 levels of nesting.
2255 The default is for this limit to be enabled, but disabling it may be
2256 necessary in order to demangle truly complicated names. Note however
2257 that if the recursion limit is disabled then stack exhaustion is
2258 possible and any bug reports about such an event will be rejected.
2262 Display debugging information. This attempts to parse STABS
2263 debugging format information stored in the file and print it out using
2264 a C like syntax. If no STABS debuging was found this option
2265 falls back on the @option{-W} option to print any DWARF information in
2269 @itemx --debugging-tags
2270 Like @option{-g}, but the information is generated in a format compatible
2274 @itemx --disassemble
2275 @itemx --disassemble=@var{symbol}
2276 @cindex disassembling object code
2277 @cindex machine instructions
2278 Display the assembler mnemonics for the machine instructions from the
2279 input file. This option only disassembles those sections which are
2280 expected to contain instructions. If the optional @var{symbol}
2281 argument is given, then display the assembler mnemonics starting at
2282 @var{symbol}. If @var{symbol} is a function name then disassembly
2283 will stop at the end of the function, otherwise it will stop when the
2284 next symbol is encountered. If there are no matches for @var{symbol}
2285 then nothing will be displayed.
2287 Note if the @option{--dwarf=follow-links} option has also been enabled
2288 then any symbol tables in linked debug info files will be read in and
2289 used when disassembling.
2292 @itemx --disassemble-all
2293 Like @option{-d}, but disassemble the contents of all sections, not just
2294 those expected to contain instructions.
2296 This option also has a subtle effect on the disassembly of
2297 instructions in code sections. When option @option{-d} is in effect
2298 objdump will assume that any symbols present in a code section occur
2299 on the boundary between instructions and it will refuse to disassemble
2300 across such a boundary. When option @option{-D} is in effect however
2301 this assumption is supressed. This means that it is possible for the
2302 output of @option{-d} and @option{-D} to differ if, for example, data
2303 is stored in code sections.
2305 If the target is an ARM architecture this switch also has the effect
2306 of forcing the disassembler to decode pieces of data found in code
2307 sections as if they were instructions.
2309 Note if the @option{--dwarf=follow-links} option has also been enabled
2310 then any symbol tables in linked debug info files will be read in and
2311 used when disassembling.
2313 @item --prefix-addresses
2314 When disassembling, print the complete address on each line. This is
2315 the older disassembly format.
2319 @itemx --endian=@{big|little@}
2321 @cindex disassembly endianness
2322 Specify the endianness of the object files. This only affects
2323 disassembly. This can be useful when disassembling a file format which
2324 does not describe endianness information, such as S-records.
2327 @itemx --file-headers
2328 @cindex object file header
2329 Display summary information from the overall header of
2330 each of the @var{objfile} files.
2333 @itemx --file-offsets
2334 @cindex object file offsets
2335 When disassembling sections, whenever a symbol is displayed, also
2336 display the file offset of the region of data that is about to be
2337 dumped. If zeroes are being skipped, then when disassembly resumes,
2338 tell the user how many zeroes were skipped and the file offset of the
2339 location from where the disassembly resumes. When dumping sections,
2340 display the file offset of the location from where the dump starts.
2342 @item --file-start-context
2343 @cindex source code context
2344 Specify that when displaying interlisted source code/disassembly
2345 (assumes @option{-S}) from a file that has not yet been displayed, extend the
2346 context to the start of the file.
2349 @itemx --section-headers
2351 @cindex section headers
2352 Display summary information from the section headers of the
2355 File segments may be relocated to nonstandard addresses, for example by
2356 using the @option{-Ttext}, @option{-Tdata}, or @option{-Tbss} options to
2357 @command{ld}. However, some object file formats, such as a.out, do not
2358 store the starting address of the file segments. In those situations,
2359 although @command{ld} relocates the sections correctly, using @samp{objdump
2360 -h} to list the file section headers cannot show the correct addresses.
2361 Instead, it shows the usual addresses, which are implicit for the
2364 Note, in some cases it is possible for a section to have both the
2365 READONLY and the NOREAD attributes set. In such cases the NOREAD
2366 attribute takes precedence, but @command{objdump} will report both
2367 since the exact setting of the flag bits might be important.
2371 Print a summary of the options to @command{objdump} and exit.
2375 @cindex architectures available
2376 @cindex object formats available
2377 Display a list showing all architectures and object formats available
2378 for specification with @option{-b} or @option{-m}.
2381 @itemx --section=@var{name}
2382 @cindex section information
2383 Display information only for section @var{name}.
2386 @itemx --line-numbers
2387 @cindex source filenames for object files
2388 Label the display (using debugging information) with the filename and
2389 source line numbers corresponding to the object code or relocs shown.
2390 Only useful with @option{-d}, @option{-D}, or @option{-r}.
2392 @item -m @var{machine}
2393 @itemx --architecture=@var{machine}
2394 @cindex architecture
2395 @cindex disassembly architecture
2396 Specify the architecture to use when disassembling object files. This
2397 can be useful when disassembling object files which do not describe
2398 architecture information, such as S-records. You can list the available
2399 architectures with the @option{-i} option.
2401 If the target is an ARM architecture then this switch has an
2402 additional effect. It restricts the disassembly to only those
2403 instructions supported by the architecture specified by @var{machine}.
2404 If it is necessary to use this switch because the input file does not
2405 contain any architecture information, but it is also desired to
2406 disassemble all the instructions use @option{-marm}.
2408 @item -M @var{options}
2409 @itemx --disassembler-options=@var{options}
2410 Pass target specific information to the disassembler. Only supported on
2411 some targets. If it is necessary to specify more than one
2412 disassembler option then multiple @option{-M} options can be used or
2413 can be placed together into a comma separated list.
2415 For ARC, @option{dsp} controls the printing of DSP instructions,
2416 @option{spfp} selects the printing of FPX single precision FP
2417 instructions, @option{dpfp} selects the printing of FPX double
2418 precision FP instructions, @option{quarkse_em} selects the printing of
2419 special QuarkSE-EM instructions, @option{fpuda} selects the printing
2420 of double precision assist instructions, @option{fpus} selects the
2421 printing of FPU single precision FP instructions, while @option{fpud}
2422 selects the printing of FPU double precision FP instructions.
2423 Additionally, one can choose to have all the immediates printed in
2424 hexadecimal using @option{hex}. By default, the short immediates are
2425 printed using the decimal representation, while the long immediate
2426 values are printed as hexadecimal.
2428 @option{cpu=...} allows to enforce a particular ISA when disassembling
2429 instructions, overriding the @option{-m} value or whatever is in the ELF file.
2430 This might be useful to select ARC EM or HS ISA, because architecture is same
2431 for those and disassembler relies on private ELF header data to decide if code
2432 is for EM or HS. This option might be specified multiple times - only the
2433 latest value will be used. Valid values are same as for the assembler
2434 @option{-mcpu=...} option.
2436 If the target is an ARM architecture then this switch can be used to
2437 select which register name set is used during disassembler. Specifying
2438 @option{-M reg-names-std} (the default) will select the register names as
2439 used in ARM's instruction set documentation, but with register 13 called
2440 'sp', register 14 called 'lr' and register 15 called 'pc'. Specifying
2441 @option{-M reg-names-apcs} will select the name set used by the ARM
2442 Procedure Call Standard, whilst specifying @option{-M reg-names-raw} will
2443 just use @samp{r} followed by the register number.
2445 There are also two variants on the APCS register naming scheme enabled
2446 by @option{-M reg-names-atpcs} and @option{-M reg-names-special-atpcs} which
2447 use the ARM/Thumb Procedure Call Standard naming conventions. (Either
2448 with the normal register names or the special register names).
2450 This option can also be used for ARM architectures to force the
2451 disassembler to interpret all instructions as Thumb instructions by
2452 using the switch @option{--disassembler-options=force-thumb}. This can be
2453 useful when attempting to disassemble thumb code produced by other
2456 For AArch64 targets this switch can be used to set whether instructions are
2457 disassembled as the most general instruction using the @option{-M no-aliases}
2458 option or whether instruction notes should be generated as comments in the
2459 disasssembly using @option{-M notes}.
2461 For the x86, some of the options duplicate functions of the @option{-m}
2462 switch, but allow finer grained control. Multiple selections from the
2463 following may be specified as a comma separated string.
2468 Select disassembly for the given architecture.
2472 Select between intel syntax mode and AT&T syntax mode.
2476 Select between AMD64 ISA and Intel64 ISA.
2478 @item intel-mnemonic
2480 Select between intel mnemonic mode and AT&T mnemonic mode.
2481 Note: @code{intel-mnemonic} implies @code{intel} and
2482 @code{att-mnemonic} implies @code{att}.
2489 Specify the default address size and operand size. These five options
2490 will be overridden if @code{x86-64}, @code{i386} or @code{i8086}
2491 appear later in the option string.
2494 When in AT&T mode, instructs the disassembler to print a mnemonic
2495 suffix even when the suffix could be inferred by the operands.
2498 For PowerPC, the @option{-M} argument @option{raw} selects
2499 disasssembly of hardware insns rather than aliases. For example, you
2500 will see @code{rlwinm} rather than @code{clrlwi}, and @code{addi}
2501 rather than @code{li}. All of the @option{-m} arguments for
2502 @command{gas} that select a CPU are supported. These are:
2503 @option{403}, @option{405}, @option{440}, @option{464}, @option{476},
2504 @option{601}, @option{603}, @option{604}, @option{620}, @option{7400},
2505 @option{7410}, @option{7450}, @option{7455}, @option{750cl},
2506 @option{821}, @option{850}, @option{860}, @option{a2}, @option{booke},
2507 @option{booke32}, @option{cell}, @option{com}, @option{e200z4},
2508 @option{e300}, @option{e500}, @option{e500mc}, @option{e500mc64},
2509 @option{e500x2}, @option{e5500}, @option{e6500}, @option{efs},
2510 @option{power4}, @option{power5}, @option{power6}, @option{power7},
2511 @option{power8}, @option{power9}, @option{ppc}, @option{ppc32},
2512 @option{ppc64}, @option{ppc64bridge}, @option{ppcps}, @option{pwr},
2513 @option{pwr2}, @option{pwr4}, @option{pwr5}, @option{pwr5x},
2514 @option{pwr6}, @option{pwr7}, @option{pwr8}, @option{pwr9},
2515 @option{pwrx}, @option{titan}, and @option{vle}.
2516 @option{32} and @option{64} modify the default or a prior CPU
2517 selection, disabling and enabling 64-bit insns respectively. In
2518 addition, @option{altivec}, @option{any}, @option{htm}, @option{vsx},
2519 and @option{spe} add capabilities to a previous @emph{or later} CPU
2520 selection. @option{any} will disassemble any opcode known to
2521 binutils, but in cases where an opcode has two different meanings or
2522 different arguments, you may not see the disassembly you expect.
2523 If you disassemble without giving a CPU selection, a default will be
2524 chosen from information gleaned by BFD from the object files headers,
2525 but the result again may not be as you expect.
2527 For MIPS, this option controls the printing of instruction mnemonic
2528 names and register names in disassembled instructions. Multiple
2529 selections from the following may be specified as a comma separated
2530 string, and invalid options are ignored:
2534 Print the 'raw' instruction mnemonic instead of some pseudo
2535 instruction mnemonic. I.e., print 'daddu' or 'or' instead of 'move',
2536 'sll' instead of 'nop', etc.
2539 Disassemble MSA instructions.
2542 Disassemble the virtualization ASE instructions.
2545 Disassemble the eXtended Physical Address (XPA) ASE instructions.
2547 @item gpr-names=@var{ABI}
2548 Print GPR (general-purpose register) names as appropriate
2549 for the specified ABI. By default, GPR names are selected according to
2550 the ABI of the binary being disassembled.
2552 @item fpr-names=@var{ABI}
2553 Print FPR (floating-point register) names as
2554 appropriate for the specified ABI. By default, FPR numbers are printed
2557 @item cp0-names=@var{ARCH}
2558 Print CP0 (system control coprocessor; coprocessor 0) register names
2559 as appropriate for the CPU or architecture specified by
2560 @var{ARCH}. By default, CP0 register names are selected according to
2561 the architecture and CPU of the binary being disassembled.
2563 @item hwr-names=@var{ARCH}
2564 Print HWR (hardware register, used by the @code{rdhwr} instruction) names
2565 as appropriate for the CPU or architecture specified by
2566 @var{ARCH}. By default, HWR names are selected according to
2567 the architecture and CPU of the binary being disassembled.
2569 @item reg-names=@var{ABI}
2570 Print GPR and FPR names as appropriate for the selected ABI.
2572 @item reg-names=@var{ARCH}
2573 Print CPU-specific register names (CP0 register and HWR names)
2574 as appropriate for the selected CPU or architecture.
2577 For any of the options listed above, @var{ABI} or
2578 @var{ARCH} may be specified as @samp{numeric} to have numbers printed
2579 rather than names, for the selected types of registers.
2580 You can list the available values of @var{ABI} and @var{ARCH} using
2581 the @option{--help} option.
2583 For VAX, you can specify function entry addresses with @option{-M
2584 entry:0xf00ba}. You can use this multiple times to properly
2585 disassemble VAX binary files that don't contain symbol tables (like
2586 ROM dumps). In these cases, the function entry mask would otherwise
2587 be decoded as VAX instructions, which would probably lead the rest
2588 of the function being wrongly disassembled.
2591 @itemx --private-headers
2592 Print information that is specific to the object file format. The exact
2593 information printed depends upon the object file format. For some
2594 object file formats, no additional information is printed.
2596 @item -P @var{options}
2597 @itemx --private=@var{options}
2598 Print information that is specific to the object file format. The
2599 argument @var{options} is a comma separated list that depends on the
2600 format (the lists of options is displayed with the help).
2602 For XCOFF, the available options are:
2618 Not all object formats support this option. In particular the ELF
2619 format does not use it.
2623 @cindex relocation entries, in object file
2624 Print the relocation entries of the file. If used with @option{-d} or
2625 @option{-D}, the relocations are printed interspersed with the
2629 @itemx --dynamic-reloc
2630 @cindex dynamic relocation entries, in object file
2631 Print the dynamic relocation entries of the file. This is only
2632 meaningful for dynamic objects, such as certain types of shared
2633 libraries. As for @option{-r}, if used with @option{-d} or
2634 @option{-D}, the relocations are printed interspersed with the
2638 @itemx --full-contents
2639 @cindex sections, full contents
2640 @cindex object file sections
2641 Display the full contents of any sections requested. By default all
2642 non-empty sections are displayed.
2646 @cindex source disassembly
2647 @cindex disassembly, with source
2648 Display source code intermixed with disassembly, if possible. Implies
2651 @item --source-comment[=@var{txt}]
2652 @cindex source disassembly
2653 @cindex disassembly, with source
2654 Like the @option{-S} option, but all source code lines are displayed
2655 with a prefix of @var{txt}. Typically @var{txt} will be a comment
2656 string which can be used to distinguish the assembler code from the
2657 source code. If @var{txt} is not provided then a default string of
2658 @var{``# ``} (hash followed by a space), will be used.
2660 @item --prefix=@var{prefix}
2661 @cindex Add prefix to absolute paths
2662 Specify @var{prefix} to add to the absolute paths when used with
2665 @item --prefix-strip=@var{level}
2666 @cindex Strip absolute paths
2667 Indicate how many initial directory names to strip off the hardwired
2668 absolute paths. It has no effect without @option{--prefix=}@var{prefix}.
2670 @item --show-raw-insn
2671 When disassembling instructions, print the instruction in hex as well as
2672 in symbolic form. This is the default except when
2673 @option{--prefix-addresses} is used.
2675 @item --no-show-raw-insn
2676 When disassembling instructions, do not print the instruction bytes.
2677 This is the default when @option{--prefix-addresses} is used.
2679 @item --insn-width=@var{width}
2680 @cindex Instruction width
2681 Display @var{width} bytes on a single line when disassembling
2684 @item -W[lLiaprmfFsoRtUuTgAckK]
2685 @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]
2686 @include debug.options.texi
2689 Enable additional checks for consistency of Dwarf information.
2691 @include ctf.options.texi
2697 @cindex debug symbols
2698 @cindex ELF object file format
2699 Display the full contents of any sections requested. Display the
2700 contents of the .stab and .stab.index and .stab.excl sections from an
2701 ELF file. This is only useful on systems (such as Solaris 2.0) in which
2702 @code{.stab} debugging symbol-table entries are carried in an ELF
2703 section. In most other file formats, debugging symbol-table entries are
2704 interleaved with linkage symbols, and are visible in the @option{--syms}
2707 @item --start-address=@var{address}
2708 @cindex start-address
2709 Start displaying data at the specified address. This affects the output
2710 of the @option{-d}, @option{-r} and @option{-s} options.
2712 @item --stop-address=@var{address}
2713 @cindex stop-address
2714 Stop displaying data at the specified address. This affects the output
2715 of the @option{-d}, @option{-r} and @option{-s} options.
2719 @cindex symbol table entries, printing
2720 Print the symbol table entries of the file.
2721 This is similar to the information provided by the @samp{nm} program,
2722 although the display format is different. The format of the output
2723 depends upon the format of the file being dumped, but there are two main
2724 types. One looks like this:
2727 [ 4](sec 3)(fl 0x00)(ty 0)(scl 3) (nx 1) 0x00000000 .bss
2728 [ 6](sec 1)(fl 0x00)(ty 0)(scl 2) (nx 0) 0x00000000 fred
2731 where the number inside the square brackets is the number of the entry
2732 in the symbol table, the @var{sec} number is the section number, the
2733 @var{fl} value are the symbol's flag bits, the @var{ty} number is the
2734 symbol's type, the @var{scl} number is the symbol's storage class and
2735 the @var{nx} value is the number of auxilary entries associated with
2736 the symbol. The last two fields are the symbol's value and its name.
2738 The other common output format, usually seen with ELF based files,
2742 00000000 l d .bss 00000000 .bss
2743 00000000 g .text 00000000 fred
2746 Here the first number is the symbol's value (sometimes refered to as
2747 its address). The next field is actually a set of characters and
2748 spaces indicating the flag bits that are set on the symbol. These
2749 characters are described below. Next is the section with which the
2750 symbol is associated or @emph{*ABS*} if the section is absolute (ie
2751 not connected with any section), or @emph{*UND*} if the section is
2752 referenced in the file being dumped, but not defined there.
2754 After the section name comes another field, a number, which for common
2755 symbols is the alignment and for other symbol is the size. Finally
2756 the symbol's name is displayed.
2758 The flag characters are divided into 7 groups as follows:
2764 The symbol is a local (l), global (g), unique global (u), neither
2765 global nor local (a space) or both global and local (!). A
2766 symbol can be neither local or global for a variety of reasons, e.g.,
2767 because it is used for debugging, but it is probably an indication of
2768 a bug if it is ever both local and global. Unique global symbols are
2769 a GNU extension to the standard set of ELF symbol bindings. For such
2770 a symbol the dynamic linker will make sure that in the entire process
2771 there is just one symbol with this name and type in use.
2774 The symbol is weak (w) or strong (a space).
2777 The symbol denotes a constructor (C) or an ordinary symbol (a space).
2780 The symbol is a warning (W) or a normal symbol (a space). A warning
2781 symbol's name is a message to be displayed if the symbol following the
2782 warning symbol is ever referenced.
2786 The symbol is an indirect reference to another symbol (I), a function
2787 to be evaluated during reloc processing (i) or a normal symbol (a
2792 The symbol is a debugging symbol (d) or a dynamic symbol (D) or a
2793 normal symbol (a space).
2798 The symbol is the name of a function (F) or a file (f) or an object
2799 (O) or just a normal symbol (a space).
2803 @itemx --dynamic-syms
2804 @cindex dynamic symbol table entries, printing
2805 Print the dynamic symbol table entries of the file. This is only
2806 meaningful for dynamic objects, such as certain types of shared
2807 libraries. This is similar to the information provided by the @samp{nm}
2808 program when given the @option{-D} (@option{--dynamic}) option.
2810 The output format is similar to that produced by the @option{--syms}
2811 option, except that an extra field is inserted before the symbol's
2812 name, giving the version information associated with the symbol.
2813 If the version is the default version to be used when resolving
2814 unversioned references to the symbol then it's displayed as is,
2815 otherwise it's put into parentheses.
2817 @item --special-syms
2818 When displaying symbols include those which the target considers to be
2819 special in some way and which would not normally be of interest to the
2824 Print the version number of @command{objdump} and exit.
2827 @itemx --all-headers
2828 @cindex all header information, object file
2829 @cindex header information, all
2830 Display all available header information, including the symbol table and
2831 relocation entries. Using @option{-x} is equivalent to specifying all of
2832 @option{-a -f -h -p -r -t}.
2836 @cindex wide output, printing
2837 Format some lines for output devices that have more than 80 columns.
2838 Also do not truncate symbol names when they are displayed.
2841 @itemx --disassemble-zeroes
2842 Normally the disassembly output will skip blocks of zeroes. This
2843 option directs the disassembler to disassemble those blocks, just like
2850 @c man begin SEEALSO objdump
2851 nm(1), readelf(1), and the Info entries for @file{binutils}.
2859 @cindex archive contents
2860 @cindex symbol index
2862 @c man title ranlib generate an index to an archive
2865 @c man begin SYNOPSIS ranlib
2866 ranlib [@option{--plugin} @var{name}] [@option{-DhHvVt}] @var{archive}
2870 @c man begin DESCRIPTION ranlib
2872 @command{ranlib} generates an index to the contents of an archive and
2873 stores it in the archive. The index lists each symbol defined by a
2874 member of an archive that is a relocatable object file.
2876 You may use @samp{nm -s} or @samp{nm --print-armap} to list this index.
2878 An archive with such an index speeds up linking to the library and
2879 allows routines in the library to call each other without regard to
2880 their placement in the archive.
2882 The @sc{gnu} @command{ranlib} program is another form of @sc{gnu} @command{ar}; running
2883 @command{ranlib} is completely equivalent to executing @samp{ar -s}.
2888 @c man begin OPTIONS ranlib
2894 Show usage information for @command{ranlib}.
2899 Show the version number of @command{ranlib}.
2902 @cindex deterministic archives
2903 @kindex --enable-deterministic-archives
2904 Operate in @emph{deterministic} mode. The symbol map archive member's
2905 header will show zero for the UID, GID, and timestamp. When this
2906 option is used, multiple runs will produce identical output files.
2908 If @file{binutils} was configured with
2909 @option{--enable-deterministic-archives}, then this mode is on by
2910 default. It can be disabled with the @samp{-U} option, described
2914 Update the timestamp of the symbol map of an archive.
2917 @cindex deterministic archives
2918 @kindex --enable-deterministic-archives
2919 Do @emph{not} operate in @emph{deterministic} mode. This is the
2920 inverse of the @samp{-D} option, above: the archive index will get
2921 actual UID, GID, timestamp, and file mode values.
2923 If @file{binutils} was configured @emph{without}
2924 @option{--enable-deterministic-archives}, then this mode is on by
2932 @c man begin SEEALSO ranlib
2933 ar(1), nm(1), and the Info entries for @file{binutils}.
2941 @cindex section sizes
2943 @c man title size list section sizes and total size of binary files
2946 @c man begin SYNOPSIS size
2947 size [@option{-A}|@option{-B}|@option{-G}|@option{--format=}@var{compatibility}]
2949 [@option{-d}|@option{-o}|@option{-x}|@option{--radix=}@var{number}]
2951 [@option{-t}|@option{--totals}]
2952 [@option{--target=}@var{bfdname}] [@option{-V}|@option{--version}]
2953 [@var{objfile}@dots{}]
2957 @c man begin DESCRIPTION size
2959 The @sc{gnu} @command{size} utility lists the section sizes and the total
2960 size for each of the binary files @var{objfile} on its argument list.
2961 By default, one line of output is generated for each file or each
2962 module if the file is an archive.
2964 @var{objfile}@dots{} are the files to be examined. If none are
2965 specified, the file @code{a.out} will be used instead.
2969 @c man begin OPTIONS size
2971 The command-line options have the following meanings:
2977 @itemx --format=@var{compatibility}
2978 @cindex @command{size} display format
2979 Using one of these options, you can choose whether the output from @sc{gnu}
2980 @command{size} resembles output from System V @command{size} (using @option{-A},
2981 or @option{--format=sysv}), or Berkeley @command{size} (using @option{-B}, or
2982 @option{--format=berkeley}). The default is the one-line format similar to
2983 Berkeley's. Alternatively, you can choose the GNU format output
2984 (using @option{-G}, or @option{--format=gnu}), this is similar to
2985 Berkeley's output format, but sizes are counted differently.
2986 @c Bonus for doc-source readers: you can also say --format=strange (or
2987 @c anything else that starts with 's') for sysv, and --format=boring (or
2988 @c anything else that starts with 'b') for Berkeley.
2990 Here is an example of the Berkeley (default) format of output from
2993 $ size --format=Berkeley ranlib size
2994 text data bss dec hex filename
2995 294880 81920 11592 388392 5ed28 ranlib
2996 294880 81920 11888 388688 5ee50 size
2999 The Berkeley style output counts read only data in the @code{text}
3000 column, not in the @code{data} column, the @code{dec} and @code{hex}
3001 columns both display the sum of the @code{text}, @code{data}, and
3002 @code{bss} columns in decimal and hexadecimal respectively.
3004 The GNU format counts read only data in the @code{data} column, not
3005 the @code{text} column, and only displays the sum of the @code{text},
3006 @code{data}, and @code{bss} columns once, in the @code{total} column.
3007 The @option{--radix} option can be used to change the number base for
3008 all columns. Here is the same data displayed with GNU conventions:
3011 $ size --format=GNU ranlib size
3012 text data bss total filename
3013 279880 96920 11592 388392 ranlib
3014 279880 96920 11888 388688 size
3018 This is the same data, but displayed closer to System V conventions:
3021 $ size --format=SysV ranlib size
3039 Show a summary of acceptable arguments and options.
3044 @itemx --radix=@var{number}
3045 @cindex @command{size} number format
3046 @cindex radix for section sizes
3047 Using one of these options, you can control whether the size of each
3048 section is given in decimal (@option{-d}, or @option{--radix=10}); octal
3049 (@option{-o}, or @option{--radix=8}); or hexadecimal (@option{-x}, or
3050 @option{--radix=16}). In @option{--radix=@var{number}}, only the three
3051 values (8, 10, 16) are supported. The total size is always given in two
3052 radices; decimal and hexadecimal for @option{-d} or @option{-x} output, or
3053 octal and hexadecimal if you're using @option{-o}.
3056 Print total size of common symbols in each file. When using Berkeley
3057 or GNU format these are included in the bss size.
3061 Show totals of all objects listed (Berkeley or GNU format mode only).
3063 @item --target=@var{bfdname}
3064 @cindex object code format
3065 Specify that the object-code format for @var{objfile} is
3066 @var{bfdname}. This option may not be necessary; @command{size} can
3067 automatically recognize many formats.
3068 @xref{Target Selection}, for more information.
3072 Display the version number of @command{size}.
3078 @c man begin SEEALSO size
3079 ar(1), objdump(1), readelf(1), and the Info entries for @file{binutils}.
3086 @cindex listings strings
3087 @cindex printing strings
3088 @cindex strings, printing
3090 @c man title strings print the sequences of printable characters in files
3093 @c man begin SYNOPSIS strings
3094 strings [@option{-afovV}] [@option{-}@var{min-len}]
3095 [@option{-n} @var{min-len}] [@option{--bytes=}@var{min-len}]
3096 [@option{-t} @var{radix}] [@option{--radix=}@var{radix}]
3097 [@option{-e} @var{encoding}] [@option{--encoding=}@var{encoding}]
3098 [@option{-}] [@option{--all}] [@option{--print-file-name}]
3099 [@option{-T} @var{bfdname}] [@option{--target=}@var{bfdname}]
3100 [@option{-w}] [@option{--include-all-whitespace}]
3101 [@option{-s}] [@option{--output-separator}@var{sep_string}]
3102 [@option{--help}] [@option{--version}] @var{file}@dots{}
3106 @c man begin DESCRIPTION strings
3108 For each @var{file} given, @sc{gnu} @command{strings} prints the
3109 printable character sequences that are at least 4 characters long (or
3110 the number given with the options below) and are followed by an
3111 unprintable character.
3113 Depending upon how the strings program was configured it will default
3114 to either displaying all the printable sequences that it can find in
3115 each file, or only those sequences that are in loadable, initialized
3116 data sections. If the file type in unrecognizable, or if strings is
3117 reading from stdin then it will always display all of the printable
3118 sequences that it can find.
3120 For backwards compatibility any file that occurs after a command-line
3121 option of just @option{-} will also be scanned in full, regardless of
3122 the presence of any @option{-d} option.
3124 @command{strings} is mainly useful for determining the contents of
3129 @c man begin OPTIONS strings
3135 Scan the whole file, regardless of what sections it contains or
3136 whether those sections are loaded or initialized. Normally this is
3137 the default behaviour, but strings can be configured so that the
3138 @option{-d} is the default instead.
3140 The @option{-} option is position dependent and forces strings to
3141 perform full scans of any file that is mentioned after the @option{-}
3142 on the command line, even if the @option{-d} option has been
3147 Only print strings from initialized, loaded data sections in the
3148 file. This may reduce the amount of garbage in the output, but it
3149 also exposes the strings program to any security flaws that may be
3150 present in the BFD library used to scan and load sections. Strings
3151 can be configured so that this option is the default behaviour. In
3152 such cases the @option{-a} option can be used to avoid using the BFD
3153 library and instead just print all of the strings found in the file.
3156 @itemx --print-file-name
3157 Print the name of the file before each string.
3160 Print a summary of the program usage on the standard output and exit.
3162 @item -@var{min-len}
3163 @itemx -n @var{min-len}
3164 @itemx --bytes=@var{min-len}
3165 Print sequences of characters that are at least @var{min-len} characters
3166 long, instead of the default 4.
3169 Like @samp{-t o}. Some other versions of @command{strings} have @option{-o}
3170 act like @samp{-t d} instead. Since we can not be compatible with both
3171 ways, we simply chose one.
3173 @item -t @var{radix}
3174 @itemx --radix=@var{radix}
3175 Print the offset within the file before each string. The single
3176 character argument specifies the radix of the offset---@samp{o} for
3177 octal, @samp{x} for hexadecimal, or @samp{d} for decimal.
3179 @item -e @var{encoding}
3180 @itemx --encoding=@var{encoding}
3181 Select the character encoding of the strings that are to be found.
3182 Possible values for @var{encoding} are: @samp{s} = single-7-bit-byte
3183 characters (ASCII, ISO 8859, etc., default), @samp{S} =
3184 single-8-bit-byte characters, @samp{b} = 16-bit bigendian, @samp{l} =
3185 16-bit littleendian, @samp{B} = 32-bit bigendian, @samp{L} = 32-bit
3186 littleendian. Useful for finding wide character strings. (@samp{l}
3187 and @samp{b} apply to, for example, Unicode UTF-16/UCS-2 encodings).
3189 @item -T @var{bfdname}
3190 @itemx --target=@var{bfdname}
3191 @cindex object code format
3192 Specify an object code format other than your system's default format.
3193 @xref{Target Selection}, for more information.
3198 Print the program version number on the standard output and exit.
3201 @itemx --include-all-whitespace
3202 By default tab and space characters are included in the strings that
3203 are displayed, but other whitespace characters, such a newlines and
3204 carriage returns, are not. The @option{-w} option changes this so
3205 that all whitespace characters are considered to be part of a string.
3208 @itemx --output-separator
3209 By default, output strings are delimited by a new-line. This option
3210 allows you to supply any string to be used as the output record
3211 separator. Useful with --include-all-whitespace where strings
3212 may contain new-lines internally.
3218 @c man begin SEEALSO strings
3219 ar(1), nm(1), objdump(1), ranlib(1), readelf(1)
3220 and the Info entries for @file{binutils}.
3228 @cindex removing symbols
3229 @cindex discarding symbols
3230 @cindex symbols, discarding
3232 @c man title strip discard symbols and other data from object files
3235 @c man begin SYNOPSIS strip
3236 strip [@option{-F} @var{bfdname} |@option{--target=}@var{bfdname}]
3237 [@option{-I} @var{bfdname} |@option{--input-target=}@var{bfdname}]
3238 [@option{-O} @var{bfdname} |@option{--output-target=}@var{bfdname}]
3239 [@option{-s}|@option{--strip-all}]
3240 [@option{-S}|@option{-g}|@option{-d}|@option{--strip-debug}]
3241 [@option{--strip-dwo}]
3242 [@option{-K} @var{symbolname}|@option{--keep-symbol=}@var{symbolname}]
3243 [@option{-M}|@option{--merge-notes}][@option{--no-merge-notes}]
3244 [@option{-N} @var{symbolname} |@option{--strip-symbol=}@var{symbolname}]
3245 [@option{-w}|@option{--wildcard}]
3246 [@option{-x}|@option{--discard-all}] [@option{-X} |@option{--discard-locals}]
3247 [@option{-R} @var{sectionname} |@option{--remove-section=}@var{sectionname}]
3248 [@option{--keep-section=}@var{sectionpattern}]
3249 [@option{--remove-relocations=}@var{sectionpattern}]
3250 [@option{-o} @var{file}] [@option{-p}|@option{--preserve-dates}]
3251 [@option{-D}|@option{--enable-deterministic-archives}]
3252 [@option{-U}|@option{--disable-deterministic-archives}]
3253 [@option{--keep-file-symbols}]
3254 [@option{--only-keep-debug}]
3255 [@option{-v} |@option{--verbose}] [@option{-V}|@option{--version}]
3256 [@option{--help}] [@option{--info}]
3257 @var{objfile}@dots{}
3261 @c man begin DESCRIPTION strip
3263 @sc{gnu} @command{strip} discards all symbols from object files
3264 @var{objfile}. The list of object files may include archives.
3265 At least one object file must be given.
3267 @command{strip} modifies the files named in its argument,
3268 rather than writing modified copies under different names.
3272 @c man begin OPTIONS strip
3275 @item -F @var{bfdname}
3276 @itemx --target=@var{bfdname}
3277 Treat the original @var{objfile} as a file with the object
3278 code format @var{bfdname}, and rewrite it in the same format.
3279 @xref{Target Selection}, for more information.
3282 Show a summary of the options to @command{strip} and exit.
3285 Display a list showing all architectures and object formats available.
3287 @item -I @var{bfdname}
3288 @itemx --input-target=@var{bfdname}
3289 Treat the original @var{objfile} as a file with the object
3290 code format @var{bfdname}.
3291 @xref{Target Selection}, for more information.
3293 @item -O @var{bfdname}
3294 @itemx --output-target=@var{bfdname}
3295 Replace @var{objfile} with a file in the output format @var{bfdname}.
3296 @xref{Target Selection}, for more information.
3298 @item -R @var{sectionname}
3299 @itemx --remove-section=@var{sectionname}
3300 Remove any section named @var{sectionname} from the output file, in
3301 addition to whatever sections would otherwise be removed. This
3302 option may be given more than once. Note that using this option
3303 inappropriately may make the output file unusable. The wildcard
3304 character @samp{*} may be given at the end of @var{sectionname}. If
3305 so, then any section starting with @var{sectionname} will be removed.
3307 If the first character of @var{sectionpattern} is the exclamation
3308 point (!) then matching sections will not be removed even if an
3309 earlier use of @option{--remove-section} on the same command line
3310 would otherwise remove it. For example:
3313 --remove-section=.text.* --remove-section=!.text.foo
3316 will remove all sections matching the pattern '.text.*', but will not
3317 remove the section '.text.foo'.
3319 @item --keep-section=@var{sectionpattern}
3320 When removing sections from the output file, keep sections that match
3321 @var{sectionpattern}.
3323 @item --remove-relocations=@var{sectionpattern}
3324 Remove relocations from the output file for any section matching
3325 @var{sectionpattern}. This option may be given more than once. Note
3326 that using this option inappropriately may make the output file
3327 unusable. Wildcard characters are accepted in @var{sectionpattern}.
3331 --remove-relocations=.text.*
3334 will remove the relocations for all sections matching the patter
3337 If the first character of @var{sectionpattern} is the exclamation
3338 point (!) then matching sections will not have their relocation
3339 removed even if an earlier use of @option{--remove-relocations} on the
3340 same command line would otherwise cause the relocations to be removed.
3344 --remove-relocations=.text.* --remove-relocations=!.text.foo
3347 will remove all relocations for sections matching the pattern
3348 '.text.*', but will not remove relocations for the section
3358 @itemx --strip-debug
3359 Remove debugging symbols only.
3362 Remove the contents of all DWARF .dwo sections, leaving the
3363 remaining debugging sections and all symbols intact.
3364 See the description of this option in the @command{objcopy} section
3365 for more information.
3367 @item --strip-unneeded
3368 Remove all symbols that are not needed for relocation processing.
3370 @item -K @var{symbolname}
3371 @itemx --keep-symbol=@var{symbolname}
3372 When stripping symbols, keep symbol @var{symbolname} even if it would
3373 normally be stripped. This option may be given more than once.
3376 @itemx --merge-notes
3377 @itemx --no-merge-notes
3378 For ELF files, attempt (or do not attempt) to reduce the size of any
3379 SHT_NOTE type sections by removing duplicate notes. The default is to
3380 attempt this reduction unless stripping debug or DWO information.
3382 @item -N @var{symbolname}
3383 @itemx --strip-symbol=@var{symbolname}
3384 Remove symbol @var{symbolname} from the source file. This option may be
3385 given more than once, and may be combined with strip options other than
3389 Put the stripped output in @var{file}, rather than replacing the
3390 existing file. When this argument is used, only one @var{objfile}
3391 argument may be specified.
3394 @itemx --preserve-dates
3395 Preserve the access and modification dates of the file.
3398 @itemx --enable-deterministic-archives
3399 @cindex deterministic archives
3400 @kindex --enable-deterministic-archives
3401 Operate in @emph{deterministic} mode. When copying archive members
3402 and writing the archive index, use zero for UIDs, GIDs, timestamps,
3403 and use consistent file modes for all files.
3405 If @file{binutils} was configured with
3406 @option{--enable-deterministic-archives}, then this mode is on by default.
3407 It can be disabled with the @samp{-U} option, below.
3410 @itemx --disable-deterministic-archives
3411 @cindex deterministic archives
3412 @kindex --enable-deterministic-archives
3413 Do @emph{not} operate in @emph{deterministic} mode. This is the
3414 inverse of the @option{-D} option, above: when copying archive members
3415 and writing the archive index, use their actual UID, GID, timestamp,
3416 and file mode values.
3418 This is the default unless @file{binutils} was configured with
3419 @option{--enable-deterministic-archives}.
3423 Permit regular expressions in @var{symbolname}s used in other command
3424 line options. The question mark (?), asterisk (*), backslash (\) and
3425 square brackets ([]) operators can be used anywhere in the symbol
3426 name. If the first character of the symbol name is the exclamation
3427 point (!) then the sense of the switch is reversed for that symbol.
3434 would cause strip to only keep symbols that start with the letters
3435 ``fo'', but to discard the symbol ``foo''.
3438 @itemx --discard-all
3439 Remove non-global symbols.
3442 @itemx --discard-locals
3443 Remove compiler-generated local symbols.
3444 (These usually start with @samp{L} or @samp{.}.)
3446 @item --keep-file-symbols
3447 When stripping a file, perhaps with @option{--strip-debug} or
3448 @option{--strip-unneeded}, retain any symbols specifying source file names,
3449 which would otherwise get stripped.
3451 @item --only-keep-debug
3452 Strip a file, emptying the contents of any sections that would not be
3453 stripped by @option{--strip-debug} and leaving the debugging sections
3454 intact. In ELF files, this preserves all the note sections in the
3457 Note - the section headers of the stripped sections are preserved,
3458 including their sizes, but the contents of the section are discarded.
3459 The section headers are preserved so that other tools can match up the
3460 debuginfo file with the real executable, even if that executable has
3461 been relocated to a different address space.
3463 The intention is that this option will be used in conjunction with
3464 @option{--add-gnu-debuglink} to create a two part executable. One a
3465 stripped binary which will occupy less space in RAM and in a
3466 distribution and the second a debugging information file which is only
3467 needed if debugging abilities are required. The suggested procedure
3468 to create these files is as follows:
3471 @item Link the executable as normal. Assuming that it is called
3473 @item Run @code{objcopy --only-keep-debug foo foo.dbg} to
3474 create a file containing the debugging info.
3475 @item Run @code{objcopy --strip-debug foo} to create a
3476 stripped executable.
3477 @item Run @code{objcopy --add-gnu-debuglink=foo.dbg foo}
3478 to add a link to the debugging info into the stripped executable.
3481 Note---the choice of @code{.dbg} as an extension for the debug info
3482 file is arbitrary. Also the @code{--only-keep-debug} step is
3483 optional. You could instead do this:
3486 @item Link the executable as normal.
3487 @item Copy @code{foo} to @code{foo.full}
3488 @item Run @code{strip --strip-debug foo}
3489 @item Run @code{objcopy --add-gnu-debuglink=foo.full foo}
3492 i.e., the file pointed to by the @option{--add-gnu-debuglink} can be the
3493 full executable. It does not have to be a file created by the
3494 @option{--only-keep-debug} switch.
3496 Note---this switch is only intended for use on fully linked files. It
3497 does not make sense to use it on object files where the debugging
3498 information may be incomplete. Besides the gnu_debuglink feature
3499 currently only supports the presence of one filename containing
3500 debugging information, not multiple filenames on a one-per-object-file
3505 Show the version number for @command{strip}.
3509 Verbose output: list all object files modified. In the case of
3510 archives, @samp{strip -v} lists all members of the archive.
3516 @c man begin SEEALSO strip
3517 the Info entries for @file{binutils}.
3521 @node c++filt, addr2line, strip, Top
3525 @cindex demangling C++ symbols
3527 @c man title cxxfilt demangle C++ and Java symbols
3530 @c man begin SYNOPSIS cxxfilt
3531 c++filt [@option{-_}|@option{--strip-underscore}]
3532 [@option{-n}|@option{--no-strip-underscore}]
3533 [@option{-p}|@option{--no-params}]
3534 [@option{-t}|@option{--types}]
3535 [@option{-i}|@option{--no-verbose}]
3536 [@option{-r}|@option{--no-recurse-limit}]
3537 [@option{-R}|@option{--recurse-limit}]
3538 [@option{-s} @var{format}|@option{--format=}@var{format}]
3539 [@option{--help}] [@option{--version}] [@var{symbol}@dots{}]
3543 @c man begin DESCRIPTION cxxfilt
3546 The C++ and Java languages provide function overloading, which means
3547 that you can write many functions with the same name, providing that
3548 each function takes parameters of different types. In order to be
3549 able to distinguish these similarly named functions C++ and Java
3550 encode them into a low-level assembler name which uniquely identifies
3551 each different version. This process is known as @dfn{mangling}. The
3553 @footnote{MS-DOS does not allow @kbd{+} characters in file names, so on
3554 MS-DOS this program is named @command{CXXFILT}.}
3555 program does the inverse mapping: it decodes (@dfn{demangles}) low-level
3556 names into user-level names so that they can be read.
3558 Every alphanumeric word (consisting of letters, digits, underscores,
3559 dollars, or periods) seen in the input is a potential mangled name.
3560 If the name decodes into a C++ name, the C++ name replaces the
3561 low-level name in the output, otherwise the original word is output.
3562 In this way you can pass an entire assembler source file, containing
3563 mangled names, through @command{c++filt} and see the same source file
3564 containing demangled names.
3566 You can also use @command{c++filt} to decipher individual symbols by
3567 passing them on the command line:
3570 c++filt @var{symbol}
3573 If no @var{symbol} arguments are given, @command{c++filt} reads symbol
3574 names from the standard input instead. All the results are printed on
3575 the standard output. The difference between reading names from the
3576 command line versus reading names from the standard input is that
3577 command-line arguments are expected to be just mangled names and no
3578 checking is performed to separate them from surrounding text. Thus
3585 will work and demangle the name to ``f()'' whereas:
3591 will not work. (Note the extra comma at the end of the mangled
3592 name which makes it invalid). This command however will work:
3595 echo _Z1fv, | c++filt -n
3598 and will display ``f(),'', i.e., the demangled name followed by a
3599 trailing comma. This behaviour is because when the names are read
3600 from the standard input it is expected that they might be part of an
3601 assembler source file where there might be extra, extraneous
3602 characters trailing after a mangled name. For example:
3605 .type _Z1fv, @@function
3610 @c man begin OPTIONS cxxfilt
3614 @itemx --strip-underscore
3615 On some systems, both the C and C++ compilers put an underscore in front
3616 of every name. For example, the C name @code{foo} gets the low-level
3617 name @code{_foo}. This option removes the initial underscore. Whether
3618 @command{c++filt} removes the underscore by default is target dependent.
3621 @itemx --no-strip-underscore
3622 Do not remove the initial underscore.
3626 When demangling the name of a function, do not display the types of
3627 the function's parameters.
3631 Attempt to demangle types as well as function names. This is disabled
3632 by default since mangled types are normally only used internally in
3633 the compiler, and they can be confused with non-mangled names. For example,
3634 a function called ``a'' treated as a mangled type name would be
3635 demangled to ``signed char''.
3639 Do not include implementation details (if any) in the demangled
3644 @itemx --recurse-limit
3645 @itemx --no-recurse-limit
3646 @itemx --recursion-limit
3647 @itemx --no-recursion-limit
3648 Enables or disables a limit on the amount of recursion performed
3649 whilst demangling strings. Since the name mangling formats allow for
3650 an inifinite level of recursion it is possible to create strings whose
3651 decoding will exhaust the amount of stack space available on the host
3652 machine, triggering a memory fault. The limit tries to prevent this
3653 from happening by restricting recursion to 2048 levels of nesting.
3655 The default is for this limit to be enabled, but disabling it may be
3656 necessary in order to demangle truly complicated names. Note however
3657 that if the recursion limit is disabled then stack exhaustion is
3658 possible and any bug reports about such an event will be rejected.
3660 The @option{-r} option is a synonym for the
3661 @option{--no-recurse-limit} option. The @option{-R} option is a
3662 synonym for the @option{--recurse-limit} option.
3664 @item -s @var{format}
3665 @itemx --format=@var{format}
3666 @command{c++filt} can decode various methods of mangling, used by
3667 different compilers. The argument to this option selects which
3672 Automatic selection based on executable (the default method)
3674 the one used by the @sc{gnu} C++ compiler (g++)
3676 the one used by the Lucid compiler (lcc)
3678 the one specified by the C++ Annotated Reference Manual
3680 the one used by the HP compiler (aCC)
3682 the one used by the EDG compiler
3684 the one used by the @sc{gnu} C++ compiler (g++) with the V3 ABI.
3686 the one used by the @sc{gnu} Java compiler (gcj)
3688 the one used by the @sc{gnu} Ada compiler (GNAT).
3692 Print a summary of the options to @command{c++filt} and exit.
3695 Print the version number of @command{c++filt} and exit.
3701 @c man begin SEEALSO cxxfilt
3702 the Info entries for @file{binutils}.
3707 @emph{Warning:} @command{c++filt} is a new utility, and the details of its
3708 user interface are subject to change in future releases. In particular,
3709 a command-line option may be required in the future to decode a name
3710 passed as an argument on the command line; in other words,
3713 c++filt @var{symbol}
3717 may in a future release become
3720 c++filt @var{option} @var{symbol}
3728 @cindex address to file name and line number
3730 @c man title addr2line convert addresses into file names and line numbers
3733 @c man begin SYNOPSIS addr2line
3734 addr2line [@option{-a}|@option{--addresses}]
3735 [@option{-b} @var{bfdname}|@option{--target=}@var{bfdname}]
3736 [@option{-C}|@option{--demangle}[=@var{style}]]
3737 [@option{-r}|@option{--no-recurse-limit}]
3738 [@option{-R}|@option{--recurse-limit}]
3739 [@option{-e} @var{filename}|@option{--exe=}@var{filename}]
3740 [@option{-f}|@option{--functions}] [@option{-s}|@option{--basename}]
3741 [@option{-i}|@option{--inlines}]
3742 [@option{-p}|@option{--pretty-print}]
3743 [@option{-j}|@option{--section=}@var{name}]
3744 [@option{-H}|@option{--help}] [@option{-V}|@option{--version}]
3749 @c man begin DESCRIPTION addr2line
3751 @command{addr2line} translates addresses into file names and line numbers.
3752 Given an address in an executable or an offset in a section of a relocatable
3753 object, it uses the debugging information to figure out which file name and
3754 line number are associated with it.
3756 The executable or relocatable object to use is specified with the @option{-e}
3757 option. The default is the file @file{a.out}. The section in the relocatable
3758 object to use is specified with the @option{-j} option.
3760 @command{addr2line} has two modes of operation.
3762 In the first, hexadecimal addresses are specified on the command line,
3763 and @command{addr2line} displays the file name and line number for each
3766 In the second, @command{addr2line} reads hexadecimal addresses from
3767 standard input, and prints the file name and line number for each
3768 address on standard output. In this mode, @command{addr2line} may be used
3769 in a pipe to convert dynamically chosen addresses.
3771 The format of the output is @samp{FILENAME:LINENO}. By default
3772 each input address generates one line of output.
3774 Two options can generate additional lines before each
3775 @samp{FILENAME:LINENO} line (in that order).
3777 If the @option{-a} option is used then a line with the input address
3780 If the @option{-f} option is used, then a line with the
3781 @samp{FUNCTIONNAME} is displayed. This is the name of the function
3782 containing the address.
3784 One option can generate additional lines after the
3785 @samp{FILENAME:LINENO} line.
3787 If the @option{-i} option is used and the code at the given address is
3788 present there because of inlining by the compiler then additional
3789 lines are displayed afterwards. One or two extra lines (if the
3790 @option{-f} option is used) are displayed for each inlined function.
3792 Alternatively if the @option{-p} option is used then each input
3793 address generates a single, long, output line containing the address,
3794 the function name, the file name and the line number. If the
3795 @option{-i} option has also been used then any inlined functions will
3796 be displayed in the same manner, but on separate lines, and prefixed
3797 by the text @samp{(inlined by)}.
3799 If the file name or function name can not be determined,
3800 @command{addr2line} will print two question marks in their place. If the
3801 line number can not be determined, @command{addr2line} will print 0.
3805 @c man begin OPTIONS addr2line
3807 The long and short forms of options, shown here as alternatives, are
3813 Display the address before the function name, file and line number
3814 information. The address is printed with a @samp{0x} prefix to easily
3817 @item -b @var{bfdname}
3818 @itemx --target=@var{bfdname}
3819 @cindex object code format
3820 Specify that the object-code format for the object files is
3824 @itemx --demangle[=@var{style}]
3825 @cindex demangling in objdump
3826 Decode (@dfn{demangle}) low-level symbol names into user-level names.
3827 Besides removing any initial underscore prepended by the system, this
3828 makes C++ function names readable. Different compilers have different
3829 mangling styles. The optional demangling style argument can be used to
3830 choose an appropriate demangling style for your compiler. @xref{c++filt},
3831 for more information on demangling.
3833 @item -e @var{filename}
3834 @itemx --exe=@var{filename}
3835 Specify the name of the executable for which addresses should be
3836 translated. The default file is @file{a.out}.
3840 Display function names as well as file and line number information.
3844 Display only the base of each file name.
3848 If the address belongs to a function that was inlined, the source
3849 information for all enclosing scopes back to the first non-inlined
3850 function will also be printed. For example, if @code{main} inlines
3851 @code{callee1} which inlines @code{callee2}, and address is from
3852 @code{callee2}, the source information for @code{callee1} and @code{main}
3853 will also be printed.
3857 Read offsets relative to the specified section instead of absolute addresses.
3860 @itemx --pretty-print
3861 Make the output more human friendly: each location are printed on one line.
3862 If option @option{-i} is specified, lines for all enclosing scopes are
3863 prefixed with @samp{(inlined by)}.
3867 @itemx --recurse-limit
3868 @itemx --no-recurse-limit
3869 @itemx --recursion-limit
3870 @itemx --no-recursion-limit
3871 Enables or disables a limit on the amount of recursion performed
3872 whilst demangling strings. Since the name mangling formats allow for
3873 an inifinite level of recursion it is possible to create strings whose
3874 decoding will exhaust the amount of stack space available on the host
3875 machine, triggering a memory fault. The limit tries to prevent this
3876 from happening by restricting recursion to 2048 levels of nesting.
3878 The default is for this limit to be enabled, but disabling it may be
3879 necessary in order to demangle truly complicated names. Note however
3880 that if the recursion limit is disabled then stack exhaustion is
3881 possible and any bug reports about such an event will be rejected.
3883 The @option{-r} option is a synonym for the
3884 @option{--no-recurse-limit} option. The @option{-R} option is a
3885 synonym for the @option{--recurse-limit} option.
3887 Note this option is only effective if the @option{-C} or
3888 @option{--demangle} option has been enabled.
3895 @c man begin SEEALSO addr2line
3896 Info entries for @file{binutils}.
3903 @command{windmc} may be used to generator Windows message resources.
3906 @emph{Warning:} @command{windmc} is not always built as part of the binary
3907 utilities, since it is only useful for Windows targets.
3910 @c man title windmc generates Windows message resources
3913 @c man begin SYNOPSIS windmc
3914 windmc [options] input-file
3918 @c man begin DESCRIPTION windmc
3920 @command{windmc} reads message definitions from an input file (.mc) and
3921 translate them into a set of output files. The output files may be of
3926 A C header file containing the message definitions.
3929 A resource file compilable by the @command{windres} tool.
3932 One or more binary files containing the resource data for a specific
3936 A C include file that maps message id's to their symbolic name.
3939 The exact description of these different formats is available in
3940 documentation from Microsoft.
3942 When @command{windmc} converts from the @code{mc} format to the @code{bin}
3943 format, @code{rc}, @code{h}, and optional @code{dbg} it is acting like the
3944 Windows Message Compiler.
3948 @c man begin OPTIONS windmc
3953 Specifies that the input file specified is ASCII. This is the default
3958 Specifies that messages in the output @code{bin} files should be in ASCII
3963 Specifies that @code{bin} filenames should have to be prefixed by the
3964 basename of the source file.
3968 Sets the customer bit in all message id's.
3970 @item -C @var{codepage}
3971 @itemx --codepage_in @var{codepage}
3972 Sets the default codepage to be used to convert input file to UTF16. The
3973 default is ocdepage 1252.
3976 @itemx --decimal_values
3977 Outputs the constants in the header file in decimal. Default is using
3981 @itemx --extension @var{ext}
3982 The extension for the header file. The default is .h extension.
3984 @item -F @var{target}
3985 @itemx --target @var{target}
3986 Specify the BFD format to use for a bin file as output. This
3987 is a BFD target name; you can use the @option{--help} option to see a list
3988 of supported targets. Normally @command{windmc} will use the default
3989 format, which is the first one listed by the @option{--help} option.
3991 @ref{Target Selection}.
3995 @itemx --headerdir @var{path}
3996 The target directory of the generated header file. The default is the
4001 Displays a list of command-line options and then exits.
4003 @item -m @var{characters}
4004 @itemx --maxlength @var{characters}
4005 Instructs @command{windmc} to generate a warning if the length
4006 of any message exceeds the number specified.
4009 @itemx --nullterminate
4010 Terminate message text in @code{bin} files by zero. By default they are
4011 terminated by CR/LF.
4014 @itemx --hresult_use
4015 Not yet implemented. Instructs @code{windmc} to generate an OLE2 header
4016 file, using HRESULT definitions. Status codes are used if the flag is not
4019 @item -O @var{codepage}
4020 @itemx --codepage_out @var{codepage}
4021 Sets the default codepage to be used to output text files. The default
4025 @itemx --rcdir @var{path}
4026 The target directory for the generated @code{rc} script and the generated
4027 @code{bin} files that the resource compiler script includes. The default
4028 is the current directory.
4032 Specifies that the input file is UTF16.
4035 @itemx --unicode_out
4036 Specifies that messages in the output @code{bin} file should be in UTF16
4037 format. This is the default behaviour.
4041 Enable verbose mode.
4045 Prints the version number for @command{windmc}.
4048 @itemx --xdgb @var{path}
4049 The path of the @code{dbg} C include file that maps message id's to the
4050 symbolic name. No such file is generated without specifying the switch.
4056 @c man begin SEEALSO windmc
4057 the Info entries for @file{binutils}.
4064 @command{windres} may be used to manipulate Windows resources.
4067 @emph{Warning:} @command{windres} is not always built as part of the binary
4068 utilities, since it is only useful for Windows targets.
4071 @c man title windres manipulate Windows resources
4074 @c man begin SYNOPSIS windres
4075 windres [options] [input-file] [output-file]
4079 @c man begin DESCRIPTION windres
4081 @command{windres} reads resources from an input file and copies them into
4082 an output file. Either file may be in one of three formats:
4086 A text format read by the Resource Compiler.
4089 A binary format generated by the Resource Compiler.
4092 A COFF object or executable.
4095 The exact description of these different formats is available in
4096 documentation from Microsoft.
4098 When @command{windres} converts from the @code{rc} format to the @code{res}
4099 format, it is acting like the Windows Resource Compiler. When
4100 @command{windres} converts from the @code{res} format to the @code{coff}
4101 format, it is acting like the Windows @code{CVTRES} program.
4103 When @command{windres} generates an @code{rc} file, the output is similar
4104 but not identical to the format expected for the input. When an input
4105 @code{rc} file refers to an external filename, an output @code{rc} file
4106 will instead include the file contents.
4108 If the input or output format is not specified, @command{windres} will
4109 guess based on the file name, or, for the input file, the file contents.
4110 A file with an extension of @file{.rc} will be treated as an @code{rc}
4111 file, a file with an extension of @file{.res} will be treated as a
4112 @code{res} file, and a file with an extension of @file{.o} or
4113 @file{.exe} will be treated as a @code{coff} file.
4115 If no output file is specified, @command{windres} will print the resources
4116 in @code{rc} format to standard output.
4118 The normal use is for you to write an @code{rc} file, use @command{windres}
4119 to convert it to a COFF object file, and then link the COFF file into
4120 your application. This will make the resources described in the
4121 @code{rc} file available to Windows.
4125 @c man begin OPTIONS windres
4128 @item -i @var{filename}
4129 @itemx --input @var{filename}
4130 The name of the input file. If this option is not used, then
4131 @command{windres} will use the first non-option argument as the input file
4132 name. If there are no non-option arguments, then @command{windres} will
4133 read from standard input. @command{windres} can not read a COFF file from
4136 @item -o @var{filename}
4137 @itemx --output @var{filename}
4138 The name of the output file. If this option is not used, then
4139 @command{windres} will use the first non-option argument, after any used
4140 for the input file name, as the output file name. If there is no
4141 non-option argument, then @command{windres} will write to standard output.
4142 @command{windres} can not write a COFF file to standard output. Note,
4143 for compatibility with @command{rc} the option @option{-fo} is also
4144 accepted, but its use is not recommended.
4146 @item -J @var{format}
4147 @itemx --input-format @var{format}
4148 The input format to read. @var{format} may be @samp{res}, @samp{rc}, or
4149 @samp{coff}. If no input format is specified, @command{windres} will
4150 guess, as described above.
4152 @item -O @var{format}
4153 @itemx --output-format @var{format}
4154 The output format to generate. @var{format} may be @samp{res},
4155 @samp{rc}, or @samp{coff}. If no output format is specified,
4156 @command{windres} will guess, as described above.
4158 @item -F @var{target}
4159 @itemx --target @var{target}
4160 Specify the BFD format to use for a COFF file as input or output. This
4161 is a BFD target name; you can use the @option{--help} option to see a list
4162 of supported targets. Normally @command{windres} will use the default
4163 format, which is the first one listed by the @option{--help} option.
4165 @ref{Target Selection}.
4168 @item --preprocessor @var{program}
4169 When @command{windres} reads an @code{rc} file, it runs it through the C
4170 preprocessor first. This option may be used to specify the preprocessor
4171 to use, including any leading arguments. The default preprocessor
4172 argument is @code{gcc -E -xc-header -DRC_INVOKED}.
4174 @item --preprocessor-arg @var{option}
4175 When @command{windres} reads an @code{rc} file, it runs it through
4176 the C preprocessor first. This option may be used to specify additional
4177 text to be passed to preprocessor on its command line.
4178 This option can be used multiple times to add multiple options to the
4179 preprocessor command line.
4181 @item -I @var{directory}
4182 @itemx --include-dir @var{directory}
4183 Specify an include directory to use when reading an @code{rc} file.
4184 @command{windres} will pass this to the preprocessor as an @option{-I}
4185 option. @command{windres} will also search this directory when looking for
4186 files named in the @code{rc} file. If the argument passed to this command
4187 matches any of the supported @var{formats} (as described in the @option{-J}
4188 option), it will issue a deprecation warning, and behave just like the
4189 @option{-J} option. New programs should not use this behaviour. If a
4190 directory happens to match a @var{format}, simple prefix it with @samp{./}
4191 to disable the backward compatibility.
4193 @item -D @var{target}
4194 @itemx --define @var{sym}[=@var{val}]
4195 Specify a @option{-D} option to pass to the preprocessor when reading an
4198 @item -U @var{target}
4199 @itemx --undefine @var{sym}
4200 Specify a @option{-U} option to pass to the preprocessor when reading an
4204 Ignored for compatibility with rc.
4207 Enable verbose mode. This tells you what the preprocessor is if you
4211 @item --codepage @var{val}
4212 Specify the default codepage to use when reading an @code{rc} file.
4213 @var{val} should be a hexadecimal prefixed by @samp{0x} or decimal
4214 codepage code. The valid range is from zero up to 0xffff, but the
4215 validity of the codepage is host and configuration dependent.
4218 @item --language @var{val}
4219 Specify the default language to use when reading an @code{rc} file.
4220 @var{val} should be a hexadecimal language code. The low eight bits are
4221 the language, and the high eight bits are the sublanguage.
4223 @item --use-temp-file
4224 Use a temporary file to instead of using popen to read the output of
4225 the preprocessor. Use this option if the popen implementation is buggy
4226 on the host (eg., certain non-English language versions of Windows 95 and
4227 Windows 98 are known to have buggy popen where the output will instead
4230 @item --no-use-temp-file
4231 Use popen, not a temporary file, to read the output of the preprocessor.
4232 This is the default behaviour.
4236 Prints a usage summary.
4240 Prints the version number for @command{windres}.
4243 If @command{windres} is compiled with @code{YYDEBUG} defined as @code{1},
4244 this will turn on parser debugging.
4250 @c man begin SEEALSO windres
4251 the Info entries for @file{binutils}.
4260 @command{dlltool} is used to create the files needed to create dynamic
4261 link libraries (DLLs) on systems which understand PE format image
4262 files such as Windows. A DLL contains an export table which contains
4263 information that the runtime loader needs to resolve references from a
4264 referencing program.
4266 The export table is generated by this program by reading in a
4267 @file{.def} file or scanning the @file{.a} and @file{.o} files which
4268 will be in the DLL. A @file{.o} file can contain information in
4269 special @samp{.drectve} sections with export information.
4272 @emph{Note:} @command{dlltool} is not always built as part of the
4273 binary utilities, since it is only useful for those targets which
4277 @c man title dlltool create files needed to build and use DLLs
4280 @c man begin SYNOPSIS dlltool
4281 dlltool [@option{-d}|@option{--input-def} @var{def-file-name}]
4282 [@option{-b}|@option{--base-file} @var{base-file-name}]
4283 [@option{-e}|@option{--output-exp} @var{exports-file-name}]
4284 [@option{-z}|@option{--output-def} @var{def-file-name}]
4285 [@option{-l}|@option{--output-lib} @var{library-file-name}]
4286 [@option{-y}|@option{--output-delaylib} @var{library-file-name}]
4287 [@option{--export-all-symbols}] [@option{--no-export-all-symbols}]
4288 [@option{--exclude-symbols} @var{list}]
4289 [@option{--no-default-excludes}]
4290 [@option{-S}|@option{--as} @var{path-to-assembler}] [@option{-f}|@option{--as-flags} @var{options}]
4291 [@option{-D}|@option{--dllname} @var{name}] [@option{-m}|@option{--machine} @var{machine}]
4292 [@option{-a}|@option{--add-indirect}]
4293 [@option{-U}|@option{--add-underscore}] [@option{--add-stdcall-underscore}]
4294 [@option{-k}|@option{--kill-at}] [@option{-A}|@option{--add-stdcall-alias}]
4295 [@option{-p}|@option{--ext-prefix-alias} @var{prefix}]
4296 [@option{-x}|@option{--no-idata4}] [@option{-c}|@option{--no-idata5}]
4297 [@option{--use-nul-prefixed-import-tables}]
4298 [@option{-I}|@option{--identify} @var{library-file-name}] [@option{--identify-strict}]
4299 [@option{-i}|@option{--interwork}]
4300 [@option{-n}|@option{--nodelete}] [@option{-t}|@option{--temp-prefix} @var{prefix}]
4301 [@option{-v}|@option{--verbose}]
4302 [@option{-h}|@option{--help}] [@option{-V}|@option{--version}]
4303 [@option{--no-leading-underscore}] [@option{--leading-underscore}]
4304 [object-file @dots{}]
4308 @c man begin DESCRIPTION dlltool
4310 @command{dlltool} reads its inputs, which can come from the @option{-d} and
4311 @option{-b} options as well as object files specified on the command
4312 line. It then processes these inputs and if the @option{-e} option has
4313 been specified it creates a exports file. If the @option{-l} option
4314 has been specified it creates a library file and if the @option{-z} option
4315 has been specified it creates a def file. Any or all of the @option{-e},
4316 @option{-l} and @option{-z} options can be present in one invocation of
4319 When creating a DLL, along with the source for the DLL, it is necessary
4320 to have three other files. @command{dlltool} can help with the creation of
4323 The first file is a @file{.def} file which specifies which functions are
4324 exported from the DLL, which functions the DLL imports, and so on. This
4325 is a text file and can be created by hand, or @command{dlltool} can be used
4326 to create it using the @option{-z} option. In this case @command{dlltool}
4327 will scan the object files specified on its command line looking for
4328 those functions which have been specially marked as being exported and
4329 put entries for them in the @file{.def} file it creates.
4331 In order to mark a function as being exported from a DLL, it needs to
4332 have an @option{-export:<name_of_function>} entry in the @samp{.drectve}
4333 section of the object file. This can be done in C by using the
4337 asm (".section .drectve");
4338 asm (".ascii \"-export:my_func\"");
4340 int my_func (void) @{ @dots{} @}
4343 The second file needed for DLL creation is an exports file. This file
4344 is linked with the object files that make up the body of the DLL and it
4345 handles the interface between the DLL and the outside world. This is a
4346 binary file and it can be created by giving the @option{-e} option to
4347 @command{dlltool} when it is creating or reading in a @file{.def} file.
4349 The third file needed for DLL creation is the library file that programs
4350 will link with in order to access the functions in the DLL (an `import
4351 library'). This file can be created by giving the @option{-l} option to
4352 dlltool when it is creating or reading in a @file{.def} file.
4354 If the @option{-y} option is specified, dlltool generates a delay-import
4355 library that can be used instead of the normal import library to allow
4356 a program to link to the dll only as soon as an imported function is
4357 called for the first time. The resulting executable will need to be
4358 linked to the static delayimp library containing __delayLoadHelper2(),
4359 which in turn will import LoadLibraryA and GetProcAddress from kernel32.
4361 @command{dlltool} builds the library file by hand, but it builds the
4362 exports file by creating temporary files containing assembler statements
4363 and then assembling these. The @option{-S} command-line option can be
4364 used to specify the path to the assembler that dlltool will use,
4365 and the @option{-f} option can be used to pass specific flags to that
4366 assembler. The @option{-n} can be used to prevent dlltool from deleting
4367 these temporary assembler files when it is done, and if @option{-n} is
4368 specified twice then this will prevent dlltool from deleting the
4369 temporary object files it used to build the library.
4371 Here is an example of creating a DLL from a source file @samp{dll.c} and
4372 also creating a program (from an object file called @samp{program.o})
4377 dlltool -e exports.o -l dll.lib dll.o
4378 gcc dll.o exports.o -o dll.dll
4379 gcc program.o dll.lib -o program
4383 @command{dlltool} may also be used to query an existing import library
4384 to determine the name of the DLL to which it is associated. See the
4385 description of the @option{-I} or @option{--identify} option.
4389 @c man begin OPTIONS dlltool
4391 The command-line options have the following meanings:
4395 @item -d @var{filename}
4396 @itemx --input-def @var{filename}
4397 @cindex input .def file
4398 Specifies the name of a @file{.def} file to be read in and processed.
4400 @item -b @var{filename}
4401 @itemx --base-file @var{filename}
4403 Specifies the name of a base file to be read in and processed. The
4404 contents of this file will be added to the relocation section in the
4405 exports file generated by dlltool.
4407 @item -e @var{filename}
4408 @itemx --output-exp @var{filename}
4409 Specifies the name of the export file to be created by dlltool.
4411 @item -z @var{filename}
4412 @itemx --output-def @var{filename}
4413 Specifies the name of the @file{.def} file to be created by dlltool.
4415 @item -l @var{filename}
4416 @itemx --output-lib @var{filename}
4417 Specifies the name of the library file to be created by dlltool.
4419 @item -y @var{filename}
4420 @itemx --output-delaylib @var{filename}
4421 Specifies the name of the delay-import library file to be created by dlltool.
4423 @item --export-all-symbols
4424 Treat all global and weak defined symbols found in the input object
4425 files as symbols to be exported. There is a small list of symbols which
4426 are not exported by default; see the @option{--no-default-excludes}
4427 option. You may add to the list of symbols to not export by using the
4428 @option{--exclude-symbols} option.
4430 @item --no-export-all-symbols
4431 Only export symbols explicitly listed in an input @file{.def} file or in
4432 @samp{.drectve} sections in the input object files. This is the default
4433 behaviour. The @samp{.drectve} sections are created by @samp{dllexport}
4434 attributes in the source code.
4436 @item --exclude-symbols @var{list}
4437 Do not export the symbols in @var{list}. This is a list of symbol names
4438 separated by comma or colon characters. The symbol names should not
4439 contain a leading underscore. This is only meaningful when
4440 @option{--export-all-symbols} is used.
4442 @item --no-default-excludes
4443 When @option{--export-all-symbols} is used, it will by default avoid
4444 exporting certain special symbols. The current list of symbols to avoid
4445 exporting is @samp{DllMain@@12}, @samp{DllEntryPoint@@0},
4446 @samp{impure_ptr}. You may use the @option{--no-default-excludes} option
4447 to go ahead and export these special symbols. This is only meaningful
4448 when @option{--export-all-symbols} is used.
4451 @itemx --as @var{path}
4452 Specifies the path, including the filename, of the assembler to be used
4453 to create the exports file.
4455 @item -f @var{options}
4456 @itemx --as-flags @var{options}
4457 Specifies any specific command-line options to be passed to the
4458 assembler when building the exports file. This option will work even if
4459 the @option{-S} option is not used. This option only takes one argument,
4460 and if it occurs more than once on the command line, then later
4461 occurrences will override earlier occurrences. So if it is necessary to
4462 pass multiple options to the assembler they should be enclosed in
4466 @itemx --dll-name @var{name}
4467 Specifies the name to be stored in the @file{.def} file as the name of
4468 the DLL when the @option{-e} option is used. If this option is not
4469 present, then the filename given to the @option{-e} option will be
4470 used as the name of the DLL.
4472 @item -m @var{machine}
4473 @itemx -machine @var{machine}
4474 Specifies the type of machine for which the library file should be
4475 built. @command{dlltool} has a built in default type, depending upon how
4476 it was created, but this option can be used to override that. This is
4477 normally only useful when creating DLLs for an ARM processor, when the
4478 contents of the DLL are actually encode using Thumb instructions.
4481 @itemx --add-indirect
4482 Specifies that when @command{dlltool} is creating the exports file it
4483 should add a section which allows the exported functions to be
4484 referenced without using the import library. Whatever the hell that
4488 @itemx --add-underscore
4489 Specifies that when @command{dlltool} is creating the exports file it
4490 should prepend an underscore to the names of @emph{all} exported symbols.
4492 @item --no-leading-underscore
4493 @item --leading-underscore
4494 Specifies whether standard symbol should be forced to be prefixed, or
4497 @item --add-stdcall-underscore
4498 Specifies that when @command{dlltool} is creating the exports file it
4499 should prepend an underscore to the names of exported @emph{stdcall}
4500 functions. Variable names and non-stdcall function names are not modified.
4501 This option is useful when creating GNU-compatible import libs for third
4502 party DLLs that were built with MS-Windows tools.
4506 Specifies that @samp{@@<number>} suffixes should be omitted from the names
4507 of stdcall functions that will be imported from the DLL. This is
4508 useful when creating an import library for a DLL which exports stdcall
4509 functions but without the usual @samp{@@<number>} symbol name suffix.
4511 This does not change the naming of symbols provided by the import library
4512 to programs linked against it, but only the entries in the import table
4513 (ie the .idata section).
4516 @itemx --add-stdcall-alias
4517 Specifies that when @command{dlltool} is creating the exports file it
4518 should add aliases for stdcall symbols without @samp{@@ <number>}
4519 in addition to the symbols with @samp{@@ <number>}.
4522 @itemx --ext-prefix-alias @var{prefix}
4523 Causes @command{dlltool} to create external aliases for all DLL
4524 imports with the specified prefix. The aliases are created for both
4525 external and import symbols with no leading underscore.
4529 Specifies that when @command{dlltool} is creating the exports and library
4530 files it should omit the @code{.idata4} section. This is for compatibility
4531 with certain operating systems.
4533 @item --use-nul-prefixed-import-tables
4534 Specifies that when @command{dlltool} is creating the exports and library
4535 files it should prefix the @code{.idata4} and @code{.idata5} by zero an
4536 element. This emulates old gnu import library generation of
4537 @code{dlltool}. By default this option is turned off.
4541 Specifies that when @command{dlltool} is creating the exports and library
4542 files it should omit the @code{.idata5} section. This is for compatibility
4543 with certain operating systems.
4545 @item -I @var{filename}
4546 @itemx --identify @var{filename}
4547 Specifies that @command{dlltool} should inspect the import library
4548 indicated by @var{filename} and report, on @code{stdout}, the name(s)
4549 of the associated DLL(s). This can be performed in addition to any
4550 other operations indicated by the other options and arguments.
4551 @command{dlltool} fails if the import library does not exist or is not
4552 actually an import library. See also @option{--identify-strict}.
4554 @item --identify-strict
4555 Modifies the behavior of the @option{--identify} option, such
4556 that an error is reported if @var{filename} is associated with
4561 Specifies that @command{dlltool} should mark the objects in the library
4562 file and exports file that it produces as supporting interworking
4563 between ARM and Thumb code.
4567 Makes @command{dlltool} preserve the temporary assembler files it used to
4568 create the exports file. If this option is repeated then dlltool will
4569 also preserve the temporary object files it uses to create the library
4572 @item -t @var{prefix}
4573 @itemx --temp-prefix @var{prefix}
4574 Makes @command{dlltool} use @var{prefix} when constructing the names of
4575 temporary assembler and object files. By default, the temp file prefix
4576 is generated from the pid.
4580 Make dlltool describe what it is doing.
4584 Displays a list of command-line options and then exits.
4588 Displays dlltool's version number and then exits.
4595 * def file format:: The format of the dlltool @file{.def} file
4598 @node def file format
4599 @section The format of the @command{dlltool} @file{.def} file
4601 A @file{.def} file contains any number of the following commands:
4605 @item @code{NAME} @var{name} @code{[ ,} @var{base} @code{]}
4606 The result is going to be named @var{name}@code{.exe}.
4608 @item @code{LIBRARY} @var{name} @code{[ ,} @var{base} @code{]}
4609 The result is going to be named @var{name}@code{.dll}.
4610 Note: If you want to use LIBRARY as name then you need to quote. Otherwise
4611 this will fail due a necessary hack for libtool (see PR binutils/13710 for more
4614 @item @code{EXPORTS ( ( (} @var{name1} @code{[ = } @var{name2} @code{] ) | ( } @var{name1} @code{=} @var{module-name} @code{.} @var{external-name} @code{) ) [ == } @var{its_name} @code{]}
4615 @item @code{[} @var{integer} @code{] [ NONAME ] [ CONSTANT ] [ DATA ] [ PRIVATE ] ) *}
4616 Declares @var{name1} as an exported symbol from the DLL, with optional
4617 ordinal number @var{integer}, or declares @var{name1} as an alias
4618 (forward) of the function @var{external-name} in the DLL.
4619 If @var{its_name} is specified, this name is used as string in export table.
4621 Note: The @code{EXPORTS} has to be the last command in .def file, as keywords
4622 are treated - beside @code{LIBRARY} - as simple name-identifiers.
4623 If you want to use LIBRARY as name then you need to quote it.
4625 @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{]} *}
4626 Declares that @var{external-name} or the exported function whose
4627 ordinal number is @var{integer} is to be imported from the file
4628 @var{module-name}. If @var{internal-name} is specified then this is
4629 the name that the imported function will be referred to in the body of
4631 If @var{its_name} is specified, this name is used as string in import table.
4632 Note: The @code{IMPORTS} has to be the last command in .def file, as keywords
4633 are treated - beside @code{LIBRARY} - as simple name-identifiers.
4634 If you want to use LIBRARY as name then you need to quote it.
4636 @item @code{DESCRIPTION} @var{string}
4637 Puts @var{string} into the output @file{.exp} file in the
4638 @code{.rdata} section.
4640 @item @code{STACKSIZE} @var{number-reserve} @code{[, } @var{number-commit} @code{]}
4641 @item @code{HEAPSIZE} @var{number-reserve} @code{[, } @var{number-commit} @code{]}
4642 Generates @code{--stack} or @code{--heap}
4643 @var{number-reserve},@var{number-commit} in the output @code{.drectve}
4644 section. The linker will see this and act upon it.
4646 @item @code{CODE} @var{attr} @code{+}
4647 @item @code{DATA} @var{attr} @code{+}
4648 @item @code{SECTIONS (} @var{section-name} @var{attr}@code{ + ) *}
4649 Generates @code{--attr} @var{section-name} @var{attr} in the output
4650 @code{.drectve} section, where @var{attr} is one of @code{READ},
4651 @code{WRITE}, @code{EXECUTE} or @code{SHARED}. The linker will see
4652 this and act upon it.
4657 @c man begin SEEALSO dlltool
4658 The Info pages for @file{binutils}.
4665 @cindex ELF file information
4668 @c man title readelf display information about ELF files
4671 @c man begin SYNOPSIS readelf
4672 readelf [@option{-a}|@option{--all}]
4673 [@option{-h}|@option{--file-header}]
4674 [@option{-l}|@option{--program-headers}|@option{--segments}]
4675 [@option{-S}|@option{--section-headers}|@option{--sections}]
4676 [@option{-g}|@option{--section-groups}]
4677 [@option{-t}|@option{--section-details}]
4678 [@option{-e}|@option{--headers}]
4679 [@option{-s}|@option{--syms}|@option{--symbols}]
4680 [@option{--dyn-syms}]
4681 [@option{-n}|@option{--notes}]
4682 [@option{-r}|@option{--relocs}]
4683 [@option{-u}|@option{--unwind}]
4684 [@option{-d}|@option{--dynamic}]
4685 [@option{-V}|@option{--version-info}]
4686 [@option{-A}|@option{--arch-specific}]
4687 [@option{-D}|@option{--use-dynamic}]
4688 [@option{-x} <number or name>|@option{--hex-dump=}<number or name>]
4689 [@option{-p} <number or name>|@option{--string-dump=}<number or name>]
4690 [@option{-R} <number or name>|@option{--relocated-dump=}<number or name>]
4691 [@option{-z}|@option{--decompress}]
4692 [@option{-c}|@option{--archive-index}]
4693 [@option{-w[lLiaprmfFsoRtUuTgAckK]}|
4694 @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]]
4695 [@option{--dwarf-depth=@var{n}}]
4696 [@option{--dwarf-start=@var{n}}]
4697 [@option{--ctf=}@var{section}]
4698 [@option{--ctf-parent=}@var{section}]
4699 [@option{--ctf-symbols=}@var{section}]
4700 [@option{--ctf-strings=}@var{section}]
4701 [@option{-I}|@option{--histogram}]
4702 [@option{-v}|@option{--version}]
4703 [@option{-W}|@option{--wide}]
4704 [@option{-H}|@option{--help}]
4705 @var{elffile}@dots{}
4709 @c man begin DESCRIPTION readelf
4711 @command{readelf} displays information about one or more ELF format object
4712 files. The options control what particular information to display.
4714 @var{elffile}@dots{} are the object files to be examined. 32-bit and
4715 64-bit ELF files are supported, as are archives containing ELF files.
4717 This program performs a similar function to @command{objdump} but it
4718 goes into more detail and it exists independently of the @sc{bfd}
4719 library, so if there is a bug in @sc{bfd} then readelf will not be
4724 @c man begin OPTIONS readelf
4726 The long and short forms of options, shown here as alternatives, are
4727 equivalent. At least one option besides @samp{-v} or @samp{-H} must be
4733 Equivalent to specifying @option{--file-header},
4734 @option{--program-headers}, @option{--sections}, @option{--symbols},
4735 @option{--relocs}, @option{--dynamic}, @option{--notes},
4736 @option{--version-info}, @option{--arch-specific}, @option{--unwind},
4737 @option{--section-groups} and @option{--histogram}.
4739 Note - this option does not enable @option{--use-dynamic} itself, so
4740 if that option is not present on the command line then dynamic symbols
4741 and dynamic relocs will not be displayed.
4744 @itemx --file-header
4745 @cindex ELF file header information
4746 Displays the information contained in the ELF header at the start of the
4750 @itemx --program-headers
4752 @cindex ELF program header information
4753 @cindex ELF segment information
4754 Displays the information contained in the file's segment headers, if it
4759 @itemx --section-headers
4760 @cindex ELF section information
4761 Displays the information contained in the file's section headers, if it
4765 @itemx --section-groups
4766 @cindex ELF section group information
4767 Displays the information contained in the file's section groups, if it
4771 @itemx --section-details
4772 @cindex ELF section information
4773 Displays the detailed section information. Implies @option{-S}.
4778 @cindex ELF symbol table information
4779 Displays the entries in symbol table section of the file, if it has one.
4780 If a symbol has version information associated with it then this is
4781 displayed as well. The version string is displayed as a suffix to the
4782 symbol name, preceeded by an @@ character. For example
4783 @samp{foo@@VER_1}. If the version is the default version to be used
4784 when resolving unversioned references to the symbol then it is
4785 displayed as a suffix preceeded by two @@ characters. For example
4786 @samp{foo@@@@VER_2}.
4789 @cindex ELF dynamic symbol table information
4790 Displays the entries in dynamic symbol table section of the file, if it
4791 has one. The output format is the same as the format used by the
4792 @option{--syms} option.
4796 Display all the headers in the file. Equivalent to @option{-h -l -S}.
4801 Displays the contents of the NOTE segments and/or sections, if any.
4805 @cindex ELF reloc information
4806 Displays the contents of the file's relocation section, if it has one.
4810 @cindex unwind information
4811 Displays the contents of the file's unwind section, if it has one. Only
4812 the unwind sections for IA64 ELF files, as well as ARM unwind tables
4813 (@code{.ARM.exidx} / @code{.ARM.extab}) are currently supported. If
4814 support is not yet implemented for your architecture you could try
4815 dumping the contents of the @var{.eh_frames} section using the
4816 @option{--debug-dump=frames} or @option{--debug-dump=frames-interp}
4821 @cindex ELF dynamic section information
4822 Displays the contents of the file's dynamic section, if it has one.
4825 @itemx --version-info
4826 @cindex ELF version sections information
4827 Displays the contents of the version sections in the file, it they
4831 @itemx --arch-specific
4832 Displays architecture-specific information in the file, if there
4836 @itemx --use-dynamic
4837 When displaying symbols, this option makes @command{readelf} use the
4838 symbol hash tables in the file's dynamic section, rather than the
4839 symbol table sections.
4841 When displaying relocations, this option makes @command{readelf}
4842 display the dynamic relocations rather than the static relocations.
4844 @item -x <number or name>
4845 @itemx --hex-dump=<number or name>
4846 Displays the contents of the indicated section as a hexadecimal bytes.
4847 A number identifies a particular section by index in the section table;
4848 any other string identifies all sections with that name in the object file.
4850 @item -R <number or name>
4851 @itemx --relocated-dump=<number or name>
4852 Displays the contents of the indicated section as a hexadecimal
4853 bytes. A number identifies a particular section by index in the
4854 section table; any other string identifies all sections with that name
4855 in the object file. The contents of the section will be relocated
4856 before they are displayed.
4858 @item -p <number or name>
4859 @itemx --string-dump=<number or name>
4860 Displays the contents of the indicated section as printable strings.
4861 A number identifies a particular section by index in the section table;
4862 any other string identifies all sections with that name in the object file.
4866 Requests that the section(s) being dumped by @option{x}, @option{R} or
4867 @option{p} options are decompressed before being displayed. If the
4868 section(s) are not compressed then they are displayed as is.
4871 @itemx --archive-index
4872 @cindex Archive file symbol index information
4873 Displays the file symbol index information contained in the header part
4874 of binary archives. Performs the same function as the @option{t}
4875 command to @command{ar}, but without using the BFD library. @xref{ar}.
4877 @item -w[lLiaprmfFsoRtUuTgAckK]
4878 @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]
4879 @include debug.options.texi
4881 @include ctf.options.texi
4882 @item --ctf-symbols=@var{section}
4883 @item --ctf-strings=@var{section}
4884 Specify the name of another section from which the CTF file can inherit
4885 strings and symbols. By default, the @code{.symtab} and its linked
4886 string table are used.
4888 If either of @option{--ctf-symbols} or @option{--ctf-strings} is specified, the
4889 other must be specified as well.
4893 Display a histogram of bucket list lengths when displaying the contents
4894 of the symbol tables.
4898 Display the version number of readelf.
4902 Don't break output lines to fit into 80 columns. By default
4903 @command{readelf} breaks section header and segment listing lines for
4904 64-bit ELF files, so that they fit into 80 columns. This option causes
4905 @command{readelf} to print each section header resp. each segment one a
4906 single line, which is far more readable on terminals wider than 80 columns.
4910 Display the command-line options understood by @command{readelf}.
4917 @c man begin SEEALSO readelf
4918 objdump(1), and the Info entries for @file{binutils}.
4925 @cindex Update ELF header
4928 @c man title elfedit update ELF header and program property of ELF files
4931 @c man begin SYNOPSIS elfedit
4932 elfedit [@option{--input-mach=}@var{machine}]
4933 [@option{--input-type=}@var{type}]
4934 [@option{--input-osabi=}@var{osabi}]
4935 @option{--output-mach=}@var{machine}
4936 @option{--output-type=}@var{type}
4937 @option{--output-osabi=}@var{osabi}
4938 @option{--enable-x86-feature=}@var{feature}
4939 @option{--disable-x86-feature=}@var{feature}
4940 [@option{-v}|@option{--version}]
4941 [@option{-h}|@option{--help}]
4942 @var{elffile}@dots{}
4946 @c man begin DESCRIPTION elfedit
4948 @command{elfedit} updates the ELF header and program property of ELF
4949 files which have the matching ELF machine and file types. The options
4950 control how and which fields in the ELF header and program property
4953 @var{elffile}@dots{} are the ELF files to be updated. 32-bit and
4954 64-bit ELF files are supported, as are archives containing ELF files.
4957 @c man begin OPTIONS elfedit
4959 The long and short forms of options, shown here as alternatives, are
4960 equivalent. At least one of the @option{--output-mach},
4961 @option{--output-type}, @option{--output-osabi},
4962 @option{--enable-x86-feature} and @option{--disable-x86-feature}
4963 options must be given.
4967 @item --input-mach=@var{machine}
4968 Set the matching input ELF machine type to @var{machine}. If
4969 @option{--input-mach} isn't specified, it will match any ELF
4972 The supported ELF machine types are, @var{i386}, @var{IAMCU}, @var{L1OM},
4973 @var{K1OM} and @var{x86-64}.
4975 @item --output-mach=@var{machine}
4976 Change the ELF machine type in the ELF header to @var{machine}. The
4977 supported ELF machine types are the same as @option{--input-mach}.
4979 @item --input-type=@var{type}
4980 Set the matching input ELF file type to @var{type}. If
4981 @option{--input-type} isn't specified, it will match any ELF file types.
4983 The supported ELF file types are, @var{rel}, @var{exec} and @var{dyn}.
4985 @item --output-type=@var{type}
4986 Change the ELF file type in the ELF header to @var{type}. The
4987 supported ELF types are the same as @option{--input-type}.
4989 @item --input-osabi=@var{osabi}
4990 Set the matching input ELF file OSABI to @var{osabi}. If
4991 @option{--input-osabi} isn't specified, it will match any ELF OSABIs.
4993 The supported ELF OSABIs are, @var{none}, @var{HPUX}, @var{NetBSD},
4994 @var{GNU}, @var{Linux} (alias for @var{GNU}),
4995 @var{Solaris}, @var{AIX}, @var{Irix},
4996 @var{FreeBSD}, @var{TRU64}, @var{Modesto}, @var{OpenBSD}, @var{OpenVMS},
4997 @var{NSK}, @var{AROS} and @var{FenixOS}.
4999 @item --output-osabi=@var{osabi}
5000 Change the ELF OSABI in the ELF header to @var{osabi}. The
5001 supported ELF OSABI are the same as @option{--input-osabi}.
5003 @item --enable-x86-feature=@var{feature}
5004 Set the @var{feature} bit in program property in @var{exec} or @var{dyn}
5005 ELF files with machine types of @var{i386} or @var{x86-64}. The
5006 supported features are, @var{ibt} and @var{shstk}.
5008 @item --disable-x86-feature=@var{feature}
5009 Clear the @var{feature} bit in program property in @var{exec} or
5010 @var{dyn} ELF files with machine types of @var{i386} or @var{x86-64}.
5011 The supported features are the same as @option{--enable-x86-feature}.
5013 Note: @option{--enable-x86-feature} and @option{--disable-x86-feature}
5014 are available only on hosts with @samp{mmap} support.
5018 Display the version number of @command{elfedit}.
5022 Display the command-line options understood by @command{elfedit}.
5029 @c man begin SEEALSO elfedit
5030 readelf(1), and the Info entries for @file{binutils}.
5034 @node Common Options
5035 @chapter Common Options
5037 The following command-line options are supported by all of the
5038 programs described in this manual.
5040 @c man begin OPTIONS
5042 @include at-file.texi
5046 Display the command-line options supported by the program.
5049 Display the version number of the program.
5051 @c man begin OPTIONS
5055 @node Selecting the Target System
5056 @chapter Selecting the Target System
5058 You can specify two aspects of the target system to the @sc{gnu}
5059 binary file utilities, each in several ways:
5069 In the following summaries, the lists of ways to specify values are in
5070 order of decreasing precedence. The ways listed first override those
5073 The commands to list valid values only list the values for which the
5074 programs you are running were configured. If they were configured with
5075 @option{--enable-targets=all}, the commands list most of the available
5076 values, but a few are left out; not all targets can be configured in at
5077 once because some of them can only be configured @dfn{native} (on hosts
5078 with the same type as the target system).
5081 * Target Selection::
5082 * Architecture Selection::
5085 @node Target Selection
5086 @section Target Selection
5088 A @dfn{target} is an object file format. A given target may be
5089 supported for multiple architectures (@pxref{Architecture Selection}).
5090 A target selection may also have variations for different operating
5091 systems or architectures.
5093 The command to list valid target values is @samp{objdump -i}
5094 (the first column of output contains the relevant information).
5096 Some sample values are: @samp{a.out-hp300bsd}, @samp{ecoff-littlemips},
5097 @samp{a.out-sunos-big}.
5099 You can also specify a target using a configuration triplet. This is
5100 the same sort of name that is passed to @file{configure} to specify a
5101 target. When you use a configuration triplet as an argument, it must be
5102 fully canonicalized. You can see the canonical version of a triplet by
5103 running the shell script @file{config.sub} which is included with the
5106 Some sample configuration triplets are: @samp{m68k-hp-bsd},
5107 @samp{mips-dec-ultrix}, @samp{sparc-sun-sunos}.
5109 @subheading @command{objdump} Target
5115 command-line option: @option{-b} or @option{--target}
5118 environment variable @code{GNUTARGET}
5121 deduced from the input file
5124 @subheading @command{objcopy} and @command{strip} Input Target
5130 command-line options: @option{-I} or @option{--input-target}, or @option{-F} or @option{--target}
5133 environment variable @code{GNUTARGET}
5136 deduced from the input file
5139 @subheading @command{objcopy} and @command{strip} Output Target
5145 command-line options: @option{-O} or @option{--output-target}, or @option{-F} or @option{--target}
5148 the input target (see ``@command{objcopy} and @command{strip} Input Target'' above)
5151 environment variable @code{GNUTARGET}
5154 deduced from the input file
5157 @subheading @command{nm}, @command{size}, and @command{strings} Target
5163 command-line option: @option{--target}
5166 environment variable @code{GNUTARGET}
5169 deduced from the input file
5172 @node Architecture Selection
5173 @section Architecture Selection
5175 An @dfn{architecture} is a type of @sc{cpu} on which an object file is
5176 to run. Its name may contain a colon, separating the name of the
5177 processor family from the name of the particular @sc{cpu}.
5179 The command to list valid architecture values is @samp{objdump -i} (the
5180 second column contains the relevant information).
5182 Sample values: @samp{m68k:68020}, @samp{mips:3000}, @samp{sparc}.
5184 @subheading @command{objdump} Architecture
5190 command-line option: @option{-m} or @option{--architecture}
5193 deduced from the input file
5196 @subheading @command{objcopy}, @command{nm}, @command{size}, @command{strings} Architecture
5202 deduced from the input file
5207 @cindex separate debug files
5209 debuginfod is a web service that indexes ELF/DWARF debugging resources
5210 by build-id and serves them over HTTP.
5212 Binutils can be built with the debuginfod client library
5213 @code{libdebuginfod} using the @option{--with-debuginfod} configure option.
5214 This option is enabled by default if @code{libdebuginfod} is installed
5215 and found at configure time. This allows @command{objdump} and
5216 @command{readelf} to automatically query debuginfod servers for
5217 separate debug files when the files are otherwise not found.
5219 debuginfod is packaged with elfutils, starting with version 0.178.
5220 You can get the latest version from `https://sourceware.org/elfutils/'.
5222 @node Reporting Bugs
5223 @chapter Reporting Bugs
5225 @cindex reporting bugs
5227 Your bug reports play an essential role in making the binary utilities
5230 Reporting a bug may help you by bringing a solution to your problem, or
5231 it may not. But in any case the principal function of a bug report is
5232 to help the entire community by making the next version of the binary
5233 utilities work better. Bug reports are your contribution to their
5236 In order for a bug report to serve its purpose, you must include the
5237 information that enables us to fix the bug.
5240 * Bug Criteria:: Have you found a bug?
5241 * Bug Reporting:: How to report bugs
5245 @section Have You Found a Bug?
5246 @cindex bug criteria
5248 If you are not sure whether you have found a bug, here are some guidelines:
5251 @cindex fatal signal
5254 If a binary utility gets a fatal signal, for any input whatever, that is
5255 a bug. Reliable utilities never crash.
5257 @cindex error on valid input
5259 If a binary utility produces an error message for valid input, that is a
5263 If you are an experienced user of binary utilities, your suggestions for
5264 improvement are welcome in any case.
5268 @section How to Report Bugs
5270 @cindex bugs, reporting
5272 A number of companies and individuals offer support for @sc{gnu}
5273 products. If you obtained the binary utilities from a support
5274 organization, we recommend you contact that organization first.
5276 You can find contact information for many support companies and
5277 individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs
5281 In any event, we also recommend that you send bug reports for the binary
5282 utilities to @value{BUGURL}.
5285 The fundamental principle of reporting bugs usefully is this:
5286 @strong{report all the facts}. If you are not sure whether to state a
5287 fact or leave it out, state it!
5289 Often people omit facts because they think they know what causes the
5290 problem and assume that some details do not matter. Thus, you might
5291 assume that the name of a file you use in an example does not matter.
5292 Well, probably it does not, but one cannot be sure. Perhaps the bug is
5293 a stray memory reference which happens to fetch from the location where
5294 that pathname is stored in memory; perhaps, if the pathname were
5295 different, the contents of that location would fool the utility into
5296 doing the right thing despite the bug. Play it safe and give a
5297 specific, complete example. That is the easiest thing for you to do,
5298 and the most helpful.
5300 Keep in mind that the purpose of a bug report is to enable us to fix the bug if
5301 it is new to us. Therefore, always write your bug reports on the assumption
5302 that the bug has not been reported previously.
5304 Sometimes people give a few sketchy facts and ask, ``Does this ring a
5305 bell?'' This cannot help us fix a bug, so it is basically useless. We
5306 respond by asking for enough details to enable us to investigate.
5307 You might as well expedite matters by sending them to begin with.
5309 To enable us to fix the bug, you should include all these things:
5313 The version of the utility. Each utility announces it if you start it
5314 with the @option{--version} argument.
5316 Without this, we will not know whether there is any point in looking for
5317 the bug in the current version of the binary utilities.
5320 Any patches you may have applied to the source, including any patches
5321 made to the @code{BFD} library.
5324 The type of machine you are using, and the operating system name and
5328 What compiler (and its version) was used to compile the utilities---e.g.
5332 The command arguments you gave the utility to observe the bug. To
5333 guarantee you will not omit something important, list them all. A copy
5334 of the Makefile (or the output from make) is sufficient.
5336 If we were to try to guess the arguments, we would probably guess wrong
5337 and then we might not encounter the bug.
5340 A complete input file, or set of input files, that will reproduce the
5341 bug. If the utility is reading an object file or files, then it is
5342 generally most helpful to send the actual object files.
5344 If the source files were produced exclusively using @sc{gnu} programs
5345 (e.g., @command{gcc}, @command{gas}, and/or the @sc{gnu} @command{ld}), then it
5346 may be OK to send the source files rather than the object files. In
5347 this case, be sure to say exactly what version of @command{gcc}, or
5348 whatever, was used to produce the object files. Also say how
5349 @command{gcc}, or whatever, was configured.
5352 A description of what behavior you observe that you believe is
5353 incorrect. For example, ``It gets a fatal signal.''
5355 Of course, if the bug is that the utility gets a fatal signal, then we
5356 will certainly notice it. But if the bug is incorrect output, we might
5357 not notice unless it is glaringly wrong. You might as well not give us
5358 a chance to make a mistake.
5360 Even if the problem you experience is a fatal signal, you should still
5361 say so explicitly. Suppose something strange is going on, such as your
5362 copy of the utility is out of sync, or you have encountered a bug in
5363 the C library on your system. (This has happened!) Your copy might
5364 crash and ours would not. If you told us to expect a crash, then when
5365 ours fails to crash, we would know that the bug was not happening for
5366 us. If you had not told us to expect a crash, then we would not be able
5367 to draw any conclusion from our observations.
5370 If you wish to suggest changes to the source, send us context diffs, as
5371 generated by @command{diff} with the @option{-u}, @option{-c}, or @option{-p}
5372 option. Always send diffs from the old file to the new file. If you
5373 wish to discuss something in the @command{ld} source, refer to it by
5374 context, not by line number.
5376 The line numbers in our development sources will not match those in your
5377 sources. Your line numbers would convey no useful information to us.
5380 Here are some things that are not necessary:
5384 A description of the envelope of the bug.
5386 Often people who encounter a bug spend a lot of time investigating
5387 which changes to the input file will make the bug go away and which
5388 changes will not affect it.
5390 This is often time consuming and not very useful, because the way we
5391 will find the bug is by running a single example under the debugger
5392 with breakpoints, not by pure deduction from a series of examples.
5393 We recommend that you save your time for something else.
5395 Of course, if you can find a simpler example to report @emph{instead}
5396 of the original one, that is a convenience for us. Errors in the
5397 output will be easier to spot, running under the debugger will take
5398 less time, and so on.
5400 However, simplification is not vital; if you do not want to do this,
5401 report the bug anyway and send us the entire test case you used.
5404 A patch for the bug.
5406 A patch for the bug does help us if it is a good one. But do not omit
5407 the necessary information, such as the test case, on the assumption that
5408 a patch is all we need. We might see problems with your patch and decide
5409 to fix the problem another way, or we might not understand it at all.
5411 Sometimes with programs as complicated as the binary utilities it is
5412 very hard to construct an example that will make the program follow a
5413 certain path through the code. If you do not send us the example, we
5414 will not be able to construct one, so we will not be able to verify that
5417 And if we cannot understand what bug you are trying to fix, or why your
5418 patch should be an improvement, we will not install it. A test case will
5419 help us to understand.
5422 A guess about what the bug is or what it depends on.
5424 Such guesses are usually wrong. Even we cannot guess right about such
5425 things without first using the debugger to find the facts.
5428 @node GNU Free Documentation License
5429 @appendix GNU Free Documentation License
5433 @node Binutils Index
5434 @unnumbered Binutils Index