1 \input texinfo @c -*- Texinfo -*-
2 @setfilename binutils.info
8 * Binutils: (binutils). The GNU binary utilities.
9 * ar: (binutils)ar. Create, modify, and extract from archives
10 * nm: (binutils)nm. List symbols from object files
11 * objcopy: (binutils)objcopy. Copy and translate object files
12 * objdump: (binutils)objdump. Display information from object files
13 * ranlib: (binutils)ranlib. Generate index to archive contents
14 * readelf: (binutils)readelf. Display the contents of ELF format files.
15 * size: (binutils)size. List section sizes and total size
16 * strings: (binutils)strings. List printable strings from files
17 * strip: (binutils)strip. Discard symbols
18 * c++filt: (binutils)c++filt. Filter to demangle encoded C++ symbols
19 * cxxfilt: (binutils)c++filt. MS-DOS name for c++filt
20 * addr2line: (binutils)addr2line. Convert addresses to file and line
21 * nlmconv: (binutils)nlmconv. Converts object code into an NLM
22 * windres: (binutils)windres. Manipulate Windows resources
23 * dlltool: (binutils)dlltool. Create files needed to build and use DLLs
29 Copyright @copyright{} 1991, 92, 93, 94, 95, 96, 97, 98, 99, 2000 Free Software Foundation, Inc.
31 Permission is granted to make and distribute verbatim copies of
32 this manual provided the copyright notice and this permission notice
33 are preserved on all copies.
36 Permission is granted to process this file through TeX and print the
37 results, provided the printed document carries a copying permission
38 notice identical to this one except for the removal of this paragraph
39 (this paragraph not being relevant to the printed manual).
43 Permission is granted to copy and distribute modified versions of this
44 manual under the conditions for verbatim copying, provided also that
45 the entire resulting derived work is distributed under the terms of a
46 permission notice identical to this one.
48 Permission is granted to copy and distribute translations of this manual
49 into another language, under the above conditions for modified versions.
54 @c This file documents the GNU binary utilities "ar", "ld", "objcopy",
55 @c "objdump", "nm", "size", "strings", "strip", "readelf" and "ranlib".
57 @c Copyright (C) 1991, 92, 93, 94, 95, 96, 97, 98, 99, 2000 Free Software Foundation, Inc.
59 @c This text may be freely distributed under the terms of the GNU
60 @c General Public License.
63 @setchapternewpage odd
64 @settitle @sc{gnu} Binary Utilities
67 @title The @sc{gnu} Binary Utilities
68 @subtitle Version @value{VERSION}
71 @author Roland H. Pesch
72 @author Jeffrey M. Osier
73 @author Cygnus Support
77 {\parskip=0pt \hfill Cygnus Support\par \hfill
78 \TeX{}info \texinfoversion\par }
81 @vskip 0pt plus 1filll
82 Copyright @copyright{} 1991, 92, 93, 94, 95, 96, 97, 1998 Free Software Foundation, Inc.
84 Permission is granted to make and distribute verbatim copies of
85 this manual provided the copyright notice and this permission notice
86 are preserved on all copies.
88 Permission is granted to copy and distribute modified versions of this
89 manual under the conditions for verbatim copying, provided also that
90 the entire resulting derived work is distributed under the terms of a
91 permission notice identical to this one.
93 Permission is granted to copy and distribute translations of this manual
94 into another language, under the above conditions for modified versions.
101 This brief manual contains preliminary documentation for the @sc{gnu} binary
102 utilities (collectively version @value{VERSION}):
107 Create, modify, and extract from archives
110 List symbols from object files
113 Copy and translate object files
116 Display information from object files
119 Generate index to archive contents
122 Display the contents of ELF format files.
125 List file section sizes and total size
128 List printable strings from files
134 Demangle encoded C++ symbols (on MS-DOS, this program is named
138 Convert addresses into file names and line numbers
141 Convert object code into a Netware Loadable Module
144 Manipulate Windows resources
147 Create the files needed to build and use Dynamic Link Libraries
152 * ar:: Create, modify, and extract from archives
153 * nm:: List symbols from object files
154 * objcopy:: Copy and translate object files
155 * objdump:: Display information from object files
156 * ranlib:: Generate index to archive contents
157 * readelf:: Display the contents of ELF format files.
158 * size:: List section sizes and total size
159 * strings:: List printable strings from files
160 * strip:: Discard symbols
161 * c++filt:: Filter to demangle encoded C++ symbols
162 * cxxfilt: c++filt. MS-DOS name for c++filt
163 * addr2line:: Convert addresses to file and line
164 * nlmconv:: Converts object code into an NLM
165 * windres:: Manipulate Windows resources
166 * dlltool:: Create files needed to build and use DLLs
167 * Selecting The Target System:: How these utilities determine the target.
168 * Reporting Bugs:: Reporting Bugs
177 @cindex collections of files
179 ar [-]@var{p}[@var{mod} [@var{relpos}] [@var{count}]] @var{archive} [@var{member}@dots{}]
180 ar -M [ <mri-script ]
183 The @sc{gnu} @code{ar} program creates, modifies, and extracts from
184 archives. An @dfn{archive} is a single file holding a collection of
185 other files in a structure that makes it possible to retrieve
186 the original individual files (called @dfn{members} of the archive).
188 The original files' contents, mode (permissions), timestamp, owner, and
189 group are preserved in the archive, and can be restored on
193 @sc{gnu} @code{ar} can maintain archives whose members have names of any
194 length; however, depending on how @code{ar} is configured on your
195 system, a limit on member-name length may be imposed for compatibility
196 with archive formats maintained with other tools. If it exists, the
197 limit is often 15 characters (typical of formats related to a.out) or 16
198 characters (typical of formats related to coff).
201 @code{ar} is considered a binary utility because archives of this sort
202 are most often used as @dfn{libraries} holding commonly needed
206 @code{ar} creates an index to the symbols defined in relocatable
207 object modules in the archive when you specify the modifier @samp{s}.
208 Once created, this index is updated in the archive whenever @code{ar}
209 makes a change to its contents (save for the @samp{q} update operation).
210 An archive with such an index speeds up linking to the library, and
211 allows routines in the library to call each other without regard to
212 their placement in the archive.
214 You may use @samp{nm -s} or @samp{nm --print-armap} to list this index
215 table. If an archive lacks the table, another form of @code{ar} called
216 @code{ranlib} can be used to add just the table.
218 @cindex compatibility, @code{ar}
219 @cindex @code{ar} compatibility
220 @sc{gnu} @code{ar} is designed to be compatible with two different
221 facilities. You can control its activity using command-line options,
222 like the different varieties of @code{ar} on Unix systems; or, if you
223 specify the single command-line option @samp{-M}, you can control it
224 with a script supplied via standard input, like the MRI ``librarian''
228 * ar cmdline:: Controlling @code{ar} on the command line
229 * ar scripts:: Controlling @code{ar} with a script
234 @section Controlling @code{ar} on the command line
237 ar [-]@var{p}[@var{mod} [@var{relpos}] [@var{count}]] @var{archive} [@var{member}@dots{}]
240 @cindex Unix compatibility, @code{ar}
241 When you use @code{ar} in the Unix style, @code{ar} insists on at least two
242 arguments to execute: one keyletter specifying the @emph{operation}
243 (optionally accompanied by other keyletters specifying
244 @emph{modifiers}), and the archive name to act on.
246 Most operations can also accept further @var{member} arguments,
247 specifying particular files to operate on.
249 @sc{gnu} @code{ar} allows you to mix the operation code @var{p} and modifier
250 flags @var{mod} in any order, within the first command-line argument.
252 If you wish, you may begin the first command-line argument with a
255 @cindex operations on archive
256 The @var{p} keyletter specifies what operation to execute; it may be
257 any of the following, but you must specify only one of them:
261 @cindex deleting from archive
262 @emph{Delete} modules from the archive. Specify the names of modules to
263 be deleted as @var{member}@dots{}; the archive is untouched if you
264 specify no files to delete.
266 If you specify the @samp{v} modifier, @code{ar} lists each module
270 @cindex moving in archive
271 Use this operation to @emph{move} members in an archive.
273 The ordering of members in an archive can make a difference in how
274 programs are linked using the library, if a symbol is defined in more
277 If no modifiers are used with @code{m}, any members you name in the
278 @var{member} arguments are moved to the @emph{end} of the archive;
279 you can use the @samp{a}, @samp{b}, or @samp{i} modifiers to move them to a
280 specified place instead.
283 @cindex printing from archive
284 @emph{Print} the specified members of the archive, to the standard
285 output file. If the @samp{v} modifier is specified, show the member
286 name before copying its contents to standard output.
288 If you specify no @var{member} arguments, all the files in the archive are
292 @cindex quick append to archive
293 @emph{Quick append}; Historically, add the files @var{member}@dots{} to the end of
294 @var{archive}, without checking for replacement.
296 The modifiers @samp{a}, @samp{b}, and @samp{i} do @emph{not} affect this
297 operation; new members are always placed at the end of the archive.
299 The modifier @samp{v} makes @code{ar} list each file as it is appended.
301 Since the point of this operation is speed, the archive's symbol table
302 index is not updated, even if it already existed; you can use @samp{ar s} or
303 @code{ranlib} explicitly to update the symbol table index.
305 However, too many different systems assume quick append rebuilds the
306 index, so GNU ar implements @code{q} as a synonym for @code{r}.
309 @cindex replacement in archive
310 Insert the files @var{member}@dots{} into @var{archive} (with
311 @emph{replacement}). This operation differs from @samp{q} in that any
312 previously existing members are deleted if their names match those being
315 If one of the files named in @var{member}@dots{} does not exist, @code{ar}
316 displays an error message, and leaves undisturbed any existing members
317 of the archive matching that name.
319 By default, new members are added at the end of the file; but you may
320 use one of the modifiers @samp{a}, @samp{b}, or @samp{i} to request
321 placement relative to some existing member.
323 The modifier @samp{v} used with this operation elicits a line of
324 output for each file inserted, along with one of the letters @samp{a} or
325 @samp{r} to indicate whether the file was appended (no old member
326 deleted) or replaced.
329 @cindex contents of archive
330 Display a @emph{table} listing the contents of @var{archive}, or those
331 of the files listed in @var{member}@dots{} that are present in the
332 archive. Normally only the member name is shown; if you also want to
333 see the modes (permissions), timestamp, owner, group, and size, you can
334 request that by also specifying the @samp{v} modifier.
336 If you do not specify a @var{member}, all files in the archive
339 @cindex repeated names in archive
340 @cindex name duplication in archive
341 If there is more than one file with the same name (say, @samp{fie}) in
342 an archive (say @samp{b.a}), @samp{ar t b.a fie} lists only the
343 first instance; to see them all, you must ask for a complete
344 listing---in our example, @samp{ar t b.a}.
345 @c WRS only; per Gumby, this is implementation-dependent, and in a more
346 @c recent case in fact works the other way.
349 @cindex extract from archive
350 @emph{Extract} members (named @var{member}) from the archive. You can
351 use the @samp{v} modifier with this operation, to request that
352 @code{ar} list each name as it extracts it.
354 If you do not specify a @var{member}, all files in the archive
359 A number of modifiers (@var{mod}) may immediately follow the @var{p}
360 keyletter, to specify variations on an operation's behavior:
364 @cindex relative placement in archive
365 Add new files @emph{after} an existing member of the
366 archive. If you use the modifier @samp{a}, the name of an existing archive
367 member must be present as the @var{relpos} argument, before the
368 @var{archive} specification.
371 Add new files @emph{before} an existing member of the
372 archive. If you use the modifier @samp{b}, the name of an existing archive
373 member must be present as the @var{relpos} argument, before the
374 @var{archive} specification. (same as @samp{i}).
377 @cindex creating archives
378 @emph{Create} the archive. The specified @var{archive} is always
379 created if it did not exist, when you request an update. But a warning is
380 issued unless you specify in advance that you expect to create it, by
384 Truncate names in the archive. @sc{gnu} @code{ar} will normally permit file
385 names of any length. This will cause it to create archives which are
386 not compatible with the native @code{ar} program on some systems. If
387 this is a concern, the @samp{f} modifier may be used to truncate file
388 names when putting them in the archive.
391 Insert new files @emph{before} an existing member of the
392 archive. If you use the modifier @samp{i}, the name of an existing archive
393 member must be present as the @var{relpos} argument, before the
394 @var{archive} specification. (same as @samp{b}).
397 This modifier is accepted but not used.
398 @c whaffor ar l modifier??? presumably compat; with
399 @c what???---doc@@cygnus.com, 25jan91
402 Uses the @var{count} parameter. This is used if there are multiple
403 entries in the archive with the same name. Extract or delete instance
404 @var{count} of the given name from the archive.
407 @cindex dates in archive
408 Preserve the @emph{original} dates of members when extracting them. If
409 you do not specify this modifier, files extracted from the archive
410 are stamped with the time of extraction.
413 Use the full path name when matching names in the archive. @sc{gnu}
414 @code{ar} can not create an archive with a full path name (such archives
415 are not POSIX complaint), but other archive creators can. This option
416 will cause @sc{gnu} @code{ar} to match file names using a complete path
417 name, which can be convenient when extracting a single file from an
418 archive created by another tool.
421 @cindex writing archive index
422 Write an object-file index into the archive, or update an existing one,
423 even if no other change is made to the archive. You may use this modifier
424 flag either with any operation, or alone. Running @samp{ar s} on an
425 archive is equivalent to running @samp{ranlib} on it.
428 @cindex not writing archive index
429 Do not generate an archive symbol table. This can speed up building a
430 large library in several steps. The resulting archive can not be used
431 with the linker. In order to build a symbol table, you must omit the
432 @samp{S} modifier on the last execution of @samp{ar}, or you must run
433 @samp{ranlib} on the archive.
436 @cindex updating an archive
437 Normally, @samp{ar r}@dots{} inserts all files
438 listed into the archive. If you would like to insert @emph{only} those
439 of the files you list that are newer than existing members of the same
440 names, use this modifier. The @samp{u} modifier is allowed only for the
441 operation @samp{r} (replace). In particular, the combination @samp{qu} is
442 not allowed, since checking the timestamps would lose any speed
443 advantage from the operation @samp{q}.
446 This modifier requests the @emph{verbose} version of an operation. Many
447 operations display additional information, such as filenames processed,
448 when the modifier @samp{v} is appended.
451 This modifier shows the version number of @code{ar}.
455 @section Controlling @code{ar} with a script
458 ar -M [ <@var{script} ]
461 @cindex MRI compatibility, @code{ar}
462 @cindex scripts, @code{ar}
463 If you use the single command-line option @samp{-M} with @code{ar}, you
464 can control its operation with a rudimentary command language. This
465 form of @code{ar} operates interactively if standard input is coming
466 directly from a terminal. During interactive use, @code{ar} prompts for
467 input (the prompt is @samp{AR >}), and continues executing even after
468 errors. If you redirect standard input to a script file, no prompts are
469 issued, and @code{ar} abandons execution (with a nonzero exit code)
472 The @code{ar} command language is @emph{not} designed to be equivalent
473 to the command-line options; in fact, it provides somewhat less control
474 over archives. The only purpose of the command language is to ease the
475 transition to @sc{gnu} @code{ar} for developers who already have scripts
476 written for the MRI ``librarian'' program.
478 The syntax for the @code{ar} command language is straightforward:
481 commands are recognized in upper or lower case; for example, @code{LIST}
482 is the same as @code{list}. In the following descriptions, commands are
483 shown in upper case for clarity.
486 a single command may appear on each line; it is the first word on the
490 empty lines are allowed, and have no effect.
493 comments are allowed; text after either of the characters @samp{*}
494 or @samp{;} is ignored.
497 Whenever you use a list of names as part of the argument to an @code{ar}
498 command, you can separate the individual names with either commas or
499 blanks. Commas are shown in the explanations below, for clarity.
502 @samp{+} is used as a line continuation character; if @samp{+} appears
503 at the end of a line, the text on the following line is considered part
504 of the current command.
507 Here are the commands you can use in @code{ar} scripts, or when using
508 @code{ar} interactively. Three of them have special significance:
510 @code{OPEN} or @code{CREATE} specify a @dfn{current archive}, which is
511 a temporary file required for most of the other commands.
513 @code{SAVE} commits the changes so far specified by the script. Prior
514 to @code{SAVE}, commands affect only the temporary copy of the current
518 @item ADDLIB @var{archive}
519 @itemx ADDLIB @var{archive} (@var{module}, @var{module}, @dots{} @var{module})
520 Add all the contents of @var{archive} (or, if specified, each named
521 @var{module} from @var{archive}) to the current archive.
523 Requires prior use of @code{OPEN} or @code{CREATE}.
525 @item ADDMOD @var{member}, @var{member}, @dots{} @var{member}
526 @c FIXME! w/Replacement?? If so, like "ar r @var{archive} @var{names}"
527 @c else like "ar q..."
528 Add each named @var{member} as a module in the current archive.
530 Requires prior use of @code{OPEN} or @code{CREATE}.
533 Discard the contents of the current archive, canceling the effect of
534 any operations since the last @code{SAVE}. May be executed (with no
535 effect) even if no current archive is specified.
537 @item CREATE @var{archive}
538 Creates an archive, and makes it the current archive (required for many
539 other commands). The new archive is created with a temporary name; it
540 is not actually saved as @var{archive} until you use @code{SAVE}.
541 You can overwrite existing archives; similarly, the contents of any
542 existing file named @var{archive} will not be destroyed until @code{SAVE}.
544 @item DELETE @var{module}, @var{module}, @dots{} @var{module}
545 Delete each listed @var{module} from the current archive; equivalent to
546 @samp{ar -d @var{archive} @var{module} @dots{} @var{module}}.
548 Requires prior use of @code{OPEN} or @code{CREATE}.
550 @item DIRECTORY @var{archive} (@var{module}, @dots{} @var{module})
551 @itemx DIRECTORY @var{archive} (@var{module}, @dots{} @var{module}) @var{outputfile}
552 List each named @var{module} present in @var{archive}. The separate
553 command @code{VERBOSE} specifies the form of the output: when verbose
554 output is off, output is like that of @samp{ar -t @var{archive}
555 @var{module}@dots{}}. When verbose output is on, the listing is like
556 @samp{ar -tv @var{archive} @var{module}@dots{}}.
558 Output normally goes to the standard output stream; however, if you
559 specify @var{outputfile} as a final argument, @code{ar} directs the
563 Exit from @code{ar}, with a @code{0} exit code to indicate successful
564 completion. This command does not save the output file; if you have
565 changed the current archive since the last @code{SAVE} command, those
568 @item EXTRACT @var{module}, @var{module}, @dots{} @var{module}
569 Extract each named @var{module} from the current archive, writing them
570 into the current directory as separate files. Equivalent to @samp{ar -x
571 @var{archive} @var{module}@dots{}}.
573 Requires prior use of @code{OPEN} or @code{CREATE}.
576 @c FIXME Tokens but no commands???
583 Display full contents of the current archive, in ``verbose'' style
584 regardless of the state of @code{VERBOSE}. The effect is like @samp{ar
585 tv @var{archive}}. (This single command is a @sc{gnu} @code{ar}
586 enhancement, rather than present for MRI compatibility.)
588 Requires prior use of @code{OPEN} or @code{CREATE}.
590 @item OPEN @var{archive}
591 Opens an existing archive for use as the current archive (required for
592 many other commands). Any changes as the result of subsequent commands
593 will not actually affect @var{archive} until you next use @code{SAVE}.
595 @item REPLACE @var{module}, @var{module}, @dots{} @var{module}
596 In the current archive, replace each existing @var{module} (named in
597 the @code{REPLACE} arguments) from files in the current working directory.
598 To execute this command without errors, both the file, and the module in
599 the current archive, must exist.
601 Requires prior use of @code{OPEN} or @code{CREATE}.
604 Toggle an internal flag governing the output from @code{DIRECTORY}.
605 When the flag is on, @code{DIRECTORY} output matches output from
606 @samp{ar -tv }@dots{}.
609 Commit your changes to the current archive, and actually save it as a
610 file with the name specified in the last @code{CREATE} or @code{OPEN}
613 Requires prior use of @code{OPEN} or @code{CREATE}.
622 The @sc{gnu} linker @code{ld} is now described in a separate manual.
623 @xref{Top,, Overview,, Using LD: the @sc{gnu} linker}.
632 nm [ -a | --debug-syms ] [ -g | --extern-only ]
633 [ -B ] [ -C | --demangle ] [ -D | --dynamic ]
634 [ -s | --print-armap ] [ -A | -o | --print-file-name ]
635 [ -n | -v | --numeric-sort ] [ -p | --no-sort ]
636 [ -r | --reverse-sort ] [ --size-sort ] [ -u | --undefined-only ]
637 [ -t @var{radix} | --radix=@var{radix} ] [ -P | --portability ]
638 [ --target=@var{bfdname} ] [ -f @var{format} | --format=@var{format} ]
639 [ --defined-only ] [-l | --line-numbers ]
640 [ --no-demangle ] [ -V | --version ] [ --help ] [ @var{objfile}@dots{} ]
643 @sc{gnu} @code{nm} lists the symbols from object files @var{objfile}@dots{}.
644 If no object files are listed as arguments, @code{nm} assumes the file
647 For each symbol, @code{nm} shows:
651 The symbol value, in the radix selected by options (see below), or
652 hexadecimal by default.
655 The symbol type. At least the following types are used; others are, as
656 well, depending on the object file format. If lowercase, the symbol is
657 local; if uppercase, the symbol is global (external).
659 @c Some more detail on exactly what these symbol types are used for
663 The symbol's value is absolute, and will not be changed by further
667 The symbol is in the uninitialized data section (known as BSS).
670 The symbol is common. Common symbols are uninitialized data. When
671 linking, multiple common symbols may appear with the same name. If the
672 symbol is defined anywhere, the common symbols are treated as undefined
673 references. For more details on common symbols, see the discussion of
674 --warn-common in @ref{Options,,Linker options,ld.info,The GNU linker}.
677 The symbol is in the initialized data section.
680 The symbol is in an initialized data section for small objects. Some
681 object file formats permit more efficient access to small data objects,
682 such as a global int variable as opposed to a large global array.
685 The symbol is an indirect reference to another symbol. This is a GNU
686 extension to the a.out object file format which is rarely used.
689 The symbol is a debugging symbol.
692 The symbol is in a read only data section.
695 The symbol is in an uninitialized data section for small objects.
698 The symbol is in the text (code) section.
701 The symbol is undefined.
704 The symbol is a weak object. When a weak defined symbol is linked with
705 a normal defined symbol, the normal defined symbol is used with no error.
706 When a weak undefined symbol is linked and the symbol is not defined,
707 the value of the weak symbol becomes zero with no error.
710 The symbol is a weak symbol that has not been specifically tagged as a
711 weak object symbol. When a weak defined symbol is linked with a normal
712 defined symbol, the normal defined symbol is used with no error.
713 When a weak undefined symbol is linked and the symbol is not defined,
714 the value of the weak symbol becomes zero with no error.
717 The symbol is a stabs symbol in an a.out object file. In this case, the
718 next values printed are the stabs other field, the stabs desc field, and
719 the stab type. Stabs symbols are used to hold debugging information;
720 for more information, see @ref{Top,Stabs,Stabs Overview,stabs.info, The
721 ``stabs'' debug format}.
724 The symbol type is unknown, or object file format specific.
731 The long and short forms of options, shown here as alternatives, are
737 @itemx --print-file-name
738 @cindex input file name
740 @cindex source file name
741 Precede each symbol by the name of the input file (or archive member)
742 in which it was found, rather than identifying the input file once only,
743 before all of its symbols.
747 @cindex debugging symbols
748 Display all symbols, even debugger-only symbols; normally these are not
752 @cindex @code{nm} format
753 @cindex @code{nm} compatibility
754 The same as @samp{--format=bsd} (for compatibility with the MIPS @code{nm}).
758 @cindex demangling in nm
759 Decode (@dfn{demangle}) low-level symbol names into user-level names.
760 Besides removing any initial underscore prepended by the system, this
761 makes C++ function names readable. @xref{c++filt}, for more information
765 Do not demangle low-level symbol names. This is the default.
769 @cindex dynamic symbols
770 Display the dynamic symbols rather than the normal symbols. This is
771 only meaningful for dynamic objects, such as certain types of shared
774 @item -f @var{format}
775 @itemx --format=@var{format}
776 @cindex @code{nm} format
777 @cindex @code{nm} compatibility
778 Use the output format @var{format}, which can be @code{bsd},
779 @code{sysv}, or @code{posix}. The default is @code{bsd}.
780 Only the first character of @var{format} is significant; it can be
781 either upper or lower case.
785 @cindex external symbols
786 Display only external symbols.
789 @itemx --line-numbers
790 @cindex symbol line numbers
791 For each symbol, use debugging information to try to find a filename and
792 line number. For a defined symbol, look for the line number of the
793 address of the symbol. For an undefined symbol, look for the line
794 number of a relocation entry which refers to the symbol. If line number
795 information can be found, print it after the other symbol information.
799 @itemx --numeric-sort
800 Sort symbols numerically by their addresses, rather than alphabetically
805 @cindex sorting symbols
806 Do not bother to sort the symbols in any order; print them in the order
811 Use the POSIX.2 standard output format instead of the default format.
812 Equivalent to @samp{-f posix}.
816 @cindex symbol index, listing
817 When listing symbols from archive members, include the index: a mapping
818 (stored in the archive by @code{ar} or @code{ranlib}) of which modules
819 contain definitions for which names.
822 @itemx --reverse-sort
823 Reverse the order of the sort (whether numeric or alphabetic); let the
827 Sort symbols by size. The size is computed as the difference between
828 the value of the symbol and the value of the symbol with the next higher
829 value. The size of the symbol is printed, rather than the value.
832 @itemx --radix=@var{radix}
833 Use @var{radix} as the radix for printing the symbol values. It must be
834 @samp{d} for decimal, @samp{o} for octal, or @samp{x} for hexadecimal.
836 @item --target=@var{bfdname}
837 @cindex object code format
838 Specify an object code format other than your system's default format.
839 @xref{Target Selection}, for more information.
842 @itemx --undefined-only
843 @cindex external symbols
844 @cindex undefined symbols
845 Display only undefined symbols (those external to each object file).
848 @cindex external symbols
849 @cindex undefined symbols
850 Display only defined symbols for each object file.
854 Show the version number of @code{nm} and exit.
857 Show a summary of the options to @code{nm} and exit.
864 objcopy [ -F @var{bfdname} | --target=@var{bfdname} ]
865 [ -I @var{bfdname} | --input-target=@var{bfdname} ]
866 [ -O @var{bfdname} | --output-target=@var{bfdname} ]
867 [ -S | --strip-all ] [ -g | --strip-debug ]
868 [ -K @var{symbolname} | --keep-symbol=@var{symbolname} ]
869 [ -N @var{symbolname} | --strip-symbol=@var{symbolname} ]
870 [ -L @var{symbolname} | --localize-symbol=@var{symbolname} ]
871 [ -W @var{symbolname} | --weaken-symbol=@var{symbolname} ]
872 [ -x | --discard-all ] [ -X | --discard-locals ]
873 [ -b @var{byte} | --byte=@var{byte} ]
874 [ -i @var{interleave} | --interleave=@var{interleave} ]
875 [ -j @var{sectionname} | --only-section=@var{sectionname} ]
876 [ -R @var{sectionname} | --remove-section=@var{sectionname} ]
877 [ -p | --preserve-dates ] [ --debugging ]
878 [ --gap-fill=@var{val} ] [ --pad-to=@var{address} ]
879 [ --set-start=@var{val} ] [ --adjust-start=@var{incr} ]
880 [ --change-addresses=@var{incr} ]
881 [ --change-section-address=@var{section}@{=,+,-@}@var{val} ]
882 [ --change-section-lma=@var{section}@{=,+,-@}@var{val} ]
883 [ --change-section-vma=@var{section}@{=,+,-@}@var{val} ]
884 [ --change-warnings ] [ --no-change-warnings ]
885 [ --set-section-flags=@var{section}=@var{flags} ]
886 [ --add-section=@var{sectionname}=@var{filename} ]
887 [ --change-leading-char ] [ --remove-leading-char ]
889 [ -v | --verbose ] [ -V | --version ] [ --help ]
890 @var{infile} [@var{outfile}]
893 The @sc{gnu} @code{objcopy} utility copies the contents of an object
894 file to another. @code{objcopy} uses the @sc{gnu} @sc{bfd} Library to
895 read and write the object files. It can write the destination object
896 file in a format different from that of the source object file. The
897 exact behavior of @code{objcopy} is controlled by command-line options.
899 @code{objcopy} creates temporary files to do its translations and
900 deletes them afterward. @code{objcopy} uses @sc{bfd} to do all its
901 translation work; it has access to all the formats described in @sc{bfd}
902 and thus is able to recognize most formats without being told
903 explicitly. @xref{BFD,,BFD,ld.info,Using LD}.
905 @code{objcopy} can be used to generate S-records by using an output
906 target of @samp{srec} (e.g., use @samp{-O srec}).
908 @code{objcopy} can be used to generate a raw binary file by using an
909 output target of @samp{binary} (e.g., use @samp{-O binary}). When
910 @code{objcopy} generates a raw binary file, it will essentially produce
911 a memory dump of the contents of the input object file. All symbols and
912 relocation information will be discarded. The memory dump will start at
913 the load address of the lowest section copied into the output file.
915 When generating an S-record or a raw binary file, it may be helpful to
916 use @samp{-S} to remove sections containing debugging information. In
917 some cases @samp{-R} will be useful to remove sections which contain
918 information that is not needed by the binary file.
923 The input and output files, respectively.
924 If you do not specify @var{outfile}, @code{objcopy} creates a
925 temporary file and destructively renames the result with
926 the name of @var{infile}.
928 @item -I @var{bfdname}
929 @itemx --input-target=@var{bfdname}
930 Consider the source file's object format to be @var{bfdname}, rather than
931 attempting to deduce it. @xref{Target Selection}, for more information.
933 @item -O @var{bfdname}
934 @itemx --output-target=@var{bfdname}
935 Write the output file using the object format @var{bfdname}.
936 @xref{Target Selection}, for more information.
938 @item -F @var{bfdname}
939 @itemx --target=@var{bfdname}
940 Use @var{bfdname} as the object format for both the input and the output
941 file; i.e., simply transfer data from source to destination with no
942 translation. @xref{Target Selection}, for more information.
944 @item -j @var{sectionname}
945 @itemx --only-section=@var{sectionname}
946 Copy only the named section from the input file to the output file.
947 This option may be given more than once. Note that using this option
948 inappropriately may make the output file unusable.
950 @item -R @var{sectionname}
951 @itemx --remove-section=@var{sectionname}
952 Remove any section named @var{sectionname} from the output file. This
953 option may be given more than once. Note that using this option
954 inappropriately may make the output file unusable.
958 Do not copy relocation and symbol information from the source file.
962 Do not copy debugging symbols from the source file.
964 @item --strip-unneeded
965 Strip all symbols that are not needed for relocation processing.
967 @item -K @var{symbolname}
968 @itemx --keep-symbol=@var{symbolname}
969 Copy only symbol @var{symbolname} from the source file. This option may
970 be given more than once.
972 @item -N @var{symbolname}
973 @itemx --strip-symbol=@var{symbolname}
974 Do not copy symbol @var{symbolname} from the source file. This option
975 may be given more than once.
977 @item -L @var{symbolname}
978 @itemx --localize-symbol=@var{symbolname}
979 Make symbol @var{symbolname} local to the file, so that it is not
980 visible externally. This option may be given more than once.
982 @item -W @var{symbolname}
983 @itemx --weaken-symbol=@var{symbolname}
984 Make symbol @var{symbolname} weak. This option may be given more than once.
988 Do not copy non-global symbols from the source file.
989 @c FIXME any reason to prefer "non-global" to "local" here?
992 @itemx --discard-locals
993 Do not copy compiler-generated local symbols.
994 (These usually start with @samp{L} or @samp{.}.)
997 @itemx --byte=@var{byte}
998 Keep only every @var{byte}th byte of the input file (header data is not
999 affected). @var{byte} can be in the range from 0 to @var{interleave}-1,
1000 where @var{interleave} is given by the @samp{-i} or @samp{--interleave}
1001 option, or the default of 4. This option is useful for creating files
1002 to program @sc{rom}. It is typically used with an @code{srec} output
1005 @item -i @var{interleave}
1006 @itemx --interleave=@var{interleave}
1007 Only copy one out of every @var{interleave} bytes. Select which byte to
1008 copy with the @var{-b} or @samp{--byte} option. The default is 4.
1009 @code{objcopy} ignores this option if you do not specify either @samp{-b} or
1013 @itemx --preserve-dates
1014 Set the access and modification dates of the output file to be the same
1015 as those of the input file.
1018 Convert debugging information, if possible. This is not the default
1019 because only certain debugging formats are supported, and the
1020 conversion process can be time consuming.
1022 @item --gap-fill @var{val}
1023 Fill gaps between sections with @var{val}. This operation applies to
1024 the @emph{load address} (LMA) of the sections. It is done by increasing
1025 the size of the section with the lower address, and filling in the extra
1026 space created with @var{val}.
1028 @item --pad-to @var{address}
1029 Pad the output file up to the load address @var{address}. This is
1030 done by increasing the size of the last section. The extra space is
1031 filled in with the value specified by @samp{--gap-fill} (default zero).
1033 @item --set-start @var{val}
1034 Set the start address of the new file to @var{val}. Not all object file
1035 formats support setting the start address.
1037 @item --change-start @var{incr}
1038 @itemx --adjust-start @var{incr}
1039 @cindex changing start address
1040 Change the start address by adding @var{incr}. Not all object file
1041 formats support setting the start address.
1043 @item --change-addresses @var{incr}
1044 @itemx --adjust-vma @var{incr}
1045 @cindex changing object addresses
1046 Change the VMA and LMA addresses of all sections, as well as the start
1047 address, by adding @var{incr}. Some object file formats do not permit
1048 section addresses to be changed arbitrarily. Note that this does not
1049 relocate the sections; if the program expects sections to be loaded at a
1050 certain address, and this option is used to change the sections such
1051 that they are loaded at a different address, the program may fail.
1053 @item --change-section-address @var{section}@{=,+,-@}@var{val}
1054 @itemx --adjust-section-vma @var{section}@{=,+,-@}@var{val}
1055 @cindex changing section address
1056 Set or change both the VMA address and the LMA address of the named
1057 @var{section}. If @samp{=} is used, the section address is set to
1058 @var{val}. Otherwise, @var{val} is added to or subtracted from the
1059 section address. See the comments under @samp{--change-addresses},
1060 above. If @var{section} does not exist in the input file, a warning will
1061 be issued, unless @samp{--no-change-warnings} is used.
1063 @item --change-section-lma @var{section}@{=,+,-@}@var{val}
1064 @cindex changing section LMA
1065 Set or change the LMA address of the named @var{section}. The LMA
1066 address is the address where the section will be loaded into memory at
1067 program load time. Normally this is the same as the VMA address, which
1068 is the address of the section at program run time, but on some systems,
1069 especially those where a program is held in ROM, the two can be
1070 different. If @samp{=} is used, the section address is set to
1071 @var{val}. Otherwise, @var{val} is added to or subtracted from the
1072 section address. See the comments under @samp{--change-addresses},
1073 above. If @var{section} does not exist in the input file, a warning
1074 will be issued, unless @samp{--no-change-warnings} is used.
1076 @item --change-section-vma @var{section}@{=,+,-@}@var{val}
1077 @cindex changing section VMA
1078 Set or change the VMA address of the named @var{section}. The VMA
1079 address is the address where the section will be located once the
1080 program has started executing. Normally this is the same as the LMA
1081 address, which is the address where the section will be loaded into
1082 memory, but on some systems, especially those where a program is held in
1083 ROM, the two can be different. If @samp{=} is used, the section address
1084 is set to @var{val}. Otherwise, @var{val} is added to or subtracted
1085 from the section address. See the comments under
1086 @samp{--change-addresses}, above. If @var{section} does not exist in
1087 the input file, a warning will be issued, unless
1088 @samp{--no-change-warnings} is used.
1090 @item --change-warnings
1091 @itemx --adjust-warnings
1092 If @samp{--change-section-address} or @samp{--change-section-lma} or
1093 @samp{--change-section-vma} is used, and the named section does not
1094 exist, issue a warning. This is the default.
1096 @item --no-change-warnings
1097 @itemx --no-adjust-warnings
1098 Do not issue a warning if @samp{--change-section-address} or
1099 @samp{--adjust-section-lma} or @samp{--adjust-section-vma} is used, even
1100 if the named section does not exist.
1102 @item --set-section-flags @var{section}=@var{flags}
1103 Set the flags for the named section. The @var{flags} argument is a
1104 comma separated string of flag names. The recognized names are
1105 @samp{alloc}, @samp{contents}, @samp{load}, @samp{noload},
1106 @samp{readonly}, @samp{code}, @samp{data}, @samp{rom}, @samp{share}, and
1107 @samp{debug}. You can set the @samp{contents} flag for a section which
1108 does not have contents, but it is not meaningful to clear the
1109 @samp{contents} flag of a section which does have contents--just remove
1110 the section instead. Not all flags are meaningful for all object file
1113 @item --add-section @var{sectionname}=@var{filename}
1114 Add a new section named @var{sectionname} while copying the file. The
1115 contents of the new section are taken from the file @var{filename}. The
1116 size of the section will be the size of the file. This option only
1117 works on file formats which can support sections with arbitrary names.
1119 @item --change-leading-char
1120 Some object file formats use special characters at the start of
1121 symbols. The most common such character is underscore, which compilers
1122 often add before every symbol. This option tells @code{objcopy} to
1123 change the leading character of every symbol when it converts between
1124 object file formats. If the object file formats use the same leading
1125 character, this option has no effect. Otherwise, it will add a
1126 character, or remove a character, or change a character, as
1129 @item --remove-leading-char
1130 If the first character of a global symbol is a special symbol leading
1131 character used by the object file format, remove the character. The
1132 most common symbol leading character is underscore. This option will
1133 remove a leading underscore from all global symbols. This can be useful
1134 if you want to link together objects of different file formats with
1135 different conventions for symbol names. This is different from
1136 @code{--change-leading-char} because it always changes the symbol name
1137 when appropriate, regardless of the object file format of the output
1141 Change all global symbols in the file to be weak. This can be useful
1142 when building an object which will be linked against other objects using
1143 the @code{-R} option to the linker. This option is only effective when
1144 using an object file format which supports weak symbols.
1148 Show the version number of @code{objcopy}.
1152 Verbose output: list all object files modified. In the case of
1153 archives, @samp{objcopy -V} lists all members of the archive.
1156 Show a summary of the options to @code{objcopy}.
1162 @cindex object file information
1166 objdump [ -a | --archive-headers ]
1167 [ -b @var{bfdname} | --target=@var{bfdname} ]
1169 [ -d | --disassemble ]
1170 [ -D | --disassemble-all ]
1171 [ -z | --disassemble-zeroes ]
1172 [ -EB | -EL | --endian=@{big | little @} ]
1173 [ -f | --file-headers ]
1174 [ -g | --debugging ]
1175 [ -h | --section-headers | --headers ]
1177 [ -j @var{section} | --section=@var{section} ]
1178 [ -l | --line-numbers ]
1180 [ -m @var{machine} | --architecture=@var{machine} ]
1181 [ -M @var{options} | --disassembler-options=@var{options}]
1182 [ -p | --private-headers ]
1184 [ -R | --dynamic-reloc ]
1185 [ -s | --full-contents ]
1188 [ -T | --dynamic-syms ]
1189 [ -x | --all-headers ]
1191 [ --start-address=@var{address} ]
1192 [ --stop-address=@var{address} ]
1193 [ --prefix-addresses]
1194 [ --[no-]show-raw-insn ]
1195 [ --adjust-vma=@var{offset} ]
1198 @var{objfile}@dots{}
1201 @code{objdump} displays information about one or more object files.
1202 The options control what particular information to display. This
1203 information is mostly useful to programmers who are working on the
1204 compilation tools, as opposed to programmers who just want their
1205 program to compile and work.
1207 @var{objfile}@dots{} are the object files to be examined. When you
1208 specify archives, @code{objdump} shows information on each of the member
1211 The long and short forms of options, shown here as alternatives, are
1212 equivalent. At least one option from the list
1213 @samp{-a,-d,-D,-f,-g,-G,-h,-H,-p,-r,-R,-S,-t,-T,-V,-x} must be given.
1217 @itemx --archive-header
1218 @cindex archive headers
1219 If any of the @var{objfile} files are archives, display the archive
1220 header information (in a format similar to @samp{ls -l}). Besides the
1221 information you could list with @samp{ar tv}, @samp{objdump -a} shows
1222 the object file format of each archive member.
1224 @item --adjust-vma=@var{offset}
1225 @cindex section addresses in objdump
1226 @cindex VMA in objdump
1227 When dumping information, first add @var{offset} to all the section
1228 addresses. This is useful if the section addresses do not correspond to
1229 the symbol table, which can happen when putting sections at particular
1230 addresses when using a format which can not represent section addresses,
1233 @item -b @var{bfdname}
1234 @itemx --target=@var{bfdname}
1235 @cindex object code format
1236 Specify that the object-code format for the object files is
1237 @var{bfdname}. This option may not be necessary; @var{objdump} can
1238 automatically recognize many formats.
1242 objdump -b oasys -m vax -h fu.o
1245 displays summary information from the section headers (@samp{-h}) of
1246 @file{fu.o}, which is explicitly identified (@samp{-m}) as a VAX object
1247 file in the format produced by Oasys compilers. You can list the
1248 formats available with the @samp{-i} option.
1249 @xref{Target Selection}, for more information.
1253 @cindex demangling in objdump
1254 Decode (@dfn{demangle}) low-level symbol names into user-level names.
1255 Besides removing any initial underscore prepended by the system, this
1256 makes C++ function names readable. @xref{c++filt}, for more information
1261 Display debugging information. This attempts to parse debugging
1262 information stored in the file and print it out using a C like syntax.
1263 Only certain types of debugging information have been implemented.
1266 @itemx --disassemble
1267 @cindex disassembling object code
1268 @cindex machine instructions
1269 Display the assembler mnemonics for the machine instructions from
1270 @var{objfile}. This option only disassembles those sections which are
1271 expected to contain instructions.
1274 @itemx --disassemble-all
1275 Like @samp{-d}, but disassemble the contents of all sections, not just
1276 those expected to contain instructions.
1278 @item --prefix-addresses
1279 When disassembling, print the complete address on each line. This is
1280 the older disassembly format.
1282 @item --disassemble-zeroes
1283 Normally the disassembly output will skip blocks of zeroes. This
1284 option directs the disassembler to disassemble those blocks, just like
1289 @itemx --endian=@{big|little@}
1291 @cindex disassembly endianness
1292 Specify the endianness of the object files. This only affects
1293 disassembly. This can be useful when disassembling a file format which
1294 does not describe endianness information, such as S-records.
1297 @itemx --file-header
1298 @cindex object file header
1299 Display summary information from the overall header of
1300 each of the @var{objfile} files.
1303 @itemx --section-header
1305 @cindex section headers
1306 Display summary information from the section headers of the
1309 File segments may be relocated to nonstandard addresses, for example by
1310 using the @samp{-Ttext}, @samp{-Tdata}, or @samp{-Tbss} options to
1311 @code{ld}. However, some object file formats, such as a.out, do not
1312 store the starting address of the file segments. In those situations,
1313 although @code{ld} relocates the sections correctly, using @samp{objdump
1314 -h} to list the file section headers cannot show the correct addresses.
1315 Instead, it shows the usual addresses, which are implicit for the
1319 Print a summary of the options to @code{objdump} and exit.
1323 @cindex architectures available
1324 @cindex object formats available
1325 Display a list showing all architectures and object formats available
1326 for specification with @samp{-b} or @samp{-m}.
1329 @itemx --section=@var{name}
1330 @cindex section information
1331 Display information only for section @var{name}.
1334 @itemx --line-numbers
1335 @cindex source filenames for object files
1336 Label the display (using debugging information) with the filename and
1337 source line numbers corresponding to the object code or relocs shown.
1338 Only useful with @samp{-d}, @samp{-D}, or @samp{-r}.
1340 @item -m @var{machine}
1341 @itemx --architecture=@var{machine}
1342 @cindex architecture
1343 @cindex disassembly architecture
1344 Specify the architecture to use when disassembling object files. This
1345 can be useful when disassembling object files which do not describe
1346 architecture information, such as S-records. You can list the available
1347 architectures with the @samp{-i} option.
1349 @item -M @var{options}
1350 @itemx --disassembler-options=@var{options}
1351 Pass target specific information to the disassembler. Only supported on
1354 If the target is an ARM architecture then this switch can be used to
1355 select which register name set is used during disassembler. Specifying
1356 @samp{-M reg-name-std} (the default) will select the register names as
1357 used in ARM's instruction set documentation, but with register 13 called
1358 'sp', register 14 called 'lr' and register 15 called 'pc'. Specifying
1359 @samp{-M reg-names-apcs} will select the name set used by the ARM
1360 Procedure Call Standard, whilst specifying @samp{-M reg-names-raw} will
1361 just use @samp{r} followed by the register number.
1363 There are also two variants on the APCS register naming scheme enabled
1364 by @samp{-M reg-names-atpcs} and @samp{-M reg-names-atpcs-special} which
1365 use the ARM/Thumb Procedure Call Standard naming conventions. (Eiuther
1366 with the normal register name sor the special register names).
1368 This option can also be used for ARM architectures to force the
1369 disassembler to interpret all instructions as THUMB instructions by
1370 using the switch @samp{--disassembler-options=force-thumb}. This can be
1371 useful when attempting to disassemble thumb code produced by other
1375 @itemx --private-headers
1376 Print information that is specific to the object file format. The exact
1377 information printed depends upon the object file format. For some
1378 object file formats, no additional information is printed.
1382 @cindex relocation entries, in object file
1383 Print the relocation entries of the file. If used with @samp{-d} or
1384 @samp{-D}, the relocations are printed interspersed with the
1388 @itemx --dynamic-reloc
1389 @cindex dynamic relocation entries, in object file
1390 Print the dynamic relocation entries of the file. This is only
1391 meaningful for dynamic objects, such as certain types of shared
1395 @itemx --full-contents
1396 @cindex sections, full contents
1397 @cindex object file sections
1398 Display the full contents of any sections requested.
1402 @cindex source disassembly
1403 @cindex disassembly, with source
1404 Display source code intermixed with disassembly, if possible. Implies
1407 @item --show-raw-insn
1408 When disassembling instructions, print the instruction in hex as well as
1409 in symbolic form. This is the default except when
1410 @code{--prefix-addresses} is used.
1412 @item --no-show-raw-insn
1413 When disassembling instructions, do not print the instruction bytes.
1414 This is the default when @code{--prefix-addresses} is used.
1420 @cindex debug symbols
1421 @cindex ELF object file format
1422 Display the full contents of any sections requested. Display the
1423 contents of the .stab and .stab.index and .stab.excl sections from an
1424 ELF file. This is only useful on systems (such as Solaris 2.0) in which
1425 @code{.stab} debugging symbol-table entries are carried in an ELF
1426 section. In most other file formats, debugging symbol-table entries are
1427 interleaved with linkage symbols, and are visible in the @samp{--syms}
1428 output. For more information on stabs symbols, see @ref{Top,Stabs,Stabs
1429 Overview,stabs.info, The ``stabs'' debug format}.
1431 @item --start-address=@var{address}
1432 @cindex start-address
1433 Start displaying data at the specified address. This affects the output
1434 of the @code{-d}, @code{-r} and @code{-s} options.
1436 @item --stop-address=@var{address}
1437 @cindex stop-address
1438 Stop displaying data at the specified address. This affects the output
1439 of the @code{-d}, @code{-r} and @code{-s} options.
1443 @cindex symbol table entries, printing
1444 Print the symbol table entries of the file.
1445 This is similar to the information provided by the @samp{nm} program.
1448 @itemx --dynamic-syms
1449 @cindex dynamic symbol table entries, printing
1450 Print the dynamic symbol table entries of the file. This is only
1451 meaningful for dynamic objects, such as certain types of shared
1452 libraries. This is similar to the information provided by the @samp{nm}
1453 program when given the @samp{-D} (@samp{--dynamic}) option.
1456 Print the version number of @code{objdump} and exit.
1460 @cindex all header information, object file
1461 @cindex header information, all
1462 Display all available header information, including the symbol table and
1463 relocation entries. Using @samp{-x} is equivalent to specifying all of
1464 @samp{-a -f -h -r -t}.
1468 @cindex wide output, printing
1469 Format some lines for output devices that have more than 80 columns.
1476 @cindex archive contents
1477 @cindex symbol index
1480 ranlib [-vV] @var{archive}
1483 @code{ranlib} generates an index to the contents of an archive and
1484 stores it in the archive. The index lists each symbol defined by a
1485 member of an archive that is a relocatable object file.
1487 You may use @samp{nm -s} or @samp{nm --print-armap} to list this index.
1489 An archive with such an index speeds up linking to the library and
1490 allows routines in the library to call each other without regard to
1491 their placement in the archive.
1493 The @sc{gnu} @code{ranlib} program is another form of @sc{gnu} @code{ar}; running
1494 @code{ranlib} is completely equivalent to executing @samp{ar -s}.
1501 Show the version number of @code{ranlib}.
1508 @cindex section sizes
1511 size [ -A | -B | --format=@var{compatibility} ]
1512 [ --help ] [ -d | -o | -x | --radix=@var{number} ]
1513 [ --target=@var{bfdname} ] [ -V | --version ]
1514 [ @var{objfile}@dots{} ]
1517 The @sc{gnu} @code{size} utility lists the section sizes---and the total
1518 size---for each of the object or archive files @var{objfile} in its
1519 argument list. By default, one line of output is generated for each
1520 object file or each module in an archive.
1522 @var{objfile}@dots{} are the object files to be examined.
1523 If none are specified, the file @code{a.out} will be used.
1525 The command line options have the following meanings:
1530 @itemx --format=@var{compatibility}
1531 @cindex @code{size} display format
1532 Using one of these options, you can choose whether the output from @sc{gnu}
1533 @code{size} resembles output from System V @code{size} (using @samp{-A},
1534 or @samp{--format=sysv}), or Berkeley @code{size} (using @samp{-B}, or
1535 @samp{--format=berkeley}). The default is the one-line format similar to
1537 @c Bonus for doc-source readers: you can also say --format=strange (or
1538 @c anything else that starts with 's') for sysv, and --format=boring (or
1539 @c anything else that starts with 'b') for Berkeley.
1541 Here is an example of the Berkeley (default) format of output from
1544 $ size --format=Berkeley ranlib size
1545 text data bss dec hex filename
1546 294880 81920 11592 388392 5ed28 ranlib
1547 294880 81920 11888 388688 5ee50 size
1551 This is the same data, but displayed closer to System V conventions:
1554 $ size --format=SysV ranlib size
1572 Show a summary of acceptable arguments and options.
1577 @itemx --radix=@var{number}
1578 @cindex @code{size} number format
1579 @cindex radix for section sizes
1580 Using one of these options, you can control whether the size of each
1581 section is given in decimal (@samp{-d}, or @samp{--radix=10}); octal
1582 (@samp{-o}, or @samp{--radix=8}); or hexadecimal (@samp{-x}, or
1583 @samp{--radix=16}). In @samp{--radix=@var{number}}, only the three
1584 values (8, 10, 16) are supported. The total size is always given in two
1585 radices; decimal and hexadecimal for @samp{-d} or @samp{-x} output, or
1586 octal and hexadecimal if you're using @samp{-o}.
1588 @item --target=@var{bfdname}
1589 @cindex object code format
1590 Specify that the object-code format for @var{objfile} is
1591 @var{bfdname}. This option may not be necessary; @code{size} can
1592 automatically recognize many formats.
1593 @xref{Target Selection}, for more information.
1597 Display the version number of @code{size}.
1603 @cindex listings strings
1604 @cindex printing strings
1605 @cindex strings, printing
1608 strings [-afov] [-@var{min-len}] [-n @var{min-len}] [-t @var{radix}] [-]
1609 [--all] [--print-file-name] [--bytes=@var{min-len}]
1610 [--radix=@var{radix}] [--target=@var{bfdname}]
1611 [--help] [--version] @var{file}@dots{}
1614 For each @var{file} given, @sc{gnu} @code{strings} prints the printable
1615 character sequences that are at least 4 characters long (or the number
1616 given with the options below) and are followed by an unprintable
1617 character. By default, it only prints the strings from the initialized
1618 and loaded sections of object files; for other types of files, it prints
1619 the strings from the whole file.
1621 @code{strings} is mainly useful for determining the contents of non-text
1628 Do not scan only the initialized and loaded sections of object files;
1629 scan the whole files.
1632 @itemx --print-file-name
1633 Print the name of the file before each string.
1636 Print a summary of the program usage on the standard output and exit.
1638 @item -@var{min-len}
1639 @itemx -n @var{min-len}
1640 @itemx --bytes=@var{min-len}
1641 Print sequences of characters that are at least @var{min-len} characters
1642 long, instead of the default 4.
1645 Like @samp{-t o}. Some other versions of @code{strings} have @samp{-o}
1646 act like @samp{-t d} instead. Since we can not be compatible with both
1647 ways, we simply chose one.
1649 @item -t @var{radix}
1650 @itemx --radix=@var{radix}
1651 Print the offset within the file before each string. The single
1652 character argument specifies the radix of the offset---@samp{o} for
1653 octal, @samp{x} for hexadecimal, or @samp{d} for decimal.
1655 @item --target=@var{bfdname}
1656 @cindex object code format
1657 Specify an object code format other than your system's default format.
1658 @xref{Target Selection}, for more information.
1662 Print the program version number on the standard output and exit.
1669 @cindex removing symbols
1670 @cindex discarding symbols
1671 @cindex symbols, discarding
1674 strip [ -F @var{bfdname} | --target=@var{bfdname} ]
1675 [ -I @var{bfdname} | --input-target=@var{bfdname} ]
1676 [ -O @var{bfdname} | --output-target=@var{bfdname} ]
1677 [ -s | --strip-all ] [ -S | -g | --strip-debug ]
1678 [ -K @var{symbolname} | --keep-symbol=@var{symbolname} ]
1679 [ -N @var{symbolname} | --strip-symbol=@var{symbolname} ]
1680 [ -x | --discard-all ] [ -X | --discard-locals ]
1681 [ -R @var{sectionname} | --remove-section=@var{sectionname} ]
1682 [ -o @var{file} ] [ -p | --preserve-dates ]
1683 [ -v | --verbose ] [ -V | --version ] [ --help ]
1684 @var{objfile}@dots{}
1687 @sc{gnu} @code{strip} discards all symbols from object files
1688 @var{objfile}. The list of object files may include archives.
1689 At least one object file must be given.
1691 @code{strip} modifies the files named in its argument,
1692 rather than writing modified copies under different names.
1695 @item -F @var{bfdname}
1696 @itemx --target=@var{bfdname}
1697 Treat the original @var{objfile} as a file with the object
1698 code format @var{bfdname}, and rewrite it in the same format.
1699 @xref{Target Selection}, for more information.
1702 Show a summary of the options to @code{strip} and exit.
1704 @item -I @var{bfdname}
1705 @itemx --input-target=@var{bfdname}
1706 Treat the original @var{objfile} as a file with the object
1707 code format @var{bfdname}.
1708 @xref{Target Selection}, for more information.
1710 @item -O @var{bfdname}
1711 @itemx --output-target=@var{bfdname}
1712 Replace @var{objfile} with a file in the output format @var{bfdname}.
1713 @xref{Target Selection}, for more information.
1715 @item -R @var{sectionname}
1716 @itemx --remove-section=@var{sectionname}
1717 Remove any section named @var{sectionname} from the output file. This
1718 option may be given more than once. Note that using this option
1719 inappropriately may make the output file unusable.
1727 @itemx --strip-debug
1728 Remove debugging symbols only.
1730 @item --strip-unneeded
1731 Remove all symbols that are not needed for relocation processing.
1733 @item -K @var{symbolname}
1734 @itemx --keep-symbol=@var{symbolname}
1735 Keep only symbol @var{symbolname} from the source file. This option may
1736 be given more than once.
1738 @item -N @var{symbolname}
1739 @itemx --strip-symbol=@var{symbolname}
1740 Remove symbol @var{symbolname} from the source file. This option may be
1741 given more than once, and may be combined with strip options other than
1745 Put the stripped output in @var{file}, rather than replacing the
1746 existing file. When this argument is used, only one @var{objfile}
1747 argument may be specified.
1750 @itemx --preserve-dates
1751 Preserve the access and modification dates of the file.
1754 @itemx --discard-all
1755 Remove non-global symbols.
1758 @itemx --discard-locals
1759 Remove compiler-generated local symbols.
1760 (These usually start with @samp{L} or @samp{.}.)
1764 Show the version number for @code{strip}.
1768 Verbose output: list all object files modified. In the case of
1769 archives, @samp{strip -v} lists all members of the archive.
1772 @node c++filt, addr2line, strip, Top
1776 @cindex demangling C++ symbols
1779 c++filt [ -_ | --strip-underscores ]
1781 [ -n | --no-strip-underscores ]
1782 [ -s @var{format} | --format=@var{format} ]
1783 [ --help ] [ --version ] [ @var{symbol}@dots{} ]
1787 The C++ and Java languages provides function overloading, which means
1788 that you can write many functions with the same name (providing each
1789 takes parameters of different types). All C++ and Java function names
1790 are encoded into a low-level assembly label (this process is known as
1791 @dfn{mangling}). The @code{c++filt}
1792 @footnote{MS-DOS does not allow @kbd{+} characters in file names, so on
1793 MS-DOS this program is named @code{cxxfilt}.}
1794 program does the inverse mapping: it decodes (@dfn{demangles}) low-level
1795 names into user-level names so that the linker can keep these overloaded
1796 functions from clashing.
1798 Every alphanumeric word (consisting of letters, digits, underscores,
1799 dollars, or periods) seen in the input is a potential label. If the
1800 label decodes into a C++ name, the C++ name replaces the low-level
1803 You can use @code{c++filt} to decipher individual symbols:
1806 c++filt @var{symbol}
1809 If no @var{symbol} arguments are given, @code{c++filt} reads symbol
1810 names from the standard input and writes the demangled names to the
1811 standard output. All results are printed on the standard output.
1815 @itemx --strip-underscores
1816 On some systems, both the C and C++ compilers put an underscore in front
1817 of every name. For example, the C name @code{foo} gets the low-level
1818 name @code{_foo}. This option removes the initial underscore. Whether
1819 @code{c++filt} removes the underscore by default is target dependent.
1823 Prints demangled names using Java syntax. The default is to use C++
1827 @itemx --no-strip-underscores
1828 Do not remove the initial underscore.
1830 @item -s @var{format}
1831 @itemx --format=@var{format}
1832 @sc{gnu} @code{nm} can decode three different methods of mangling, used by
1833 different C++ compilers. The argument to this option selects which
1838 the one used by the @sc{gnu} compiler (the default method)
1840 the one used by the Lucid compiler
1842 the one specified by the C++ Annotated Reference Manual
1844 the one used by the HP compiler
1846 the one used by the EDG compiler
1850 Print a summary of the options to @code{c++filt} and exit.
1853 Print the version number of @code{c++filt} and exit.
1857 @emph{Warning:} @code{c++filt} is a new utility, and the details of its
1858 user interface are subject to change in future releases. In particular,
1859 a command-line option may be required in the the future to decode a name
1860 passed as an argument on the command line; in other words,
1863 c++filt @var{symbol}
1867 may in a future release become
1870 c++filt @var{option} @var{symbol}
1878 @cindex address to file name and line number
1881 addr2line [ -b @var{bfdname} | --target=@var{bfdname} ]
1883 [ -e @var{filename} | --exe=@var{filename} ]
1884 [ -f | --functions ] [ -s | --basename ]
1885 [ -H | --help ] [ -V | --version ]
1889 @code{addr2line} translates program addresses into file names and line
1890 numbers. Given an address and an executable, it uses the debugging
1891 information in the executable to figure out which file name and line
1892 number are associated with a given address.
1894 The executable to use is specified with the @code{-e} option. The
1895 default is the file @file{a.out}.
1897 @code{addr2line} has two modes of operation.
1899 In the first, hexadecimal addresses are specified on the command line,
1900 and @code{addr2line} displays the file name and line number for each
1903 In the second, @code{addr2line} reads hexadecimal addresses from
1904 standard input, and prints the file name and line number for each
1905 address on standard output. In this mode, @code{addr2line} may be used
1906 in a pipe to convert dynamically chosen addresses.
1908 The format of the output is @samp{FILENAME:LINENO}. The file name and
1909 line number for each address is printed on a separate line. If the
1910 @code{-f} option is used, then each @samp{FILENAME:LINENO} line is
1911 preceded by a @samp{FUNCTIONNAME} line which is the name of the function
1912 containing the address.
1914 If the file name or function name can not be determined,
1915 @code{addr2line} will print two question marks in their place. If the
1916 line number can not be determined, @code{addr2line} will print 0.
1918 The long and short forms of options, shown here as alternatives, are
1922 @item -b @var{bfdname}
1923 @itemx --target=@var{bfdname}
1924 @cindex object code format
1925 Specify that the object-code format for the object files is
1930 @cindex demangling in objdump
1931 Decode (@dfn{demangle}) low-level symbol names into user-level names.
1932 Besides removing any initial underscore prepended by the system, this
1933 makes C++ function names readable. @xref{c++filt}, for more information
1936 @item -e @var{filename}
1937 @itemx --exe=@var{filename}
1938 Specify the name of the executable for which addresses should be
1939 translated. The default file is @file{a.out}.
1943 Display function names as well as file and line number information.
1947 Display only the base of each file name.
1953 @code{nlmconv} converts a relocatable object file into a NetWare
1957 @code{nlmconv} currently works with @samp{i386} object
1958 files in @code{coff}, @sc{elf}, or @code{a.out} format, and @sc{SPARC}
1959 object files in @sc{elf}, or @code{a.out} format@footnote{
1960 @code{nlmconv} should work with any @samp{i386} or @sc{sparc} object
1961 format in the Binary File Descriptor library. It has only been tested
1962 with the above formats.}.
1966 @emph{Warning:} @code{nlmconv} is not always built as part of the binary
1967 utilities, since it is only useful for NLM targets.
1971 nlmconv [ -I @var{bfdname} | --input-target=@var{bfdname} ]
1972 [ -O @var{bfdname} | --output-target=@var{bfdname} ]
1973 [ -T @var{headerfile} | --header-file=@var{headerfile} ]
1974 [ -d | --debug] [ -l @var{linker} | --linker=@var{linker} ]
1975 [ -h | --help ] [ -V | --version ]
1976 @var{infile} @var{outfile}
1979 @code{nlmconv} converts the relocatable @samp{i386} object file
1980 @var{infile} into the NetWare Loadable Module @var{outfile}, optionally
1981 reading @var{headerfile} for NLM header information. For instructions
1982 on writing the NLM command file language used in header files, see the
1983 @samp{linkers} section, @samp{NLMLINK} in particular, of the @cite{NLM
1984 Development and Tools Overview}, which is part of the NLM Software
1985 Developer's Kit (``NLM SDK''), available from Novell, Inc.
1986 @code{nlmconv} uses the @sc{gnu} Binary File Descriptor library to read
1987 @var{infile}; see @ref{BFD,,BFD,ld.info,Using LD}, for
1990 @code{nlmconv} can perform a link step. In other words, you can list
1991 more than one object file for input if you list them in the definitions
1992 file (rather than simply specifying one input file on the command line).
1993 In this case, @code{nlmconv} calls the linker for you.
1996 @item -I @var{bfdname}
1997 @itemx --input-target=@var{bfdname}
1998 Object format of the input file. @code{nlmconv} can usually determine
1999 the format of a given file (so no default is necessary).
2000 @xref{Target Selection}, for more information.
2002 @item -O @var{bfdname}
2003 @itemx --output-target=@var{bfdname}
2004 Object format of the output file. @code{nlmconv} infers the output
2005 format based on the input format, e.g. for a @samp{i386} input file the
2006 output format is @samp{nlm32-i386}.
2007 @xref{Target Selection}, for more information.
2009 @item -T @var{headerfile}
2010 @itemx --header-file=@var{headerfile}
2011 Reads @var{headerfile} for NLM header information. For instructions on
2012 writing the NLM command file language used in header files, see@ see the
2013 @samp{linkers} section, of the @cite{NLM Development and Tools
2014 Overview}, which is part of the NLM Software Developer's Kit, available
2019 Displays (on standard error) the linker command line used by @code{nlmconv}.
2021 @item -l @var{linker}
2022 @itemx --linker=@var{linker}
2023 Use @var{linker} for any linking. @var{linker} can be an absolute or a
2028 Prints a usage summary.
2032 Prints the version number for @code{nlmconv}.
2038 @code{windres} may be used to manipulate Windows resources.
2041 @emph{Warning:} @code{windres} is not always built as part of the binary
2042 utilities, since it is only useful for Windows targets.
2046 windres [options] [input-file] [output-file]
2049 @code{windres} reads resources from an input file and copies them into
2050 an output file. Either file may be in one of three formats:
2054 A text format read by the Resource Compiler.
2057 A binary format generated by the Resource Compiler.
2060 A COFF object or executable.
2063 The exact description of these different formats is available in
2064 documentation from Microsoft.
2066 When @code{windres} converts from the @code{rc} format to the @code{res}
2067 format, it is acting like the Windows Resource Compiler. When
2068 @code{windres} converts from the @code{res} format to the @code{coff}
2069 format, it is acting like the Windows @code{CVTRES} program.
2071 When @code{windres} generates an @code{rc} file, the output is similar
2072 but not identical to the format expected for the input. When an input
2073 @code{rc} file refers to an external filename, an output @code{rc} file
2074 will instead include the file contents.
2076 If the input or output format is not specified, @code{windres} will
2077 guess based on the file name, or, for the input file, the file contents.
2078 A file with an extension of @file{.rc} will be treated as an @code{rc}
2079 file, a file with an extension of @file{.res} will be treated as a
2080 @code{res} file, and a file with an extension of @file{.o} or
2081 @file{.exe} will be treated as a @code{coff} file.
2083 If no output file is specified, @code{windres} will print the resources
2084 in @code{rc} format to standard output.
2086 The normal use is for you to write an @code{rc} file, use @code{windres}
2087 to convert it to a COFF object file, and then link the COFF file into
2088 your application. This will make the resources described in the
2089 @code{rc} file available to Windows.
2092 @item -i @var{filename}
2093 @itemx --input @var{filename}
2094 The name of the input file. If this option is not used, then
2095 @code{windres} will use the first non-option argument as the input file
2096 name. If there are no non-option arguments, then @code{windres} will
2097 read from standard input. @code{windres} can not read a COFF file from
2100 @item -o @var{filename}
2101 @itemx --output @var{filename}
2102 The name of the output file. If this option is not used, then
2103 @code{windres} will use the first non-option argument, after any used
2104 for the input file name, as the output file name. If there is no
2105 non-option argument, then @code{windres} will write to standard output.
2106 @code{windres} can not write a COFF file to standard output.
2108 @item -I @var{format}
2109 @itemx --input-format @var{format}
2110 The input format to read. @var{format} may be @samp{res}, @samp{rc}, or
2111 @samp{coff}. If no input format is specified, @code{windres} will
2112 guess, as described above.
2114 @item -O @var{format}
2115 @itemx --output-format @var{format}
2116 The output format to generate. @var{format} may be @samp{res},
2117 @samp{rc}, or @samp{coff}. If no output format is specified,
2118 @code{windres} will guess, as described above.
2120 @item -F @var{target}
2121 @itemx --target @var{target}
2122 Specify the BFD format to use for a COFF file as input or output. This
2123 is a BFD target name; you can use the @code{--help} option to see a list
2124 of supported targets. Normally @code{windres} will use the default
2125 format, which is the first one listed by the @code{--help} option.
2126 @ref{Target Selection}.
2128 @item --preprocessor @var{program}
2129 When @code{windres} reads an @code{rc} file, it runs it through the C
2130 preprocessor first. This option may be used to specify the preprocessor
2131 to use, including any leading arguments. The default preprocessor
2132 argument is @code{gcc -E -xc-header -DRC_INVOKED}.
2134 @item --include-dir @var{directory}
2135 Specify an include directory to use when reading an @code{rc} file.
2136 @code{windres} will pass this to the preprocessor as an @code{-I}
2137 option. @code{windres} will also search this directory when looking for
2138 files named in the @code{rc} file.
2140 @item -D @var{target}
2141 @itemx --define @var{sym}[=@var{val}]
2142 Specify a @code{-D} option to pass to the preprocessor when reading an
2146 Enable verbose mode. This tells you what the preprocessor is if you
2149 @item --language @var{val}
2150 Specify the default language to use when reading an @code{rc} file.
2151 @var{val} should be a hexadecimal language code. The low eight bits are
2152 the language, and the high eight bits are the sublanguage.
2154 @item --use-temp-file
2155 Use a temporary file to instead of using popen to read the output of
2156 the preprocessor. Use this option if the popen implementation is buggy
2157 on the host (eg., certain non-English language versions of Windows 95 and
2158 Windows 98 are known to have buggy popen where the output will instead
2161 @item --no-use-temp-file
2162 Use popen, not a temporary file, to read the output of the preprocessor.
2163 This is the default behaviour.
2166 Prints a usage summary.
2169 Prints the version number for @code{windres}.
2172 If @code{windres} is compiled with @code{YYDEBUG} defined as @code{1},
2173 this will turn on parser debugging.
2178 @chapter Create files needed to build and use DLLs
2182 @code{dlltool} may be used to create the files needed to build and use
2183 dynamic link libraries (DLLs).
2186 @emph{Warning:} @code{dlltool} is not always built as part of the binary
2187 utilities, since it is only useful for those targets which support DLLs.
2191 dlltool [-d|--input-def @var{def-file-name}]
2192 [-b|--base-file @var{base-file-name}]
2193 [-e|--output-exp @var{exports-file-name}]
2194 [-z|--output-def @var{def-file-name}]
2195 [-l|--output-lib @var{library-file-name}]
2196 [--export-all-symbols] [--no-export-all-symbols]
2197 [--exclude-symbols @var{list}]
2198 [--no-default-excludes]
2199 [-S|--as @var{path-to-assembler}] [-f|--as-flags @var{options}]
2200 [-D|--dllname @var{name}] [-m|--machine @var{machine}]
2201 [-a|--add-indirect] [-U|--add-underscore] [-k|--kill-at]
2202 [-A|--add-stdcall-alias]
2203 [-x|--no-idata4] [-c|--no-idata5] [-i|--interwork]
2204 [-n|--nodelete] [-v|--verbose] [-h|--help] [-V|--version]
2205 [object-file @dots{}]
2208 @code{dlltool} reads its inputs, which can come from the @samp{-d} and
2209 @samp{-b} options as well as object files specified on the command
2210 line. It then processes these inputs and if the @samp{-e} option has
2211 been specified it creates a exports file. If the @samp{-l} option
2212 has been specified it creates a library file and if the @samp{-z} option
2213 has been specified it creates a def file. Any or all of the -e, -l
2214 and -z options can be present in one invocation of dlltool.
2216 When creating a DLL, along with the source for the DLL, it is necessary
2217 to have three other files. @code{dlltool} can help with the creation of
2220 The first file is a @samp{.def} file which specifies which functions are
2221 exported from the DLL, which functions the DLL imports, and so on. This
2222 is a text file and can be created by hand, or @code{dlltool} can be used
2223 to create it using the @samp{-z} option. In this case @code{dlltool}
2224 will scan the object files specified on its command line looking for
2225 those functions which have been specially marked as being exported and
2226 put entries for them in the .def file it creates.
2228 In order to mark a function as being exported from a DLL, it needs to
2229 have an @samp{-export:<name_of_function>} entry in the @samp{.drectve}
2230 section of the object file. This can be done in C by using the
2234 asm (".section .drectve");
2235 asm (".ascii \"-export:my_func\"");
2237 int my_func (void) @{ @dots{} @}
2240 The second file needed for DLL creation is an exports file. This file
2241 is linked with the object files that make up the body of the DLL and it
2242 handles the interface between the DLL and the outside world. This is a
2243 binary file and it can be created by giving the @samp{-e} option to
2244 @code{dlltool} when it is creating or reading in a .def file.
2246 The third file needed for DLL creation is the library file that programs
2247 will link with in order to access the functions in the DLL. This file
2248 can be created by giving the @samp{-l} option to dlltool when it
2249 is creating or reading in a .def file.
2251 @code{dlltool} builds the library file by hand, but it builds the
2252 exports file by creating temporary files containing assembler statements
2253 and then assembling these. The @samp{-S} command line option can be
2254 used to specify the path to the assembler that dlltool will use,
2255 and the @samp{-f} option can be used to pass specific flags to that
2256 assembler. The @samp{-n} can be used to prevent dlltool from deleting
2257 these temporary assembler files when it is done, and if @samp{-n} is
2258 specified twice then this will prevent dlltool from deleting the
2259 temporary object files it used to build the library.
2261 Here is an example of creating a DLL from a source file @samp{dll.c} and
2262 also creating a program (from an object file called @samp{program.o})
2267 dlltool -e exports.o -l dll.lib dll.o
2268 gcc dll.o exports.o -o dll.dll
2269 gcc program.o dll.lib -o program
2272 The command line options have the following meanings:
2276 @item -d @var{filename}
2277 @itemx --input-def @var{filename}
2278 @cindex input .def file
2279 Specifies the name of a .def file to be read in and processed.
2281 @item -b @var{filename}
2282 @itemx --base-file @var{filename}
2284 Specifies the name of a base file to be read in and processed. The
2285 contents of this file will be added to the relocation section in the
2286 exports file generated by dlltool.
2288 @item -e @var{filename}
2289 @itemx --output-exp @var{filename}
2290 Specifies the name of the export file to be created by dlltool.
2292 @item -z @var{filename}
2293 @itemx --output-def @var{filename}
2294 Specifies the name of the .def file to be created by dlltool.
2296 @item -l @var{filename}
2297 @itemx --output-lib @var{filename}
2298 Specifies the name of the library file to be created by dlltool.
2300 @item --export-all-symbols
2301 Treat all global and weak defined symbols found in the input object
2302 files as symbols to be exported. There is a small list of symbols which
2303 are not exported by default; see the @code{--no-default-excludes}
2304 option. You may add to the list of symbols to not export by using the
2305 @code{--exclude-symbols} option.
2307 @item --no-export-all-symbols
2308 Only export symbols explicitly listed in an input .def file or in
2309 @samp{.drectve} sections in the input object files. This is the default
2310 behaviour. The @samp{.drectve} sections are created by @samp{dllexport}
2311 attributes in the source code.
2313 @item --exclude-symbols @var{list}
2314 Do not export the symbols in @var{list}. This is a list of symbol names
2315 separated by comma or colon characters. The symbol names should not
2316 contain a leading underscore. This is only meaningful when
2317 @code{--export-all-symbols} is used.
2319 @item --no-default-excludes
2320 When @code{--export-all-symbols} is used, it will by default avoid
2321 exporting certain special symbols. The current list of symbols to avoid
2322 exporting is @samp{DllMain@@12}, @samp{DllEntryPoint@@0},
2323 @samp{impure_ptr}. You may use the @code{--no-default-excludes} option
2324 to go ahead and export these special symbols. This is only meaningful
2325 when @code{--export-all-symbols} is used.
2328 @itemx --as @var{path}
2329 Specifies the path, including the filename, of the assembler to be used
2330 to create the exports file.
2332 @item -f @var{switches}
2333 @itemx --as-flags @var{switches}
2334 Specifies any specific command line switches to be passed to the
2335 assembler when building the exports file. This option will work even if
2336 the @samp{-S} option is not used. This option only takes one argument,
2337 and if it occurs more than once on the command line, then later
2338 occurrences will override earlier occurrences. So if it is necessary to
2339 pass multiple switches to the assembler they should be enclosed in
2343 @itemx --dll-name @var{name}
2344 Specifies the name to be stored in the .def file as the name of the DLL
2345 when the @samp{-e} option is used. If this option is not present, then
2346 the filename given to the @samp{-e} option will be used as the name of
2349 @item -m @var{machine}
2350 @itemx -machine @var{machine}
2351 Specifies the type of machine for which the library file should be
2352 built. @code{dlltool} has a built in default type, depending upon how
2353 it was created, but this option can be used to override that. This is
2354 normally only useful when creating DLLs for an ARM processor, when the
2355 contents of the DLL are actually encode using THUMB instructions.
2358 @itemx --add-indirect
2359 Specifies that when @code{dlltool} is creating the exports file it
2360 should add a section which allows the exported functions to be
2361 referenced without using the import library. Whatever the hell that
2365 @itemx --add-underscore
2366 Specifies that when @code{dlltool} is creating the exports file it
2367 should prepend an underscore to the names of the exported functions.
2371 Specifies that when @code{dlltool} is creating the exports file it
2372 should not append the string @samp{@@ <number>}. These numbers are
2373 called ordinal numbers and they represent another way of accessing the
2374 function in a DLL, other than by name.
2377 @itemx --add-stdcall-alias
2378 Specifies that when @code{dlltool} is creating the exports file it
2379 should add aliases for stdcall symbols without @samp{@@ <number>}
2380 in addition to the symbols with @samp{@@ <number>}.
2384 Specifies that when @code{dlltool} is creating the exports and library
2385 files it should omit the .idata4 section. This is for compatibility
2386 with certain operating systems.
2390 Specifies that when @code{dlltool} is creating the exports and library
2391 files it should omit the .idata5 section. This is for compatibility
2392 with certain operating systems.
2396 Specifies that @code{dlltool} should mark the objects in the library
2397 file and exports file that it produces as supporting interworking
2398 between ARM and THUMB code.
2402 Makes @code{dlltool} preserve the temporary assembler files it used to
2403 create the exports file. If this option is repeated then dlltool will
2404 also preserve the temporary object files it uses to create the library
2409 Make dlltool describe what it is doing.
2413 Displays a list of command line options and then exits.
2417 Displays dlltool's version number and then exits.
2424 @cindex ELF file information
2428 readelf [ -a | --all ]
2429 [ -h | --file-header]
2430 [ -l | --program-headers | --segments]
2431 [ -S | --section-headers | --sections]
2433 [ -s | --syms | --symbols]
2437 [ -V | --version-info]
2438 [ -D | --use-dynamic]
2439 [ -x <number> | --hex-dump=<number>]
2440 [ -w[liapr] | --debug-dump[=info,=line,=abbrev,=pubnames,=ranges]]
2444 @var{elffile}@dots{}
2447 @code{readelf} displays information about one or more ELF format object
2448 files. The options control what particular information to display.
2450 @var{elffile}@dots{} are the object files to be examined. At the
2451 moment, @code{readelf} does not support examining archives, nor does it
2452 support examing 64 bit ELF files.
2454 The long and short forms of options, shown here as alternatives, are
2455 equivalent. At least one option besides @samp{-v} or @samp{-H} must be
2461 Equivalent to specifiying @samp{--file-header},
2462 @samp{--program-headers}, @samp{--sections}, @samp{--symbols},
2463 @samp{--relocs}, @samp{--dynamic}, @samp{--notes} and
2464 @samp{--version-info}.
2467 @itemx --file-header
2468 @cindex ELF file header information
2469 Displays the information contained in the ELF header at the start of the
2473 @itemx --program-headers
2475 @cindex ELF program header information
2476 @cindex ELF segment information
2477 Displays the information contained in the file's segment headers, if it
2482 @itemx --section-headers
2483 @cindex ELF section information
2484 Displays the information contained in the file's section headers, if it
2490 @cindex ELF symbol table information
2491 Displays the entries in symbol table section of the file, if it has one.
2495 Display all the headers in the file. Equivalent to @samp{-h -l -S}.
2499 @cindex ELF core notes
2500 Displays the contents of the NOTE segment, if it exists.
2504 @cindex ELF reloc information
2505 Displays the contents of the file's relocation section, if it ha one.
2509 @cindex ELF dynamic section information
2510 Displays the contents of the file's dynamic section, if it has one.
2513 @itemx --version-info
2514 @cindex ELF version sections informations
2515 Displays the contents of the version sections in the file, it they
2519 @itemx --use-dynamic
2520 When displaying symbols, this option makes @code{readelf} use the
2521 symblol table in the file's dynamic section, rather than the one in the
2525 @itemx --hex-dump=<number>
2526 Displays the contents of the indicated section as a hexadecimal dump.
2529 @itemx --debug-dump[=line,=info,=abbrev,=pubnames,=ranges]
2530 Displays the contents of the debug sections in the file, if any are
2531 present. If one of the optional letters or words follows the switch
2532 then only data found in those specific sections will be dumped.
2535 Display a histogram of bucket list lengths when displaying the contents
2536 of the symbol tables.
2540 Display the version number of readelf.
2544 Display the command line options understood by @code{readelf}.
2549 @node Selecting The Target System
2550 @chapter Selecting the target system
2552 You can specify three aspects of the target system to the @sc{gnu}
2553 binary file utilities, each in several ways:
2563 the linker emulation (which applies to the linker only)
2566 In the following summaries, the lists of ways to specify values are in
2567 order of decreasing precedence. The ways listed first override those
2570 The commands to list valid values only list the values for which the
2571 programs you are running were configured. If they were configured with
2572 @samp{--enable-targets=all}, the commands list most of the available
2573 values, but a few are left out; not all targets can be configured in at
2574 once because some of them can only be configured @dfn{native} (on hosts
2575 with the same type as the target system).
2578 * Target Selection::
2579 * Architecture Selection::
2580 * Linker Emulation Selection::
2583 @node Target Selection
2584 @section Target Selection
2586 A @dfn{target} is an object file format. A given target may be
2587 supported for multiple architectures (@pxref{Architecture Selection}).
2588 A target selection may also have variations for different operating
2589 systems or architectures.
2591 The command to list valid target values is @samp{objdump -i}
2592 (the first column of output contains the relevant information).
2594 Some sample values are: @samp{a.out-hp300bsd}, @samp{ecoff-littlemips},
2595 @samp{a.out-sunos-big}.
2597 You can also specify a target using a configuration triplet. This is
2598 the same sort of name that is passed to @file{configure} to specify a
2599 target. When you use a configuration triplet as an argument, it must be
2600 fully canonicalized. You can see the canonical version of a triplet by
2601 running the shell script @file{config.sub} which is included with the
2604 Some sample configuration triplets are: @samp{m68k-hp-bsd},
2605 @samp{mips-dec-ultrix}, @samp{sparc-sun-sunos}.
2607 @subheading @code{objdump} Target
2613 command line option: @samp{-b} or @samp{--target}
2616 environment variable @code{GNUTARGET}
2619 deduced from the input file
2622 @subheading @code{objcopy} and @code{strip} Input Target
2628 command line options: @samp{-I} or @samp{--input-target}, or @samp{-F} or @samp{--target}
2631 environment variable @code{GNUTARGET}
2634 deduced from the input file
2637 @subheading @code{objcopy} and @code{strip} Output Target
2643 command line options: @samp{-O} or @samp{--output-target}, or @samp{-F} or @samp{--target}
2646 the input target (see ``@code{objcopy} and @code{strip} Input Target'' above)
2649 environment variable @code{GNUTARGET}
2652 deduced from the input file
2655 @subheading @code{nm}, @code{size}, and @code{strings} Target
2661 command line option: @samp{--target}
2664 environment variable @code{GNUTARGET}
2667 deduced from the input file
2670 @subheading Linker Input Target
2676 command line option: @samp{-b} or @samp{--format}
2677 (@pxref{Options,,Options,ld.info,Using LD})
2680 script command @code{TARGET}
2681 (@pxref{Option Commands,,Option Commands,ld.info,Using LD})
2684 environment variable @code{GNUTARGET}
2685 (@pxref{Environment,,Environment,ld.info,Using LD})
2688 the default target of the selected linker emulation
2689 (@pxref{Linker Emulation Selection})
2692 @subheading Linker Output Target
2698 command line option: @samp{-oformat}
2699 (@pxref{Options,,Options,ld.info,Using LD})
2702 script command @code{OUTPUT_FORMAT}
2703 (@pxref{Option Commands,,Option Commands,ld.info,Using LD})
2706 the linker input target (see ``Linker Input Target'' above)
2709 @node Architecture Selection
2710 @section Architecture selection
2712 An @dfn{architecture} is a type of @sc{cpu} on which an object file is
2713 to run. Its name may contain a colon, separating the name of the
2714 processor family from the name of the particular @sc{cpu}.
2716 The command to list valid architecture values is @samp{objdump -i} (the
2717 second column contains the relevant information).
2719 Sample values: @samp{m68k:68020}, @samp{mips:3000}, @samp{sparc}.
2721 @subheading @code{objdump} Architecture
2727 command line option: @samp{-m} or @samp{--architecture}
2730 deduced from the input file
2733 @subheading @code{objcopy}, @code{nm}, @code{size}, @code{strings} Architecture
2739 deduced from the input file
2742 @subheading Linker Input Architecture
2748 deduced from the input file
2751 @subheading Linker Output Architecture
2757 script command @code{OUTPUT_ARCH}
2758 (@pxref{Option Commands,,Option Commands,ld.info,Using LD})
2761 the default architecture from the linker output target
2762 (@pxref{Target Selection})
2765 @node Linker Emulation Selection
2766 @section Linker emulation selection
2768 A linker @dfn{emulation} is a ``personality'' of the linker, which gives
2769 the linker default values for the other aspects of the target system.
2770 In particular, it consists of
2780 several ``hook'' functions that are run at certain stages of the linking
2781 process to do special things that some targets require
2784 The command to list valid linker emulation values is @samp{ld -V}.
2786 Sample values: @samp{hp300bsd}, @samp{mipslit}, @samp{sun4}.
2792 command line option: @samp{-m}
2793 (@pxref{Options,,Options,ld.info,Using LD})
2796 environment variable @code{LDEMULATION}
2799 compiled-in @code{DEFAULT_EMULATION} from @file{Makefile},
2800 which comes from @code{EMUL} in @file{config/@var{target}.mt}
2803 @node Reporting Bugs
2804 @chapter Reporting Bugs
2806 @cindex reporting bugs
2808 Your bug reports play an essential role in making the binary utilities
2811 Reporting a bug may help you by bringing a solution to your problem, or
2812 it may not. But in any case the principal function of a bug report is
2813 to help the entire community by making the next version of the binary
2814 utilities work better. Bug reports are your contribution to their
2817 In order for a bug report to serve its purpose, you must include the
2818 information that enables us to fix the bug.
2821 * Bug Criteria:: Have you found a bug?
2822 * Bug Reporting:: How to report bugs
2826 @section Have you found a bug?
2827 @cindex bug criteria
2829 If you are not sure whether you have found a bug, here are some guidelines:
2832 @cindex fatal signal
2835 If a binary utility gets a fatal signal, for any input whatever, that is
2836 a bug. Reliable utilities never crash.
2838 @cindex error on valid input
2840 If a binary utility produces an error message for valid input, that is a
2844 If you are an experienced user of binary utilities, your suggestions for
2845 improvement are welcome in any case.
2849 @section How to report bugs
2851 @cindex bugs, reporting
2853 A number of companies and individuals offer support for @sc{gnu}
2854 products. If you obtained the binary utilities from a support
2855 organization, we recommend you contact that organization first.
2857 You can find contact information for many support companies and
2858 individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs
2861 In any event, we also recommend that you send bug reports for the binary
2862 utilities to @samp{bug-gnu-utils@@gnu.org}.
2864 The fundamental principle of reporting bugs usefully is this:
2865 @strong{report all the facts}. If you are not sure whether to state a
2866 fact or leave it out, state it!
2868 Often people omit facts because they think they know what causes the
2869 problem and assume that some details do not matter. Thus, you might
2870 assume that the name of a file you use in an example does not matter.
2871 Well, probably it does not, but one cannot be sure. Perhaps the bug is
2872 a stray memory reference which happens to fetch from the location where
2873 that pathname is stored in memory; perhaps, if the pathname were
2874 different, the contents of that location would fool the utility into
2875 doing the right thing despite the bug. Play it safe and give a
2876 specific, complete example. That is the easiest thing for you to do,
2877 and the most helpful.
2879 Keep in mind that the purpose of a bug report is to enable us to fix the bug if
2880 it is new to us. Therefore, always write your bug reports on the assumption
2881 that the bug has not been reported previously.
2883 Sometimes people give a few sketchy facts and ask, ``Does this ring a
2884 bell?'' Those bug reports are useless, and we urge everyone to
2885 @emph{refuse to respond to them} except to chide the sender to report
2888 To enable us to fix the bug, you should include all these things:
2892 The version of the utility. Each utility announces it if you start it
2893 with the @samp{--version} argument.
2895 Without this, we will not know whether there is any point in looking for
2896 the bug in the current version of the binary utilities.
2899 Any patches you may have applied to the source, including any patches
2900 made to the @code{BFD} library.
2903 The type of machine you are using, and the operating system name and
2907 What compiler (and its version) was used to compile the utilities---e.g.
2911 The command arguments you gave the utility to observe the bug. To
2912 guarantee you will not omit something important, list them all. A copy
2913 of the Makefile (or the output from make) is sufficient.
2915 If we were to try to guess the arguments, we would probably guess wrong
2916 and then we might not encounter the bug.
2919 A complete input file, or set of input files, that will reproduce the
2920 bug. If the utility is reading an object file or files, then it is
2921 generally most helpful to send the actual object files, uuencoded if
2922 necessary to get them through the mail system. Note that
2923 @samp{bug-gnu-utils@@gnu.org} is a mailing list, so you should avoid
2924 sending very large files to it. Making the files available for
2925 anonymous FTP is OK.
2927 If the source files were produced exclusively using @sc{gnu} programs
2928 (e.g., @code{gcc}, @code{gas}, and/or the @sc{gnu} @code{ld}), then it
2929 may be OK to send the source files rather than the object files. In
2930 this case, be sure to say exactly what version of @code{gcc}, or
2931 whatever, was used to produce the object files. Also say how
2932 @code{gcc}, or whatever, was configured.
2935 A description of what behavior you observe that you believe is
2936 incorrect. For example, ``It gets a fatal signal.''
2938 Of course, if the bug is that the utility gets a fatal signal, then we
2939 will certainly notice it. But if the bug is incorrect output, we might
2940 not notice unless it is glaringly wrong. You might as well not give us
2941 a chance to make a mistake.
2943 Even if the problem you experience is a fatal signal, you should still
2944 say so explicitly. Suppose something strange is going on, such as your
2945 copy of the utility is out of synch, or you have encountered a bug in
2946 the C library on your system. (This has happened!) Your copy might
2947 crash and ours would not. If you told us to expect a crash, then when
2948 ours fails to crash, we would know that the bug was not happening for
2949 us. If you had not told us to expect a crash, then we would not be able
2950 to draw any conclusion from our observations.
2953 If you wish to suggest changes to the source, send us context diffs, as
2954 generated by @code{diff} with the @samp{-u}, @samp{-c}, or @samp{-p}
2955 option. Always send diffs from the old file to the new file. If you
2956 wish to discuss something in the @code{ld} source, refer to it by
2957 context, not by line number.
2959 The line numbers in our development sources will not match those in your
2960 sources. Your line numbers would convey no useful information to us.
2963 Here are some things that are not necessary:
2967 A description of the envelope of the bug.
2969 Often people who encounter a bug spend a lot of time investigating
2970 which changes to the input file will make the bug go away and which
2971 changes will not affect it.
2973 This is often time consuming and not very useful, because the way we
2974 will find the bug is by running a single example under the debugger
2975 with breakpoints, not by pure deduction from a series of examples.
2976 We recommend that you save your time for something else.
2978 Of course, if you can find a simpler example to report @emph{instead}
2979 of the original one, that is a convenience for us. Errors in the
2980 output will be easier to spot, running under the debugger will take
2981 less time, and so on.
2983 However, simplification is not vital; if you do not want to do this,
2984 report the bug anyway and send us the entire test case you used.
2987 A patch for the bug.
2989 A patch for the bug does help us if it is a good one. But do not omit
2990 the necessary information, such as the test case, on the assumption that
2991 a patch is all we need. We might see problems with your patch and decide
2992 to fix the problem another way, or we might not understand it at all.
2994 Sometimes with programs as complicated as the binary utilities it is
2995 very hard to construct an example that will make the program follow a
2996 certain path through the code. If you do not send us the example, we
2997 will not be able to construct one, so we will not be able to verify that
3000 And if we cannot understand what bug you are trying to fix, or why your
3001 patch should be an improvement, we will not install it. A test case will
3002 help us to understand.
3005 A guess about what the bug is or what it depends on.
3007 Such guesses are usually wrong. Even we cannot guess right about such
3008 things without first using the debugger to find the facts.