This is binutils.info, produced by makeinfo version 4.8 from
|
This is binutils.info, produced by makeinfo version 4.8 from
|
binutils.texi.
|
binutils.texi.
|
|
|
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
|
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
|
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software
|
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software
|
Foundation, Inc.
|
Foundation, Inc.
|
|
|
Permission is granted to copy, distribute and/or modify this document
|
Permission is granted to copy, distribute and/or modify this document
|
under the terms of the GNU Free Documentation License, Version 1.2 or
|
under the terms of the GNU Free Documentation License, Version 1.2 or
|
any later version published by the Free Software Foundation; with no
|
any later version published by the Free Software Foundation; with no
|
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
|
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
|
Texts. A copy of the license is included in the section entitled "GNU
|
Texts. A copy of the license is included in the section entitled "GNU
|
Free Documentation License".
|
Free Documentation License".
|
|
|
INFO-DIR-SECTION Software development
|
INFO-DIR-SECTION Software development
|
START-INFO-DIR-ENTRY
|
START-INFO-DIR-ENTRY
|
* Binutils: (binutils). The GNU binary utilities.
|
* Binutils: (binutils). The GNU binary utilities.
|
END-INFO-DIR-ENTRY
|
END-INFO-DIR-ENTRY
|
|
|
INFO-DIR-SECTION Individual utilities
|
INFO-DIR-SECTION Individual utilities
|
START-INFO-DIR-ENTRY
|
START-INFO-DIR-ENTRY
|
* addr2line: (binutils)addr2line. Convert addresses to file and line.
|
* addr2line: (binutils)addr2line. Convert addresses to file and line.
|
* ar: (binutils)ar. Create, modify, and extract from archives.
|
* ar: (binutils)ar. Create, modify, and extract from archives.
|
* c++filt: (binutils)c++filt. Filter to demangle encoded C++ symbols.
|
* c++filt: (binutils)c++filt. Filter to demangle encoded C++ symbols.
|
* cxxfilt: (binutils)c++filt. MS-DOS name for c++filt.
|
* cxxfilt: (binutils)c++filt. MS-DOS name for c++filt.
|
* dlltool: (binutils)dlltool. Create files needed to build and use DLLs.
|
* dlltool: (binutils)dlltool. Create files needed to build and use DLLs.
|
* nlmconv: (binutils)nlmconv. Converts object code into an NLM.
|
* nlmconv: (binutils)nlmconv. Converts object code into an NLM.
|
* nm: (binutils)nm. List symbols from object files.
|
* nm: (binutils)nm. List symbols from object files.
|
* objcopy: (binutils)objcopy. Copy and translate object files.
|
* objcopy: (binutils)objcopy. Copy and translate object files.
|
* objdump: (binutils)objdump. Display information from object files.
|
* objdump: (binutils)objdump. Display information from object files.
|
* ranlib: (binutils)ranlib. Generate index to archive contents.
|
* ranlib: (binutils)ranlib. Generate index to archive contents.
|
* readelf: (binutils)readelf. Display the contents of ELF format files.
|
* readelf: (binutils)readelf. Display the contents of ELF format files.
|
* size: (binutils)size. List section sizes and total size.
|
* size: (binutils)size. List section sizes and total size.
|
* strings: (binutils)strings. List printable strings from files.
|
* strings: (binutils)strings. List printable strings from files.
|
* strip: (binutils)strip. Discard symbols.
|
* strip: (binutils)strip. Discard symbols.
|
* windmc: (binutils)windmc. Generator for Windows message resources.
|
* windmc: (binutils)windmc. Generator for Windows message resources.
|
* windres: (binutils)windres. Manipulate Windows resources.
|
* windres: (binutils)windres. Manipulate Windows resources.
|
END-INFO-DIR-ENTRY
|
END-INFO-DIR-ENTRY
|
|
|
|
|
File: binutils.info, Node: Top, Next: ar, Up: (dir)
|
File: binutils.info, Node: Top, Next: ar, Up: (dir)
|
|
|
Introduction
|
Introduction
|
************
|
************
|
|
|
This brief manual contains documentation for the GNU binary utilities
|
This brief manual contains documentation for the GNU binary utilities
|
(GNU Binutils) version 2.18.50:
|
(GNU Binutils) version 2.18.50:
|
|
|
This document is distributed under the terms of the GNU Free
|
This document is distributed under the terms of the GNU Free
|
Documentation License. A copy of the license is included in the
|
Documentation License. A copy of the license is included in the
|
section entitled "GNU Free Documentation License".
|
section entitled "GNU Free Documentation License".
|
|
|
* Menu:
|
* Menu:
|
|
|
* ar:: Create, modify, and extract from archives
|
* ar:: Create, modify, and extract from archives
|
* nm:: List symbols from object files
|
* nm:: List symbols from object files
|
* objcopy:: Copy and translate object files
|
* objcopy:: Copy and translate object files
|
* objdump:: Display information from object files
|
* objdump:: Display information from object files
|
* ranlib:: Generate index to archive contents
|
* ranlib:: Generate index to archive contents
|
* readelf:: Display the contents of ELF format files
|
* readelf:: Display the contents of ELF format files
|
* size:: List section sizes and total size
|
* size:: List section sizes and total size
|
* strings:: List printable strings from files
|
* strings:: List printable strings from files
|
* strip:: Discard symbols
|
* strip:: Discard symbols
|
* c++filt:: Filter to demangle encoded C++ symbols
|
* c++filt:: Filter to demangle encoded C++ symbols
|
* cxxfilt: c++filt. MS-DOS name for c++filt
|
* cxxfilt: c++filt. MS-DOS name for c++filt
|
* addr2line:: Convert addresses to file and line
|
* addr2line:: Convert addresses to file and line
|
* nlmconv:: Converts object code into an NLM
|
* nlmconv:: Converts object code into an NLM
|
* windres:: Manipulate Windows resources
|
* windres:: Manipulate Windows resources
|
* windmc:: Generator for Windows message resources
|
* windmc:: Generator for Windows message resources
|
* dlltool:: Create files needed to build and use DLLs
|
* dlltool:: Create files needed to build and use DLLs
|
* Common Options:: Command-line options for all utilities
|
* Common Options:: Command-line options for all utilities
|
* Selecting the Target System:: How these utilities determine the target
|
* Selecting the Target System:: How these utilities determine the target
|
* Reporting Bugs:: Reporting Bugs
|
* Reporting Bugs:: Reporting Bugs
|
* GNU Free Documentation License:: GNU Free Documentation License
|
* GNU Free Documentation License:: GNU Free Documentation License
|
* Binutils Index:: Binutils Index
|
* Binutils Index:: Binutils Index
|
|
|
|
|
File: binutils.info, Node: ar, Next: nm, Prev: Top, Up: Top
|
File: binutils.info, Node: ar, Next: nm, Prev: Top, Up: Top
|
|
|
1 ar
|
1 ar
|
****
|
****
|
|
|
ar [-]P[MOD [RELPOS] [COUNT]] ARCHIVE [MEMBER...]
|
ar [-]P[MOD [RELPOS] [COUNT]] ARCHIVE [MEMBER...]
|
ar -M [
|
ar -M [
|
|
|
The GNU `ar' program creates, modifies, and extracts from archives.
|
The GNU `ar' program creates, modifies, and extracts from archives.
|
An "archive" is a single file holding a collection of other files in a
|
An "archive" is a single file holding a collection of other files in a
|
structure that makes it possible to retrieve the original individual
|
structure that makes it possible to retrieve the original individual
|
files (called "members" of the archive).
|
files (called "members" of the archive).
|
|
|
The original files' contents, mode (permissions), timestamp, owner,
|
The original files' contents, mode (permissions), timestamp, owner,
|
and group are preserved in the archive, and can be restored on
|
and group are preserved in the archive, and can be restored on
|
extraction.
|
extraction.
|
|
|
GNU `ar' can maintain archives whose members have names of any
|
GNU `ar' can maintain archives whose members have names of any
|
length; however, depending on how `ar' is configured on your system, a
|
length; however, depending on how `ar' is configured on your system, a
|
limit on member-name length may be imposed for compatibility with
|
limit on member-name length may be imposed for compatibility with
|
archive formats maintained with other tools. If it exists, the limit
|
archive formats maintained with other tools. If it exists, the limit
|
is often 15 characters (typical of formats related to a.out) or 16
|
is often 15 characters (typical of formats related to a.out) or 16
|
characters (typical of formats related to coff).
|
characters (typical of formats related to coff).
|
|
|
`ar' is considered a binary utility because archives of this sort
|
`ar' is considered a binary utility because archives of this sort
|
are most often used as "libraries" holding commonly needed subroutines.
|
are most often used as "libraries" holding commonly needed subroutines.
|
|
|
`ar' creates an index to the symbols defined in relocatable object
|
`ar' creates an index to the symbols defined in relocatable object
|
modules in the archive when you specify the modifier `s'. Once
|
modules in the archive when you specify the modifier `s'. Once
|
created, this index is updated in the archive whenever `ar' makes a
|
created, this index is updated in the archive whenever `ar' makes a
|
change to its contents (save for the `q' update operation). An archive
|
change to its contents (save for the `q' update operation). An archive
|
with such an index speeds up linking to the library, and allows
|
with such an index speeds up linking to the library, and allows
|
routines in the library to call each other without regard to their
|
routines in the library to call each other without regard to their
|
placement in the archive.
|
placement in the archive.
|
|
|
You may use `nm -s' or `nm --print-armap' to list this index table.
|
You may use `nm -s' or `nm --print-armap' to list this index table.
|
If an archive lacks the table, another form of `ar' called `ranlib' can
|
If an archive lacks the table, another form of `ar' called `ranlib' can
|
be used to add just the table.
|
be used to add just the table.
|
|
|
GNU `ar' can optionally create a _thin_ archive, which contains a
|
GNU `ar' can optionally create a _thin_ archive, which contains a
|
symbol index and references to the original copies of the member files
|
symbol index and references to the original copies of the member files
|
of the archives. Such an archive is useful for building libraries for
|
of the archives. Such an archive is useful for building libraries for
|
use within a local build, where the relocatable objects are expected to
|
use within a local build, where the relocatable objects are expected to
|
remain available, and copying the contents of each object would only
|
remain available, and copying the contents of each object would only
|
waste time and space. Thin archives are also _flattened_, so that
|
waste time and space. Thin archives are also _flattened_, so that
|
adding one or more archives to a thin archive will add the elements of
|
adding one or more archives to a thin archive will add the elements of
|
the nested archive individually. The paths to the elements of the
|
the nested archive individually. The paths to the elements of the
|
archive are stored relative to the archive itself.
|
archive are stored relative to the archive itself.
|
|
|
GNU `ar' is designed to be compatible with two different facilities.
|
GNU `ar' is designed to be compatible with two different facilities.
|
You can control its activity using command-line options, like the
|
You can control its activity using command-line options, like the
|
different varieties of `ar' on Unix systems; or, if you specify the
|
different varieties of `ar' on Unix systems; or, if you specify the
|
single command-line option `-M', you can control it with a script
|
single command-line option `-M', you can control it with a script
|
supplied via standard input, like the MRI "librarian" program.
|
supplied via standard input, like the MRI "librarian" program.
|
|
|
* Menu:
|
* Menu:
|
|
|
* ar cmdline:: Controlling `ar' on the command line
|
* ar cmdline:: Controlling `ar' on the command line
|
* ar scripts:: Controlling `ar' with a script
|
* ar scripts:: Controlling `ar' with a script
|
|
|
|
|
File: binutils.info, Node: ar cmdline, Next: ar scripts, Up: ar
|
File: binutils.info, Node: ar cmdline, Next: ar scripts, Up: ar
|
|
|
1.1 Controlling `ar' on the Command Line
|
1.1 Controlling `ar' on the Command Line
|
========================================
|
========================================
|
|
|
ar [`-X32_64'] [`-']P[MOD [RELPOS] [COUNT]] ARCHIVE [MEMBER...]
|
ar [`-X32_64'] [`-']P[MOD [RELPOS] [COUNT]] ARCHIVE [MEMBER...]
|
|
|
When you use `ar' in the Unix style, `ar' insists on at least two
|
When you use `ar' in the Unix style, `ar' insists on at least two
|
arguments to execute: one keyletter specifying the _operation_
|
arguments to execute: one keyletter specifying the _operation_
|
(optionally accompanied by other keyletters specifying _modifiers_),
|
(optionally accompanied by other keyletters specifying _modifiers_),
|
and the archive name to act on.
|
and the archive name to act on.
|
|
|
Most operations can also accept further MEMBER arguments, specifying
|
Most operations can also accept further MEMBER arguments, specifying
|
particular files to operate on.
|
particular files to operate on.
|
|
|
GNU `ar' allows you to mix the operation code P and modifier flags
|
GNU `ar' allows you to mix the operation code P and modifier flags
|
MOD in any order, within the first command-line argument.
|
MOD in any order, within the first command-line argument.
|
|
|
If you wish, you may begin the first command-line argument with a
|
If you wish, you may begin the first command-line argument with a
|
dash.
|
dash.
|
|
|
The P keyletter specifies what operation to execute; it may be any
|
The P keyletter specifies what operation to execute; it may be any
|
of the following, but you must specify only one of them:
|
of the following, but you must specify only one of them:
|
|
|
`d'
|
`d'
|
_Delete_ modules from the archive. Specify the names of modules to
|
_Delete_ modules from the archive. Specify the names of modules to
|
be deleted as MEMBER...; the archive is untouched if you specify
|
be deleted as MEMBER...; the archive is untouched if you specify
|
no files to delete.
|
no files to delete.
|
|
|
If you specify the `v' modifier, `ar' lists each module as it is
|
If you specify the `v' modifier, `ar' lists each module as it is
|
deleted.
|
deleted.
|
|
|
`m'
|
`m'
|
Use this operation to _move_ members in an archive.
|
Use this operation to _move_ members in an archive.
|
|
|
The ordering of members in an archive can make a difference in how
|
The ordering of members in an archive can make a difference in how
|
programs are linked using the library, if a symbol is defined in
|
programs are linked using the library, if a symbol is defined in
|
more than one member.
|
more than one member.
|
|
|
If no modifiers are used with `m', any members you name in the
|
If no modifiers are used with `m', any members you name in the
|
MEMBER arguments are moved to the _end_ of the archive; you can
|
MEMBER arguments are moved to the _end_ of the archive; you can
|
use the `a', `b', or `i' modifiers to move them to a specified
|
use the `a', `b', or `i' modifiers to move them to a specified
|
place instead.
|
place instead.
|
|
|
`p'
|
`p'
|
_Print_ the specified members of the archive, to the standard
|
_Print_ the specified members of the archive, to the standard
|
output file. If the `v' modifier is specified, show the member
|
output file. If the `v' modifier is specified, show the member
|
name before copying its contents to standard output.
|
name before copying its contents to standard output.
|
|
|
If you specify no MEMBER arguments, all the files in the archive
|
If you specify no MEMBER arguments, all the files in the archive
|
are printed.
|
are printed.
|
|
|
`q'
|
`q'
|
_Quick append_; Historically, add the files MEMBER... to the end of
|
_Quick append_; Historically, add the files MEMBER... to the end of
|
ARCHIVE, without checking for replacement.
|
ARCHIVE, without checking for replacement.
|
|
|
The modifiers `a', `b', and `i' do _not_ affect this operation;
|
The modifiers `a', `b', and `i' do _not_ affect this operation;
|
new members are always placed at the end of the archive.
|
new members are always placed at the end of the archive.
|
|
|
The modifier `v' makes `ar' list each file as it is appended.
|
The modifier `v' makes `ar' list each file as it is appended.
|
|
|
Since the point of this operation is speed, the archive's symbol
|
Since the point of this operation is speed, the archive's symbol
|
table index is not updated, even if it already existed; you can
|
table index is not updated, even if it already existed; you can
|
use `ar s' or `ranlib' explicitly to update the symbol table index.
|
use `ar s' or `ranlib' explicitly to update the symbol table index.
|
|
|
However, too many different systems assume quick append rebuilds
|
However, too many different systems assume quick append rebuilds
|
the index, so GNU `ar' implements `q' as a synonym for `r'.
|
the index, so GNU `ar' implements `q' as a synonym for `r'.
|
|
|
`r'
|
`r'
|
Insert the files MEMBER... into ARCHIVE (with _replacement_). This
|
Insert the files MEMBER... into ARCHIVE (with _replacement_). This
|
operation differs from `q' in that any previously existing members
|
operation differs from `q' in that any previously existing members
|
are deleted if their names match those being added.
|
are deleted if their names match those being added.
|
|
|
If one of the files named in MEMBER... does not exist, `ar'
|
If one of the files named in MEMBER... does not exist, `ar'
|
displays an error message, and leaves undisturbed any existing
|
displays an error message, and leaves undisturbed any existing
|
members of the archive matching that name.
|
members of the archive matching that name.
|
|
|
By default, new members are added at the end of the file; but you
|
By default, new members are added at the end of the file; but you
|
may use one of the modifiers `a', `b', or `i' to request placement
|
may use one of the modifiers `a', `b', or `i' to request placement
|
relative to some existing member.
|
relative to some existing member.
|
|
|
The modifier `v' used with this operation elicits a line of output
|
The modifier `v' used with this operation elicits a line of output
|
for each file inserted, along with one of the letters `a' or `r'
|
for each file inserted, along with one of the letters `a' or `r'
|
to indicate whether the file was appended (no old member deleted)
|
to indicate whether the file was appended (no old member deleted)
|
or replaced.
|
or replaced.
|
|
|
`t'
|
`t'
|
Display a _table_ listing the contents of ARCHIVE, or those of the
|
Display a _table_ listing the contents of ARCHIVE, or those of the
|
files listed in MEMBER... that are present in the archive.
|
files listed in MEMBER... that are present in the archive.
|
Normally only the member name is shown; if you also want to see
|
Normally only the member name is shown; if you also want to see
|
the modes (permissions), timestamp, owner, group, and size, you can
|
the modes (permissions), timestamp, owner, group, and size, you can
|
request that by also specifying the `v' modifier.
|
request that by also specifying the `v' modifier.
|
|
|
If you do not specify a MEMBER, all files in the archive are
|
If you do not specify a MEMBER, all files in the archive are
|
listed.
|
listed.
|
|
|
If there is more than one file with the same name (say, `fie') in
|
If there is more than one file with the same name (say, `fie') in
|
an archive (say `b.a'), `ar t b.a fie' lists only the first
|
an archive (say `b.a'), `ar t b.a fie' lists only the first
|
instance; to see them all, you must ask for a complete listing--in
|
instance; to see them all, you must ask for a complete listing--in
|
our example, `ar t b.a'.
|
our example, `ar t b.a'.
|
|
|
`x'
|
`x'
|
_Extract_ members (named MEMBER) from the archive. You can use
|
_Extract_ members (named MEMBER) from the archive. You can use
|
the `v' modifier with this operation, to request that `ar' list
|
the `v' modifier with this operation, to request that `ar' list
|
each name as it extracts it.
|
each name as it extracts it.
|
|
|
If you do not specify a MEMBER, all files in the archive are
|
If you do not specify a MEMBER, all files in the archive are
|
extracted.
|
extracted.
|
|
|
Files cannot be extracted from a thin archive.
|
Files cannot be extracted from a thin archive.
|
|
|
|
|
A number of modifiers (MOD) may immediately follow the P keyletter,
|
A number of modifiers (MOD) may immediately follow the P keyletter,
|
to specify variations on an operation's behavior:
|
to specify variations on an operation's behavior:
|
|
|
`a'
|
`a'
|
Add new files _after_ an existing member of the archive. If you
|
Add new files _after_ an existing member of the archive. If you
|
use the modifier `a', the name of an existing archive member must
|
use the modifier `a', the name of an existing archive member must
|
be present as the RELPOS argument, before the ARCHIVE
|
be present as the RELPOS argument, before the ARCHIVE
|
specification.
|
specification.
|
|
|
`b'
|
`b'
|
Add new files _before_ an existing member of the archive. If you
|
Add new files _before_ an existing member of the archive. If you
|
use the modifier `b', the name of an existing archive member must
|
use the modifier `b', the name of an existing archive member must
|
be present as the RELPOS argument, before the ARCHIVE
|
be present as the RELPOS argument, before the ARCHIVE
|
specification. (same as `i').
|
specification. (same as `i').
|
|
|
`c'
|
`c'
|
_Create_ the archive. The specified ARCHIVE is always created if
|
_Create_ the archive. The specified ARCHIVE is always created if
|
it did not exist, when you request an update. But a warning is
|
it did not exist, when you request an update. But a warning is
|
issued unless you specify in advance that you expect to create it,
|
issued unless you specify in advance that you expect to create it,
|
by using this modifier.
|
by using this modifier.
|
|
|
`f'
|
`f'
|
Truncate names in the archive. GNU `ar' will normally permit file
|
Truncate names in the archive. GNU `ar' will normally permit file
|
names of any length. This will cause it to create archives which
|
names of any length. This will cause it to create archives which
|
are not compatible with the native `ar' program on some systems.
|
are not compatible with the native `ar' program on some systems.
|
If this is a concern, the `f' modifier may be used to truncate file
|
If this is a concern, the `f' modifier may be used to truncate file
|
names when putting them in the archive.
|
names when putting them in the archive.
|
|
|
`i'
|
`i'
|
Insert new files _before_ an existing member of the archive. If
|
Insert new files _before_ an existing member of the archive. If
|
you use the modifier `i', the name of an existing archive member
|
you use the modifier `i', the name of an existing archive member
|
must be present as the RELPOS argument, before the ARCHIVE
|
must be present as the RELPOS argument, before the ARCHIVE
|
specification. (same as `b').
|
specification. (same as `b').
|
|
|
`l'
|
`l'
|
This modifier is accepted but not used.
|
This modifier is accepted but not used.
|
|
|
`N'
|
`N'
|
Uses the COUNT parameter. This is used if there are multiple
|
Uses the COUNT parameter. This is used if there are multiple
|
entries in the archive with the same name. Extract or delete
|
entries in the archive with the same name. Extract or delete
|
instance COUNT of the given name from the archive.
|
instance COUNT of the given name from the archive.
|
|
|
`o'
|
`o'
|
Preserve the _original_ dates of members when extracting them. If
|
Preserve the _original_ dates of members when extracting them. If
|
you do not specify this modifier, files extracted from the archive
|
you do not specify this modifier, files extracted from the archive
|
are stamped with the time of extraction.
|
are stamped with the time of extraction.
|
|
|
`P'
|
`P'
|
Use the full path name when matching names in the archive. GNU
|
Use the full path name when matching names in the archive. GNU
|
`ar' can not create an archive with a full path name (such archives
|
`ar' can not create an archive with a full path name (such archives
|
are not POSIX complaint), but other archive creators can. This
|
are not POSIX complaint), but other archive creators can. This
|
option will cause GNU `ar' to match file names using a complete
|
option will cause GNU `ar' to match file names using a complete
|
path name, which can be convenient when extracting a single file
|
path name, which can be convenient when extracting a single file
|
from an archive created by another tool.
|
from an archive created by another tool.
|
|
|
`s'
|
`s'
|
Write an object-file index into the archive, or update an existing
|
Write an object-file index into the archive, or update an existing
|
one, even if no other change is made to the archive. You may use
|
one, even if no other change is made to the archive. You may use
|
this modifier flag either with any operation, or alone. Running
|
this modifier flag either with any operation, or alone. Running
|
`ar s' on an archive is equivalent to running `ranlib' on it.
|
`ar s' on an archive is equivalent to running `ranlib' on it.
|
|
|
`S'
|
`S'
|
Do not generate an archive symbol table. This can speed up
|
Do not generate an archive symbol table. This can speed up
|
building a large library in several steps. The resulting archive
|
building a large library in several steps. The resulting archive
|
can not be used with the linker. In order to build a symbol
|
can not be used with the linker. In order to build a symbol
|
table, you must omit the `S' modifier on the last execution of
|
table, you must omit the `S' modifier on the last execution of
|
`ar', or you must run `ranlib' on the archive.
|
`ar', or you must run `ranlib' on the archive.
|
|
|
`T'
|
`T'
|
Make the specified ARCHIVE a _thin_ archive. If it already exists
|
Make the specified ARCHIVE a _thin_ archive. If it already exists
|
and is a regular archive, the existing members must be present in
|
and is a regular archive, the existing members must be present in
|
the same directory as ARCHIVE.
|
the same directory as ARCHIVE.
|
|
|
`u'
|
`u'
|
Normally, `ar r'... inserts all files listed into the archive. If
|
Normally, `ar r'... inserts all files listed into the archive. If
|
you would like to insert _only_ those of the files you list that
|
you would like to insert _only_ those of the files you list that
|
are newer than existing members of the same names, use this
|
are newer than existing members of the same names, use this
|
modifier. The `u' modifier is allowed only for the operation `r'
|
modifier. The `u' modifier is allowed only for the operation `r'
|
(replace). In particular, the combination `qu' is not allowed,
|
(replace). In particular, the combination `qu' is not allowed,
|
since checking the timestamps would lose any speed advantage from
|
since checking the timestamps would lose any speed advantage from
|
the operation `q'.
|
the operation `q'.
|
|
|
`v'
|
`v'
|
This modifier requests the _verbose_ version of an operation. Many
|
This modifier requests the _verbose_ version of an operation. Many
|
operations display additional information, such as filenames
|
operations display additional information, such as filenames
|
processed, when the modifier `v' is appended.
|
processed, when the modifier `v' is appended.
|
|
|
`V'
|
`V'
|
This modifier shows the version number of `ar'.
|
This modifier shows the version number of `ar'.
|
|
|
`ar' ignores an initial option spelt `-X32_64', for compatibility
|
`ar' ignores an initial option spelt `-X32_64', for compatibility
|
with AIX. The behaviour produced by this option is the default for GNU
|
with AIX. The behaviour produced by this option is the default for GNU
|
`ar'. `ar' does not support any of the other `-X' options; in
|
`ar'. `ar' does not support any of the other `-X' options; in
|
particular, it does not support `-X32' which is the default for AIX
|
particular, it does not support `-X32' which is the default for AIX
|
`ar'.
|
`ar'.
|
|
|
|
|
File: binutils.info, Node: ar scripts, Prev: ar cmdline, Up: ar
|
File: binutils.info, Node: ar scripts, Prev: ar cmdline, Up: ar
|
|
|
1.2 Controlling `ar' with a Script
|
1.2 Controlling `ar' with a Script
|
==================================
|
==================================
|
|
|
ar -M [
|
ar -M [
|
|
|
If you use the single command-line option `-M' with `ar', you can
|
If you use the single command-line option `-M' with `ar', you can
|
control its operation with a rudimentary command language. This form
|
control its operation with a rudimentary command language. This form
|
of `ar' operates interactively if standard input is coming directly
|
of `ar' operates interactively if standard input is coming directly
|
from a terminal. During interactive use, `ar' prompts for input (the
|
from a terminal. During interactive use, `ar' prompts for input (the
|
prompt is `AR >'), and continues executing even after errors. If you
|
prompt is `AR >'), and continues executing even after errors. If you
|
redirect standard input to a script file, no prompts are issued, and
|
redirect standard input to a script file, no prompts are issued, and
|
`ar' abandons execution (with a nonzero exit code) on any error.
|
`ar' abandons execution (with a nonzero exit code) on any error.
|
|
|
The `ar' command language is _not_ designed to be equivalent to the
|
The `ar' command language is _not_ designed to be equivalent to the
|
command-line options; in fact, it provides somewhat less control over
|
command-line options; in fact, it provides somewhat less control over
|
archives. The only purpose of the command language is to ease the
|
archives. The only purpose of the command language is to ease the
|
transition to GNU `ar' for developers who already have scripts written
|
transition to GNU `ar' for developers who already have scripts written
|
for the MRI "librarian" program.
|
for the MRI "librarian" program.
|
|
|
The syntax for the `ar' command language is straightforward:
|
The syntax for the `ar' command language is straightforward:
|
* commands are recognized in upper or lower case; for example, `LIST'
|
* commands are recognized in upper or lower case; for example, `LIST'
|
is the same as `list'. In the following descriptions, commands are
|
is the same as `list'. In the following descriptions, commands are
|
shown in upper case for clarity.
|
shown in upper case for clarity.
|
|
|
* a single command may appear on each line; it is the first word on
|
* a single command may appear on each line; it is the first word on
|
the line.
|
the line.
|
|
|
* empty lines are allowed, and have no effect.
|
* empty lines are allowed, and have no effect.
|
|
|
* comments are allowed; text after either of the characters `*' or
|
* comments are allowed; text after either of the characters `*' or
|
`;' is ignored.
|
`;' is ignored.
|
|
|
* Whenever you use a list of names as part of the argument to an `ar'
|
* Whenever you use a list of names as part of the argument to an `ar'
|
command, you can separate the individual names with either commas
|
command, you can separate the individual names with either commas
|
or blanks. Commas are shown in the explanations below, for
|
or blanks. Commas are shown in the explanations below, for
|
clarity.
|
clarity.
|
|
|
* `+' is used as a line continuation character; if `+' appears at
|
* `+' is used as a line continuation character; if `+' appears at
|
the end of a line, the text on the following line is considered
|
the end of a line, the text on the following line is considered
|
part of the current command.
|
part of the current command.
|
|
|
Here are the commands you can use in `ar' scripts, or when using
|
Here are the commands you can use in `ar' scripts, or when using
|
`ar' interactively. Three of them have special significance:
|
`ar' interactively. Three of them have special significance:
|
|
|
`OPEN' or `CREATE' specify a "current archive", which is a temporary
|
`OPEN' or `CREATE' specify a "current archive", which is a temporary
|
file required for most of the other commands.
|
file required for most of the other commands.
|
|
|
`SAVE' commits the changes so far specified by the script. Prior to
|
`SAVE' commits the changes so far specified by the script. Prior to
|
`SAVE', commands affect only the temporary copy of the current archive.
|
`SAVE', commands affect only the temporary copy of the current archive.
|
|
|
`ADDLIB ARCHIVE'
|
`ADDLIB ARCHIVE'
|
`ADDLIB ARCHIVE (MODULE, MODULE, ... MODULE)'
|
`ADDLIB ARCHIVE (MODULE, MODULE, ... MODULE)'
|
Add all the contents of ARCHIVE (or, if specified, each named
|
Add all the contents of ARCHIVE (or, if specified, each named
|
MODULE from ARCHIVE) to the current archive.
|
MODULE from ARCHIVE) to the current archive.
|
|
|
Requires prior use of `OPEN' or `CREATE'.
|
Requires prior use of `OPEN' or `CREATE'.
|
|
|
`ADDMOD MEMBER, MEMBER, ... MEMBER'
|
`ADDMOD MEMBER, MEMBER, ... MEMBER'
|
Add each named MEMBER as a module in the current archive.
|
Add each named MEMBER as a module in the current archive.
|
|
|
Requires prior use of `OPEN' or `CREATE'.
|
Requires prior use of `OPEN' or `CREATE'.
|
|
|
`CLEAR'
|
`CLEAR'
|
Discard the contents of the current archive, canceling the effect
|
Discard the contents of the current archive, canceling the effect
|
of any operations since the last `SAVE'. May be executed (with no
|
of any operations since the last `SAVE'. May be executed (with no
|
effect) even if no current archive is specified.
|
effect) even if no current archive is specified.
|
|
|
`CREATE ARCHIVE'
|
`CREATE ARCHIVE'
|
Creates an archive, and makes it the current archive (required for
|
Creates an archive, and makes it the current archive (required for
|
many other commands). The new archive is created with a temporary
|
many other commands). The new archive is created with a temporary
|
name; it is not actually saved as ARCHIVE until you use `SAVE'.
|
name; it is not actually saved as ARCHIVE until you use `SAVE'.
|
You can overwrite existing archives; similarly, the contents of any
|
You can overwrite existing archives; similarly, the contents of any
|
existing file named ARCHIVE will not be destroyed until `SAVE'.
|
existing file named ARCHIVE will not be destroyed until `SAVE'.
|
|
|
`DELETE MODULE, MODULE, ... MODULE'
|
`DELETE MODULE, MODULE, ... MODULE'
|
Delete each listed MODULE from the current archive; equivalent to
|
Delete each listed MODULE from the current archive; equivalent to
|
`ar -d ARCHIVE MODULE ... MODULE'.
|
`ar -d ARCHIVE MODULE ... MODULE'.
|
|
|
Requires prior use of `OPEN' or `CREATE'.
|
Requires prior use of `OPEN' or `CREATE'.
|
|
|
`DIRECTORY ARCHIVE (MODULE, ... MODULE)'
|
`DIRECTORY ARCHIVE (MODULE, ... MODULE)'
|
`DIRECTORY ARCHIVE (MODULE, ... MODULE) OUTPUTFILE'
|
`DIRECTORY ARCHIVE (MODULE, ... MODULE) OUTPUTFILE'
|
List each named MODULE present in ARCHIVE. The separate command
|
List each named MODULE present in ARCHIVE. The separate command
|
`VERBOSE' specifies the form of the output: when verbose output is
|
`VERBOSE' specifies the form of the output: when verbose output is
|
off, output is like that of `ar -t ARCHIVE MODULE...'. When
|
off, output is like that of `ar -t ARCHIVE MODULE...'. When
|
verbose output is on, the listing is like `ar -tv ARCHIVE
|
verbose output is on, the listing is like `ar -tv ARCHIVE
|
MODULE...'.
|
MODULE...'.
|
|
|
Output normally goes to the standard output stream; however, if you
|
Output normally goes to the standard output stream; however, if you
|
specify OUTPUTFILE as a final argument, `ar' directs the output to
|
specify OUTPUTFILE as a final argument, `ar' directs the output to
|
that file.
|
that file.
|
|
|
`END'
|
`END'
|
Exit from `ar', with a `0' exit code to indicate successful
|
Exit from `ar', with a `0' exit code to indicate successful
|
completion. This command does not save the output file; if you
|
completion. This command does not save the output file; if you
|
have changed the current archive since the last `SAVE' command,
|
have changed the current archive since the last `SAVE' command,
|
those changes are lost.
|
those changes are lost.
|
|
|
`EXTRACT MODULE, MODULE, ... MODULE'
|
`EXTRACT MODULE, MODULE, ... MODULE'
|
Extract each named MODULE from the current archive, writing them
|
Extract each named MODULE from the current archive, writing them
|
into the current directory as separate files. Equivalent to `ar -x
|
into the current directory as separate files. Equivalent to `ar -x
|
ARCHIVE MODULE...'.
|
ARCHIVE MODULE...'.
|
|
|
Requires prior use of `OPEN' or `CREATE'.
|
Requires prior use of `OPEN' or `CREATE'.
|
|
|
`LIST'
|
`LIST'
|
Display full contents of the current archive, in "verbose" style
|
Display full contents of the current archive, in "verbose" style
|
regardless of the state of `VERBOSE'. The effect is like `ar tv
|
regardless of the state of `VERBOSE'. The effect is like `ar tv
|
ARCHIVE'. (This single command is a GNU `ar' enhancement, rather
|
ARCHIVE'. (This single command is a GNU `ar' enhancement, rather
|
than present for MRI compatibility.)
|
than present for MRI compatibility.)
|
|
|
Requires prior use of `OPEN' or `CREATE'.
|
Requires prior use of `OPEN' or `CREATE'.
|
|
|
`OPEN ARCHIVE'
|
`OPEN ARCHIVE'
|
Opens an existing archive for use as the current archive (required
|
Opens an existing archive for use as the current archive (required
|
for many other commands). Any changes as the result of subsequent
|
for many other commands). Any changes as the result of subsequent
|
commands will not actually affect ARCHIVE until you next use
|
commands will not actually affect ARCHIVE until you next use
|
`SAVE'.
|
`SAVE'.
|
|
|
`REPLACE MODULE, MODULE, ... MODULE'
|
`REPLACE MODULE, MODULE, ... MODULE'
|
In the current archive, replace each existing MODULE (named in the
|
In the current archive, replace each existing MODULE (named in the
|
`REPLACE' arguments) from files in the current working directory.
|
`REPLACE' arguments) from files in the current working directory.
|
To execute this command without errors, both the file, and the
|
To execute this command without errors, both the file, and the
|
module in the current archive, must exist.
|
module in the current archive, must exist.
|
|
|
Requires prior use of `OPEN' or `CREATE'.
|
Requires prior use of `OPEN' or `CREATE'.
|
|
|
`VERBOSE'
|
`VERBOSE'
|
Toggle an internal flag governing the output from `DIRECTORY'.
|
Toggle an internal flag governing the output from `DIRECTORY'.
|
When the flag is on, `DIRECTORY' output matches output from `ar
|
When the flag is on, `DIRECTORY' output matches output from `ar
|
-tv '....
|
-tv '....
|
|
|
`SAVE'
|
`SAVE'
|
Commit your changes to the current archive, and actually save it
|
Commit your changes to the current archive, and actually save it
|
as a file with the name specified in the last `CREATE' or `OPEN'
|
as a file with the name specified in the last `CREATE' or `OPEN'
|
command.
|
command.
|
|
|
Requires prior use of `OPEN' or `CREATE'.
|
Requires prior use of `OPEN' or `CREATE'.
|
|
|
|
|
|
|
File: binutils.info, Node: nm, Next: objcopy, Prev: ar, Up: Top
|
File: binutils.info, Node: nm, Next: objcopy, Prev: ar, Up: Top
|
|
|
2 nm
|
2 nm
|
****
|
****
|
|
|
nm [`-a'|`--debug-syms'] [`-g'|`--extern-only']
|
nm [`-a'|`--debug-syms'] [`-g'|`--extern-only']
|
[`-B'] [`-C'|`--demangle'[=STYLE]] [`-D'|`--dynamic']
|
[`-B'] [`-C'|`--demangle'[=STYLE]] [`-D'|`--dynamic']
|
[`-S'|`--print-size'] [`-s'|`--print-armap']
|
[`-S'|`--print-size'] [`-s'|`--print-armap']
|
[`-A'|`-o'|`--print-file-name'][`--special-syms']
|
[`-A'|`-o'|`--print-file-name'][`--special-syms']
|
[`-n'|`-v'|`--numeric-sort'] [`-p'|`--no-sort']
|
[`-n'|`-v'|`--numeric-sort'] [`-p'|`--no-sort']
|
[`-r'|`--reverse-sort'] [`--size-sort'] [`-u'|`--undefined-only']
|
[`-r'|`--reverse-sort'] [`--size-sort'] [`-u'|`--undefined-only']
|
[`-t' RADIX|`--radix='RADIX] [`-P'|`--portability']
|
[`-t' RADIX|`--radix='RADIX] [`-P'|`--portability']
|
[`--target='BFDNAME] [`-f'FORMAT|`--format='FORMAT]
|
[`--target='BFDNAME] [`-f'FORMAT|`--format='FORMAT]
|
[`--defined-only'] [`-l'|`--line-numbers'] [`--no-demangle']
|
[`--defined-only'] [`-l'|`--line-numbers'] [`--no-demangle']
|
[`-V'|`--version'] [`-X 32_64'] [`--help'] [OBJFILE...]
|
[`-V'|`--version'] [`-X 32_64'] [`--help'] [OBJFILE...]
|
|
|
GNU `nm' lists the symbols from object files OBJFILE.... If no
|
GNU `nm' lists the symbols from object files OBJFILE.... If no
|
object files are listed as arguments, `nm' assumes the file `a.out'.
|
object files are listed as arguments, `nm' assumes the file `a.out'.
|
|
|
For each symbol, `nm' shows:
|
For each symbol, `nm' shows:
|
|
|
* The symbol value, in the radix selected by options (see below), or
|
* The symbol value, in the radix selected by options (see below), or
|
hexadecimal by default.
|
hexadecimal by default.
|
|
|
* The symbol type. At least the following types are used; others
|
* The symbol type. At least the following types are used; others
|
are, as well, depending on the object file format. If lowercase,
|
are, as well, depending on the object file format. If lowercase,
|
the symbol is local; if uppercase, the symbol is global (external).
|
the symbol is local; if uppercase, the symbol is global (external).
|
|
|
`A'
|
`A'
|
The symbol's value is absolute, and will not be changed by
|
The symbol's value is absolute, and will not be changed by
|
further linking.
|
further linking.
|
|
|
`B'
|
`B'
|
`b'
|
`b'
|
The symbol is in the uninitialized data section (known as
|
The symbol is in the uninitialized data section (known as
|
BSS).
|
BSS).
|
|
|
`C'
|
`C'
|
The symbol is common. Common symbols are uninitialized data.
|
The symbol is common. Common symbols are uninitialized data.
|
When linking, multiple common symbols may appear with the
|
When linking, multiple common symbols may appear with the
|
same name. If the symbol is defined anywhere, the common
|
same name. If the symbol is defined anywhere, the common
|
symbols are treated as undefined references. For more
|
symbols are treated as undefined references. For more
|
details on common symbols, see the discussion of -warn-common
|
details on common symbols, see the discussion of -warn-common
|
in *Note Linker options: (ld.info)Options.
|
in *Note Linker options: (ld.info)Options.
|
|
|
`D'
|
`D'
|
`d'
|
`d'
|
The symbol is in the initialized data section.
|
The symbol is in the initialized data section.
|
|
|
`G'
|
`G'
|
`g'
|
`g'
|
The symbol is in an initialized data section for small
|
The symbol is in an initialized data section for small
|
objects. Some object file formats permit more efficient
|
objects. Some object file formats permit more efficient
|
access to small data objects, such as a global int variable
|
access to small data objects, such as a global int variable
|
as opposed to a large global array.
|
as opposed to a large global array.
|
|
|
`I'
|
`I'
|
The symbol is an indirect reference to another symbol. This
|
The symbol is an indirect reference to another symbol. This
|
is a GNU extension to the a.out object file format which is
|
is a GNU extension to the a.out object file format which is
|
rarely used.
|
rarely used.
|
|
|
`i'
|
`i'
|
The symbol is in a section specific to the implementation of
|
The symbol is in a section specific to the implementation of
|
DLLs.
|
DLLs.
|
|
|
`N'
|
`N'
|
The symbol is a debugging symbol.
|
The symbol is a debugging symbol.
|
|
|
`p'
|
`p'
|
The symbols is in a stack unwind section.
|
The symbols is in a stack unwind section.
|
|
|
`R'
|
`R'
|
`r'
|
`r'
|
The symbol is in a read only data section.
|
The symbol is in a read only data section.
|
|
|
`S'
|
`S'
|
`s'
|
`s'
|
The symbol is in an uninitialized data section for small
|
The symbol is in an uninitialized data section for small
|
objects.
|
objects.
|
|
|
`T'
|
`T'
|
`t'
|
`t'
|
The symbol is in the text (code) section.
|
The symbol is in the text (code) section.
|
|
|
`U'
|
`U'
|
The symbol is undefined.
|
The symbol is undefined.
|
|
|
`V'
|
`V'
|
`v'
|
`v'
|
The symbol is a weak object. When a weak defined symbol is
|
The symbol is a weak object. When a weak defined symbol is
|
linked with a normal defined symbol, the normal defined
|
linked with a normal defined symbol, the normal defined
|
symbol is used with no error. When a weak undefined symbol
|
symbol is used with no error. When a weak undefined symbol
|
is linked and the symbol is not defined, the value of the
|
is linked and the symbol is not defined, the value of the
|
weak symbol becomes zero with no error. On some systems,
|
weak symbol becomes zero with no error. On some systems,
|
uppercase indicates that a default value has been specified.
|
uppercase indicates that a default value has been specified.
|
|
|
`W'
|
`W'
|
`w'
|
`w'
|
The symbol is a weak symbol that has not been specifically
|
The symbol is a weak symbol that has not been specifically
|
tagged as a weak object symbol. When a weak defined symbol
|
tagged as a weak object symbol. When a weak defined symbol
|
is linked with a normal defined symbol, the normal defined
|
is linked with a normal defined symbol, the normal defined
|
symbol is used with no error. When a weak undefined symbol
|
symbol is used with no error. When a weak undefined symbol
|
is linked and the symbol is not defined, the value of the
|
is linked and the symbol is not defined, the value of the
|
symbol is determined in a system-specific manner without
|
symbol is determined in a system-specific manner without
|
error. On some systems, uppercase indicates that a default
|
error. On some systems, uppercase indicates that a default
|
value has been specified.
|
value has been specified.
|
|
|
`-'
|
`-'
|
The symbol is a stabs symbol in an a.out object file. In
|
The symbol is a stabs symbol in an a.out object file. In
|
this case, the next values printed are the stabs other field,
|
this case, the next values printed are the stabs other field,
|
the stabs desc field, and the stab type. Stabs symbols are
|
the stabs desc field, and the stab type. Stabs symbols are
|
used to hold debugging information. For more information,
|
used to hold debugging information. For more information,
|
see *Note Stabs: (stabs.info)Top.
|
see *Note Stabs: (stabs.info)Top.
|
|
|
`?'
|
`?'
|
The symbol type is unknown, or object file format specific.
|
The symbol type is unknown, or object file format specific.
|
|
|
* The symbol name.
|
* The symbol name.
|
|
|
The long and short forms of options, shown here as alternatives, are
|
The long and short forms of options, shown here as alternatives, are
|
equivalent.
|
equivalent.
|
|
|
`-A'
|
`-A'
|
`-o'
|
`-o'
|
`--print-file-name'
|
`--print-file-name'
|
Precede each symbol by the name of the input file (or archive
|
Precede each symbol by the name of the input file (or archive
|
member) in which it was found, rather than identifying the input
|
member) in which it was found, rather than identifying the input
|
file once only, before all of its symbols.
|
file once only, before all of its symbols.
|
|
|
`-a'
|
`-a'
|
`--debug-syms'
|
`--debug-syms'
|
Display all symbols, even debugger-only symbols; normally these
|
Display all symbols, even debugger-only symbols; normally these
|
are not listed.
|
are not listed.
|
|
|
`-B'
|
`-B'
|
The same as `--format=bsd' (for compatibility with the MIPS `nm').
|
The same as `--format=bsd' (for compatibility with the MIPS `nm').
|
|
|
`-C'
|
`-C'
|
`--demangle[=STYLE]'
|
`--demangle[=STYLE]'
|
Decode ("demangle") low-level symbol names into user-level names.
|
Decode ("demangle") low-level symbol names into user-level names.
|
Besides removing any initial underscore prepended by the system,
|
Besides removing any initial underscore prepended by the system,
|
this makes C++ function names readable. Different compilers have
|
this makes C++ function names readable. Different compilers have
|
different mangling styles. The optional demangling style argument
|
different mangling styles. The optional demangling style argument
|
can be used to choose an appropriate demangling style for your
|
can be used to choose an appropriate demangling style for your
|
compiler. *Note c++filt::, for more information on demangling.
|
compiler. *Note c++filt::, for more information on demangling.
|
|
|
`--no-demangle'
|
`--no-demangle'
|
Do not demangle low-level symbol names. This is the default.
|
Do not demangle low-level symbol names. This is the default.
|
|
|
`-D'
|
`-D'
|
`--dynamic'
|
`--dynamic'
|
Display the dynamic symbols rather than the normal symbols. This
|
Display the dynamic symbols rather than the normal symbols. This
|
is only meaningful for dynamic objects, such as certain types of
|
is only meaningful for dynamic objects, such as certain types of
|
shared libraries.
|
shared libraries.
|
|
|
`-f FORMAT'
|
`-f FORMAT'
|
`--format=FORMAT'
|
`--format=FORMAT'
|
Use the output format FORMAT, which can be `bsd', `sysv', or
|
Use the output format FORMAT, which can be `bsd', `sysv', or
|
`posix'. The default is `bsd'. Only the first character of
|
`posix'. The default is `bsd'. Only the first character of
|
FORMAT is significant; it can be either upper or lower case.
|
FORMAT is significant; it can be either upper or lower case.
|
|
|
`-g'
|
`-g'
|
`--extern-only'
|
`--extern-only'
|
Display only external symbols.
|
Display only external symbols.
|
|
|
`-l'
|
`-l'
|
`--line-numbers'
|
`--line-numbers'
|
For each symbol, use debugging information to try to find a
|
For each symbol, use debugging information to try to find a
|
filename and line number. For a defined symbol, look for the line
|
filename and line number. For a defined symbol, look for the line
|
number of the address of the symbol. For an undefined symbol,
|
number of the address of the symbol. For an undefined symbol,
|
look for the line number of a relocation entry which refers to the
|
look for the line number of a relocation entry which refers to the
|
symbol. If line number information can be found, print it after
|
symbol. If line number information can be found, print it after
|
the other symbol information.
|
the other symbol information.
|
|
|
`-n'
|
`-n'
|
`-v'
|
`-v'
|
`--numeric-sort'
|
`--numeric-sort'
|
Sort symbols numerically by their addresses, rather than
|
Sort symbols numerically by their addresses, rather than
|
alphabetically by their names.
|
alphabetically by their names.
|
|
|
`-p'
|
`-p'
|
`--no-sort'
|
`--no-sort'
|
Do not bother to sort the symbols in any order; print them in the
|
Do not bother to sort the symbols in any order; print them in the
|
order encountered.
|
order encountered.
|
|
|
`-P'
|
`-P'
|
`--portability'
|
`--portability'
|
Use the POSIX.2 standard output format instead of the default
|
Use the POSIX.2 standard output format instead of the default
|
format. Equivalent to `-f posix'.
|
format. Equivalent to `-f posix'.
|
|
|
`-S'
|
`-S'
|
`--print-size'
|
`--print-size'
|
Print size, not the value, of defined symbols for the `bsd' output
|
Print size, not the value, of defined symbols for the `bsd' output
|
format.
|
format.
|
|
|
`-s'
|
`-s'
|
`--print-armap'
|
`--print-armap'
|
When listing symbols from archive members, include the index: a
|
When listing symbols from archive members, include the index: a
|
mapping (stored in the archive by `ar' or `ranlib') of which
|
mapping (stored in the archive by `ar' or `ranlib') of which
|
modules contain definitions for which names.
|
modules contain definitions for which names.
|
|
|
`-r'
|
`-r'
|
`--reverse-sort'
|
`--reverse-sort'
|
Reverse the order of the sort (whether numeric or alphabetic); let
|
Reverse the order of the sort (whether numeric or alphabetic); let
|
the last come first.
|
the last come first.
|
|
|
`--size-sort'
|
`--size-sort'
|
Sort symbols by size. The size is computed as the difference
|
Sort symbols by size. The size is computed as the difference
|
between the value of the symbol and the value of the symbol with
|
between the value of the symbol and the value of the symbol with
|
the next higher value. If the `bsd' output format is used the
|
the next higher value. If the `bsd' output format is used the
|
size of the symbol is printed, rather than the value, and `-S'
|
size of the symbol is printed, rather than the value, and `-S'
|
must be used in order both size and value to be printed.
|
must be used in order both size and value to be printed.
|
|
|
`--special-syms'
|
`--special-syms'
|
Display symbols which have a target-specific special meaning.
|
Display symbols which have a target-specific special meaning.
|
These symbols are usually used by the target for some special
|
These symbols are usually used by the target for some special
|
processing and are not normally helpful when included included in
|
processing and are not normally helpful when included included in
|
the normal symbol lists. For example for ARM targets this option
|
the normal symbol lists. For example for ARM targets this option
|
would skip the mapping symbols used to mark transitions between
|
would skip the mapping symbols used to mark transitions between
|
ARM code, THUMB code and data.
|
ARM code, THUMB code and data.
|
|
|
`-t RADIX'
|
`-t RADIX'
|
`--radix=RADIX'
|
`--radix=RADIX'
|
Use RADIX as the radix for printing the symbol values. It must be
|
Use RADIX as the radix for printing the symbol values. It must be
|
`d' for decimal, `o' for octal, or `x' for hexadecimal.
|
`d' for decimal, `o' for octal, or `x' for hexadecimal.
|
|
|
`--target=BFDNAME'
|
`--target=BFDNAME'
|
Specify an object code format other than your system's default
|
Specify an object code format other than your system's default
|
format. *Note Target Selection::, for more information.
|
format. *Note Target Selection::, for more information.
|
|
|
`-u'
|
`-u'
|
`--undefined-only'
|
`--undefined-only'
|
Display only undefined symbols (those external to each object
|
Display only undefined symbols (those external to each object
|
file).
|
file).
|
|
|
`--defined-only'
|
`--defined-only'
|
Display only defined symbols for each object file.
|
Display only defined symbols for each object file.
|
|
|
`-V'
|
`-V'
|
`--version'
|
`--version'
|
Show the version number of `nm' and exit.
|
Show the version number of `nm' and exit.
|
|
|
`-X'
|
`-X'
|
This option is ignored for compatibility with the AIX version of
|
This option is ignored for compatibility with the AIX version of
|
`nm'. It takes one parameter which must be the string `32_64'.
|
`nm'. It takes one parameter which must be the string `32_64'.
|
The default mode of AIX `nm' corresponds to `-X 32', which is not
|
The default mode of AIX `nm' corresponds to `-X 32', which is not
|
supported by GNU `nm'.
|
supported by GNU `nm'.
|
|
|
`--help'
|
`--help'
|
Show a summary of the options to `nm' and exit.
|
Show a summary of the options to `nm' and exit.
|
|
|
|
|
File: binutils.info, Node: objcopy, Next: objdump, Prev: nm, Up: Top
|
File: binutils.info, Node: objcopy, Next: objdump, Prev: nm, Up: Top
|
|
|
3 objcopy
|
3 objcopy
|
*********
|
*********
|
|
|
objcopy [`-F' BFDNAME|`--target='BFDNAME]
|
objcopy [`-F' BFDNAME|`--target='BFDNAME]
|
[`-I' BFDNAME|`--input-target='BFDNAME]
|
[`-I' BFDNAME|`--input-target='BFDNAME]
|
[`-O' BFDNAME|`--output-target='BFDNAME]
|
[`-O' BFDNAME|`--output-target='BFDNAME]
|
[`-B' BFDARCH|`--binary-architecture='BFDARCH]
|
[`-B' BFDARCH|`--binary-architecture='BFDARCH]
|
[`-S'|`--strip-all']
|
[`-S'|`--strip-all']
|
[`-g'|`--strip-debug']
|
[`-g'|`--strip-debug']
|
[`-K' SYMBOLNAME|`--keep-symbol='SYMBOLNAME]
|
[`-K' SYMBOLNAME|`--keep-symbol='SYMBOLNAME]
|
[`-N' SYMBOLNAME|`--strip-symbol='SYMBOLNAME]
|
[`-N' SYMBOLNAME|`--strip-symbol='SYMBOLNAME]
|
[`--strip-unneeded-symbol='SYMBOLNAME]
|
[`--strip-unneeded-symbol='SYMBOLNAME]
|
[`-G' SYMBOLNAME|`--keep-global-symbol='SYMBOLNAME]
|
[`-G' SYMBOLNAME|`--keep-global-symbol='SYMBOLNAME]
|
[`--localize-hidden']
|
[`--localize-hidden']
|
[`-L' SYMBOLNAME|`--localize-symbol='SYMBOLNAME]
|
[`-L' SYMBOLNAME|`--localize-symbol='SYMBOLNAME]
|
[`--globalize-symbol='SYMBOLNAME]
|
[`--globalize-symbol='SYMBOLNAME]
|
[`-W' SYMBOLNAME|`--weaken-symbol='SYMBOLNAME]
|
[`-W' SYMBOLNAME|`--weaken-symbol='SYMBOLNAME]
|
[`-w'|`--wildcard']
|
[`-w'|`--wildcard']
|
[`-x'|`--discard-all']
|
[`-x'|`--discard-all']
|
[`-X'|`--discard-locals']
|
[`-X'|`--discard-locals']
|
[`-b' BYTE|`--byte='BYTE]
|
[`-b' BYTE|`--byte='BYTE]
|
[`-i' INTERLEAVE|`--interleave='INTERLEAVE]
|
[`-i' INTERLEAVE|`--interleave='INTERLEAVE]
|
[`-j' SECTIONNAME|`--only-section='SECTIONNAME]
|
[`-j' SECTIONNAME|`--only-section='SECTIONNAME]
|
[`-R' SECTIONNAME|`--remove-section='SECTIONNAME]
|
[`-R' SECTIONNAME|`--remove-section='SECTIONNAME]
|
[`-p'|`--preserve-dates']
|
[`-p'|`--preserve-dates']
|
[`--debugging']
|
[`--debugging']
|
[`--gap-fill='VAL]
|
[`--gap-fill='VAL]
|
[`--pad-to='ADDRESS]
|
[`--pad-to='ADDRESS]
|
[`--set-start='VAL]
|
[`--set-start='VAL]
|
[`--adjust-start='INCR]
|
[`--adjust-start='INCR]
|
[`--change-addresses='INCR]
|
[`--change-addresses='INCR]
|
[`--change-section-address' SECTION{=,+,-}VAL]
|
[`--change-section-address' SECTION{=,+,-}VAL]
|
[`--change-section-lma' SECTION{=,+,-}VAL]
|
[`--change-section-lma' SECTION{=,+,-}VAL]
|
[`--change-section-vma' SECTION{=,+,-}VAL]
|
[`--change-section-vma' SECTION{=,+,-}VAL]
|
[`--change-warnings'] [`--no-change-warnings']
|
[`--change-warnings'] [`--no-change-warnings']
|
[`--set-section-flags' SECTION=FLAGS]
|
[`--set-section-flags' SECTION=FLAGS]
|
[`--add-section' SECTIONNAME=FILENAME]
|
[`--add-section' SECTIONNAME=FILENAME]
|
[`--rename-section' OLDNAME=NEWNAME[,FLAGS]]
|
[`--rename-section' OLDNAME=NEWNAME[,FLAGS]]
|
[`--change-leading-char'] [`--remove-leading-char']
|
[`--change-leading-char'] [`--remove-leading-char']
|
[`--reverse-bytes='NUM]
|
[`--reverse-bytes='NUM]
|
[`--srec-len='IVAL] [`--srec-forceS3']
|
[`--srec-len='IVAL] [`--srec-forceS3']
|
[`--redefine-sym' OLD=NEW]
|
[`--redefine-sym' OLD=NEW]
|
[`--redefine-syms='FILENAME]
|
[`--redefine-syms='FILENAME]
|
[`--weaken']
|
[`--weaken']
|
[`--keep-symbols='FILENAME]
|
[`--keep-symbols='FILENAME]
|
[`--strip-symbols='FILENAME]
|
[`--strip-symbols='FILENAME]
|
[`--strip-unneeded-symbols='FILENAME]
|
[`--strip-unneeded-symbols='FILENAME]
|
[`--keep-global-symbols='FILENAME]
|
[`--keep-global-symbols='FILENAME]
|
[`--localize-symbols='FILENAME]
|
[`--localize-symbols='FILENAME]
|
[`--globalize-symbols='FILENAME]
|
[`--globalize-symbols='FILENAME]
|
[`--weaken-symbols='FILENAME]
|
[`--weaken-symbols='FILENAME]
|
[`--alt-machine-code='INDEX]
|
[`--alt-machine-code='INDEX]
|
[`--prefix-symbols='STRING]
|
[`--prefix-symbols='STRING]
|
[`--prefix-sections='STRING]
|
[`--prefix-sections='STRING]
|
[`--prefix-alloc-sections='STRING]
|
[`--prefix-alloc-sections='STRING]
|
[`--add-gnu-debuglink='PATH-TO-FILE]
|
[`--add-gnu-debuglink='PATH-TO-FILE]
|
[`--keep-file-symbols']
|
[`--keep-file-symbols']
|
[`--only-keep-debug']
|
[`--only-keep-debug']
|
[`--extract-symbol']
|
[`--extract-symbol']
|
[`--writable-text']
|
[`--writable-text']
|
[`--readonly-text']
|
[`--readonly-text']
|
[`--pure']
|
[`--pure']
|
[`--impure']
|
[`--impure']
|
[`-v'|`--verbose']
|
[`-v'|`--verbose']
|
[`-V'|`--version']
|
[`-V'|`--version']
|
[`--help'] [`--info']
|
[`--help'] [`--info']
|
INFILE [OUTFILE]
|
INFILE [OUTFILE]
|
|
|
The GNU `objcopy' utility copies the contents of an object file to
|
The GNU `objcopy' utility copies the contents of an object file to
|
another. `objcopy' uses the GNU BFD Library to read and write the
|
another. `objcopy' uses the GNU BFD Library to read and write the
|
object files. It can write the destination object file in a format
|
object files. It can write the destination object file in a format
|
different from that of the source object file. The exact behavior of
|
different from that of the source object file. The exact behavior of
|
`objcopy' is controlled by command-line options. Note that `objcopy'
|
`objcopy' is controlled by command-line options. Note that `objcopy'
|
should be able to copy a fully linked file between any two formats.
|
should be able to copy a fully linked file between any two formats.
|
However, copying a relocatable object file between any two formats may
|
However, copying a relocatable object file between any two formats may
|
not work as expected.
|
not work as expected.
|
|
|
`objcopy' creates temporary files to do its translations and deletes
|
`objcopy' creates temporary files to do its translations and deletes
|
them afterward. `objcopy' uses BFD to do all its translation work; it
|
them afterward. `objcopy' uses BFD to do all its translation work; it
|
has access to all the formats described in BFD and thus is able to
|
has access to all the formats described in BFD and thus is able to
|
recognize most formats without being told explicitly. *Note BFD:
|
recognize most formats without being told explicitly. *Note BFD:
|
(ld.info)BFD.
|
(ld.info)BFD.
|
|
|
`objcopy' can be used to generate S-records by using an output
|
`objcopy' can be used to generate S-records by using an output
|
target of `srec' (e.g., use `-O srec').
|
target of `srec' (e.g., use `-O srec').
|
|
|
`objcopy' can be used to generate a raw binary file by using an
|
`objcopy' can be used to generate a raw binary file by using an
|
output target of `binary' (e.g., use `-O binary'). When `objcopy'
|
output target of `binary' (e.g., use `-O binary'). When `objcopy'
|
generates a raw binary file, it will essentially produce a memory dump
|
generates a raw binary file, it will essentially produce a memory dump
|
of the contents of the input object file. All symbols and relocation
|
of the contents of the input object file. All symbols and relocation
|
information will be discarded. The memory dump will start at the load
|
information will be discarded. The memory dump will start at the load
|
address of the lowest section copied into the output file.
|
address of the lowest section copied into the output file.
|
|
|
When generating an S-record or a raw binary file, it may be helpful
|
When generating an S-record or a raw binary file, it may be helpful
|
to use `-S' to remove sections containing debugging information. In
|
to use `-S' to remove sections containing debugging information. In
|
some cases `-R' will be useful to remove sections which contain
|
some cases `-R' will be useful to remove sections which contain
|
information that is not needed by the binary file.
|
information that is not needed by the binary file.
|
|
|
Note--`objcopy' is not able to change the endianness of its input
|
Note--`objcopy' is not able to change the endianness of its input
|
files. If the input format has an endianness (some formats do not),
|
files. If the input format has an endianness (some formats do not),
|
`objcopy' can only copy the inputs into file formats that have the same
|
`objcopy' can only copy the inputs into file formats that have the same
|
endianness or which have no endianness (e.g., `srec'). (However, see
|
endianness or which have no endianness (e.g., `srec'). (However, see
|
the `--reverse-bytes' option.)
|
the `--reverse-bytes' option.)
|
|
|
`INFILE'
|
`INFILE'
|
`OUTFILE'
|
`OUTFILE'
|
The input and output files, respectively. If you do not specify
|
The input and output files, respectively. If you do not specify
|
OUTFILE, `objcopy' creates a temporary file and destructively
|
OUTFILE, `objcopy' creates a temporary file and destructively
|
renames the result with the name of INFILE.
|
renames the result with the name of INFILE.
|
|
|
`-I BFDNAME'
|
`-I BFDNAME'
|
`--input-target=BFDNAME'
|
`--input-target=BFDNAME'
|
Consider the source file's object format to be BFDNAME, rather than
|
Consider the source file's object format to be BFDNAME, rather than
|
attempting to deduce it. *Note Target Selection::, for more
|
attempting to deduce it. *Note Target Selection::, for more
|
information.
|
information.
|
|
|
`-O BFDNAME'
|
`-O BFDNAME'
|
`--output-target=BFDNAME'
|
`--output-target=BFDNAME'
|
Write the output file using the object format BFDNAME. *Note
|
Write the output file using the object format BFDNAME. *Note
|
Target Selection::, for more information.
|
Target Selection::, for more information.
|
|
|
`-F BFDNAME'
|
`-F BFDNAME'
|
`--target=BFDNAME'
|
`--target=BFDNAME'
|
Use BFDNAME as the object format for both the input and the output
|
Use BFDNAME as the object format for both the input and the output
|
file; i.e., simply transfer data from source to destination with no
|
file; i.e., simply transfer data from source to destination with no
|
translation. *Note Target Selection::, for more information.
|
translation. *Note Target Selection::, for more information.
|
|
|
`-B BFDARCH'
|
`-B BFDARCH'
|
`--binary-architecture=BFDARCH'
|
`--binary-architecture=BFDARCH'
|
Useful when transforming a raw binary input file into an object
|
Useful when transforming a raw binary input file into an object
|
file. In this case the output architecture can be set to BFDARCH.
|
file. In this case the output architecture can be set to BFDARCH.
|
This option will be ignored if the input file has a known BFDARCH.
|
This option will be ignored if the input file has a known BFDARCH.
|
You can access this binary data inside a program by referencing
|
You can access this binary data inside a program by referencing
|
the special symbols that are created by the conversion process.
|
the special symbols that are created by the conversion process.
|
These symbols are called _binary_OBJFILE_start,
|
These symbols are called _binary_OBJFILE_start,
|
_binary_OBJFILE_end and _binary_OBJFILE_size. e.g. you can
|
_binary_OBJFILE_end and _binary_OBJFILE_size. e.g. you can
|
transform a picture file into an object file and then access it in
|
transform a picture file into an object file and then access it in
|
your code using these symbols.
|
your code using these symbols.
|
|
|
`-j SECTIONNAME'
|
`-j SECTIONNAME'
|
`--only-section=SECTIONNAME'
|
`--only-section=SECTIONNAME'
|
Copy only the named section from the input file to the output file.
|
Copy only the named section from the input file to the output file.
|
This option may be given more than once. Note that using this
|
This option may be given more than once. Note that using this
|
option inappropriately may make the output file unusable.
|
option inappropriately may make the output file unusable.
|
|
|
`-R SECTIONNAME'
|
`-R SECTIONNAME'
|
`--remove-section=SECTIONNAME'
|
`--remove-section=SECTIONNAME'
|
Remove any section named SECTIONNAME from the output file. This
|
Remove any section named SECTIONNAME from the output file. This
|
option may be given more than once. Note that using this option
|
option may be given more than once. Note that using this option
|
inappropriately may make the output file unusable.
|
inappropriately may make the output file unusable.
|
|
|
`-S'
|
`-S'
|
`--strip-all'
|
`--strip-all'
|
Do not copy relocation and symbol information from the source file.
|
Do not copy relocation and symbol information from the source file.
|
|
|
`-g'
|
`-g'
|
`--strip-debug'
|
`--strip-debug'
|
Do not copy debugging symbols or sections from the source file.
|
Do not copy debugging symbols or sections from the source file.
|
|
|
`--strip-unneeded'
|
`--strip-unneeded'
|
Strip all symbols that are not needed for relocation processing.
|
Strip all symbols that are not needed for relocation processing.
|
|
|
`-K SYMBOLNAME'
|
`-K SYMBOLNAME'
|
`--keep-symbol=SYMBOLNAME'
|
`--keep-symbol=SYMBOLNAME'
|
When stripping symbols, keep symbol SYMBOLNAME even if it would
|
When stripping symbols, keep symbol SYMBOLNAME even if it would
|
normally be stripped. This option may be given more than once.
|
normally be stripped. This option may be given more than once.
|
|
|
`-N SYMBOLNAME'
|
`-N SYMBOLNAME'
|
`--strip-symbol=SYMBOLNAME'
|
`--strip-symbol=SYMBOLNAME'
|
Do not copy symbol SYMBOLNAME from the source file. This option
|
Do not copy symbol SYMBOLNAME from the source file. This option
|
may be given more than once.
|
may be given more than once.
|
|
|
`--strip-unneeded-symbol=SYMBOLNAME'
|
`--strip-unneeded-symbol=SYMBOLNAME'
|
Do not copy symbol SYMBOLNAME from the source file unless it is
|
Do not copy symbol SYMBOLNAME from the source file unless it is
|
needed by a relocation. This option may be given more than once.
|
needed by a relocation. This option may be given more than once.
|
|
|
`-G SYMBOLNAME'
|
`-G SYMBOLNAME'
|
`--keep-global-symbol=SYMBOLNAME'
|
`--keep-global-symbol=SYMBOLNAME'
|
Keep only symbol SYMBOLNAME global. Make all other symbols local
|
Keep only symbol SYMBOLNAME global. Make all other symbols local
|
to the file, so that they are not visible externally. This option
|
to the file, so that they are not visible externally. This option
|
may be given more than once.
|
may be given more than once.
|
|
|
`--localize-hidden'
|
`--localize-hidden'
|
In an ELF object, mark all symbols that have hidden or internal
|
In an ELF object, mark all symbols that have hidden or internal
|
visibility as local. This option applies on top of
|
visibility as local. This option applies on top of
|
symbol-specific localization options such as `-L'.
|
symbol-specific localization options such as `-L'.
|
|
|
`-L SYMBOLNAME'
|
`-L SYMBOLNAME'
|
`--localize-symbol=SYMBOLNAME'
|
`--localize-symbol=SYMBOLNAME'
|
Make symbol SYMBOLNAME local to the file, so that it is not
|
Make symbol SYMBOLNAME local to the file, so that it is not
|
visible externally. This option may be given more than once.
|
visible externally. This option may be given more than once.
|
|
|
`-W SYMBOLNAME'
|
`-W SYMBOLNAME'
|
`--weaken-symbol=SYMBOLNAME'
|
`--weaken-symbol=SYMBOLNAME'
|
Make symbol SYMBOLNAME weak. This option may be given more than
|
Make symbol SYMBOLNAME weak. This option may be given more than
|
once.
|
once.
|
|
|
`--globalize-symbol=SYMBOLNAME'
|
`--globalize-symbol=SYMBOLNAME'
|
Give symbol SYMBOLNAME global scoping so that it is visible
|
Give symbol SYMBOLNAME global scoping so that it is visible
|
outside of the file in which it is defined. This option may be
|
outside of the file in which it is defined. This option may be
|
given more than once.
|
given more than once.
|
|
|
`-w'
|
`-w'
|
`--wildcard'
|
`--wildcard'
|
Permit regular expressions in SYMBOLNAMEs used in other command
|
Permit regular expressions in SYMBOLNAMEs used in other command
|
line options. The question mark (?), asterisk (*), backslash (\)
|
line options. The question mark (?), asterisk (*), backslash (\)
|
and square brackets ([]) operators can be used anywhere in the
|
and square brackets ([]) operators can be used anywhere in the
|
symbol name. If the first character of the symbol name is the
|
symbol name. If the first character of the symbol name is the
|
exclamation point (!) then the sense of the switch is reversed for
|
exclamation point (!) then the sense of the switch is reversed for
|
that symbol. For example:
|
that symbol. For example:
|
|
|
-w -W !foo -W fo*
|
-w -W !foo -W fo*
|
|
|
would cause objcopy to weaken all symbols that start with "fo"
|
would cause objcopy to weaken all symbols that start with "fo"
|
except for the symbol "foo".
|
except for the symbol "foo".
|
|
|
`-x'
|
`-x'
|
`--discard-all'
|
`--discard-all'
|
Do not copy non-global symbols from the source file.
|
Do not copy non-global symbols from the source file.
|
|
|
`-X'
|
`-X'
|
`--discard-locals'
|
`--discard-locals'
|
Do not copy compiler-generated local symbols. (These usually
|
Do not copy compiler-generated local symbols. (These usually
|
start with `L' or `.'.)
|
start with `L' or `.'.)
|
|
|
`-b BYTE'
|
`-b BYTE'
|
`--byte=BYTE'
|
`--byte=BYTE'
|
Keep only every BYTEth byte of the input file (header data is not
|
Keep only every BYTEth byte of the input file (header data is not
|
affected). BYTE can be in the range from 0 to INTERLEAVE-1, where
|
affected). BYTE can be in the range from 0 to INTERLEAVE-1, where
|
INTERLEAVE is given by the `-i' or `--interleave' option, or the
|
INTERLEAVE is given by the `-i' or `--interleave' option, or the
|
default of 4. This option is useful for creating files to program
|
default of 4. This option is useful for creating files to program
|
ROM. It is typically used with an `srec' output target.
|
ROM. It is typically used with an `srec' output target.
|
|
|
`-i INTERLEAVE'
|
`-i INTERLEAVE'
|
`--interleave=INTERLEAVE'
|
`--interleave=INTERLEAVE'
|
Only copy one out of every INTERLEAVE bytes. Select which byte to
|
Only copy one out of every INTERLEAVE bytes. Select which byte to
|
copy with the `-b' or `--byte' option. The default is 4.
|
copy with the `-b' or `--byte' option. The default is 4.
|
`objcopy' ignores this option if you do not specify either `-b' or
|
`objcopy' ignores this option if you do not specify either `-b' or
|
`--byte'.
|
`--byte'.
|
|
|
`-p'
|
`-p'
|
`--preserve-dates'
|
`--preserve-dates'
|
Set the access and modification dates of the output file to be the
|
Set the access and modification dates of the output file to be the
|
same as those of the input file.
|
same as those of the input file.
|
|
|
`--debugging'
|
`--debugging'
|
Convert debugging information, if possible. This is not the
|
Convert debugging information, if possible. This is not the
|
default because only certain debugging formats are supported, and
|
default because only certain debugging formats are supported, and
|
the conversion process can be time consuming.
|
the conversion process can be time consuming.
|
|
|
`--gap-fill VAL'
|
`--gap-fill VAL'
|
Fill gaps between sections with VAL. This operation applies to
|
Fill gaps between sections with VAL. This operation applies to
|
the _load address_ (LMA) of the sections. It is done by increasing
|
the _load address_ (LMA) of the sections. It is done by increasing
|
the size of the section with the lower address, and filling in the
|
the size of the section with the lower address, and filling in the
|
extra space created with VAL.
|
extra space created with VAL.
|
|
|
`--pad-to ADDRESS'
|
`--pad-to ADDRESS'
|
Pad the output file up to the load address ADDRESS. This is done
|
Pad the output file up to the load address ADDRESS. This is done
|
by increasing the size of the last section. The extra space is
|
by increasing the size of the last section. The extra space is
|
filled in with the value specified by `--gap-fill' (default zero).
|
filled in with the value specified by `--gap-fill' (default zero).
|
|
|
`--set-start VAL'
|
`--set-start VAL'
|
Set the start address of the new file to VAL. Not all object file
|
Set the start address of the new file to VAL. Not all object file
|
formats support setting the start address.
|
formats support setting the start address.
|
|
|
`--change-start INCR'
|
`--change-start INCR'
|
`--adjust-start INCR'
|
`--adjust-start INCR'
|
Change the start address by adding INCR. Not all object file
|
Change the start address by adding INCR. Not all object file
|
formats support setting the start address.
|
formats support setting the start address.
|
|
|
`--change-addresses INCR'
|
`--change-addresses INCR'
|
`--adjust-vma INCR'
|
`--adjust-vma INCR'
|
Change the VMA and LMA addresses of all sections, as well as the
|
Change the VMA and LMA addresses of all sections, as well as the
|
start address, by adding INCR. Some object file formats do not
|
start address, by adding INCR. Some object file formats do not
|
permit section addresses to be changed arbitrarily. Note that
|
permit section addresses to be changed arbitrarily. Note that
|
this does not relocate the sections; if the program expects
|
this does not relocate the sections; if the program expects
|
sections to be loaded at a certain address, and this option is
|
sections to be loaded at a certain address, and this option is
|
used to change the sections such that they are loaded at a
|
used to change the sections such that they are loaded at a
|
different address, the program may fail.
|
different address, the program may fail.
|
|
|
`--change-section-address SECTION{=,+,-}VAL'
|
`--change-section-address SECTION{=,+,-}VAL'
|
`--adjust-section-vma SECTION{=,+,-}VAL'
|
`--adjust-section-vma SECTION{=,+,-}VAL'
|
Set or change both the VMA address and the LMA address of the named
|
Set or change both the VMA address and the LMA address of the named
|
SECTION. If `=' is used, the section address is set to VAL.
|
SECTION. If `=' is used, the section address is set to VAL.
|
Otherwise, VAL is added to or subtracted from the section address.
|
Otherwise, VAL is added to or subtracted from the section address.
|
See the comments under `--change-addresses', above. If SECTION
|
See the comments under `--change-addresses', above. If SECTION
|
does not exist in the input file, a warning will be issued, unless
|
does not exist in the input file, a warning will be issued, unless
|
`--no-change-warnings' is used.
|
`--no-change-warnings' is used.
|
|
|
`--change-section-lma SECTION{=,+,-}VAL'
|
`--change-section-lma SECTION{=,+,-}VAL'
|
Set or change the LMA address of the named SECTION. The LMA
|
Set or change the LMA address of the named SECTION. The LMA
|
address is the address where the section will be loaded into
|
address is the address where the section will be loaded into
|
memory at program load time. Normally this is the same as the VMA
|
memory at program load time. Normally this is the same as the VMA
|
address, which is the address of the section at program run time,
|
address, which is the address of the section at program run time,
|
but on some systems, especially those where a program is held in
|
but on some systems, especially those where a program is held in
|
ROM, the two can be different. If `=' is used, the section
|
ROM, the two can be different. If `=' is used, the section
|
address is set to VAL. Otherwise, VAL is added to or subtracted
|
address is set to VAL. Otherwise, VAL is added to or subtracted
|
from the section address. See the comments under
|
from the section address. See the comments under
|
`--change-addresses', above. If SECTION does not exist in the
|
`--change-addresses', above. If SECTION does not exist in the
|
input file, a warning will be issued, unless
|
input file, a warning will be issued, unless
|
`--no-change-warnings' is used.
|
`--no-change-warnings' is used.
|
|
|
`--change-section-vma SECTION{=,+,-}VAL'
|
`--change-section-vma SECTION{=,+,-}VAL'
|
Set or change the VMA address of the named SECTION. The VMA
|
Set or change the VMA address of the named SECTION. The VMA
|
address is the address where the section will be located once the
|
address is the address where the section will be located once the
|
program has started executing. Normally this is the same as the
|
program has started executing. Normally this is the same as the
|
LMA address, which is the address where the section will be loaded
|
LMA address, which is the address where the section will be loaded
|
into memory, but on some systems, especially those where a program
|
into memory, but on some systems, especially those where a program
|
is held in ROM, the two can be different. If `=' is used, the
|
is held in ROM, the two can be different. If `=' is used, the
|
section address is set to VAL. Otherwise, VAL is added to or
|
section address is set to VAL. Otherwise, VAL is added to or
|
subtracted from the section address. See the comments under
|
subtracted from the section address. See the comments under
|
`--change-addresses', above. If SECTION does not exist in the
|
`--change-addresses', above. If SECTION does not exist in the
|
input file, a warning will be issued, unless
|
input file, a warning will be issued, unless
|
`--no-change-warnings' is used.
|
`--no-change-warnings' is used.
|
|
|
`--change-warnings'
|
`--change-warnings'
|
`--adjust-warnings'
|
`--adjust-warnings'
|
If `--change-section-address' or `--change-section-lma' or
|
If `--change-section-address' or `--change-section-lma' or
|
`--change-section-vma' is used, and the named section does not
|
`--change-section-vma' is used, and the named section does not
|
exist, issue a warning. This is the default.
|
exist, issue a warning. This is the default.
|
|
|
`--no-change-warnings'
|
`--no-change-warnings'
|
`--no-adjust-warnings'
|
`--no-adjust-warnings'
|
Do not issue a warning if `--change-section-address' or
|
Do not issue a warning if `--change-section-address' or
|
`--adjust-section-lma' or `--adjust-section-vma' is used, even if
|
`--adjust-section-lma' or `--adjust-section-vma' is used, even if
|
the named section does not exist.
|
the named section does not exist.
|
|
|
`--set-section-flags SECTION=FLAGS'
|
`--set-section-flags SECTION=FLAGS'
|
Set the flags for the named section. The FLAGS argument is a
|
Set the flags for the named section. The FLAGS argument is a
|
comma separated string of flag names. The recognized names are
|
comma separated string of flag names. The recognized names are
|
`alloc', `contents', `load', `noload', `readonly', `code', `data',
|
`alloc', `contents', `load', `noload', `readonly', `code', `data',
|
`rom', `share', and `debug'. You can set the `contents' flag for
|
`rom', `share', and `debug'. You can set the `contents' flag for
|
a section which does not have contents, but it is not meaningful
|
a section which does not have contents, but it is not meaningful
|
to clear the `contents' flag of a section which does have
|
to clear the `contents' flag of a section which does have
|
contents-just remove the section instead. Not all flags are
|
contents-just remove the section instead. Not all flags are
|
meaningful for all object file formats.
|
meaningful for all object file formats.
|
|
|
`--add-section SECTIONNAME=FILENAME'
|
`--add-section SECTIONNAME=FILENAME'
|
Add a new section named SECTIONNAME while copying the file. The
|
Add a new section named SECTIONNAME while copying the file. The
|
contents of the new section are taken from the file FILENAME. The
|
contents of the new section are taken from the file FILENAME. The
|
size of the section will be the size of the file. This option only
|
size of the section will be the size of the file. This option only
|
works on file formats which can support sections with arbitrary
|
works on file formats which can support sections with arbitrary
|
names.
|
names.
|
|
|
`--rename-section OLDNAME=NEWNAME[,FLAGS]'
|
`--rename-section OLDNAME=NEWNAME[,FLAGS]'
|
Rename a section from OLDNAME to NEWNAME, optionally changing the
|
Rename a section from OLDNAME to NEWNAME, optionally changing the
|
section's flags to FLAGS in the process. This has the advantage
|
section's flags to FLAGS in the process. This has the advantage
|
over usng a linker script to perform the rename in that the output
|
over usng a linker script to perform the rename in that the output
|
stays as an object file and does not become a linked executable.
|
stays as an object file and does not become a linked executable.
|
|
|
This option is particularly helpful when the input format is
|
This option is particularly helpful when the input format is
|
binary, since this will always create a section called .data. If
|
binary, since this will always create a section called .data. If
|
for example, you wanted instead to create a section called .rodata
|
for example, you wanted instead to create a section called .rodata
|
containing binary data you could use the following command line to
|
containing binary data you could use the following command line to
|
achieve it:
|
achieve it:
|
|
|
objcopy -I binary -O -B \
|
objcopy -I binary -O -B \
|
--rename-section .data=.rodata,alloc,load,readonly,data,contents \
|
--rename-section .data=.rodata,alloc,load,readonly,data,contents \
|
|
|
|
|
`--change-leading-char'
|
`--change-leading-char'
|
Some object file formats use special characters at the start of
|
Some object file formats use special characters at the start of
|
symbols. The most common such character is underscore, which
|
symbols. The most common such character is underscore, which
|
compilers often add before every symbol. This option tells
|
compilers often add before every symbol. This option tells
|
`objcopy' to change the leading character of every symbol when it
|
`objcopy' to change the leading character of every symbol when it
|
converts between object file formats. If the object file formats
|
converts between object file formats. If the object file formats
|
use the same leading character, this option has no effect.
|
use the same leading character, this option has no effect.
|
Otherwise, it will add a character, or remove a character, or
|
Otherwise, it will add a character, or remove a character, or
|
change a character, as appropriate.
|
change a character, as appropriate.
|
|
|
`--remove-leading-char'
|
`--remove-leading-char'
|
If the first character of a global symbol is a special symbol
|
If the first character of a global symbol is a special symbol
|
leading character used by the object file format, remove the
|
leading character used by the object file format, remove the
|
character. The most common symbol leading character is
|
character. The most common symbol leading character is
|
underscore. This option will remove a leading underscore from all
|
underscore. This option will remove a leading underscore from all
|
global symbols. This can be useful if you want to link together
|
global symbols. This can be useful if you want to link together
|
objects of different file formats with different conventions for
|
objects of different file formats with different conventions for
|
symbol names. This is different from `--change-leading-char'
|
symbol names. This is different from `--change-leading-char'
|
because it always changes the symbol name when appropriate,
|
because it always changes the symbol name when appropriate,
|
regardless of the object file format of the output file.
|
regardless of the object file format of the output file.
|
|
|
`--reverse-bytes=NUM'
|
`--reverse-bytes=NUM'
|
Reverse the bytes in a section with output contents. A section
|
Reverse the bytes in a section with output contents. A section
|
length must be evenly divisible by the value given in order for
|
length must be evenly divisible by the value given in order for
|
the swap to be able to take place. Reversing takes place before
|
the swap to be able to take place. Reversing takes place before
|
the interleaving is performed.
|
the interleaving is performed.
|
|
|
This option is used typically in generating ROM images for
|
This option is used typically in generating ROM images for
|
problematic target systems. For example, on some target boards,
|
problematic target systems. For example, on some target boards,
|
the 32-bit words fetched from 8-bit ROMs are re-assembled in
|
the 32-bit words fetched from 8-bit ROMs are re-assembled in
|
little-endian byte order regardless of the CPU byte order.
|
little-endian byte order regardless of the CPU byte order.
|
Depending on the programming model, the endianness of the ROM may
|
Depending on the programming model, the endianness of the ROM may
|
need to be modified.
|
need to be modified.
|
|
|
Consider a simple file with a section containing the following
|
Consider a simple file with a section containing the following
|
eight bytes: `12345678'.
|
eight bytes: `12345678'.
|
|
|
Using `--reverse-bytes=2' for the above example, the bytes in the
|
Using `--reverse-bytes=2' for the above example, the bytes in the
|
output file would be ordered `21436587'.
|
output file would be ordered `21436587'.
|
|
|
Using `--reverse-bytes=4' for the above example, the bytes in the
|
Using `--reverse-bytes=4' for the above example, the bytes in the
|
output file would be ordered `43218765'.
|
output file would be ordered `43218765'.
|
|
|
By using `--reverse-bytes=2' for the above example, followed by
|
By using `--reverse-bytes=2' for the above example, followed by
|
`--reverse-bytes=4' on the output file, the bytes in the second
|
`--reverse-bytes=4' on the output file, the bytes in the second
|
output file would be ordered `34127856'.
|
output file would be ordered `34127856'.
|
|
|
`--srec-len=IVAL'
|
`--srec-len=IVAL'
|
Meaningful only for srec output. Set the maximum length of the
|
Meaningful only for srec output. Set the maximum length of the
|
Srecords being produced to IVAL. This length covers both address,
|
Srecords being produced to IVAL. This length covers both address,
|
data and crc fields.
|
data and crc fields.
|
|
|
`--srec-forceS3'
|
`--srec-forceS3'
|
Meaningful only for srec output. Avoid generation of S1/S2
|
Meaningful only for srec output. Avoid generation of S1/S2
|
records, creating S3-only record format.
|
records, creating S3-only record format.
|
|
|
`--redefine-sym OLD=NEW'
|
`--redefine-sym OLD=NEW'
|
Change the name of a symbol OLD, to NEW. This can be useful when
|
Change the name of a symbol OLD, to NEW. This can be useful when
|
one is trying link two things together for which you have no
|
one is trying link two things together for which you have no
|
source, and there are name collisions.
|
source, and there are name collisions.
|
|
|
`--redefine-syms=FILENAME'
|
`--redefine-syms=FILENAME'
|
Apply `--redefine-sym' to each symbol pair "OLD NEW" listed in the
|
Apply `--redefine-sym' to each symbol pair "OLD NEW" listed in the
|
file FILENAME. FILENAME is simply a flat file, with one symbol
|
file FILENAME. FILENAME is simply a flat file, with one symbol
|
pair per line. Line comments may be introduced by the hash
|
pair per line. Line comments may be introduced by the hash
|
character. This option may be given more than once.
|
character. This option may be given more than once.
|
|
|
`--weaken'
|
`--weaken'
|
Change all global symbols in the file to be weak. This can be
|
Change all global symbols in the file to be weak. This can be
|
useful when building an object which will be linked against other
|
useful when building an object which will be linked against other
|
objects using the `-R' option to the linker. This option is only
|
objects using the `-R' option to the linker. This option is only
|
effective when using an object file format which supports weak
|
effective when using an object file format which supports weak
|
symbols.
|
symbols.
|
|
|
`--keep-symbols=FILENAME'
|
`--keep-symbols=FILENAME'
|
Apply `--keep-symbol' option to each symbol listed in the file
|
Apply `--keep-symbol' option to each symbol listed in the file
|
FILENAME. FILENAME is simply a flat file, with one symbol name
|
FILENAME. FILENAME is simply a flat file, with one symbol name
|
per line. Line comments may be introduced by the hash character.
|
per line. Line comments may be introduced by the hash character.
|
This option may be given more than once.
|
This option may be given more than once.
|
|
|
`--strip-symbols=FILENAME'
|
`--strip-symbols=FILENAME'
|
Apply `--strip-symbol' option to each symbol listed in the file
|
Apply `--strip-symbol' option to each symbol listed in the file
|
FILENAME. FILENAME is simply a flat file, with one symbol name
|
FILENAME. FILENAME is simply a flat file, with one symbol name
|
per line. Line comments may be introduced by the hash character.
|
per line. Line comments may be introduced by the hash character.
|
This option may be given more than once.
|
This option may be given more than once.
|
|
|
`--strip-unneeded-symbols=FILENAME'
|
`--strip-unneeded-symbols=FILENAME'
|
Apply `--strip-unneeded-symbol' option to each symbol listed in
|
Apply `--strip-unneeded-symbol' option to each symbol listed in
|
the file FILENAME. FILENAME is simply a flat file, with one
|
the file FILENAME. FILENAME is simply a flat file, with one
|
symbol name per line. Line comments may be introduced by the hash
|
symbol name per line. Line comments may be introduced by the hash
|
character. This option may be given more than once.
|
character. This option may be given more than once.
|
|
|
`--keep-global-symbols=FILENAME'
|
`--keep-global-symbols=FILENAME'
|
Apply `--keep-global-symbol' option to each symbol listed in the
|
Apply `--keep-global-symbol' option to each symbol listed in the
|
file FILENAME. FILENAME is simply a flat file, with one symbol
|
file FILENAME. FILENAME is simply a flat file, with one symbol
|
name per line. Line comments may be introduced by the hash
|
name per line. Line comments may be introduced by the hash
|
character. This option may be given more than once.
|
character. This option may be given more than once.
|
|
|
`--localize-symbols=FILENAME'
|
`--localize-symbols=FILENAME'
|
Apply `--localize-symbol' option to each symbol listed in the file
|
Apply `--localize-symbol' option to each symbol listed in the file
|
FILENAME. FILENAME is simply a flat file, with one symbol name
|
FILENAME. FILENAME is simply a flat file, with one symbol name
|
per line. Line comments may be introduced by the hash character.
|
per line. Line comments may be introduced by the hash character.
|
This option may be given more than once.
|
This option may be given more than once.
|
|
|
`--globalize-symbols=FILENAME'
|
`--globalize-symbols=FILENAME'
|
Apply `--globalize-symbol' option to each symbol listed in the file
|
Apply `--globalize-symbol' option to each symbol listed in the file
|
FILENAME. FILENAME is simply a flat file, with one symbol name
|
FILENAME. FILENAME is simply a flat file, with one symbol name
|
per line. Line comments may be introduced by the hash character.
|
per line. Line comments may be introduced by the hash character.
|
This option may be given more than once.
|
This option may be given more than once.
|
|
|
`--weaken-symbols=FILENAME'
|
`--weaken-symbols=FILENAME'
|
Apply `--weaken-symbol' option to each symbol listed in the file
|
Apply `--weaken-symbol' option to each symbol listed in the file
|
FILENAME. FILENAME is simply a flat file, with one symbol name
|
FILENAME. FILENAME is simply a flat file, with one symbol name
|
per line. Line comments may be introduced by the hash character.
|
per line. Line comments may be introduced by the hash character.
|
This option may be given more than once.
|
This option may be given more than once.
|
|
|
`--alt-machine-code=INDEX'
|
`--alt-machine-code=INDEX'
|
If the output architecture has alternate machine codes, use the
|
If the output architecture has alternate machine codes, use the
|
INDEXth code instead of the default one. This is useful in case a
|
INDEXth code instead of the default one. This is useful in case a
|
machine is assigned an official code and the tool-chain adopts the
|
machine is assigned an official code and the tool-chain adopts the
|
new code, but other applications still depend on the original code
|
new code, but other applications still depend on the original code
|
being used. For ELF based architectures if the INDEX alternative
|
being used. For ELF based architectures if the INDEX alternative
|
does not exist then the value is treated as an absolute number to
|
does not exist then the value is treated as an absolute number to
|
be stored in the e_machine field of the ELF header.
|
be stored in the e_machine field of the ELF header.
|
|
|
`--writable-text'
|
`--writable-text'
|
Mark the output text as writable. This option isn't meaningful
|
Mark the output text as writable. This option isn't meaningful
|
for all object file formats.
|
for all object file formats.
|
|
|
`--readonly-text'
|
`--readonly-text'
|
Make the output text write protected. This option isn't
|
Make the output text write protected. This option isn't
|
meaningful for all object file formats.
|
meaningful for all object file formats.
|
|
|
`--pure'
|
`--pure'
|
Mark the output file as demand paged. This option isn't
|
Mark the output file as demand paged. This option isn't
|
meaningful for all object file formats.
|
meaningful for all object file formats.
|
|
|
`--impure'
|
`--impure'
|
Mark the output file as impure. This option isn't meaningful for
|
Mark the output file as impure. This option isn't meaningful for
|
all object file formats.
|
all object file formats.
|
|
|
`--prefix-symbols=STRING'
|
`--prefix-symbols=STRING'
|
Prefix all symbols in the output file with STRING.
|
Prefix all symbols in the output file with STRING.
|
|
|
`--prefix-sections=STRING'
|
`--prefix-sections=STRING'
|
Prefix all section names in the output file with STRING.
|
Prefix all section names in the output file with STRING.
|
|
|
`--prefix-alloc-sections=STRING'
|
`--prefix-alloc-sections=STRING'
|
Prefix all the names of all allocated sections in the output file
|
Prefix all the names of all allocated sections in the output file
|
with STRING.
|
with STRING.
|
|
|
`--add-gnu-debuglink=PATH-TO-FILE'
|
`--add-gnu-debuglink=PATH-TO-FILE'
|
Creates a .gnu_debuglink section which contains a reference to
|
Creates a .gnu_debuglink section which contains a reference to
|
PATH-TO-FILE and adds it to the output file.
|
PATH-TO-FILE and adds it to the output file.
|
|
|
`--keep-file-symbols'
|
`--keep-file-symbols'
|
When stripping a file, perhaps with `--strip-debug' or
|
When stripping a file, perhaps with `--strip-debug' or
|
`--strip-unneeded', retain any symbols specifying source file
|
`--strip-unneeded', retain any symbols specifying source file
|
names, which would otherwise get stripped.
|
names, which would otherwise get stripped.
|
|
|
`--only-keep-debug'
|
`--only-keep-debug'
|
Strip a file, removing contents of any sections that would not be
|
Strip a file, removing contents of any sections that would not be
|
stripped by `--strip-debug' and leaving the debugging sections
|
stripped by `--strip-debug' and leaving the debugging sections
|
intact. In ELF files, this preserves all note sections in the
|
intact. In ELF files, this preserves all note sections in the
|
output.
|
output.
|
|
|
The intention is that this option will be used in conjunction with
|
The intention is that this option will be used in conjunction with
|
`--add-gnu-debuglink' to create a two part executable. One a
|
`--add-gnu-debuglink' to create a two part executable. One a
|
stripped binary which will occupy less space in RAM and in a
|
stripped binary which will occupy less space in RAM and in a
|
distribution and the second a debugging information file which is
|
distribution and the second a debugging information file which is
|
only needed if debugging abilities are required. The suggested
|
only needed if debugging abilities are required. The suggested
|
procedure to create these files is as follows:
|
procedure to create these files is as follows:
|
|
|
1. Link the executable as normal. Assuming that is is called
|
1. Link the executable as normal. Assuming that is is called
|
`foo' then...
|
`foo' then...
|
|
|
2. Run `objcopy --only-keep-debug foo foo.dbg' to create a file
|
2. Run `objcopy --only-keep-debug foo foo.dbg' to create a file
|
containing the debugging info.
|
containing the debugging info.
|
|
|
3. Run `objcopy --strip-debug foo' to create a stripped
|
3. Run `objcopy --strip-debug foo' to create a stripped
|
executable.
|
executable.
|
|
|
4. Run `objcopy --add-gnu-debuglink=foo.dbg foo' to add a link
|
4. Run `objcopy --add-gnu-debuglink=foo.dbg foo' to add a link
|
to the debugging info into the stripped executable.
|
to the debugging info into the stripped executable.
|
|
|
Note--the choice of `.dbg' as an extension for the debug info file
|
Note--the choice of `.dbg' as an extension for the debug info file
|
is arbitrary. Also the `--only-keep-debug' step is optional. You
|
is arbitrary. Also the `--only-keep-debug' step is optional. You
|
could instead do this:
|
could instead do this:
|
|
|
1. Link the executable as normal.
|
1. Link the executable as normal.
|
|
|
2. Copy `foo' to `foo.full'
|
2. Copy `foo' to `foo.full'
|
|
|
3. Run `objcopy --strip-debug foo'
|
3. Run `objcopy --strip-debug foo'
|
|
|
4. Run `objcopy --add-gnu-debuglink=foo.full foo'
|
4. Run `objcopy --add-gnu-debuglink=foo.full foo'
|
|
|
i.e., the file pointed to by the `--add-gnu-debuglink' can be the
|
i.e., the file pointed to by the `--add-gnu-debuglink' can be the
|
full executable. It does not have to be a file created by the
|
full executable. It does not have to be a file created by the
|
`--only-keep-debug' switch.
|
`--only-keep-debug' switch.
|
|
|
Note--this switch is only intended for use on fully linked files.
|
Note--this switch is only intended for use on fully linked files.
|
It does not make sense to use it on object files where the
|
It does not make sense to use it on object files where the
|
debugging information may be incomplete. Besides the
|
debugging information may be incomplete. Besides the
|
gnu_debuglink feature currently only supports the presence of one
|
gnu_debuglink feature currently only supports the presence of one
|
filename containing debugging information, not multiple filenames
|
filename containing debugging information, not multiple filenames
|
on a one-per-object-file basis.
|
on a one-per-object-file basis.
|
|
|
`--extract-symbol'
|
`--extract-symbol'
|
Keep the file's section flags and symbols but remove all section
|
Keep the file's section flags and symbols but remove all section
|
data. Specifically, the option:
|
data. Specifically, the option:
|
|
|
* sets the virtual and load addresses of every section to zero;
|
* sets the virtual and load addresses of every section to zero;
|
|
|
* removes the contents of all sections;
|
* removes the contents of all sections;
|
|
|
* sets the size of every section to zero; and
|
* sets the size of every section to zero; and
|
|
|
* sets the file's start address to zero.
|
* sets the file's start address to zero.
|
|
|
This option is used to build a `.sym' file for a VxWorks kernel.
|
This option is used to build a `.sym' file for a VxWorks kernel.
|
It can also be a useful way of reducing the size of a
|
It can also be a useful way of reducing the size of a
|
`--just-symbols' linker input file.
|
`--just-symbols' linker input file.
|
|
|
`-V'
|
`-V'
|
`--version'
|
`--version'
|
Show the version number of `objcopy'.
|
Show the version number of `objcopy'.
|
|
|
`-v'
|
`-v'
|
`--verbose'
|
`--verbose'
|
Verbose output: list all object files modified. In the case of
|
Verbose output: list all object files modified. In the case of
|
archives, `objcopy -V' lists all members of the archive.
|
archives, `objcopy -V' lists all members of the archive.
|
|
|
`--help'
|
`--help'
|
Show a summary of the options to `objcopy'.
|
Show a summary of the options to `objcopy'.
|
|
|
`--info'
|
`--info'
|
Display a list showing all architectures and object formats
|
Display a list showing all architectures and object formats
|
available.
|
available.
|
|
|
|
|
File: binutils.info, Node: objdump, Next: ranlib, Prev: objcopy, Up: Top
|
File: binutils.info, Node: objdump, Next: ranlib, Prev: objcopy, Up: Top
|
|
|
4 objdump
|
4 objdump
|
*********
|
*********
|
|
|
objdump [`-a'|`--archive-headers']
|
objdump [`-a'|`--archive-headers']
|
[`-b' BFDNAME|`--target=BFDNAME']
|
[`-b' BFDNAME|`--target=BFDNAME']
|
[`-C'|`--demangle'[=STYLE] ]
|
[`-C'|`--demangle'[=STYLE] ]
|
[`-d'|`--disassemble']
|
[`-d'|`--disassemble']
|
[`-D'|`--disassemble-all']
|
[`-D'|`--disassemble-all']
|
[`-z'|`--disassemble-zeroes']
|
[`-z'|`--disassemble-zeroes']
|
[`-EB'|`-EL'|`--endian='{big | little }]
|
[`-EB'|`-EL'|`--endian='{big | little }]
|
[`-f'|`--file-headers']
|
[`-f'|`--file-headers']
|
[`-F'|`--file-offsets']
|
[`-F'|`--file-offsets']
|
[`--file-start-context']
|
[`--file-start-context']
|
[`-g'|`--debugging']
|
[`-g'|`--debugging']
|
[`-e'|`--debugging-tags']
|
[`-e'|`--debugging-tags']
|
[`-h'|`--section-headers'|`--headers']
|
[`-h'|`--section-headers'|`--headers']
|
[`-i'|`--info']
|
[`-i'|`--info']
|
[`-j' SECTION|`--section='SECTION]
|
[`-j' SECTION|`--section='SECTION]
|
[`-l'|`--line-numbers']
|
[`-l'|`--line-numbers']
|
[`-S'|`--source']
|
[`-S'|`--source']
|
[`-m' MACHINE|`--architecture='MACHINE]
|
[`-m' MACHINE|`--architecture='MACHINE]
|
[`-M' OPTIONS|`--disassembler-options='OPTIONS]
|
[`-M' OPTIONS|`--disassembler-options='OPTIONS]
|
[`-p'|`--private-headers']
|
[`-p'|`--private-headers']
|
[`-r'|`--reloc']
|
[`-r'|`--reloc']
|
[`-R'|`--dynamic-reloc']
|
[`-R'|`--dynamic-reloc']
|
[`-s'|`--full-contents']
|
[`-s'|`--full-contents']
|
[`-W'|`--dwarf']
|
[`-W'|`--dwarf']
|
[`-G'|`--stabs']
|
[`-G'|`--stabs']
|
[`-t'|`--syms']
|
[`-t'|`--syms']
|
[`-T'|`--dynamic-syms']
|
[`-T'|`--dynamic-syms']
|
[`-x'|`--all-headers']
|
[`-x'|`--all-headers']
|
[`-w'|`--wide']
|
[`-w'|`--wide']
|
[`--start-address='ADDRESS]
|
[`--start-address='ADDRESS]
|
[`--stop-address='ADDRESS]
|
[`--stop-address='ADDRESS]
|
[`--prefix-addresses']
|
[`--prefix-addresses']
|
[`--[no-]show-raw-insn']
|
[`--[no-]show-raw-insn']
|
[`--adjust-vma='OFFSET]
|
[`--adjust-vma='OFFSET]
|
[`--special-syms']
|
[`--special-syms']
|
[`-V'|`--version']
|
[`-V'|`--version']
|
[`-H'|`--help']
|
[`-H'|`--help']
|
OBJFILE...
|
OBJFILE...
|
|
|
`objdump' displays information about one or more object files. The
|
`objdump' displays information about one or more object files. The
|
options control what particular information to display. This
|
options control what particular information to display. This
|
information is mostly useful to programmers who are working on the
|
information is mostly useful to programmers who are working on the
|
compilation tools, as opposed to programmers who just want their
|
compilation tools, as opposed to programmers who just want their
|
program to compile and work.
|
program to compile and work.
|
|
|
OBJFILE... are the object files to be examined. When you specify
|
OBJFILE... are the object files to be examined. When you specify
|
archives, `objdump' shows information on each of the member object
|
archives, `objdump' shows information on each of the member object
|
files.
|
files.
|
|
|
The long and short forms of options, shown here as alternatives, are
|
The long and short forms of options, shown here as alternatives, are
|
equivalent. At least one option from the list
|
equivalent. At least one option from the list
|
`-a,-d,-D,-e,-f,-g,-G,-h,-H,-p,-r,-R,-s,-S,-t,-T,-V,-x' must be given.
|
`-a,-d,-D,-e,-f,-g,-G,-h,-H,-p,-r,-R,-s,-S,-t,-T,-V,-x' must be given.
|
|
|
`-a'
|
`-a'
|
`--archive-header'
|
`--archive-header'
|
If any of the OBJFILE files are archives, display the archive
|
If any of the OBJFILE files are archives, display the archive
|
header information (in a format similar to `ls -l'). Besides the
|
header information (in a format similar to `ls -l'). Besides the
|
information you could list with `ar tv', `objdump -a' shows the
|
information you could list with `ar tv', `objdump -a' shows the
|
object file format of each archive member.
|
object file format of each archive member.
|
|
|
`--adjust-vma=OFFSET'
|
`--adjust-vma=OFFSET'
|
When dumping information, first add OFFSET to all the section
|
When dumping information, first add OFFSET to all the section
|
addresses. This is useful if the section addresses do not
|
addresses. This is useful if the section addresses do not
|
correspond to the symbol table, which can happen when putting
|
correspond to the symbol table, which can happen when putting
|
sections at particular addresses when using a format which can not
|
sections at particular addresses when using a format which can not
|
represent section addresses, such as a.out.
|
represent section addresses, such as a.out.
|
|
|
`-b BFDNAME'
|
`-b BFDNAME'
|
`--target=BFDNAME'
|
`--target=BFDNAME'
|
Specify that the object-code format for the object files is
|
Specify that the object-code format for the object files is
|
BFDNAME. This option may not be necessary; OBJDUMP can
|
BFDNAME. This option may not be necessary; OBJDUMP can
|
automatically recognize many formats.
|
automatically recognize many formats.
|
|
|
For example,
|
For example,
|
objdump -b oasys -m vax -h fu.o
|
objdump -b oasys -m vax -h fu.o
|
displays summary information from the section headers (`-h') of
|
displays summary information from the section headers (`-h') of
|
`fu.o', which is explicitly identified (`-m') as a VAX object file
|
`fu.o', which is explicitly identified (`-m') as a VAX object file
|
in the format produced by Oasys compilers. You can list the
|
in the format produced by Oasys compilers. You can list the
|
formats available with the `-i' option. *Note Target Selection::,
|
formats available with the `-i' option. *Note Target Selection::,
|
for more information.
|
for more information.
|
|
|
`-C'
|
`-C'
|
`--demangle[=STYLE]'
|
`--demangle[=STYLE]'
|
Decode ("demangle") low-level symbol names into user-level names.
|
Decode ("demangle") low-level symbol names into user-level names.
|
Besides removing any initial underscore prepended by the system,
|
Besides removing any initial underscore prepended by the system,
|
this makes C++ function names readable. Different compilers have
|
this makes C++ function names readable. Different compilers have
|
different mangling styles. The optional demangling style argument
|
different mangling styles. The optional demangling style argument
|
can be used to choose an appropriate demangling style for your
|
can be used to choose an appropriate demangling style for your
|
compiler. *Note c++filt::, for more information on demangling.
|
compiler. *Note c++filt::, for more information on demangling.
|
|
|
`-g'
|
`-g'
|
`--debugging'
|
`--debugging'
|
Display debugging information. This attempts to parse debugging
|
Display debugging information. This attempts to parse debugging
|
information stored in the file and print it out using a C like
|
information stored in the file and print it out using a C like
|
syntax. Only certain types of debugging information have been
|
syntax. Only certain types of debugging information have been
|
implemented. Some other types are supported by `readelf -w'.
|
implemented. Some other types are supported by `readelf -w'.
|
*Note readelf::.
|
*Note readelf::.
|
|
|
`-e'
|
`-e'
|
`--debugging-tags'
|
`--debugging-tags'
|
Like `-g', but the information is generated in a format compatible
|
Like `-g', but the information is generated in a format compatible
|
with ctags tool.
|
with ctags tool.
|
|
|
`-d'
|
`-d'
|
`--disassemble'
|
`--disassemble'
|
Display the assembler mnemonics for the machine instructions from
|
Display the assembler mnemonics for the machine instructions from
|
OBJFILE. This option only disassembles those sections which are
|
OBJFILE. This option only disassembles those sections which are
|
expected to contain instructions.
|
expected to contain instructions.
|
|
|
`-D'
|
`-D'
|
`--disassemble-all'
|
`--disassemble-all'
|
Like `-d', but disassemble the contents of all sections, not just
|
Like `-d', but disassemble the contents of all sections, not just
|
those expected to contain instructions.
|
those expected to contain instructions.
|
|
|
`--prefix-addresses'
|
`--prefix-addresses'
|
When disassembling, print the complete address on each line. This
|
When disassembling, print the complete address on each line. This
|
is the older disassembly format.
|
is the older disassembly format.
|
|
|
`-EB'
|
`-EB'
|
`-EL'
|
`-EL'
|
`--endian={big|little}'
|
`--endian={big|little}'
|
Specify the endianness of the object files. This only affects
|
Specify the endianness of the object files. This only affects
|
disassembly. This can be useful when disassembling a file format
|
disassembly. This can be useful when disassembling a file format
|
which does not describe endianness information, such as S-records.
|
which does not describe endianness information, such as S-records.
|
|
|
`-f'
|
`-f'
|
`--file-headers'
|
`--file-headers'
|
Display summary information from the overall header of each of the
|
Display summary information from the overall header of each of the
|
OBJFILE files.
|
OBJFILE files.
|
|
|
`-F'
|
`-F'
|
`--file-offsets'
|
`--file-offsets'
|
When disassembling sections, whenever a symbol is displayed, also
|
When disassembling sections, whenever a symbol is displayed, also
|
display the file offset of the region of data that is about to be
|
display the file offset of the region of data that is about to be
|
dumped. If zeroes are being skipped, then when disassembly
|
dumped. If zeroes are being skipped, then when disassembly
|
resumes, tell the user how many zeroes were skipped and the file
|
resumes, tell the user how many zeroes were skipped and the file
|
offset of the location from where the disassembly resumes. When
|
offset of the location from where the disassembly resumes. When
|
dumping sections, display the file offset of the location from
|
dumping sections, display the file offset of the location from
|
where the dump starts.
|
where the dump starts.
|
|
|
`--file-start-context'
|
`--file-start-context'
|
Specify that when displaying interlisted source code/disassembly
|
Specify that when displaying interlisted source code/disassembly
|
(assumes `-S') from a file that has not yet been displayed, extend
|
(assumes `-S') from a file that has not yet been displayed, extend
|
the context to the start of the file.
|
the context to the start of the file.
|
|
|
`-h'
|
`-h'
|
`--section-headers'
|
`--section-headers'
|
`--headers'
|
`--headers'
|
Display summary information from the section headers of the object
|
Display summary information from the section headers of the object
|
file.
|
file.
|
|
|
File segments may be relocated to nonstandard addresses, for
|
File segments may be relocated to nonstandard addresses, for
|
example by using the `-Ttext', `-Tdata', or `-Tbss' options to
|
example by using the `-Ttext', `-Tdata', or `-Tbss' options to
|
`ld'. However, some object file formats, such as a.out, do not
|
`ld'. However, some object file formats, such as a.out, do not
|
store the starting address of the file segments. In those
|
store the starting address of the file segments. In those
|
situations, although `ld' relocates the sections correctly, using
|
situations, although `ld' relocates the sections correctly, using
|
`objdump -h' to list the file section headers cannot show the
|
`objdump -h' to list the file section headers cannot show the
|
correct addresses. Instead, it shows the usual addresses, which
|
correct addresses. Instead, it shows the usual addresses, which
|
are implicit for the target.
|
are implicit for the target.
|
|
|
`-H'
|
`-H'
|
`--help'
|
`--help'
|
Print a summary of the options to `objdump' and exit.
|
Print a summary of the options to `objdump' and exit.
|
|
|
`-i'
|
`-i'
|
`--info'
|
`--info'
|
Display a list showing all architectures and object formats
|
Display a list showing all architectures and object formats
|
available for specification with `-b' or `-m'.
|
available for specification with `-b' or `-m'.
|
|
|
`-j NAME'
|
`-j NAME'
|
`--section=NAME'
|
`--section=NAME'
|
Display information only for section NAME.
|
Display information only for section NAME.
|
|
|
`-l'
|
`-l'
|
`--line-numbers'
|
`--line-numbers'
|
Label the display (using debugging information) with the filename
|
Label the display (using debugging information) with the filename
|
and source line numbers corresponding to the object code or relocs
|
and source line numbers corresponding to the object code or relocs
|
shown. Only useful with `-d', `-D', or `-r'.
|
shown. Only useful with `-d', `-D', or `-r'.
|
|
|
`-m MACHINE'
|
`-m MACHINE'
|
`--architecture=MACHINE'
|
`--architecture=MACHINE'
|
Specify the architecture to use when disassembling object files.
|
Specify the architecture to use when disassembling object files.
|
This can be useful when disassembling object files which do not
|
This can be useful when disassembling object files which do not
|
describe architecture information, such as S-records. You can
|
describe architecture information, such as S-records. You can
|
list the available architectures with the `-i' option.
|
list the available architectures with the `-i' option.
|
|
|
`-M OPTIONS'
|
`-M OPTIONS'
|
`--disassembler-options=OPTIONS'
|
`--disassembler-options=OPTIONS'
|
Pass target specific information to the disassembler. Only
|
Pass target specific information to the disassembler. Only
|
supported on some targets. If it is necessary to specify more
|
supported on some targets. If it is necessary to specify more
|
than one disassembler option then multiple `-M' options can be
|
than one disassembler option then multiple `-M' options can be
|
used or can be placed together into a comma separated list.
|
used or can be placed together into a comma separated list.
|
|
|
If the target is an ARM architecture then this switch can be used
|
If the target is an ARM architecture then this switch can be used
|
to select which register name set is used during disassembler.
|
to select which register name set is used during disassembler.
|
Specifying `-M reg-names-std' (the default) will select the
|
Specifying `-M reg-names-std' (the default) will select the
|
register names as used in ARM's instruction set documentation, but
|
register names as used in ARM's instruction set documentation, but
|
with register 13 called 'sp', register 14 called 'lr' and register
|
with register 13 called 'sp', register 14 called 'lr' and register
|
15 called 'pc'. Specifying `-M reg-names-apcs' will select the
|
15 called 'pc'. Specifying `-M reg-names-apcs' will select the
|
name set used by the ARM Procedure Call Standard, whilst
|
name set used by the ARM Procedure Call Standard, whilst
|
specifying `-M reg-names-raw' will just use `r' followed by the
|
specifying `-M reg-names-raw' will just use `r' followed by the
|
register number.
|
register number.
|
|
|
There are also two variants on the APCS register naming scheme
|
There are also two variants on the APCS register naming scheme
|
enabled by `-M reg-names-atpcs' and `-M reg-names-special-atpcs'
|
enabled by `-M reg-names-atpcs' and `-M reg-names-special-atpcs'
|
which use the ARM/Thumb Procedure Call Standard naming
|
which use the ARM/Thumb Procedure Call Standard naming
|
conventions. (Either with the normal register names or the
|
conventions. (Either with the normal register names or the
|
special register names).
|
special register names).
|
|
|
This option can also be used for ARM architectures to force the
|
This option can also be used for ARM architectures to force the
|
disassembler to interpret all instructions as Thumb instructions by
|
disassembler to interpret all instructions as Thumb instructions by
|
using the switch `--disassembler-options=force-thumb'. This can be
|
using the switch `--disassembler-options=force-thumb'. This can be
|
useful when attempting to disassemble thumb code produced by other
|
useful when attempting to disassemble thumb code produced by other
|
compilers.
|
compilers.
|
|
|
For the x86, some of the options duplicate functions of the `-m'
|
For the x86, some of the options duplicate functions of the `-m'
|
switch, but allow finer grained control. Multiple selections from
|
switch, but allow finer grained control. Multiple selections from
|
the following may be specified as a comma separated string.
|
the following may be specified as a comma separated string.
|
`x86-64', `i386' and `i8086' select disassembly for the given
|
`x86-64', `i386' and `i8086' select disassembly for the given
|
architecture. `intel' and `att' select between intel syntax mode
|
architecture. `intel' and `att' select between intel syntax mode
|
and AT&T syntax mode. `intel-mnemonic' and `att-mnemonic' select
|
and AT&T syntax mode. `intel-mnemonic' and `att-mnemonic' select
|
between intel mnemonic mode and AT&T mnemonic mode.
|
between intel mnemonic mode and AT&T mnemonic mode.
|
`intel-mnemonic' implies `intel' and `att-mnemonic' implies `att'.
|
`intel-mnemonic' implies `intel' and `att-mnemonic' implies `att'.
|
`addr64', `addr32', `addr16', `data32' and `data16' specify the
|
`addr64', `addr32', `addr16', `data32' and `data16' specify the
|
default address size and operand size. These four options will be
|
default address size and operand size. These four options will be
|
overridden if `x86-64', `i386' or `i8086' appear later in the
|
overridden if `x86-64', `i386' or `i8086' appear later in the
|
option string. Lastly, `suffix', when in AT&T mode, instructs the
|
option string. Lastly, `suffix', when in AT&T mode, instructs the
|
disassembler to print a mnemonic suffix even when the suffix could
|
disassembler to print a mnemonic suffix even when the suffix could
|
be inferred by the operands.
|
be inferred by the operands.
|
|
|
For PPC, `booke', `booke32' and `booke64' select disassembly of
|
For PPC, `booke', `booke32' and `booke64' select disassembly of
|
BookE instructions. `32' and `64' select PowerPC and PowerPC64
|
BookE instructions. `32' and `64' select PowerPC and PowerPC64
|
disassembly, respectively. `e300' selects disassembly for the
|
disassembly, respectively. `e300' selects disassembly for the
|
e300 family. `440' selects disassembly for the PowerPC 440.
|
e300 family. `440' selects disassembly for the PowerPC 440.
|
`ppcps' selects disassembly for the paired single instructions of
|
`ppcps' selects disassembly for the paired single instructions of
|
the PPC750CL.
|
the PPC750CL.
|
|
|
For MIPS, this option controls the printing of instruction mnemonic
|
For MIPS, this option controls the printing of instruction mnemonic
|
names and register names in disassembled instructions. Multiple
|
names and register names in disassembled instructions. Multiple
|
selections from the following may be specified as a comma separated
|
selections from the following may be specified as a comma separated
|
string, and invalid options are ignored:
|
string, and invalid options are ignored:
|
|
|
`no-aliases'
|
`no-aliases'
|
Print the 'raw' instruction mnemonic instead of some pseudo
|
Print the 'raw' instruction mnemonic instead of some pseudo
|
instruction mnemonic. I.e., print 'daddu' or 'or' instead of
|
instruction mnemonic. I.e., print 'daddu' or 'or' instead of
|
'move', 'sll' instead of 'nop', etc.
|
'move', 'sll' instead of 'nop', etc.
|
|
|
`gpr-names=ABI'
|
`gpr-names=ABI'
|
Print GPR (general-purpose register) names as appropriate for
|
Print GPR (general-purpose register) names as appropriate for
|
the specified ABI. By default, GPR names are selected
|
the specified ABI. By default, GPR names are selected
|
according to the ABI of the binary being disassembled.
|
according to the ABI of the binary being disassembled.
|
|
|
`fpr-names=ABI'
|
`fpr-names=ABI'
|
Print FPR (floating-point register) names as appropriate for
|
Print FPR (floating-point register) names as appropriate for
|
the specified ABI. By default, FPR numbers are printed
|
the specified ABI. By default, FPR numbers are printed
|
rather than names.
|
rather than names.
|
|
|
`cp0-names=ARCH'
|
`cp0-names=ARCH'
|
Print CP0 (system control coprocessor; coprocessor 0)
|
Print CP0 (system control coprocessor; coprocessor 0)
|
register names as appropriate for the CPU or architecture
|
register names as appropriate for the CPU or architecture
|
specified by ARCH. By default, CP0 register names are
|
specified by ARCH. By default, CP0 register names are
|
selected according to the architecture and CPU of the binary
|
selected according to the architecture and CPU of the binary
|
being disassembled.
|
being disassembled.
|
|
|
`hwr-names=ARCH'
|
`hwr-names=ARCH'
|
Print HWR (hardware register, used by the `rdhwr'
|
Print HWR (hardware register, used by the `rdhwr'
|
instruction) names as appropriate for the CPU or architecture
|
instruction) names as appropriate for the CPU or architecture
|
specified by ARCH. By default, HWR names are selected
|
specified by ARCH. By default, HWR names are selected
|
according to the architecture and CPU of the binary being
|
according to the architecture and CPU of the binary being
|
disassembled.
|
disassembled.
|
|
|
`reg-names=ABI'
|
`reg-names=ABI'
|
Print GPR and FPR names as appropriate for the selected ABI.
|
Print GPR and FPR names as appropriate for the selected ABI.
|
|
|
`reg-names=ARCH'
|
`reg-names=ARCH'
|
Print CPU-specific register names (CP0 register and HWR names)
|
Print CPU-specific register names (CP0 register and HWR names)
|
as appropriate for the selected CPU or architecture.
|
as appropriate for the selected CPU or architecture.
|
|
|
For any of the options listed above, ABI or ARCH may be specified
|
For any of the options listed above, ABI or ARCH may be specified
|
as `numeric' to have numbers printed rather than names, for the
|
as `numeric' to have numbers printed rather than names, for the
|
selected types of registers. You can list the available values of
|
selected types of registers. You can list the available values of
|
ABI and ARCH using the `--help' option.
|
ABI and ARCH using the `--help' option.
|
|
|
For VAX, you can specify function entry addresses with `-M
|
For VAX, you can specify function entry addresses with `-M
|
entry:0xf00ba'. You can use this multiple times to properly
|
entry:0xf00ba'. You can use this multiple times to properly
|
disassemble VAX binary files that don't contain symbol tables (like
|
disassemble VAX binary files that don't contain symbol tables (like
|
ROM dumps). In these cases, the function entry mask would
|
ROM dumps). In these cases, the function entry mask would
|
otherwise be decoded as VAX instructions, which would probably
|
otherwise be decoded as VAX instructions, which would probably
|
lead the rest of the function being wrongly disassembled.
|
lead the rest of the function being wrongly disassembled.
|
|
|
`-p'
|
`-p'
|
`--private-headers'
|
`--private-headers'
|
Print information that is specific to the object file format. The
|
Print information that is specific to the object file format. The
|
exact information printed depends upon the object file format.
|
exact information printed depends upon the object file format.
|
For some object file formats, no additional information is printed.
|
For some object file formats, no additional information is printed.
|
|
|
`-r'
|
`-r'
|
`--reloc'
|
`--reloc'
|
Print the relocation entries of the file. If used with `-d' or
|
Print the relocation entries of the file. If used with `-d' or
|
`-D', the relocations are printed interspersed with the
|
`-D', the relocations are printed interspersed with the
|
disassembly.
|
disassembly.
|
|
|
`-R'
|
`-R'
|
`--dynamic-reloc'
|
`--dynamic-reloc'
|
Print the dynamic relocation entries of the file. This is only
|
Print the dynamic relocation entries of the file. This is only
|
meaningful for dynamic objects, such as certain types of shared
|
meaningful for dynamic objects, such as certain types of shared
|
libraries.
|
libraries.
|
|
|
`-s'
|
`-s'
|
`--full-contents'
|
`--full-contents'
|
Display the full contents of any sections requested. By default
|
Display the full contents of any sections requested. By default
|
all non-empty sections are displayed.
|
all non-empty sections are displayed.
|
|
|
`-S'
|
`-S'
|
`--source'
|
`--source'
|
Display source code intermixed with disassembly, if possible.
|
Display source code intermixed with disassembly, if possible.
|
Implies `-d'.
|
Implies `-d'.
|
|
|
`--show-raw-insn'
|
`--show-raw-insn'
|
When disassembling instructions, print the instruction in hex as
|
When disassembling instructions, print the instruction in hex as
|
well as in symbolic form. This is the default except when
|
well as in symbolic form. This is the default except when
|
`--prefix-addresses' is used.
|
`--prefix-addresses' is used.
|
|
|
`--no-show-raw-insn'
|
`--no-show-raw-insn'
|
When disassembling instructions, do not print the instruction
|
When disassembling instructions, do not print the instruction
|
bytes. This is the default when `--prefix-addresses' is used.
|
bytes. This is the default when `--prefix-addresses' is used.
|
|
|
`-W'
|
`-W'
|
`--dwarf'
|
`--dwarf'
|
Displays the contents of the DWARF debug sections in the file, if
|
Displays the contents of the DWARF debug sections in the file, if
|
any are present.
|
any are present.
|
|
|
`-G'
|
`-G'
|
`--stabs'
|
`--stabs'
|
Display the full contents of any sections requested. Display the
|
Display the full contents of any sections requested. Display the
|
contents of the .stab and .stab.index and .stab.excl sections from
|
contents of the .stab and .stab.index and .stab.excl sections from
|
an ELF file. This is only useful on systems (such as Solaris 2.0)
|
an ELF file. This is only useful on systems (such as Solaris 2.0)
|
in which `.stab' debugging symbol-table entries are carried in an
|
in which `.stab' debugging symbol-table entries are carried in an
|
ELF section. In most other file formats, debugging symbol-table
|
ELF section. In most other file formats, debugging symbol-table
|
entries are interleaved with linkage symbols, and are visible in
|
entries are interleaved with linkage symbols, and are visible in
|
the `--syms' output. For more information on stabs symbols, see
|
the `--syms' output. For more information on stabs symbols, see
|
*Note Stabs: (stabs.info)Top.
|
*Note Stabs: (stabs.info)Top.
|
|
|
`--start-address=ADDRESS'
|
`--start-address=ADDRESS'
|
Start displaying data at the specified address. This affects the
|
Start displaying data at the specified address. This affects the
|
output of the `-d', `-r' and `-s' options.
|
output of the `-d', `-r' and `-s' options.
|
|
|
`--stop-address=ADDRESS'
|
`--stop-address=ADDRESS'
|
Stop displaying data at the specified address. This affects the
|
Stop displaying data at the specified address. This affects the
|
output of the `-d', `-r' and `-s' options.
|
output of the `-d', `-r' and `-s' options.
|
|
|
`-t'
|
`-t'
|
`--syms'
|
`--syms'
|
Print the symbol table entries of the file. This is similar to
|
Print the symbol table entries of the file. This is similar to
|
the information provided by the `nm' program, although the display
|
the information provided by the `nm' program, although the display
|
format is different. The format of the output depends upon the
|
format is different. The format of the output depends upon the
|
format of the file being dumped, but there are two main types.
|
format of the file being dumped, but there are two main types.
|
One looks like this:
|
One looks like this:
|
|
|
[ 4](sec 3)(fl 0x00)(ty 0)(scl 3) (nx 1) 0x00000000 .bss
|
[ 4](sec 3)(fl 0x00)(ty 0)(scl 3) (nx 1) 0x00000000 .bss
|
[ 6](sec 1)(fl 0x00)(ty 0)(scl 2) (nx 0) 0x00000000 fred
|
[ 6](sec 1)(fl 0x00)(ty 0)(scl 2) (nx 0) 0x00000000 fred
|
|
|
where the number inside the square brackets is the number of the
|
where the number inside the square brackets is the number of the
|
entry in the symbol table, the SEC number is the section number,
|
entry in the symbol table, the SEC number is the section number,
|
the FL value are the symbol's flag bits, the TY number is the
|
the FL value are the symbol's flag bits, the TY number is the
|
symbol's type, the SCL number is the symbol's storage class and
|
symbol's type, the SCL number is the symbol's storage class and
|
the NX value is the number of auxilary entries associated with the
|
the NX value is the number of auxilary entries associated with the
|
symbol. The last two fields are the symbol's value and its name.
|
symbol. The last two fields are the symbol's value and its name.
|
|
|
The other common output format, usually seen with ELF based files,
|
The other common output format, usually seen with ELF based files,
|
looks like this:
|
looks like this:
|
|
|
00000000 l d .bss 00000000 .bss
|
00000000 l d .bss 00000000 .bss
|
00000000 g .text 00000000 fred
|
00000000 g .text 00000000 fred
|
|
|
Here the first number is the symbol's value (sometimes refered to
|
Here the first number is the symbol's value (sometimes refered to
|
as its address). The next field is actually a set of characters
|
as its address). The next field is actually a set of characters
|
and spaces indicating the flag bits that are set on the symbol.
|
and spaces indicating the flag bits that are set on the symbol.
|
These characters are described below. Next is the section with
|
These characters are described below. Next is the section with
|
which the symbol is associated or _*ABS*_ if the section is
|
which the symbol is associated or _*ABS*_ if the section is
|
absolute (ie not connected with any section), or _*UND*_ if the
|
absolute (ie not connected with any section), or _*UND*_ if the
|
section is referenced in the file being dumped, but not defined
|
section is referenced in the file being dumped, but not defined
|
there.
|
there.
|
|
|
After the section name comes another field, a number, which for
|
After the section name comes another field, a number, which for
|
common symbols is the alignment and for other symbol is the size.
|
common symbols is the alignment and for other symbol is the size.
|
Finally the symbol's name is displayed.
|
Finally the symbol's name is displayed.
|
|
|
The flag characters are divided into 7 groups as follows:
|
The flag characters are divided into 7 groups as follows:
|
`l'
|
`l'
|
`g'
|
`g'
|
`!'
|
`!'
|
The symbol is local (l), global (g), neither (a space) or
|
The symbol is local (l), global (g), neither (a space) or
|
both (!). A symbol can be neither local or global for a
|
both (!). A symbol can be neither local or global for a
|
variety of reasons, e.g., because it is used for debugging,
|
variety of reasons, e.g., because it is used for debugging,
|
but it is probably an indication of a bug if it is ever both
|
but it is probably an indication of a bug if it is ever both
|
local and global.
|
local and global.
|
|
|
`w'
|
`w'
|
The symbol is weak (w) or strong (a space).
|
The symbol is weak (w) or strong (a space).
|
|
|
`C'
|
`C'
|
The symbol denotes a constructor (C) or an ordinary symbol (a
|
The symbol denotes a constructor (C) or an ordinary symbol (a
|
space).
|
space).
|
|
|
`W'
|
`W'
|
The symbol is a warning (W) or a normal symbol (a space). A
|
The symbol is a warning (W) or a normal symbol (a space). A
|
warning symbol's name is a message to be displayed if the
|
warning symbol's name is a message to be displayed if the
|
symbol following the warning symbol is ever referenced.
|
symbol following the warning symbol is ever referenced.
|
|
|
`I'
|
`I'
|
The symbol is an indirect reference to another symbol (I) or
|
The symbol is an indirect reference to another symbol (I) or
|
a normal symbol (a space).
|
a normal symbol (a space).
|
|
|
`d'
|
`d'
|
`D'
|
`D'
|
The symbol is a debugging symbol (d) or a dynamic symbol (D)
|
The symbol is a debugging symbol (d) or a dynamic symbol (D)
|
or a normal symbol (a space).
|
or a normal symbol (a space).
|
|
|
`F'
|
`F'
|
|
|
`f'
|
`f'
|
|
|
`O'
|
`O'
|
The symbol is the name of a function (F) or a file (f) or an
|
The symbol is the name of a function (F) or a file (f) or an
|
object (O) or just a normal symbol (a space).
|
object (O) or just a normal symbol (a space).
|
|
|
`-T'
|
`-T'
|
`--dynamic-syms'
|
`--dynamic-syms'
|
Print the dynamic symbol table entries of the file. This is only
|
Print the dynamic symbol table entries of the file. This is only
|
meaningful for dynamic objects, such as certain types of shared
|
meaningful for dynamic objects, such as certain types of shared
|
libraries. This is similar to the information provided by the `nm'
|
libraries. This is similar to the information provided by the `nm'
|
program when given the `-D' (`--dynamic') option.
|
program when given the `-D' (`--dynamic') option.
|
|
|
`--special-syms'
|
`--special-syms'
|
When displaying symbols include those which the target considers
|
When displaying symbols include those which the target considers
|
to be special in some way and which would not normally be of
|
to be special in some way and which would not normally be of
|
interest to the user.
|
interest to the user.
|
|
|
`-V'
|
`-V'
|
`--version'
|
`--version'
|
Print the version number of `objdump' and exit.
|
Print the version number of `objdump' and exit.
|
|
|
`-x'
|
`-x'
|
`--all-headers'
|
`--all-headers'
|
Display all available header information, including the symbol
|
Display all available header information, including the symbol
|
table and relocation entries. Using `-x' is equivalent to
|
table and relocation entries. Using `-x' is equivalent to
|
specifying all of `-a -f -h -p -r -t'.
|
specifying all of `-a -f -h -p -r -t'.
|
|
|
`-w'
|
`-w'
|
`--wide'
|
`--wide'
|
Format some lines for output devices that have more than 80
|
Format some lines for output devices that have more than 80
|
columns. Also do not truncate symbol names when they are
|
columns. Also do not truncate symbol names when they are
|
displayed.
|
displayed.
|
|
|
`-z'
|
`-z'
|
`--disassemble-zeroes'
|
`--disassemble-zeroes'
|
Normally the disassembly output will skip blocks of zeroes. This
|
Normally the disassembly output will skip blocks of zeroes. This
|
option directs the disassembler to disassemble those blocks, just
|
option directs the disassembler to disassemble those blocks, just
|
like any other data.
|
like any other data.
|
|
|
|
|
File: binutils.info, Node: ranlib, Next: readelf, Prev: objdump, Up: Top
|
File: binutils.info, Node: ranlib, Next: readelf, Prev: objdump, Up: Top
|
|
|
5 ranlib
|
5 ranlib
|
********
|
********
|
|
|
ranlib [`-vVt'] ARCHIVE
|
ranlib [`-vVt'] ARCHIVE
|
|
|
`ranlib' generates an index to the contents of an archive and stores
|
`ranlib' generates an index to the contents of an archive and stores
|
it in the archive. The index lists each symbol defined by a member of
|
it in the archive. The index lists each symbol defined by a member of
|
an archive that is a relocatable object file.
|
an archive that is a relocatable object file.
|
|
|
You may use `nm -s' or `nm --print-armap' to list this index.
|
You may use `nm -s' or `nm --print-armap' to list this index.
|
|
|
An archive with such an index speeds up linking to the library and
|
An archive with such an index speeds up linking to the library and
|
allows routines in the library to call each other without regard to
|
allows routines in the library to call each other without regard to
|
their placement in the archive.
|
their placement in the archive.
|
|
|
The GNU `ranlib' program is another form of GNU `ar'; running
|
The GNU `ranlib' program is another form of GNU `ar'; running
|
`ranlib' is completely equivalent to executing `ar -s'. *Note ar::.
|
`ranlib' is completely equivalent to executing `ar -s'. *Note ar::.
|
|
|
`-v'
|
`-v'
|
`-V'
|
`-V'
|
`--version'
|
`--version'
|
Show the version number of `ranlib'.
|
Show the version number of `ranlib'.
|
|
|
`-t'
|
`-t'
|
Update the timestamp of the symbol map of an archive.
|
Update the timestamp of the symbol map of an archive.
|
|
|
|
|
File: binutils.info, Node: size, Next: strings, Prev: readelf, Up: Top
|
File: binutils.info, Node: size, Next: strings, Prev: readelf, Up: Top
|
|
|
6 size
|
6 size
|
******
|
******
|
|
|
size [`-A'|`-B'|`--format='COMPATIBILITY]
|
size [`-A'|`-B'|`--format='COMPATIBILITY]
|
[`--help']
|
[`--help']
|
[`-d'|`-o'|`-x'|`--radix='NUMBER]
|
[`-d'|`-o'|`-x'|`--radix='NUMBER]
|
[`--common']
|
[`--common']
|
[`-t'|`--totals']
|
[`-t'|`--totals']
|
[`--target='BFDNAME] [`-V'|`--version']
|
[`--target='BFDNAME] [`-V'|`--version']
|
[OBJFILE...]
|
[OBJFILE...]
|
|
|
The GNU `size' utility lists the section sizes--and the total
|
The GNU `size' utility lists the section sizes--and the total
|
size--for each of the object or archive files OBJFILE in its argument
|
size--for each of the object or archive files OBJFILE in its argument
|
list. By default, one line of output is generated for each object file
|
list. By default, one line of output is generated for each object file
|
or each module in an archive.
|
or each module in an archive.
|
|
|
OBJFILE... are the object files to be examined. If none are
|
OBJFILE... are the object files to be examined. If none are
|
specified, the file `a.out' will be used.
|
specified, the file `a.out' will be used.
|
|
|
The command line options have the following meanings:
|
The command line options have the following meanings:
|
|
|
`-A'
|
`-A'
|
`-B'
|
`-B'
|
`--format=COMPATIBILITY'
|
`--format=COMPATIBILITY'
|
Using one of these options, you can choose whether the output from
|
Using one of these options, you can choose whether the output from
|
GNU `size' resembles output from System V `size' (using `-A', or
|
GNU `size' resembles output from System V `size' (using `-A', or
|
`--format=sysv'), or Berkeley `size' (using `-B', or
|
`--format=sysv'), or Berkeley `size' (using `-B', or
|
`--format=berkeley'). The default is the one-line format similar
|
`--format=berkeley'). The default is the one-line format similar
|
to Berkeley's.
|
to Berkeley's.
|
|
|
Here is an example of the Berkeley (default) format of output from
|
Here is an example of the Berkeley (default) format of output from
|
`size':
|
`size':
|
$ size --format=Berkeley ranlib size
|
$ size --format=Berkeley ranlib size
|
text data bss dec hex filename
|
text data bss dec hex filename
|
294880 81920 11592 388392 5ed28 ranlib
|
294880 81920 11592 388392 5ed28 ranlib
|
294880 81920 11888 388688 5ee50 size
|
294880 81920 11888 388688 5ee50 size
|
|
|
This is the same data, but displayed closer to System V
|
This is the same data, but displayed closer to System V
|
conventions:
|
conventions:
|
|
|
$ size --format=SysV ranlib size
|
$ size --format=SysV ranlib size
|
ranlib :
|
ranlib :
|
section size addr
|
section size addr
|
.text 294880 8192
|
.text 294880 8192
|
.data 81920 303104
|
.data 81920 303104
|
.bss 11592 385024
|
.bss 11592 385024
|
Total 388392
|
Total 388392
|
|
|
|
|
size :
|
size :
|
section size addr
|
section size addr
|
.text 294880 8192
|
.text 294880 8192
|
.data 81920 303104
|
.data 81920 303104
|
.bss 11888 385024
|
.bss 11888 385024
|
Total 388688
|
Total 388688
|
|
|
`--help'
|
`--help'
|
Show a summary of acceptable arguments and options.
|
Show a summary of acceptable arguments and options.
|
|
|
`-d'
|
`-d'
|
`-o'
|
`-o'
|
`-x'
|
`-x'
|
`--radix=NUMBER'
|
`--radix=NUMBER'
|
Using one of these options, you can control whether the size of
|
Using one of these options, you can control whether the size of
|
each section is given in decimal (`-d', or `--radix=10'); octal
|
each section is given in decimal (`-d', or `--radix=10'); octal
|
(`-o', or `--radix=8'); or hexadecimal (`-x', or `--radix=16').
|
(`-o', or `--radix=8'); or hexadecimal (`-x', or `--radix=16').
|
In `--radix=NUMBER', only the three values (8, 10, 16) are
|
In `--radix=NUMBER', only the three values (8, 10, 16) are
|
supported. The total size is always given in two radices; decimal
|
supported. The total size is always given in two radices; decimal
|
and hexadecimal for `-d' or `-x' output, or octal and hexadecimal
|
and hexadecimal for `-d' or `-x' output, or octal and hexadecimal
|
if you're using `-o'.
|
if you're using `-o'.
|
|
|
`--common'
|
`--common'
|
Print total size of common symbols in each file. When using
|
Print total size of common symbols in each file. When using
|
Berkeley format these are included in the bss size.
|
Berkeley format these are included in the bss size.
|
|
|
`-t'
|
`-t'
|
`--totals'
|
`--totals'
|
Show totals of all objects listed (Berkeley format listing mode
|
Show totals of all objects listed (Berkeley format listing mode
|
only).
|
only).
|
|
|
`--target=BFDNAME'
|
`--target=BFDNAME'
|
Specify that the object-code format for OBJFILE is BFDNAME. This
|
Specify that the object-code format for OBJFILE is BFDNAME. This
|
option may not be necessary; `size' can automatically recognize
|
option may not be necessary; `size' can automatically recognize
|
many formats. *Note Target Selection::, for more information.
|
many formats. *Note Target Selection::, for more information.
|
|
|
`-V'
|
`-V'
|
`--version'
|
`--version'
|
Display the version number of `size'.
|
Display the version number of `size'.
|
|
|
|
|
File: binutils.info, Node: strings, Next: strip, Prev: size, Up: Top
|
File: binutils.info, Node: strings, Next: strip, Prev: size, Up: Top
|
|
|
7 strings
|
7 strings
|
*********
|
*********
|
|
|
strings [`-afov'] [`-'MIN-LEN]
|
strings [`-afov'] [`-'MIN-LEN]
|
[`-n' MIN-LEN] [`--bytes='MIN-LEN]
|
[`-n' MIN-LEN] [`--bytes='MIN-LEN]
|
[`-t' RADIX] [`--radix='RADIX]
|
[`-t' RADIX] [`--radix='RADIX]
|
[`-e' ENCODING] [`--encoding='ENCODING]
|
[`-e' ENCODING] [`--encoding='ENCODING]
|
[`-'] [`--all'] [`--print-file-name']
|
[`-'] [`--all'] [`--print-file-name']
|
[`-T' BFDNAME] [`--target='BFDNAME]
|
[`-T' BFDNAME] [`--target='BFDNAME]
|
[`--help'] [`--version'] FILE...
|
[`--help'] [`--version'] FILE...
|
|
|
For each FILE given, GNU `strings' prints the printable character
|
For each FILE given, GNU `strings' prints the printable character
|
sequences that are at least 4 characters long (or the number given with
|
sequences that are at least 4 characters long (or the number given with
|
the options below) and are followed by an unprintable character. By
|
the options below) and are followed by an unprintable character. By
|
default, it only prints the strings from the initialized and loaded
|
default, it only prints the strings from the initialized and loaded
|
sections of object files; for other types of files, it prints the
|
sections of object files; for other types of files, it prints the
|
strings from the whole file.
|
strings from the whole file.
|
|
|
`strings' is mainly useful for determining the contents of non-text
|
`strings' is mainly useful for determining the contents of non-text
|
files.
|
files.
|
|
|
`-a'
|
`-a'
|
`--all'
|
`--all'
|
`-'
|
`-'
|
Do not scan only the initialized and loaded sections of object
|
Do not scan only the initialized and loaded sections of object
|
files; scan the whole files.
|
files; scan the whole files.
|
|
|
`-f'
|
`-f'
|
`--print-file-name'
|
`--print-file-name'
|
Print the name of the file before each string.
|
Print the name of the file before each string.
|
|
|
`--help'
|
`--help'
|
Print a summary of the program usage on the standard output and
|
Print a summary of the program usage on the standard output and
|
exit.
|
exit.
|
|
|
`-MIN-LEN'
|
`-MIN-LEN'
|
`-n MIN-LEN'
|
`-n MIN-LEN'
|
`--bytes=MIN-LEN'
|
`--bytes=MIN-LEN'
|
Print sequences of characters that are at least MIN-LEN characters
|
Print sequences of characters that are at least MIN-LEN characters
|
long, instead of the default 4.
|
long, instead of the default 4.
|
|
|
`-o'
|
`-o'
|
Like `-t o'. Some other versions of `strings' have `-o' act like
|
Like `-t o'. Some other versions of `strings' have `-o' act like
|
`-t d' instead. Since we can not be compatible with both ways, we
|
`-t d' instead. Since we can not be compatible with both ways, we
|
simply chose one.
|
simply chose one.
|
|
|
`-t RADIX'
|
`-t RADIX'
|
`--radix=RADIX'
|
`--radix=RADIX'
|
Print the offset within the file before each string. The single
|
Print the offset within the file before each string. The single
|
character argument specifies the radix of the offset--`o' for
|
character argument specifies the radix of the offset--`o' for
|
octal, `x' for hexadecimal, or `d' for decimal.
|
octal, `x' for hexadecimal, or `d' for decimal.
|
|
|
`-e ENCODING'
|
`-e ENCODING'
|
`--encoding=ENCODING'
|
`--encoding=ENCODING'
|
Select the character encoding of the strings that are to be found.
|
Select the character encoding of the strings that are to be found.
|
Possible values for ENCODING are: `s' = single-7-bit-byte
|
Possible values for ENCODING are: `s' = single-7-bit-byte
|
characters (ASCII, ISO 8859, etc., default), `S' =
|
characters (ASCII, ISO 8859, etc., default), `S' =
|
single-8-bit-byte characters, `b' = 16-bit bigendian, `l' = 16-bit
|
single-8-bit-byte characters, `b' = 16-bit bigendian, `l' = 16-bit
|
littleendian, `B' = 32-bit bigendian, `L' = 32-bit littleendian.
|
littleendian, `B' = 32-bit bigendian, `L' = 32-bit littleendian.
|
Useful for finding wide character strings. (`l' and `b' apply to,
|
Useful for finding wide character strings. (`l' and `b' apply to,
|
for example, Unicode UTF-16/UCS-2 encodings).
|
for example, Unicode UTF-16/UCS-2 encodings).
|
|
|
`-T BFDNAME'
|
`-T BFDNAME'
|
`--target=BFDNAME'
|
`--target=BFDNAME'
|
Specify an object code format other than your system's default
|
Specify an object code format other than your system's default
|
format. *Note Target Selection::, for more information.
|
format. *Note Target Selection::, for more information.
|
|
|
`-v'
|
`-v'
|
`--version'
|
`--version'
|
Print the program version number on the standard output and exit.
|
Print the program version number on the standard output and exit.
|
|
|
|
|
File: binutils.info, Node: strip, Next: c++filt, Prev: strings, Up: Top
|
File: binutils.info, Node: strip, Next: c++filt, Prev: strings, Up: Top
|
|
|
8 strip
|
8 strip
|
*******
|
*******
|
|
|
strip [`-F' BFDNAME |`--target='BFDNAME]
|
strip [`-F' BFDNAME |`--target='BFDNAME]
|
[`-I' BFDNAME |`--input-target='BFDNAME]
|
[`-I' BFDNAME |`--input-target='BFDNAME]
|
[`-O' BFDNAME |`--output-target='BFDNAME]
|
[`-O' BFDNAME |`--output-target='BFDNAME]
|
[`-s'|`--strip-all']
|
[`-s'|`--strip-all']
|
[`-S'|`-g'|`-d'|`--strip-debug']
|
[`-S'|`-g'|`-d'|`--strip-debug']
|
[`-K' SYMBOLNAME |`--keep-symbol='SYMBOLNAME]
|
[`-K' SYMBOLNAME |`--keep-symbol='SYMBOLNAME]
|
[`-N' SYMBOLNAME |`--strip-symbol='SYMBOLNAME]
|
[`-N' SYMBOLNAME |`--strip-symbol='SYMBOLNAME]
|
[`-w'|`--wildcard']
|
[`-w'|`--wildcard']
|
[`-x'|`--discard-all'] [`-X' |`--discard-locals']
|
[`-x'|`--discard-all'] [`-X' |`--discard-locals']
|
[`-R' SECTIONNAME |`--remove-section='SECTIONNAME]
|
[`-R' SECTIONNAME |`--remove-section='SECTIONNAME]
|
[`-o' FILE] [`-p'|`--preserve-dates']
|
[`-o' FILE] [`-p'|`--preserve-dates']
|
[`--keep-file-symbols']
|
[`--keep-file-symbols']
|
[`--only-keep-debug']
|
[`--only-keep-debug']
|
[`-v' |`--verbose'] [`-V'|`--version']
|
[`-v' |`--verbose'] [`-V'|`--version']
|
[`--help'] [`--info']
|
[`--help'] [`--info']
|
OBJFILE...
|
OBJFILE...
|
|
|
GNU `strip' discards all symbols from object files OBJFILE. The
|
GNU `strip' discards all symbols from object files OBJFILE. The
|
list of object files may include archives. At least one object file
|
list of object files may include archives. At least one object file
|
must be given.
|
must be given.
|
|
|
`strip' modifies the files named in its argument, rather than
|
`strip' modifies the files named in its argument, rather than
|
writing modified copies under different names.
|
writing modified copies under different names.
|
|
|
`-F BFDNAME'
|
`-F BFDNAME'
|
`--target=BFDNAME'
|
`--target=BFDNAME'
|
Treat the original OBJFILE as a file with the object code format
|
Treat the original OBJFILE as a file with the object code format
|
BFDNAME, and rewrite it in the same format. *Note Target
|
BFDNAME, and rewrite it in the same format. *Note Target
|
Selection::, for more information.
|
Selection::, for more information.
|
|
|
`--help'
|
`--help'
|
Show a summary of the options to `strip' and exit.
|
Show a summary of the options to `strip' and exit.
|
|
|
`--info'
|
`--info'
|
Display a list showing all architectures and object formats
|
Display a list showing all architectures and object formats
|
available.
|
available.
|
|
|
`-I BFDNAME'
|
`-I BFDNAME'
|
`--input-target=BFDNAME'
|
`--input-target=BFDNAME'
|
Treat the original OBJFILE as a file with the object code format
|
Treat the original OBJFILE as a file with the object code format
|
BFDNAME. *Note Target Selection::, for more information.
|
BFDNAME. *Note Target Selection::, for more information.
|
|
|
`-O BFDNAME'
|
`-O BFDNAME'
|
`--output-target=BFDNAME'
|
`--output-target=BFDNAME'
|
Replace OBJFILE with a file in the output format BFDNAME. *Note
|
Replace OBJFILE with a file in the output format BFDNAME. *Note
|
Target Selection::, for more information.
|
Target Selection::, for more information.
|
|
|
`-R SECTIONNAME'
|
`-R SECTIONNAME'
|
`--remove-section=SECTIONNAME'
|
`--remove-section=SECTIONNAME'
|
Remove any section named SECTIONNAME from the output file. This
|
Remove any section named SECTIONNAME from the output file. This
|
option may be given more than once. Note that using this option
|
option may be given more than once. Note that using this option
|
inappropriately may make the output file unusable.
|
inappropriately may make the output file unusable.
|
|
|
`-s'
|
`-s'
|
`--strip-all'
|
`--strip-all'
|
Remove all symbols.
|
Remove all symbols.
|
|
|
`-g'
|
`-g'
|
`-S'
|
`-S'
|
`-d'
|
`-d'
|
`--strip-debug'
|
`--strip-debug'
|
Remove debugging symbols only.
|
Remove debugging symbols only.
|
|
|
`--strip-unneeded'
|
`--strip-unneeded'
|
Remove all symbols that are not needed for relocation processing.
|
Remove all symbols that are not needed for relocation processing.
|
|
|
`-K SYMBOLNAME'
|
`-K SYMBOLNAME'
|
`--keep-symbol=SYMBOLNAME'
|
`--keep-symbol=SYMBOLNAME'
|
When stripping symbols, keep symbol SYMBOLNAME even if it would
|
When stripping symbols, keep symbol SYMBOLNAME even if it would
|
normally be stripped. This option may be given more than once.
|
normally be stripped. This option may be given more than once.
|
|
|
`-N SYMBOLNAME'
|
`-N SYMBOLNAME'
|
`--strip-symbol=SYMBOLNAME'
|
`--strip-symbol=SYMBOLNAME'
|
Remove symbol SYMBOLNAME from the source file. This option may be
|
Remove symbol SYMBOLNAME from the source file. This option may be
|
given more than once, and may be combined with strip options other
|
given more than once, and may be combined with strip options other
|
than `-K'.
|
than `-K'.
|
|
|
`-o FILE'
|
`-o FILE'
|
Put the stripped output in FILE, rather than replacing the
|
Put the stripped output in FILE, rather than replacing the
|
existing file. When this argument is used, only one OBJFILE
|
existing file. When this argument is used, only one OBJFILE
|
argument may be specified.
|
argument may be specified.
|
|
|
`-p'
|
`-p'
|
`--preserve-dates'
|
`--preserve-dates'
|
Preserve the access and modification dates of the file.
|
Preserve the access and modification dates of the file.
|
|
|
`-w'
|
`-w'
|
`--wildcard'
|
`--wildcard'
|
Permit regular expressions in SYMBOLNAMEs used in other command
|
Permit regular expressions in SYMBOLNAMEs used in other command
|
line options. The question mark (?), asterisk (*), backslash (\)
|
line options. The question mark (?), asterisk (*), backslash (\)
|
and square brackets ([]) operators can be used anywhere in the
|
and square brackets ([]) operators can be used anywhere in the
|
symbol name. If the first character of the symbol name is the
|
symbol name. If the first character of the symbol name is the
|
exclamation point (!) then the sense of the switch is reversed for
|
exclamation point (!) then the sense of the switch is reversed for
|
that symbol. For example:
|
that symbol. For example:
|
|
|
-w -K !foo -K fo*
|
-w -K !foo -K fo*
|
|
|
would cause strip to only keep symbols that start with the letters
|
would cause strip to only keep symbols that start with the letters
|
"fo", but to discard the symbol "foo".
|
"fo", but to discard the symbol "foo".
|
|
|
`-x'
|
`-x'
|
`--discard-all'
|
`--discard-all'
|
Remove non-global symbols.
|
Remove non-global symbols.
|
|
|
`-X'
|
`-X'
|
`--discard-locals'
|
`--discard-locals'
|
Remove compiler-generated local symbols. (These usually start
|
Remove compiler-generated local symbols. (These usually start
|
with `L' or `.'.)
|
with `L' or `.'.)
|
|
|
`--keep-file-symbols'
|
`--keep-file-symbols'
|
When stripping a file, perhaps with `--strip-debug' or
|
When stripping a file, perhaps with `--strip-debug' or
|
`--strip-unneeded', retain any symbols specifying source file
|
`--strip-unneeded', retain any symbols specifying source file
|
names, which would otherwise get stripped.
|
names, which would otherwise get stripped.
|
|
|
`--only-keep-debug'
|
`--only-keep-debug'
|
Strip a file, removing contents of any sections that would not be
|
Strip a file, removing contents of any sections that would not be
|
stripped by `--strip-debug' and leaving the debugging sections
|
stripped by `--strip-debug' and leaving the debugging sections
|
intact. In ELF files, this preserves all note sections in the
|
intact. In ELF files, this preserves all note sections in the
|
output.
|
output.
|
|
|
The intention is that this option will be used in conjunction with
|
The intention is that this option will be used in conjunction with
|
`--add-gnu-debuglink' to create a two part executable. One a
|
`--add-gnu-debuglink' to create a two part executable. One a
|
stripped binary which will occupy less space in RAM and in a
|
stripped binary which will occupy less space in RAM and in a
|
distribution and the second a debugging information file which is
|
distribution and the second a debugging information file which is
|
only needed if debugging abilities are required. The suggested
|
only needed if debugging abilities are required. The suggested
|
procedure to create these files is as follows:
|
procedure to create these files is as follows:
|
|
|
1. Link the executable as normal. Assuming that is is called
|
1. Link the executable as normal. Assuming that is is called
|
`foo' then...
|
`foo' then...
|
|
|
2. Run `objcopy --only-keep-debug foo foo.dbg' to create a file
|
2. Run `objcopy --only-keep-debug foo foo.dbg' to create a file
|
containing the debugging info.
|
containing the debugging info.
|
|
|
3. Run `objcopy --strip-debug foo' to create a stripped
|
3. Run `objcopy --strip-debug foo' to create a stripped
|
executable.
|
executable.
|
|
|
4. Run `objcopy --add-gnu-debuglink=foo.dbg foo' to add a link
|
4. Run `objcopy --add-gnu-debuglink=foo.dbg foo' to add a link
|
to the debugging info into the stripped executable.
|
to the debugging info into the stripped executable.
|
|
|
Note--the choice of `.dbg' as an extension for the debug info file
|
Note--the choice of `.dbg' as an extension for the debug info file
|
is arbitrary. Also the `--only-keep-debug' step is optional. You
|
is arbitrary. Also the `--only-keep-debug' step is optional. You
|
could instead do this:
|
could instead do this:
|
|
|
1. Link the executable as normal.
|
1. Link the executable as normal.
|
|
|
2. Copy `foo' to `foo.full'
|
2. Copy `foo' to `foo.full'
|
|
|
3. Run `strip --strip-debug foo'
|
3. Run `strip --strip-debug foo'
|
|
|
4. Run `objcopy --add-gnu-debuglink=foo.full foo'
|
4. Run `objcopy --add-gnu-debuglink=foo.full foo'
|
|
|
i.e., the file pointed to by the `--add-gnu-debuglink' can be the
|
i.e., the file pointed to by the `--add-gnu-debuglink' can be the
|
full executable. It does not have to be a file created by the
|
full executable. It does not have to be a file created by the
|
`--only-keep-debug' switch.
|
`--only-keep-debug' switch.
|
|
|
Note--this switch is only intended for use on fully linked files.
|
Note--this switch is only intended for use on fully linked files.
|
It does not make sense to use it on object files where the
|
It does not make sense to use it on object files where the
|
debugging information may be incomplete. Besides the
|
debugging information may be incomplete. Besides the
|
gnu_debuglink feature currently only supports the presence of one
|
gnu_debuglink feature currently only supports the presence of one
|
filename containing debugging information, not multiple filenames
|
filename containing debugging information, not multiple filenames
|
on a one-per-object-file basis.
|
on a one-per-object-file basis.
|
|
|
`-V'
|
`-V'
|
`--version'
|
`--version'
|
Show the version number for `strip'.
|
Show the version number for `strip'.
|
|
|
`-v'
|
`-v'
|
`--verbose'
|
`--verbose'
|
Verbose output: list all object files modified. In the case of
|
Verbose output: list all object files modified. In the case of
|
archives, `strip -v' lists all members of the archive.
|
archives, `strip -v' lists all members of the archive.
|
|
|
|
|
File: binutils.info, Node: c++filt, Next: addr2line, Prev: strip, Up: Top
|
File: binutils.info, Node: c++filt, Next: addr2line, Prev: strip, Up: Top
|
|
|
9 c++filt
|
9 c++filt
|
*********
|
*********
|
|
|
c++filt [`-_'|`--strip-underscores']
|
c++filt [`-_'|`--strip-underscores']
|
[`-n'|`--no-strip-underscores']
|
[`-n'|`--no-strip-underscores']
|
[`-p'|`--no-params']
|
[`-p'|`--no-params']
|
[`-t'|`--types']
|
[`-t'|`--types']
|
[`-i'|`--no-verbose']
|
[`-i'|`--no-verbose']
|
[`-s' FORMAT|`--format='FORMAT]
|
[`-s' FORMAT|`--format='FORMAT]
|
[`--help'] [`--version'] [SYMBOL...]
|
[`--help'] [`--version'] [SYMBOL...]
|
|
|
The C++ and Java languages provide function overloading, which means
|
The C++ and Java languages provide function overloading, which means
|
that you can write many functions with the same name, providing that
|
that you can write many functions with the same name, providing that
|
each function takes parameters of different types. In order to be able
|
each function takes parameters of different types. In order to be able
|
to distinguish these similarly named functions C++ and Java encode them
|
to distinguish these similarly named functions C++ and Java encode them
|
into a low-level assembler name which uniquely identifies each
|
into a low-level assembler name which uniquely identifies each
|
different version. This process is known as "mangling". The `c++filt'
|
different version. This process is known as "mangling". The `c++filt'
|
(1) program does the inverse mapping: it decodes ("demangles") low-level
|
(1) program does the inverse mapping: it decodes ("demangles") low-level
|
names into user-level names so that they can be read.
|
names into user-level names so that they can be read.
|
|
|
Every alphanumeric word (consisting of letters, digits, underscores,
|
Every alphanumeric word (consisting of letters, digits, underscores,
|
dollars, or periods) seen in the input is a potential mangled name. If
|
dollars, or periods) seen in the input is a potential mangled name. If
|
the name decodes into a C++ name, the C++ name replaces the low-level
|
the name decodes into a C++ name, the C++ name replaces the low-level
|
name in the output, otherwise the original word is output. In this way
|
name in the output, otherwise the original word is output. In this way
|
you can pass an entire assembler source file, containing mangled names,
|
you can pass an entire assembler source file, containing mangled names,
|
through `c++filt' and see the same source file containing demangled
|
through `c++filt' and see the same source file containing demangled
|
names.
|
names.
|
|
|
You can also use `c++filt' to decipher individual symbols by passing
|
You can also use `c++filt' to decipher individual symbols by passing
|
them on the command line:
|
them on the command line:
|
|
|
c++filt SYMBOL
|
c++filt SYMBOL
|
|
|
If no SYMBOL arguments are given, `c++filt' reads symbol names from
|
If no SYMBOL arguments are given, `c++filt' reads symbol names from
|
the standard input instead. All the results are printed on the
|
the standard input instead. All the results are printed on the
|
standard output. The difference between reading names from the command
|
standard output. The difference between reading names from the command
|
line versus reading names from the standard input is that command line
|
line versus reading names from the standard input is that command line
|
arguments are expected to be just mangled names and no checking is
|
arguments are expected to be just mangled names and no checking is
|
performed to separate them from surrounding text. Thus for example:
|
performed to separate them from surrounding text. Thus for example:
|
|
|
c++filt -n _Z1fv
|
c++filt -n _Z1fv
|
|
|
will work and demangle the name to "f()" whereas:
|
will work and demangle the name to "f()" whereas:
|
|
|
c++filt -n _Z1fv,
|
c++filt -n _Z1fv,
|
|
|
will not work. (Note the extra comma at the end of the mangled name
|
will not work. (Note the extra comma at the end of the mangled name
|
which makes it invalid). This command however will work:
|
which makes it invalid). This command however will work:
|
|
|
echo _Z1fv, | c++filt -n
|
echo _Z1fv, | c++filt -n
|
|
|
and will display "f(),", i.e., the demangled name followed by a
|
and will display "f(),", i.e., the demangled name followed by a
|
trailing comma. This behaviour is because when the names are read from
|
trailing comma. This behaviour is because when the names are read from
|
the standard input it is expected that they might be part of an
|
the standard input it is expected that they might be part of an
|
assembler source file where there might be extra, extraneous characters
|
assembler source file where there might be extra, extraneous characters
|
trailing after a mangled name. For example:
|
trailing after a mangled name. For example:
|
|
|
.type _Z1fv, @function
|
.type _Z1fv, @function
|
|
|
`-_'
|
`-_'
|
`--strip-underscores'
|
`--strip-underscores'
|
On some systems, both the C and C++ compilers put an underscore in
|
On some systems, both the C and C++ compilers put an underscore in
|
front of every name. For example, the C name `foo' gets the
|
front of every name. For example, the C name `foo' gets the
|
low-level name `_foo'. This option removes the initial
|
low-level name `_foo'. This option removes the initial
|
underscore. Whether `c++filt' removes the underscore by default
|
underscore. Whether `c++filt' removes the underscore by default
|
is target dependent.
|
is target dependent.
|
|
|
`-j'
|
`-j'
|
`--java'
|
`--java'
|
Prints demangled names using Java syntax. The default is to use
|
Prints demangled names using Java syntax. The default is to use
|
C++ syntax.
|
C++ syntax.
|
|
|
`-n'
|
`-n'
|
`--no-strip-underscores'
|
`--no-strip-underscores'
|
Do not remove the initial underscore.
|
Do not remove the initial underscore.
|
|
|
`-p'
|
`-p'
|
`--no-params'
|
`--no-params'
|
When demangling the name of a function, do not display the types of
|
When demangling the name of a function, do not display the types of
|
the function's parameters.
|
the function's parameters.
|
|
|
`-t'
|
`-t'
|
`--types'
|
`--types'
|
Attempt to demangle types as well as function names. This is
|
Attempt to demangle types as well as function names. This is
|
disabled by default since mangled types are normally only used
|
disabled by default since mangled types are normally only used
|
internally in the compiler, and they can be confused with
|
internally in the compiler, and they can be confused with
|
non-mangled names. For example, a function called "a" treated as
|
non-mangled names. For example, a function called "a" treated as
|
a mangled type name would be demangled to "signed char".
|
a mangled type name would be demangled to "signed char".
|
|
|
`-i'
|
`-i'
|
`--no-verbose'
|
`--no-verbose'
|
Do not include implementation details (if any) in the demangled
|
Do not include implementation details (if any) in the demangled
|
output.
|
output.
|
|
|
`-s FORMAT'
|
`-s FORMAT'
|
`--format=FORMAT'
|
`--format=FORMAT'
|
`c++filt' can decode various methods of mangling, used by
|
`c++filt' can decode various methods of mangling, used by
|
different compilers. The argument to this option selects which
|
different compilers. The argument to this option selects which
|
method it uses:
|
method it uses:
|
|
|
`auto'
|
`auto'
|
Automatic selection based on executable (the default method)
|
Automatic selection based on executable (the default method)
|
|
|
`gnu'
|
`gnu'
|
the one used by the GNU C++ compiler (g++)
|
the one used by the GNU C++ compiler (g++)
|
|
|
`lucid'
|
`lucid'
|
the one used by the Lucid compiler (lcc)
|
the one used by the Lucid compiler (lcc)
|
|
|
`arm'
|
`arm'
|
the one specified by the C++ Annotated Reference Manual
|
the one specified by the C++ Annotated Reference Manual
|
|
|
`hp'
|
`hp'
|
the one used by the HP compiler (aCC)
|
the one used by the HP compiler (aCC)
|
|
|
`edg'
|
`edg'
|
the one used by the EDG compiler
|
the one used by the EDG compiler
|
|
|
`gnu-v3'
|
`gnu-v3'
|
the one used by the GNU C++ compiler (g++) with the V3 ABI.
|
the one used by the GNU C++ compiler (g++) with the V3 ABI.
|
|
|
`java'
|
`java'
|
the one used by the GNU Java compiler (gcj)
|
the one used by the GNU Java compiler (gcj)
|
|
|
`gnat'
|
`gnat'
|
the one used by the GNU Ada compiler (GNAT).
|
the one used by the GNU Ada compiler (GNAT).
|
|
|
`--help'
|
`--help'
|
Print a summary of the options to `c++filt' and exit.
|
Print a summary of the options to `c++filt' and exit.
|
|
|
`--version'
|
`--version'
|
Print the version number of `c++filt' and exit.
|
Print the version number of `c++filt' and exit.
|
|
|
_Warning:_ `c++filt' is a new utility, and the details of its user
|
_Warning:_ `c++filt' is a new utility, and the details of its user
|
interface are subject to change in future releases. In particular,
|
interface are subject to change in future releases. In particular,
|
a command-line option may be required in the future to decode a
|
a command-line option may be required in the future to decode a
|
name passed as an argument on the command line; in other words,
|
name passed as an argument on the command line; in other words,
|
|
|
c++filt SYMBOL
|
c++filt SYMBOL
|
|
|
may in a future release become
|
may in a future release become
|
|
|
c++filt OPTION SYMBOL
|
c++filt OPTION SYMBOL
|
|
|
---------- Footnotes ----------
|
---------- Footnotes ----------
|
|
|
(1) MS-DOS does not allow `+' characters in file names, so on MS-DOS
|
(1) MS-DOS does not allow `+' characters in file names, so on MS-DOS
|
this program is named `CXXFILT'.
|
this program is named `CXXFILT'.
|
|
|
|
|
File: binutils.info, Node: addr2line, Next: nlmconv, Prev: c++filt, Up: Top
|
File: binutils.info, Node: addr2line, Next: nlmconv, Prev: c++filt, Up: Top
|
|
|
10 addr2line
|
10 addr2line
|
************
|
************
|
|
|
addr2line [`-b' BFDNAME|`--target='BFDNAME]
|
addr2line [`-b' BFDNAME|`--target='BFDNAME]
|
[`-C'|`--demangle'[=STYLE]]
|
[`-C'|`--demangle'[=STYLE]]
|
[`-e' FILENAME|`--exe='FILENAME]
|
[`-e' FILENAME|`--exe='FILENAME]
|
[`-f'|`--functions'] [`-s'|`--basename']
|
[`-f'|`--functions'] [`-s'|`--basename']
|
[`-i'|`--inlines']
|
[`-i'|`--inlines']
|
[`-j'|`--section='NAME]
|
[`-j'|`--section='NAME]
|
[`-H'|`--help'] [`-V'|`--version']
|
[`-H'|`--help'] [`-V'|`--version']
|
[addr addr ...]
|
[addr addr ...]
|
|
|
`addr2line' translates addresses into file names and line numbers.
|
`addr2line' translates addresses into file names and line numbers.
|
Given an address in an executable or an offset in a section of a
|
Given an address in an executable or an offset in a section of a
|
relocatable object, it uses the debugging information to figure out
|
relocatable object, it uses the debugging information to figure out
|
which file name and line number are associated with it.
|
which file name and line number are associated with it.
|
|
|
The executable or relocatable object to use is specified with the
|
The executable or relocatable object to use is specified with the
|
`-e' option. The default is the file `a.out'. The section in the
|
`-e' option. The default is the file `a.out'. The section in the
|
relocatable object to use is specified with the `-j' option.
|
relocatable object to use is specified with the `-j' option.
|
|
|
`addr2line' has two modes of operation.
|
`addr2line' has two modes of operation.
|
|
|
In the first, hexadecimal addresses are specified on the command
|
In the first, hexadecimal addresses are specified on the command
|
line, and `addr2line' displays the file name and line number for each
|
line, and `addr2line' displays the file name and line number for each
|
address.
|
address.
|
|
|
In the second, `addr2line' reads hexadecimal addresses from standard
|
In the second, `addr2line' reads hexadecimal addresses from standard
|
input, and prints the file name and line number for each address on
|
input, and prints the file name and line number for each address on
|
standard output. In this mode, `addr2line' may be used in a pipe to
|
standard output. In this mode, `addr2line' may be used in a pipe to
|
convert dynamically chosen addresses.
|
convert dynamically chosen addresses.
|
|
|
The format of the output is `FILENAME:LINENO'. The file name and
|
The format of the output is `FILENAME:LINENO'. The file name and
|
line number for each address is printed on a separate line. If the
|
line number for each address is printed on a separate line. If the
|
`-f' option is used, then each `FILENAME:LINENO' line is preceded by a
|
`-f' option is used, then each `FILENAME:LINENO' line is preceded by a
|
`FUNCTIONNAME' line which is the name of the function containing the
|
`FUNCTIONNAME' line which is the name of the function containing the
|
address.
|
address.
|
|
|
If the file name or function name can not be determined, `addr2line'
|
If the file name or function name can not be determined, `addr2line'
|
will print two question marks in their place. If the line number can
|
will print two question marks in their place. If the line number can
|
not be determined, `addr2line' will print 0.
|
not be determined, `addr2line' will print 0.
|
|
|
The long and short forms of options, shown here as alternatives, are
|
The long and short forms of options, shown here as alternatives, are
|
equivalent.
|
equivalent.
|
|
|
`-b BFDNAME'
|
`-b BFDNAME'
|
`--target=BFDNAME'
|
`--target=BFDNAME'
|
Specify that the object-code format for the object files is
|
Specify that the object-code format for the object files is
|
BFDNAME.
|
BFDNAME.
|
|
|
`-C'
|
`-C'
|
`--demangle[=STYLE]'
|
`--demangle[=STYLE]'
|
Decode ("demangle") low-level symbol names into user-level names.
|
Decode ("demangle") low-level symbol names into user-level names.
|
Besides removing any initial underscore prepended by the system,
|
Besides removing any initial underscore prepended by the system,
|
this makes C++ function names readable. Different compilers have
|
this makes C++ function names readable. Different compilers have
|
different mangling styles. The optional demangling style argument
|
different mangling styles. The optional demangling style argument
|
can be used to choose an appropriate demangling style for your
|
can be used to choose an appropriate demangling style for your
|
compiler. *Note c++filt::, for more information on demangling.
|
compiler. *Note c++filt::, for more information on demangling.
|
|
|
`-e FILENAME'
|
`-e FILENAME'
|
`--exe=FILENAME'
|
`--exe=FILENAME'
|
Specify the name of the executable for which addresses should be
|
Specify the name of the executable for which addresses should be
|
translated. The default file is `a.out'.
|
translated. The default file is `a.out'.
|
|
|
`-f'
|
`-f'
|
`--functions'
|
`--functions'
|
Display function names as well as file and line number information.
|
Display function names as well as file and line number information.
|
|
|
`-s'
|
`-s'
|
`--basenames'
|
`--basenames'
|
Display only the base of each file name.
|
Display only the base of each file name.
|
|
|
`-i'
|
`-i'
|
`--inlines'
|
`--inlines'
|
If the address belongs to a function that was inlined, the source
|
If the address belongs to a function that was inlined, the source
|
information for all enclosing scopes back to the first non-inlined
|
information for all enclosing scopes back to the first non-inlined
|
function will also be printed. For example, if `main' inlines
|
function will also be printed. For example, if `main' inlines
|
`callee1' which inlines `callee2', and address is from `callee2',
|
`callee1' which inlines `callee2', and address is from `callee2',
|
the source information for `callee1' and `main' will also be
|
the source information for `callee1' and `main' will also be
|
printed.
|
printed.
|
|
|
`-j'
|
`-j'
|
`--section'
|
`--section'
|
Read offsets relative to the specified section instead of absolute
|
Read offsets relative to the specified section instead of absolute
|
addresses.
|
addresses.
|
|
|
|
|
File: binutils.info, Node: nlmconv, Next: windres, Prev: addr2line, Up: Top
|
File: binutils.info, Node: nlmconv, Next: windres, Prev: addr2line, Up: Top
|
|
|
11 nlmconv
|
11 nlmconv
|
**********
|
**********
|
|
|
`nlmconv' converts a relocatable object file into a NetWare Loadable
|
`nlmconv' converts a relocatable object file into a NetWare Loadable
|
Module.
|
Module.
|
|
|
_Warning:_ `nlmconv' is not always built as part of the binary
|
_Warning:_ `nlmconv' is not always built as part of the binary
|
utilities, since it is only useful for NLM targets.
|
utilities, since it is only useful for NLM targets.
|
|
|
nlmconv [`-I' BFDNAME|`--input-target='BFDNAME]
|
nlmconv [`-I' BFDNAME|`--input-target='BFDNAME]
|
[`-O' BFDNAME|`--output-target='BFDNAME]
|
[`-O' BFDNAME|`--output-target='BFDNAME]
|
[`-T' HEADERFILE|`--header-file='HEADERFILE]
|
[`-T' HEADERFILE|`--header-file='HEADERFILE]
|
[`-d'|`--debug'] [`-l' LINKER|`--linker='LINKER]
|
[`-d'|`--debug'] [`-l' LINKER|`--linker='LINKER]
|
[`-h'|`--help'] [`-V'|`--version']
|
[`-h'|`--help'] [`-V'|`--version']
|
INFILE OUTFILE
|
INFILE OUTFILE
|
|
|
`nlmconv' converts the relocatable `i386' object file INFILE into
|
`nlmconv' converts the relocatable `i386' object file INFILE into
|
the NetWare Loadable Module OUTFILE, optionally reading HEADERFILE for
|
the NetWare Loadable Module OUTFILE, optionally reading HEADERFILE for
|
NLM header information. For instructions on writing the NLM command
|
NLM header information. For instructions on writing the NLM command
|
file language used in header files, see the `linkers' section,
|
file language used in header files, see the `linkers' section,
|
`NLMLINK' in particular, of the `NLM Development and Tools Overview',
|
`NLMLINK' in particular, of the `NLM Development and Tools Overview',
|
which is part of the NLM Software Developer's Kit ("NLM SDK"),
|
which is part of the NLM Software Developer's Kit ("NLM SDK"),
|
available from Novell, Inc. `nlmconv' uses the GNU Binary File
|
available from Novell, Inc. `nlmconv' uses the GNU Binary File
|
Descriptor library to read INFILE; see *Note BFD: (ld.info)BFD, for
|
Descriptor library to read INFILE; see *Note BFD: (ld.info)BFD, for
|
more information.
|
more information.
|
|
|
`nlmconv' can perform a link step. In other words, you can list
|
`nlmconv' can perform a link step. In other words, you can list
|
more than one object file for input if you list them in the definitions
|
more than one object file for input if you list them in the definitions
|
file (rather than simply specifying one input file on the command line).
|
file (rather than simply specifying one input file on the command line).
|
In this case, `nlmconv' calls the linker for you.
|
In this case, `nlmconv' calls the linker for you.
|
|
|
`-I BFDNAME'
|
`-I BFDNAME'
|
`--input-target=BFDNAME'
|
`--input-target=BFDNAME'
|
Object format of the input file. `nlmconv' can usually determine
|
Object format of the input file. `nlmconv' can usually determine
|
the format of a given file (so no default is necessary). *Note
|
the format of a given file (so no default is necessary). *Note
|
Target Selection::, for more information.
|
Target Selection::, for more information.
|
|
|
`-O BFDNAME'
|
`-O BFDNAME'
|
`--output-target=BFDNAME'
|
`--output-target=BFDNAME'
|
Object format of the output file. `nlmconv' infers the output
|
Object format of the output file. `nlmconv' infers the output
|
format based on the input format, e.g. for a `i386' input file the
|
format based on the input format, e.g. for a `i386' input file the
|
output format is `nlm32-i386'. *Note Target Selection::, for more
|
output format is `nlm32-i386'. *Note Target Selection::, for more
|
information.
|
information.
|
|
|
`-T HEADERFILE'
|
`-T HEADERFILE'
|
`--header-file=HEADERFILE'
|
`--header-file=HEADERFILE'
|
Reads HEADERFILE for NLM header information. For instructions on
|
Reads HEADERFILE for NLM header information. For instructions on
|
writing the NLM command file language used in header files, see
|
writing the NLM command file language used in header files, see
|
see the `linkers' section, of the `NLM Development and Tools
|
see the `linkers' section, of the `NLM Development and Tools
|
Overview', which is part of the NLM Software Developer's Kit,
|
Overview', which is part of the NLM Software Developer's Kit,
|
available from Novell, Inc.
|
available from Novell, Inc.
|
|
|
`-d'
|
`-d'
|
`--debug'
|
`--debug'
|
Displays (on standard error) the linker command line used by
|
Displays (on standard error) the linker command line used by
|
`nlmconv'.
|
`nlmconv'.
|
|
|
`-l LINKER'
|
`-l LINKER'
|
`--linker=LINKER'
|
`--linker=LINKER'
|
Use LINKER for any linking. LINKER can be an absolute or a
|
Use LINKER for any linking. LINKER can be an absolute or a
|
relative pathname.
|
relative pathname.
|
|
|
`-h'
|
`-h'
|
`--help'
|
`--help'
|
Prints a usage summary.
|
Prints a usage summary.
|
|
|
`-V'
|
`-V'
|
`--version'
|
`--version'
|
Prints the version number for `nlmconv'.
|
Prints the version number for `nlmconv'.
|
|
|
|
|
File: binutils.info, Node: windmc, Next: dlltool, Prev: windres, Up: Top
|
File: binutils.info, Node: windmc, Next: dlltool, Prev: windres, Up: Top
|
|
|
12 windmc
|
12 windmc
|
*********
|
*********
|
|
|
`windmc' may be used to generator Windows message resources.
|
`windmc' may be used to generator Windows message resources.
|
|
|
_Warning:_ `windmc' is not always built as part of the binary
|
_Warning:_ `windmc' is not always built as part of the binary
|
utilities, since it is only useful for Windows targets.
|
utilities, since it is only useful for Windows targets.
|
|
|
windmc [options] input-file
|
windmc [options] input-file
|
|
|
`windmc' reads message definitions from an input file (.mc) and
|
`windmc' reads message definitions from an input file (.mc) and
|
translate them into a set of output files. The output files may be of
|
translate them into a set of output files. The output files may be of
|
four kinds:
|
four kinds:
|
|
|
`h'
|
`h'
|
A C header file containing the message definitions.
|
A C header file containing the message definitions.
|
|
|
`rc'
|
`rc'
|
A resource file compilable by the `windres' tool.
|
A resource file compilable by the `windres' tool.
|
|
|
`bin'
|
`bin'
|
One or more binary files containing the resource data for a
|
One or more binary files containing the resource data for a
|
specific message language.
|
specific message language.
|
|
|
`dbg'
|
`dbg'
|
A C include file that maps message id's to their symbolic name.
|
A C include file that maps message id's to their symbolic name.
|
|
|
The exact description of these different formats is available in
|
The exact description of these different formats is available in
|
documentation from Microsoft.
|
documentation from Microsoft.
|
|
|
When `windmc' converts from the `mc' format to the `bin' format,
|
When `windmc' converts from the `mc' format to the `bin' format,
|
`rc', `h', and optional `dbg' it is acting like the Windows Message
|
`rc', `h', and optional `dbg' it is acting like the Windows Message
|
Compiler.
|
Compiler.
|
|
|
`-a'
|
`-a'
|
`--ascii_in'
|
`--ascii_in'
|
Specifies that the input file specified is ANSI. This is the
|
Specifies that the input file specified is ANSI. This is the
|
default behaviour.
|
default behaviour.
|
|
|
`-A'
|
`-A'
|
`--ascii_out'
|
`--ascii_out'
|
Specifies that messages in the output `bin' files should be in ANSI
|
Specifies that messages in the output `bin' files should be in ANSI
|
format.
|
format.
|
|
|
`-b'
|
`-b'
|
`--binprefix'
|
`--binprefix'
|
Specifies that `bin' filenames should have to be prefixed by the
|
Specifies that `bin' filenames should have to be prefixed by the
|
basename of the source file.
|
basename of the source file.
|
|
|
`-c'
|
`-c'
|
`--customflag'
|
`--customflag'
|
Sets the customer bit in all message id's.
|
Sets the customer bit in all message id's.
|
|
|
`-C CODEPAGE'
|
`-C CODEPAGE'
|
`--codepage_in CODEPAGE'
|
`--codepage_in CODEPAGE'
|
Sets the default codepage to be used to convert input file to
|
Sets the default codepage to be used to convert input file to
|
UTF16. The default is ocdepage 1252.
|
UTF16. The default is ocdepage 1252.
|
|
|
`-d'
|
`-d'
|
`--decimal_values'
|
`--decimal_values'
|
Outputs the constants in the header file in decimal. Default is
|
Outputs the constants in the header file in decimal. Default is
|
using hexadecimal output.
|
using hexadecimal output.
|
|
|
`-e EXT'
|
`-e EXT'
|
`--extension EXT'
|
`--extension EXT'
|
The extension for the header file. The default is .h extension.
|
The extension for the header file. The default is .h extension.
|
|
|
`-F TARGET'
|
`-F TARGET'
|
`--target TARGET'
|
`--target TARGET'
|
Specify the BFD format to use for a bin file as output. This is a
|
Specify the BFD format to use for a bin file as output. This is a
|
BFD target name; you can use the `--help' option to see a list of
|
BFD target name; you can use the `--help' option to see a list of
|
supported targets. Normally `windmc' will use the default format,
|
supported targets. Normally `windmc' will use the default format,
|
which is the first one listed by the `--help' option. *Note
|
which is the first one listed by the `--help' option. *Note
|
Target Selection::.
|
Target Selection::.
|
|
|
`-h PATH'
|
`-h PATH'
|
`--headerdir PATH'
|
`--headerdir PATH'
|
The target directory of the generated header file. The default is
|
The target directory of the generated header file. The default is
|
the current directory.
|
the current directory.
|
|
|
`-H'
|
`-H'
|
`--help'
|
`--help'
|
Displays a list of command line options and then exits.
|
Displays a list of command line options and then exits.
|
|
|
`-m CHARACTERS'
|
`-m CHARACTERS'
|
`--maxlength CHARACTERS'
|
`--maxlength CHARACTERS'
|
Instructs `windmc' to generate a warning if the length of any
|
Instructs `windmc' to generate a warning if the length of any
|
message exceeds the number specified.
|
message exceeds the number specified.
|
|
|
`-n'
|
`-n'
|
`--nullterminate'
|
`--nullterminate'
|
Terminate message text in `bin' files by zero. By default they are
|
Terminate message text in `bin' files by zero. By default they are
|
terminated by CR/LF.
|
terminated by CR/LF.
|
|
|
`-o'
|
`-o'
|
`--hresult_use'
|
`--hresult_use'
|
Not yet implemented. Instructs `windmc' to generate an OLE2 header
|
Not yet implemented. Instructs `windmc' to generate an OLE2 header
|
file, using HRESULT definitions. Status codes are used if the flag
|
file, using HRESULT definitions. Status codes are used if the flag
|
is not specified.
|
is not specified.
|
|
|
`-O CODEPAGE'
|
`-O CODEPAGE'
|
`--codepage_out CODEPAGE'
|
`--codepage_out CODEPAGE'
|
Sets the default codepage to be used to output text files. The
|
Sets the default codepage to be used to output text files. The
|
default is ocdepage 1252.
|
default is ocdepage 1252.
|
|
|
`-r PATH'
|
`-r PATH'
|
`--rcdir PATH'
|
`--rcdir PATH'
|
The target directory for the generated `rc' script and the
|
The target directory for the generated `rc' script and the
|
generated `bin' files that the resource compiler script includes.
|
generated `bin' files that the resource compiler script includes.
|
The default is the current directory.
|
The default is the current directory.
|
|
|
`-u'
|
`-u'
|
`--unicode_in'
|
`--unicode_in'
|
Specifies that the input file is UTF16.
|
Specifies that the input file is UTF16.
|
|
|
`-U'
|
`-U'
|
`--unicode_out'
|
`--unicode_out'
|
Specifies that messages in the output `bin' file should be in UTF16
|
Specifies that messages in the output `bin' file should be in UTF16
|
format. This is the default behaviour.
|
format. This is the default behaviour.
|
|
|
`-v'
|
`-v'
|
|
|
`--verbose'
|
`--verbose'
|
Enable verbose mode.
|
Enable verbose mode.
|
|
|
`-V'
|
`-V'
|
|
|
`--version'
|
`--version'
|
Prints the version number for `windmc'.
|
Prints the version number for `windmc'.
|
|
|
`-x PATH'
|
`-x PATH'
|
`--xdgb PATH'
|
`--xdgb PATH'
|
The path of the `dbg' C include file that maps message id's to the
|
The path of the `dbg' C include file that maps message id's to the
|
symbolic name. No such file is generated without specifying the
|
symbolic name. No such file is generated without specifying the
|
switch.
|
switch.
|
|
|
|
|
File: binutils.info, Node: windres, Next: windmc, Prev: nlmconv, Up: Top
|
File: binutils.info, Node: windres, Next: windmc, Prev: nlmconv, Up: Top
|
|
|
13 windres
|
13 windres
|
**********
|
**********
|
|
|
`windres' may be used to manipulate Windows resources.
|
`windres' may be used to manipulate Windows resources.
|
|
|
_Warning:_ `windres' is not always built as part of the binary
|
_Warning:_ `windres' is not always built as part of the binary
|
utilities, since it is only useful for Windows targets.
|
utilities, since it is only useful for Windows targets.
|
|
|
windres [options] [input-file] [output-file]
|
windres [options] [input-file] [output-file]
|
|
|
`windres' reads resources from an input file and copies them into an
|
`windres' reads resources from an input file and copies them into an
|
output file. Either file may be in one of three formats:
|
output file. Either file may be in one of three formats:
|
|
|
`rc'
|
`rc'
|
A text format read by the Resource Compiler.
|
A text format read by the Resource Compiler.
|
|
|
`res'
|
`res'
|
A binary format generated by the Resource Compiler.
|
A binary format generated by the Resource Compiler.
|
|
|
`coff'
|
`coff'
|
A COFF object or executable.
|
A COFF object or executable.
|
|
|
The exact description of these different formats is available in
|
The exact description of these different formats is available in
|
documentation from Microsoft.
|
documentation from Microsoft.
|
|
|
When `windres' converts from the `rc' format to the `res' format, it
|
When `windres' converts from the `rc' format to the `res' format, it
|
is acting like the Windows Resource Compiler. When `windres' converts
|
is acting like the Windows Resource Compiler. When `windres' converts
|
from the `res' format to the `coff' format, it is acting like the
|
from the `res' format to the `coff' format, it is acting like the
|
Windows `CVTRES' program.
|
Windows `CVTRES' program.
|
|
|
When `windres' generates an `rc' file, the output is similar but not
|
When `windres' generates an `rc' file, the output is similar but not
|
identical to the format expected for the input. When an input `rc'
|
identical to the format expected for the input. When an input `rc'
|
file refers to an external filename, an output `rc' file will instead
|
file refers to an external filename, an output `rc' file will instead
|
include the file contents.
|
include the file contents.
|
|
|
If the input or output format is not specified, `windres' will guess
|
If the input or output format is not specified, `windres' will guess
|
based on the file name, or, for the input file, the file contents. A
|
based on the file name, or, for the input file, the file contents. A
|
file with an extension of `.rc' will be treated as an `rc' file, a file
|
file with an extension of `.rc' will be treated as an `rc' file, a file
|
with an extension of `.res' will be treated as a `res' file, and a file
|
with an extension of `.res' will be treated as a `res' file, and a file
|
with an extension of `.o' or `.exe' will be treated as a `coff' file.
|
with an extension of `.o' or `.exe' will be treated as a `coff' file.
|
|
|
If no output file is specified, `windres' will print the resources
|
If no output file is specified, `windres' will print the resources
|
in `rc' format to standard output.
|
in `rc' format to standard output.
|
|
|
The normal use is for you to write an `rc' file, use `windres' to
|
The normal use is for you to write an `rc' file, use `windres' to
|
convert it to a COFF object file, and then link the COFF file into your
|
convert it to a COFF object file, and then link the COFF file into your
|
application. This will make the resources described in the `rc' file
|
application. This will make the resources described in the `rc' file
|
available to Windows.
|
available to Windows.
|
|
|
`-i FILENAME'
|
`-i FILENAME'
|
`--input FILENAME'
|
`--input FILENAME'
|
The name of the input file. If this option is not used, then
|
The name of the input file. If this option is not used, then
|
`windres' will use the first non-option argument as the input file
|
`windres' will use the first non-option argument as the input file
|
name. If there are no non-option arguments, then `windres' will
|
name. If there are no non-option arguments, then `windres' will
|
read from standard input. `windres' can not read a COFF file from
|
read from standard input. `windres' can not read a COFF file from
|
standard input.
|
standard input.
|
|
|
`-o FILENAME'
|
`-o FILENAME'
|
`--output FILENAME'
|
`--output FILENAME'
|
The name of the output file. If this option is not used, then
|
The name of the output file. If this option is not used, then
|
`windres' will use the first non-option argument, after any used
|
`windres' will use the first non-option argument, after any used
|
for the input file name, as the output file name. If there is no
|
for the input file name, as the output file name. If there is no
|
non-option argument, then `windres' will write to standard output.
|
non-option argument, then `windres' will write to standard output.
|
`windres' can not write a COFF file to standard output. Note, for
|
`windres' can not write a COFF file to standard output. Note, for
|
compatibility with `rc' the option `-fo' is also accepted, but its
|
compatibility with `rc' the option `-fo' is also accepted, but its
|
use is not recommended.
|
use is not recommended.
|
|
|
`-J FORMAT'
|
`-J FORMAT'
|
`--input-format FORMAT'
|
`--input-format FORMAT'
|
The input format to read. FORMAT may be `res', `rc', or `coff'.
|
The input format to read. FORMAT may be `res', `rc', or `coff'.
|
If no input format is specified, `windres' will guess, as
|
If no input format is specified, `windres' will guess, as
|
described above.
|
described above.
|
|
|
`-O FORMAT'
|
`-O FORMAT'
|
`--output-format FORMAT'
|
`--output-format FORMAT'
|
The output format to generate. FORMAT may be `res', `rc', or
|
The output format to generate. FORMAT may be `res', `rc', or
|
`coff'. If no output format is specified, `windres' will guess,
|
`coff'. If no output format is specified, `windres' will guess,
|
as described above.
|
as described above.
|
|
|
`-F TARGET'
|
`-F TARGET'
|
`--target TARGET'
|
`--target TARGET'
|
Specify the BFD format to use for a COFF file as input or output.
|
Specify the BFD format to use for a COFF file as input or output.
|
This is a BFD target name; you can use the `--help' option to see
|
This is a BFD target name; you can use the `--help' option to see
|
a list of supported targets. Normally `windres' will use the
|
a list of supported targets. Normally `windres' will use the
|
default format, which is the first one listed by the `--help'
|
default format, which is the first one listed by the `--help'
|
option. *Note Target Selection::.
|
option. *Note Target Selection::.
|
|
|
`--preprocessor PROGRAM'
|
`--preprocessor PROGRAM'
|
When `windres' reads an `rc' file, it runs it through the C
|
When `windres' reads an `rc' file, it runs it through the C
|
preprocessor first. This option may be used to specify the
|
preprocessor first. This option may be used to specify the
|
preprocessor to use, including any leading arguments. The default
|
preprocessor to use, including any leading arguments. The default
|
preprocessor argument is `gcc -E -xc-header -DRC_INVOKED'.
|
preprocessor argument is `gcc -E -xc-header -DRC_INVOKED'.
|
|
|
`-I DIRECTORY'
|
`-I DIRECTORY'
|
`--include-dir DIRECTORY'
|
`--include-dir DIRECTORY'
|
Specify an include directory to use when reading an `rc' file.
|
Specify an include directory to use when reading an `rc' file.
|
`windres' will pass this to the preprocessor as an `-I' option.
|
`windres' will pass this to the preprocessor as an `-I' option.
|
`windres' will also search this directory when looking for files
|
`windres' will also search this directory when looking for files
|
named in the `rc' file. If the argument passed to this command
|
named in the `rc' file. If the argument passed to this command
|
matches any of the supported FORMATS (as described in the `-J'
|
matches any of the supported FORMATS (as described in the `-J'
|
option), it will issue a deprecation warning, and behave just like
|
option), it will issue a deprecation warning, and behave just like
|
the `-J' option. New programs should not use this behaviour. If a
|
the `-J' option. New programs should not use this behaviour. If a
|
directory happens to match a FORMAT, simple prefix it with `./' to
|
directory happens to match a FORMAT, simple prefix it with `./' to
|
disable the backward compatibility.
|
disable the backward compatibility.
|
|
|
`-D TARGET'
|
`-D TARGET'
|
`--define SYM[=VAL]'
|
`--define SYM[=VAL]'
|
Specify a `-D' option to pass to the preprocessor when reading an
|
Specify a `-D' option to pass to the preprocessor when reading an
|
`rc' file.
|
`rc' file.
|
|
|
`-U TARGET'
|
`-U TARGET'
|
`--undefine SYM'
|
`--undefine SYM'
|
Specify a `-U' option to pass to the preprocessor when reading an
|
Specify a `-U' option to pass to the preprocessor when reading an
|
`rc' file.
|
`rc' file.
|
|
|
`-r'
|
`-r'
|
Ignored for compatibility with rc.
|
Ignored for compatibility with rc.
|
|
|
`-v'
|
`-v'
|
Enable verbose mode. This tells you what the preprocessor is if
|
Enable verbose mode. This tells you what the preprocessor is if
|
you didn't specify one.
|
you didn't specify one.
|
|
|
`-c VAL'
|
`-c VAL'
|
|
|
`--codepage VAL'
|
`--codepage VAL'
|
Specify the default codepage to use when reading an `rc' file.
|
Specify the default codepage to use when reading an `rc' file.
|
VAL should be a hexadecimal prefixed by `0x' or decimal codepage
|
VAL should be a hexadecimal prefixed by `0x' or decimal codepage
|
code. The valid range is from zero up to 0xffff, but the validity
|
code. The valid range is from zero up to 0xffff, but the validity
|
of the codepage is host and configuration dependent.
|
of the codepage is host and configuration dependent.
|
|
|
`-l VAL'
|
`-l VAL'
|
|
|
`--language VAL'
|
`--language VAL'
|
Specify the default language to use when reading an `rc' file.
|
Specify the default language to use when reading an `rc' file.
|
VAL should be a hexadecimal language code. The low eight bits are
|
VAL should be a hexadecimal language code. The low eight bits are
|
the language, and the high eight bits are the sublanguage.
|
the language, and the high eight bits are the sublanguage.
|
|
|
`--use-temp-file'
|
`--use-temp-file'
|
Use a temporary file to instead of using popen to read the output
|
Use a temporary file to instead of using popen to read the output
|
of the preprocessor. Use this option if the popen implementation
|
of the preprocessor. Use this option if the popen implementation
|
is buggy on the host (eg., certain non-English language versions
|
is buggy on the host (eg., certain non-English language versions
|
of Windows 95 and Windows 98 are known to have buggy popen where
|
of Windows 95 and Windows 98 are known to have buggy popen where
|
the output will instead go the console).
|
the output will instead go the console).
|
|
|
`--no-use-temp-file'
|
`--no-use-temp-file'
|
Use popen, not a temporary file, to read the output of the
|
Use popen, not a temporary file, to read the output of the
|
preprocessor. This is the default behaviour.
|
preprocessor. This is the default behaviour.
|
|
|
`-h'
|
`-h'
|
|
|
`--help'
|
`--help'
|
Prints a usage summary.
|
Prints a usage summary.
|
|
|
`-V'
|
`-V'
|
|
|
`--version'
|
`--version'
|
Prints the version number for `windres'.
|
Prints the version number for `windres'.
|
|
|
`--yydebug'
|
`--yydebug'
|
If `windres' is compiled with `YYDEBUG' defined as `1', this will
|
If `windres' is compiled with `YYDEBUG' defined as `1', this will
|
turn on parser debugging.
|
turn on parser debugging.
|
|
|
|
|
File: binutils.info, Node: dlltool, Next: Common Options, Prev: windmc, Up: Top
|
File: binutils.info, Node: dlltool, Next: Common Options, Prev: windmc, Up: Top
|
|
|
14 dlltool
|
14 dlltool
|
**********
|
**********
|
|
|
`dlltool' is used to create the files needed to create dynamic link
|
`dlltool' is used to create the files needed to create dynamic link
|
libraries (DLLs) on systems which understand PE format image files such
|
libraries (DLLs) on systems which understand PE format image files such
|
as Windows. A DLL contains an export table which contains information
|
as Windows. A DLL contains an export table which contains information
|
that the runtime loader needs to resolve references from a referencing
|
that the runtime loader needs to resolve references from a referencing
|
program.
|
program.
|
|
|
The export table is generated by this program by reading in a `.def'
|
The export table is generated by this program by reading in a `.def'
|
file or scanning the `.a' and `.o' files which will be in the DLL. A
|
file or scanning the `.a' and `.o' files which will be in the DLL. A
|
`.o' file can contain information in special `.drectve' sections with
|
`.o' file can contain information in special `.drectve' sections with
|
export information.
|
export information.
|
|
|
_Note:_ `dlltool' is not always built as part of the binary
|
_Note:_ `dlltool' is not always built as part of the binary
|
utilities, since it is only useful for those targets which support
|
utilities, since it is only useful for those targets which support
|
DLLs.
|
DLLs.
|
|
|
dlltool [`-d'|`--input-def' DEF-FILE-NAME]
|
dlltool [`-d'|`--input-def' DEF-FILE-NAME]
|
[`-b'|`--base-file' BASE-FILE-NAME]
|
[`-b'|`--base-file' BASE-FILE-NAME]
|
[`-e'|`--output-exp' EXPORTS-FILE-NAME]
|
[`-e'|`--output-exp' EXPORTS-FILE-NAME]
|
[`-z'|`--output-def' DEF-FILE-NAME]
|
[`-z'|`--output-def' DEF-FILE-NAME]
|
[`-l'|`--output-lib' LIBRARY-FILE-NAME]
|
[`-l'|`--output-lib' LIBRARY-FILE-NAME]
|
[`--export-all-symbols'] [`--no-export-all-symbols']
|
[`--export-all-symbols'] [`--no-export-all-symbols']
|
[`--exclude-symbols' LIST]
|
[`--exclude-symbols' LIST]
|
[`--no-default-excludes']
|
[`--no-default-excludes']
|
[`-S'|`--as' PATH-TO-ASSEMBLER] [`-f'|`--as-flags' OPTIONS]
|
[`-S'|`--as' PATH-TO-ASSEMBLER] [`-f'|`--as-flags' OPTIONS]
|
[`-D'|`--dllname' NAME] [`-m'|`--machine' MACHINE]
|
[`-D'|`--dllname' NAME] [`-m'|`--machine' MACHINE]
|
[`-a'|`--add-indirect']
|
[`-a'|`--add-indirect']
|
[`-U'|`--add-underscore'] [`--add-stdcall-underscore']
|
[`-U'|`--add-underscore'] [`--add-stdcall-underscore']
|
[`-k'|`--kill-at'] [`-A'|`--add-stdcall-alias']
|
[`-k'|`--kill-at'] [`-A'|`--add-stdcall-alias']
|
[`-p'|`--ext-prefix-alias' PREFIX]
|
[`-p'|`--ext-prefix-alias' PREFIX]
|
[`-x'|`--no-idata4'] [`-c'|`--no-idata5'] [`-i'|`--interwork']
|
[`-x'|`--no-idata4'] [`-c'|`--no-idata5'] [`-i'|`--interwork']
|
[`-n'|`--nodelete'] [`-t'|`--temp-prefix' PREFIX]
|
[`-n'|`--nodelete'] [`-t'|`--temp-prefix' PREFIX]
|
[`-v'|`--verbose']
|
[`-v'|`--verbose']
|
[`-h'|`--help'] [`-V'|`--version']
|
[`-h'|`--help'] [`-V'|`--version']
|
[object-file ...]
|
[object-file ...]
|
|
|
`dlltool' reads its inputs, which can come from the `-d' and `-b'
|
`dlltool' reads its inputs, which can come from the `-d' and `-b'
|
options as well as object files specified on the command line. It then
|
options as well as object files specified on the command line. It then
|
processes these inputs and if the `-e' option has been specified it
|
processes these inputs and if the `-e' option has been specified it
|
creates a exports file. If the `-l' option has been specified it
|
creates a exports file. If the `-l' option has been specified it
|
creates a library file and if the `-z' option has been specified it
|
creates a library file and if the `-z' option has been specified it
|
creates a def file. Any or all of the `-e', `-l' and `-z' options can
|
creates a def file. Any or all of the `-e', `-l' and `-z' options can
|
be present in one invocation of dlltool.
|
be present in one invocation of dlltool.
|
|
|
When creating a DLL, along with the source for the DLL, it is
|
When creating a DLL, along with the source for the DLL, it is
|
necessary to have three other files. `dlltool' can help with the
|
necessary to have three other files. `dlltool' can help with the
|
creation of these files.
|
creation of these files.
|
|
|
The first file is a `.def' file which specifies which functions are
|
The first file is a `.def' file which specifies which functions are
|
exported from the DLL, which functions the DLL imports, and so on. This
|
exported from the DLL, which functions the DLL imports, and so on. This
|
is a text file and can be created by hand, or `dlltool' can be used to
|
is a text file and can be created by hand, or `dlltool' can be used to
|
create it using the `-z' option. In this case `dlltool' will scan the
|
create it using the `-z' option. In this case `dlltool' will scan the
|
object files specified on its command line looking for those functions
|
object files specified on its command line looking for those functions
|
which have been specially marked as being exported and put entries for
|
which have been specially marked as being exported and put entries for
|
them in the `.def' file it creates.
|
them in the `.def' file it creates.
|
|
|
In order to mark a function as being exported from a DLL, it needs to
|
In order to mark a function as being exported from a DLL, it needs to
|
have an `-export:' entry in the `.drectve' section of
|
have an `-export:' entry in the `.drectve' section of
|
the object file. This can be done in C by using the asm() operator:
|
the object file. This can be done in C by using the asm() operator:
|
|
|
asm (".section .drectve");
|
asm (".section .drectve");
|
asm (".ascii \"-export:my_func\"");
|
asm (".ascii \"-export:my_func\"");
|
|
|
int my_func (void) { ... }
|
int my_func (void) { ... }
|
|
|
The second file needed for DLL creation is an exports file. This
|
The second file needed for DLL creation is an exports file. This
|
file is linked with the object files that make up the body of the DLL
|
file is linked with the object files that make up the body of the DLL
|
and it handles the interface between the DLL and the outside world.
|
and it handles the interface between the DLL and the outside world.
|
This is a binary file and it can be created by giving the `-e' option to
|
This is a binary file and it can be created by giving the `-e' option to
|
`dlltool' when it is creating or reading in a `.def' file.
|
`dlltool' when it is creating or reading in a `.def' file.
|
|
|
The third file needed for DLL creation is the library file that
|
The third file needed for DLL creation is the library file that
|
programs will link with in order to access the functions in the DLL.
|
programs will link with in order to access the functions in the DLL.
|
This file can be created by giving the `-l' option to dlltool when it
|
This file can be created by giving the `-l' option to dlltool when it
|
is creating or reading in a `.def' file.
|
is creating or reading in a `.def' file.
|
|
|
`dlltool' builds the library file by hand, but it builds the exports
|
`dlltool' builds the library file by hand, but it builds the exports
|
file by creating temporary files containing assembler statements and
|
file by creating temporary files containing assembler statements and
|
then assembling these. The `-S' command line option can be used to
|
then assembling these. The `-S' command line option can be used to
|
specify the path to the assembler that dlltool will use, and the `-f'
|
specify the path to the assembler that dlltool will use, and the `-f'
|
option can be used to pass specific flags to that assembler. The `-n'
|
option can be used to pass specific flags to that assembler. The `-n'
|
can be used to prevent dlltool from deleting these temporary assembler
|
can be used to prevent dlltool from deleting these temporary assembler
|
files when it is done, and if `-n' is specified twice then this will
|
files when it is done, and if `-n' is specified twice then this will
|
prevent dlltool from deleting the temporary object files it used to
|
prevent dlltool from deleting the temporary object files it used to
|
build the library.
|
build the library.
|
|
|
Here is an example of creating a DLL from a source file `dll.c' and
|
Here is an example of creating a DLL from a source file `dll.c' and
|
also creating a program (from an object file called `program.o') that
|
also creating a program (from an object file called `program.o') that
|
uses that DLL:
|
uses that DLL:
|
|
|
gcc -c dll.c
|
gcc -c dll.c
|
dlltool -e exports.o -l dll.lib dll.o
|
dlltool -e exports.o -l dll.lib dll.o
|
gcc dll.o exports.o -o dll.dll
|
gcc dll.o exports.o -o dll.dll
|
gcc program.o dll.lib -o program
|
gcc program.o dll.lib -o program
|
|
|
The command line options have the following meanings:
|
The command line options have the following meanings:
|
|
|
`-d FILENAME'
|
`-d FILENAME'
|
`--input-def FILENAME'
|
`--input-def FILENAME'
|
Specifies the name of a `.def' file to be read in and processed.
|
Specifies the name of a `.def' file to be read in and processed.
|
|
|
`-b FILENAME'
|
`-b FILENAME'
|
`--base-file FILENAME'
|
`--base-file FILENAME'
|
Specifies the name of a base file to be read in and processed. The
|
Specifies the name of a base file to be read in and processed. The
|
contents of this file will be added to the relocation section in
|
contents of this file will be added to the relocation section in
|
the exports file generated by dlltool.
|
the exports file generated by dlltool.
|
|
|
`-e FILENAME'
|
`-e FILENAME'
|
`--output-exp FILENAME'
|
`--output-exp FILENAME'
|
Specifies the name of the export file to be created by dlltool.
|
Specifies the name of the export file to be created by dlltool.
|
|
|
`-z FILENAME'
|
`-z FILENAME'
|
`--output-def FILENAME'
|
`--output-def FILENAME'
|
Specifies the name of the `.def' file to be created by dlltool.
|
Specifies the name of the `.def' file to be created by dlltool.
|
|
|
`-l FILENAME'
|
`-l FILENAME'
|
`--output-lib FILENAME'
|
`--output-lib FILENAME'
|
Specifies the name of the library file to be created by dlltool.
|
Specifies the name of the library file to be created by dlltool.
|
|
|
`--export-all-symbols'
|
`--export-all-symbols'
|
Treat all global and weak defined symbols found in the input object
|
Treat all global and weak defined symbols found in the input object
|
files as symbols to be exported. There is a small list of symbols
|
files as symbols to be exported. There is a small list of symbols
|
which are not exported by default; see the `--no-default-excludes'
|
which are not exported by default; see the `--no-default-excludes'
|
option. You may add to the list of symbols to not export by using
|
option. You may add to the list of symbols to not export by using
|
the `--exclude-symbols' option.
|
the `--exclude-symbols' option.
|
|
|
`--no-export-all-symbols'
|
`--no-export-all-symbols'
|
Only export symbols explicitly listed in an input `.def' file or in
|
Only export symbols explicitly listed in an input `.def' file or in
|
`.drectve' sections in the input object files. This is the default
|
`.drectve' sections in the input object files. This is the default
|
behaviour. The `.drectve' sections are created by `dllexport'
|
behaviour. The `.drectve' sections are created by `dllexport'
|
attributes in the source code.
|
attributes in the source code.
|
|
|
`--exclude-symbols LIST'
|
`--exclude-symbols LIST'
|
Do not export the symbols in LIST. This is a list of symbol names
|
Do not export the symbols in LIST. This is a list of symbol names
|
separated by comma or colon characters. The symbol names should
|
separated by comma or colon characters. The symbol names should
|
not contain a leading underscore. This is only meaningful when
|
not contain a leading underscore. This is only meaningful when
|
`--export-all-symbols' is used.
|
`--export-all-symbols' is used.
|
|
|
`--no-default-excludes'
|
`--no-default-excludes'
|
When `--export-all-symbols' is used, it will by default avoid
|
When `--export-all-symbols' is used, it will by default avoid
|
exporting certain special symbols. The current list of symbols to
|
exporting certain special symbols. The current list of symbols to
|
avoid exporting is `DllMain@12', `DllEntryPoint@0', `impure_ptr'.
|
avoid exporting is `DllMain@12', `DllEntryPoint@0', `impure_ptr'.
|
You may use the `--no-default-excludes' option to go ahead and
|
You may use the `--no-default-excludes' option to go ahead and
|
export these special symbols. This is only meaningful when
|
export these special symbols. This is only meaningful when
|
`--export-all-symbols' is used.
|
`--export-all-symbols' is used.
|
|
|
`-S PATH'
|
`-S PATH'
|
`--as PATH'
|
`--as PATH'
|
Specifies the path, including the filename, of the assembler to be
|
Specifies the path, including the filename, of the assembler to be
|
used to create the exports file.
|
used to create the exports file.
|
|
|
`-f OPTIONS'
|
`-f OPTIONS'
|
`--as-flags OPTIONS'
|
`--as-flags OPTIONS'
|
Specifies any specific command line options to be passed to the
|
Specifies any specific command line options to be passed to the
|
assembler when building the exports file. This option will work
|
assembler when building the exports file. This option will work
|
even if the `-S' option is not used. This option only takes one
|
even if the `-S' option is not used. This option only takes one
|
argument, and if it occurs more than once on the command line,
|
argument, and if it occurs more than once on the command line,
|
then later occurrences will override earlier occurrences. So if
|
then later occurrences will override earlier occurrences. So if
|
it is necessary to pass multiple options to the assembler they
|
it is necessary to pass multiple options to the assembler they
|
should be enclosed in double quotes.
|
should be enclosed in double quotes.
|
|
|
`-D NAME'
|
`-D NAME'
|
`--dll-name NAME'
|
`--dll-name NAME'
|
Specifies the name to be stored in the `.def' file as the name of
|
Specifies the name to be stored in the `.def' file as the name of
|
the DLL when the `-e' option is used. If this option is not
|
the DLL when the `-e' option is used. If this option is not
|
present, then the filename given to the `-e' option will be used
|
present, then the filename given to the `-e' option will be used
|
as the name of the DLL.
|
as the name of the DLL.
|
|
|
`-m MACHINE'
|
`-m MACHINE'
|
`-machine MACHINE'
|
`-machine MACHINE'
|
Specifies the type of machine for which the library file should be
|
Specifies the type of machine for which the library file should be
|
built. `dlltool' has a built in default type, depending upon how
|
built. `dlltool' has a built in default type, depending upon how
|
it was created, but this option can be used to override that.
|
it was created, but this option can be used to override that.
|
This is normally only useful when creating DLLs for an ARM
|
This is normally only useful when creating DLLs for an ARM
|
processor, when the contents of the DLL are actually encode using
|
processor, when the contents of the DLL are actually encode using
|
Thumb instructions.
|
Thumb instructions.
|
|
|
`-a'
|
`-a'
|
`--add-indirect'
|
`--add-indirect'
|
Specifies that when `dlltool' is creating the exports file it
|
Specifies that when `dlltool' is creating the exports file it
|
should add a section which allows the exported functions to be
|
should add a section which allows the exported functions to be
|
referenced without using the import library. Whatever the hell
|
referenced without using the import library. Whatever the hell
|
that means!
|
that means!
|
|
|
`-U'
|
`-U'
|
`--add-underscore'
|
`--add-underscore'
|
Specifies that when `dlltool' is creating the exports file it
|
Specifies that when `dlltool' is creating the exports file it
|
should prepend an underscore to the names of _all_ exported
|
should prepend an underscore to the names of _all_ exported
|
symbols.
|
symbols.
|
|
|
`--add-stdcall-underscore'
|
`--add-stdcall-underscore'
|
Specifies that when `dlltool' is creating the exports file it
|
Specifies that when `dlltool' is creating the exports file it
|
should prepend an underscore to the names of exported _stdcall_
|
should prepend an underscore to the names of exported _stdcall_
|
functions. Variable names and non-stdcall function names are not
|
functions. Variable names and non-stdcall function names are not
|
modified. This option is useful when creating GNU-compatible
|
modified. This option is useful when creating GNU-compatible
|
import libs for third party DLLs that were built with MS-Windows
|
import libs for third party DLLs that were built with MS-Windows
|
tools.
|
tools.
|
|
|
`-k'
|
`-k'
|
`--kill-at'
|
`--kill-at'
|
Specifies that when `dlltool' is creating the exports file it
|
Specifies that when `dlltool' is creating the exports file it
|
should not append the string `@ '. These numbers are
|
should not append the string `@ '. These numbers are
|
called ordinal numbers and they represent another way of accessing
|
called ordinal numbers and they represent another way of accessing
|
the function in a DLL, other than by name.
|
the function in a DLL, other than by name.
|
|
|
`-A'
|
`-A'
|
`--add-stdcall-alias'
|
`--add-stdcall-alias'
|
Specifies that when `dlltool' is creating the exports file it
|
Specifies that when `dlltool' is creating the exports file it
|
should add aliases for stdcall symbols without `@ ' in
|
should add aliases for stdcall symbols without `@ ' in
|
addition to the symbols with `@ '.
|
addition to the symbols with `@ '.
|
|
|
`-p'
|
`-p'
|
`--ext-prefix-alias PREFIX'
|
`--ext-prefix-alias PREFIX'
|
Causes `dlltool' to create external aliases for all DLL imports
|
Causes `dlltool' to create external aliases for all DLL imports
|
with the specified prefix. The aliases are created for both
|
with the specified prefix. The aliases are created for both
|
external and import symbols with no leading underscore.
|
external and import symbols with no leading underscore.
|
|
|
`-x'
|
`-x'
|
`--no-idata4'
|
`--no-idata4'
|
Specifies that when `dlltool' is creating the exports and library
|
Specifies that when `dlltool' is creating the exports and library
|
files it should omit the `.idata4' section. This is for
|
files it should omit the `.idata4' section. This is for
|
compatibility with certain operating systems.
|
compatibility with certain operating systems.
|
|
|
`-c'
|
`-c'
|
`--no-idata5'
|
`--no-idata5'
|
Specifies that when `dlltool' is creating the exports and library
|
Specifies that when `dlltool' is creating the exports and library
|
files it should omit the `.idata5' section. This is for
|
files it should omit the `.idata5' section. This is for
|
compatibility with certain operating systems.
|
compatibility with certain operating systems.
|
|
|
`-i'
|
`-i'
|
`--interwork'
|
`--interwork'
|
Specifies that `dlltool' should mark the objects in the library
|
Specifies that `dlltool' should mark the objects in the library
|
file and exports file that it produces as supporting interworking
|
file and exports file that it produces as supporting interworking
|
between ARM and Thumb code.
|
between ARM and Thumb code.
|
|
|
`-n'
|
`-n'
|
`--nodelete'
|
`--nodelete'
|
Makes `dlltool' preserve the temporary assembler files it used to
|
Makes `dlltool' preserve the temporary assembler files it used to
|
create the exports file. If this option is repeated then dlltool
|
create the exports file. If this option is repeated then dlltool
|
will also preserve the temporary object files it uses to create
|
will also preserve the temporary object files it uses to create
|
the library file.
|
the library file.
|
|
|
`-t PREFIX'
|
`-t PREFIX'
|
`--temp-prefix PREFIX'
|
`--temp-prefix PREFIX'
|
Makes `dlltool' use PREFIX when constructing the names of
|
Makes `dlltool' use PREFIX when constructing the names of
|
temporary assembler and object files. By default, the temp file
|
temporary assembler and object files. By default, the temp file
|
prefix is generated from the pid.
|
prefix is generated from the pid.
|
|
|
`-v'
|
`-v'
|
`--verbose'
|
`--verbose'
|
Make dlltool describe what it is doing.
|
Make dlltool describe what it is doing.
|
|
|
`-h'
|
`-h'
|
`--help'
|
`--help'
|
Displays a list of command line options and then exits.
|
Displays a list of command line options and then exits.
|
|
|
`-V'
|
`-V'
|
`--version'
|
`--version'
|
Displays dlltool's version number and then exits.
|
Displays dlltool's version number and then exits.
|
|
|
|
|
* Menu:
|
* Menu:
|
|
|
* def file format:: The format of the dlltool `.def' file
|
* def file format:: The format of the dlltool `.def' file
|
|
|
|
|
File: binutils.info, Node: def file format, Up: dlltool
|
File: binutils.info, Node: def file format, Up: dlltool
|
|
|
14.1 The format of the `dlltool' `.def' file
|
14.1 The format of the `dlltool' `.def' file
|
============================================
|
============================================
|
|
|
A `.def' file contains any number of the following commands:
|
A `.def' file contains any number of the following commands:
|
|
|
`NAME' NAME `[ ,' BASE `]'
|
`NAME' NAME `[ ,' BASE `]'
|
The result is going to be named NAME`.exe'.
|
The result is going to be named NAME`.exe'.
|
|
|
`LIBRARY' NAME `[ ,' BASE `]'
|
`LIBRARY' NAME `[ ,' BASE `]'
|
The result is going to be named NAME`.dll'.
|
The result is going to be named NAME`.dll'.
|
|
|
`EXPORTS ( ( (' NAME1 `[ = ' NAME2 `] ) | ( ' NAME1 `=' MODULE-NAME `.' EXTERNAL-NAME `) )'
|
`EXPORTS ( ( (' NAME1 `[ = ' NAME2 `] ) | ( ' NAME1 `=' MODULE-NAME `.' EXTERNAL-NAME `) )'
|
|
|
`[' INTEGER `] [ NONAME ] [ CONSTANT ] [ DATA ] [ PRIVATE ] ) *'
|
`[' INTEGER `] [ NONAME ] [ CONSTANT ] [ DATA ] [ PRIVATE ] ) *'
|
Declares NAME1 as an exported symbol from the DLL, with optional
|
Declares NAME1 as an exported symbol from the DLL, with optional
|
ordinal number INTEGER, or declares NAME1 as an alias (forward) of
|
ordinal number INTEGER, or declares NAME1 as an alias (forward) of
|
the function EXTERNAL-NAME in the DLL MODULE-NAME.
|
the function EXTERNAL-NAME in the DLL MODULE-NAME.
|
|
|
`IMPORTS ( (' INTERNAL-NAME `=' MODULE-NAME `.' INTEGER `) | [' INTERNAL-NAME `= ]' MODULE-NAME `.' EXTERNAL-NAME `) ) *'
|
`IMPORTS ( (' INTERNAL-NAME `=' MODULE-NAME `.' INTEGER `) | [' INTERNAL-NAME `= ]' MODULE-NAME `.' EXTERNAL-NAME `) ) *'
|
Declares that EXTERNAL-NAME or the exported function whose ordinal
|
Declares that EXTERNAL-NAME or the exported function whose ordinal
|
number is INTEGER is to be imported from the file MODULE-NAME. If
|
number is INTEGER is to be imported from the file MODULE-NAME. If
|
INTERNAL-NAME is specified then this is the name that the imported
|
INTERNAL-NAME is specified then this is the name that the imported
|
function will be referred to in the body of the DLL.
|
function will be referred to in the body of the DLL.
|
|
|
`DESCRIPTION' STRING
|
`DESCRIPTION' STRING
|
Puts STRING into the output `.exp' file in the `.rdata' section.
|
Puts STRING into the output `.exp' file in the `.rdata' section.
|
|
|
`STACKSIZE' NUMBER-RESERVE `[, ' NUMBER-COMMIT `]'
|
`STACKSIZE' NUMBER-RESERVE `[, ' NUMBER-COMMIT `]'
|
|
|
`HEAPSIZE' NUMBER-RESERVE `[, ' NUMBER-COMMIT `]'
|
`HEAPSIZE' NUMBER-RESERVE `[, ' NUMBER-COMMIT `]'
|
Generates `--stack' or `--heap' NUMBER-RESERVE,NUMBER-COMMIT in
|
Generates `--stack' or `--heap' NUMBER-RESERVE,NUMBER-COMMIT in
|
the output `.drectve' section. The linker will see this and act
|
the output `.drectve' section. The linker will see this and act
|
upon it.
|
upon it.
|
|
|
`CODE' ATTR `+'
|
`CODE' ATTR `+'
|
|
|
`DATA' ATTR `+'
|
`DATA' ATTR `+'
|
|
|
`SECTIONS (' SECTION-NAME ATTR` + ) *'
|
`SECTIONS (' SECTION-NAME ATTR` + ) *'
|
Generates `--attr' SECTION-NAME ATTR in the output `.drectve'
|
Generates `--attr' SECTION-NAME ATTR in the output `.drectve'
|
section, where ATTR is one of `READ', `WRITE', `EXECUTE' or
|
section, where ATTR is one of `READ', `WRITE', `EXECUTE' or
|
`SHARED'. The linker will see this and act upon it.
|
`SHARED'. The linker will see this and act upon it.
|
|
|
|
|
|
|
File: binutils.info, Node: readelf, Next: size, Prev: ranlib, Up: Top
|
File: binutils.info, Node: readelf, Next: size, Prev: ranlib, Up: Top
|
|
|
15 readelf
|
15 readelf
|
**********
|
**********
|
|
|
readelf [`-a'|`--all']
|
readelf [`-a'|`--all']
|
[`-h'|`--file-header']
|
[`-h'|`--file-header']
|
[`-l'|`--program-headers'|`--segments']
|
[`-l'|`--program-headers'|`--segments']
|
[`-S'|`--section-headers'|`--sections']
|
[`-S'|`--section-headers'|`--sections']
|
[`-g'|`--section-groups']
|
[`-g'|`--section-groups']
|
[`-t'|`--section-details']
|
[`-t'|`--section-details']
|
[`-e'|`--headers']
|
[`-e'|`--headers']
|
[`-s'|`--syms'|`--symbols']
|
[`-s'|`--syms'|`--symbols']
|
[`-n'|`--notes']
|
[`-n'|`--notes']
|
[`-r'|`--relocs']
|
[`-r'|`--relocs']
|
[`-u'|`--unwind']
|
[`-u'|`--unwind']
|
[`-d'|`--dynamic']
|
[`-d'|`--dynamic']
|
[`-V'|`--version-info']
|
[`-V'|`--version-info']
|
[`-A'|`--arch-specific']
|
[`-A'|`--arch-specific']
|
[`-D'|`--use-dynamic']
|
[`-D'|`--use-dynamic']
|
[`-x' |`--hex-dump=']
|
[`-x' |`--hex-dump=']
|
[`-p' |`--string-dump=']
|
[`-p' |`--string-dump=']
|
[`-c'|`--archive-index']
|
[`-c'|`--archive-index']
|
[`-w[lLiaprmfFsoR]'|
|
[`-w[lLiaprmfFsoR]'|
|
`--debug-dump'[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges]]
|
`--debug-dump'[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges]]
|
[`-I'|`-histogram']
|
[`-I'|`-histogram']
|
[`-v'|`--version']
|
[`-v'|`--version']
|
[`-W'|`--wide']
|
[`-W'|`--wide']
|
[`-H'|`--help']
|
[`-H'|`--help']
|
ELFFILE...
|
ELFFILE...
|
|
|
`readelf' displays information about one or more ELF format object
|
`readelf' displays information about one or more ELF format object
|
files. The options control what particular information to display.
|
files. The options control what particular information to display.
|
|
|
ELFFILE... are the object files to be examined. 32-bit and 64-bit
|
ELFFILE... are the object files to be examined. 32-bit and 64-bit
|
ELF files are supported, as are archives containing ELF files.
|
ELF files are supported, as are archives containing ELF files.
|
|
|
This program performs a similar function to `objdump' but it goes
|
This program performs a similar function to `objdump' but it goes
|
into more detail and it exists independently of the BFD library, so if
|
into more detail and it exists independently of the BFD library, so if
|
there is a bug in BFD then readelf will not be affected.
|
there is a bug in BFD then readelf will not be affected.
|
|
|
The long and short forms of options, shown here as alternatives, are
|
The long and short forms of options, shown here as alternatives, are
|
equivalent. At least one option besides `-v' or `-H' must be given.
|
equivalent. At least one option besides `-v' or `-H' must be given.
|
|
|
`-a'
|
`-a'
|
`--all'
|
`--all'
|
Equivalent to specifying `--file-header', `--program-headers',
|
Equivalent to specifying `--file-header', `--program-headers',
|
`--sections', `--symbols', `--relocs', `--dynamic', `--notes' and
|
`--sections', `--symbols', `--relocs', `--dynamic', `--notes' and
|
`--version-info'.
|
`--version-info'.
|
|
|
`-h'
|
`-h'
|
`--file-header'
|
`--file-header'
|
Displays the information contained in the ELF header at the start
|
Displays the information contained in the ELF header at the start
|
of the file.
|
of the file.
|
|
|
`-l'
|
`-l'
|
`--program-headers'
|
`--program-headers'
|
`--segments'
|
`--segments'
|
Displays the information contained in the file's segment headers,
|
Displays the information contained in the file's segment headers,
|
if it has any.
|
if it has any.
|
|
|
`-S'
|
`-S'
|
`--sections'
|
`--sections'
|
`--section-headers'
|
`--section-headers'
|
Displays the information contained in the file's section headers,
|
Displays the information contained in the file's section headers,
|
if it has any.
|
if it has any.
|
|
|
`-g'
|
`-g'
|
`--section-groups'
|
`--section-groups'
|
Displays the information contained in the file's section groups,
|
Displays the information contained in the file's section groups,
|
if it has any.
|
if it has any.
|
|
|
`-t'
|
`-t'
|
`--section-details'
|
`--section-details'
|
Displays the detailed section information. Implies `-S'.
|
Displays the detailed section information. Implies `-S'.
|
|
|
`-s'
|
`-s'
|
`--symbols'
|
`--symbols'
|
`--syms'
|
`--syms'
|
Displays the entries in symbol table section of the file, if it
|
Displays the entries in symbol table section of the file, if it
|
has one.
|
has one.
|
|
|
`-e'
|
`-e'
|
`--headers'
|
`--headers'
|
Display all the headers in the file. Equivalent to `-h -l -S'.
|
Display all the headers in the file. Equivalent to `-h -l -S'.
|
|
|
`-n'
|
`-n'
|
`--notes'
|
`--notes'
|
Displays the contents of the NOTE segments and/or sections, if any.
|
Displays the contents of the NOTE segments and/or sections, if any.
|
|
|
`-r'
|
`-r'
|
`--relocs'
|
`--relocs'
|
Displays the contents of the file's relocation section, if it has
|
Displays the contents of the file's relocation section, if it has
|
one.
|
one.
|
|
|
`-u'
|
`-u'
|
`--unwind'
|
`--unwind'
|
Displays the contents of the file's unwind section, if it has one.
|
Displays the contents of the file's unwind section, if it has one.
|
Only the unwind sections for IA64 ELF files are currently
|
Only the unwind sections for IA64 ELF files are currently
|
supported.
|
supported.
|
|
|
`-d'
|
`-d'
|
`--dynamic'
|
`--dynamic'
|
Displays the contents of the file's dynamic section, if it has one.
|
Displays the contents of the file's dynamic section, if it has one.
|
|
|
`-V'
|
`-V'
|
`--version-info'
|
`--version-info'
|
Displays the contents of the version sections in the file, it they
|
Displays the contents of the version sections in the file, it they
|
exist.
|
exist.
|
|
|
`-A'
|
`-A'
|
`--arch-specific'
|
`--arch-specific'
|
Displays architecture-specific information in the file, if there
|
Displays architecture-specific information in the file, if there
|
is any.
|
is any.
|
|
|
`-D'
|
`-D'
|
`--use-dynamic'
|
`--use-dynamic'
|
When displaying symbols, this option makes `readelf' use the
|
When displaying symbols, this option makes `readelf' use the
|
symbol table in the file's dynamic section, rather than the one in
|
symbol table in the file's dynamic section, rather than the one in
|
the symbols section.
|
the symbols section.
|
|
|
`-x '
|
`-x '
|
`--hex-dump='
|
`--hex-dump='
|
Displays the contents of the indicated section as a hexadecimal
|
Displays the contents of the indicated section as a hexadecimal
|
dump. A number identifies a particular section by index in the
|
dump. A number identifies a particular section by index in the
|
section table; any other string identifies all sections with that
|
section table; any other string identifies all sections with that
|
name in the object file.
|
name in the object file.
|
|
|
`-p '
|
`-p '
|
`--string-dump='
|
`--string-dump='
|
Displays the contents of the indicated section as printable
|
Displays the contents of the indicated section as printable
|
strings. A number identifies a particular section by index in the
|
strings. A number identifies a particular section by index in the
|
section table; any other string identifies all sections with that
|
section table; any other string identifies all sections with that
|
name in the object file.
|
name in the object file.
|
|
|
`-c'
|
`-c'
|
`--archive-index'
|
`--archive-index'
|
Displays the file symbol index infomation contained in the header
|
Displays the file symbol index infomation contained in the header
|
part of binary archives. Performs the same function as the `t'
|
part of binary archives. Performs the same function as the `t'
|
command to `ar', but without using the BFD library. *Note ar::.
|
command to `ar', but without using the BFD library. *Note ar::.
|
|
|
`-w[lLiaprmfFsoR]'
|
`-w[lLiaprmfFsoR]'
|
`--debug-dump[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges]'
|
`--debug-dump[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges]'
|
Displays the contents of the debug sections in the file, if any are
|
Displays the contents of the debug sections in the file, if any are
|
present. If one of the optional letters or words follows the
|
present. If one of the optional letters or words follows the
|
switch then only data found in those specific sections will be
|
switch then only data found in those specific sections will be
|
dumped.
|
dumped.
|
|
|
Note: the `=decodedline' option will display the interpreted
|
Note: the `=decodedline' option will display the interpreted
|
contents of a .debug_line section whereas the `=rawline' option
|
contents of a .debug_line section whereas the `=rawline' option
|
dumps the contents in a raw format.
|
dumps the contents in a raw format.
|
|
|
`-I'
|
`-I'
|
`--histogram'
|
`--histogram'
|
Display a histogram of bucket list lengths when displaying the
|
Display a histogram of bucket list lengths when displaying the
|
contents of the symbol tables.
|
contents of the symbol tables.
|
|
|
`-v'
|
`-v'
|
`--version'
|
`--version'
|
Display the version number of readelf.
|
Display the version number of readelf.
|
|
|
`-W'
|
`-W'
|
`--wide'
|
`--wide'
|
Don't break output lines to fit into 80 columns. By default
|
Don't break output lines to fit into 80 columns. By default
|
`readelf' breaks section header and segment listing lines for
|
`readelf' breaks section header and segment listing lines for
|
64-bit ELF files, so that they fit into 80 columns. This option
|
64-bit ELF files, so that they fit into 80 columns. This option
|
causes `readelf' to print each section header resp. each segment
|
causes `readelf' to print each section header resp. each segment
|
one a single line, which is far more readable on terminals wider
|
one a single line, which is far more readable on terminals wider
|
than 80 columns.
|
than 80 columns.
|
|
|
`-H'
|
`-H'
|
`--help'
|
`--help'
|
Display the command line options understood by `readelf'.
|
Display the command line options understood by `readelf'.
|
|
|
|
|
|
|
File: binutils.info, Node: Common Options, Next: Selecting the Target System, Prev: dlltool, Up: Top
|
File: binutils.info, Node: Common Options, Next: Selecting the Target System, Prev: dlltool, Up: Top
|
|
|
16 Common Options
|
16 Common Options
|
*****************
|
*****************
|
|
|
The following command-line options are supported by all of the programs
|
The following command-line options are supported by all of the programs
|
described in this manual.
|
described in this manual.
|
|
|
`@FILE'
|
`@FILE'
|
Read command-line options from FILE. The options read are
|
Read command-line options from FILE. The options read are
|
inserted in place of the original @FILE option. If FILE does not
|
inserted in place of the original @FILE option. If FILE does not
|
exist, or cannot be read, then the option will be treated
|
exist, or cannot be read, then the option will be treated
|
literally, and not removed.
|
literally, and not removed.
|
|
|
Options in FILE are separated by whitespace. A whitespace
|
Options in FILE are separated by whitespace. A whitespace
|
character may be included in an option by surrounding the entire
|
character may be included in an option by surrounding the entire
|
option in either single or double quotes. Any character
|
option in either single or double quotes. Any character
|
(including a backslash) may be included by prefixing the character
|
(including a backslash) may be included by prefixing the character
|
to be included with a backslash. The FILE may itself contain
|
to be included with a backslash. The FILE may itself contain
|
additional @FILE options; any such options will be processed
|
additional @FILE options; any such options will be processed
|
recursively.
|
recursively.
|
|
|
`--help'
|
`--help'
|
Display the command-line options supported by the program.
|
Display the command-line options supported by the program.
|
|
|
`--version'
|
`--version'
|
Display the version number of the program.
|
Display the version number of the program.
|
|
|
|
|
|
|
File: binutils.info, Node: Selecting the Target System, Next: Reporting Bugs, Prev: Common Options, Up: Top
|
File: binutils.info, Node: Selecting the Target System, Next: Reporting Bugs, Prev: Common Options, Up: Top
|
|
|
17 Selecting the Target System
|
17 Selecting the Target System
|
******************************
|
******************************
|
|
|
You can specify two aspects of the target system to the GNU binary file
|
You can specify two aspects of the target system to the GNU binary file
|
utilities, each in several ways:
|
utilities, each in several ways:
|
|
|
* the target
|
* the target
|
|
|
* the architecture
|
* the architecture
|
|
|
In the following summaries, the lists of ways to specify values are
|
In the following summaries, the lists of ways to specify values are
|
in order of decreasing precedence. The ways listed first override those
|
in order of decreasing precedence. The ways listed first override those
|
listed later.
|
listed later.
|
|
|
The commands to list valid values only list the values for which the
|
The commands to list valid values only list the values for which the
|
programs you are running were configured. If they were configured with
|
programs you are running were configured. If they were configured with
|
`--enable-targets=all', the commands list most of the available values,
|
`--enable-targets=all', the commands list most of the available values,
|
but a few are left out; not all targets can be configured in at once
|
but a few are left out; not all targets can be configured in at once
|
because some of them can only be configured "native" (on hosts with the
|
because some of them can only be configured "native" (on hosts with the
|
same type as the target system).
|
same type as the target system).
|
|
|
* Menu:
|
* Menu:
|
|
|
* Target Selection::
|
* Target Selection::
|
* Architecture Selection::
|
* Architecture Selection::
|
|
|
|
|
File: binutils.info, Node: Target Selection, Next: Architecture Selection, Up: Selecting the Target System
|
File: binutils.info, Node: Target Selection, Next: Architecture Selection, Up: Selecting the Target System
|
|
|
17.1 Target Selection
|
17.1 Target Selection
|
=====================
|
=====================
|
|
|
A "target" is an object file format. A given target may be supported
|
A "target" is an object file format. A given target may be supported
|
for multiple architectures (*note Architecture Selection::). A target
|
for multiple architectures (*note Architecture Selection::). A target
|
selection may also have variations for different operating systems or
|
selection may also have variations for different operating systems or
|
architectures.
|
architectures.
|
|
|
The command to list valid target values is `objdump -i' (the first
|
The command to list valid target values is `objdump -i' (the first
|
column of output contains the relevant information).
|
column of output contains the relevant information).
|
|
|
Some sample values are: `a.out-hp300bsd', `ecoff-littlemips',
|
Some sample values are: `a.out-hp300bsd', `ecoff-littlemips',
|
`a.out-sunos-big'.
|
`a.out-sunos-big'.
|
|
|
You can also specify a target using a configuration triplet. This is
|
You can also specify a target using a configuration triplet. This is
|
the same sort of name that is passed to `configure' to specify a
|
the same sort of name that is passed to `configure' to specify a
|
target. When you use a configuration triplet as an argument, it must be
|
target. When you use a configuration triplet as an argument, it must be
|
fully canonicalized. You can see the canonical version of a triplet by
|
fully canonicalized. You can see the canonical version of a triplet by
|
running the shell script `config.sub' which is included with the
|
running the shell script `config.sub' which is included with the
|
sources.
|
sources.
|
|
|
Some sample configuration triplets are: `m68k-hp-bsd',
|
Some sample configuration triplets are: `m68k-hp-bsd',
|
`mips-dec-ultrix', `sparc-sun-sunos'.
|
`mips-dec-ultrix', `sparc-sun-sunos'.
|
|
|
`objdump' Target
|
`objdump' Target
|
----------------
|
----------------
|
|
|
Ways to specify:
|
Ways to specify:
|
|
|
1. command line option: `-b' or `--target'
|
1. command line option: `-b' or `--target'
|
|
|
2. environment variable `GNUTARGET'
|
2. environment variable `GNUTARGET'
|
|
|
3. deduced from the input file
|
3. deduced from the input file
|
|
|
`objcopy' and `strip' Input Target
|
`objcopy' and `strip' Input Target
|
----------------------------------
|
----------------------------------
|
|
|
Ways to specify:
|
Ways to specify:
|
|
|
1. command line options: `-I' or `--input-target', or `-F' or
|
1. command line options: `-I' or `--input-target', or `-F' or
|
`--target'
|
`--target'
|
|
|
2. environment variable `GNUTARGET'
|
2. environment variable `GNUTARGET'
|
|
|
3. deduced from the input file
|
3. deduced from the input file
|
|
|
`objcopy' and `strip' Output Target
|
`objcopy' and `strip' Output Target
|
-----------------------------------
|
-----------------------------------
|
|
|
Ways to specify:
|
Ways to specify:
|
|
|
1. command line options: `-O' or `--output-target', or `-F' or
|
1. command line options: `-O' or `--output-target', or `-F' or
|
`--target'
|
`--target'
|
|
|
2. the input target (see "`objcopy' and `strip' Input Target" above)
|
2. the input target (see "`objcopy' and `strip' Input Target" above)
|
|
|
3. environment variable `GNUTARGET'
|
3. environment variable `GNUTARGET'
|
|
|
4. deduced from the input file
|
4. deduced from the input file
|
|
|
`nm', `size', and `strings' Target
|
`nm', `size', and `strings' Target
|
----------------------------------
|
----------------------------------
|
|
|
Ways to specify:
|
Ways to specify:
|
|
|
1. command line option: `--target'
|
1. command line option: `--target'
|
|
|
2. environment variable `GNUTARGET'
|
2. environment variable `GNUTARGET'
|
|
|
3. deduced from the input file
|
3. deduced from the input file
|
|
|
|
|
File: binutils.info, Node: Architecture Selection, Prev: Target Selection, Up: Selecting the Target System
|
File: binutils.info, Node: Architecture Selection, Prev: Target Selection, Up: Selecting the Target System
|
|
|
17.2 Architecture Selection
|
17.2 Architecture Selection
|
===========================
|
===========================
|
|
|
An "architecture" is a type of CPU on which an object file is to run.
|
An "architecture" is a type of CPU on which an object file is to run.
|
Its name may contain a colon, separating the name of the processor
|
Its name may contain a colon, separating the name of the processor
|
family from the name of the particular CPU.
|
family from the name of the particular CPU.
|
|
|
The command to list valid architecture values is `objdump -i' (the
|
The command to list valid architecture values is `objdump -i' (the
|
second column contains the relevant information).
|
second column contains the relevant information).
|
|
|
Sample values: `m68k:68020', `mips:3000', `sparc'.
|
Sample values: `m68k:68020', `mips:3000', `sparc'.
|
|
|
`objdump' Architecture
|
`objdump' Architecture
|
----------------------
|
----------------------
|
|
|
Ways to specify:
|
Ways to specify:
|
|
|
1. command line option: `-m' or `--architecture'
|
1. command line option: `-m' or `--architecture'
|
|
|
2. deduced from the input file
|
2. deduced from the input file
|
|
|
`objcopy', `nm', `size', `strings' Architecture
|
`objcopy', `nm', `size', `strings' Architecture
|
-----------------------------------------------
|
-----------------------------------------------
|
|
|
Ways to specify:
|
Ways to specify:
|
|
|
1. deduced from the input file
|
1. deduced from the input file
|
|
|
|
|
File: binutils.info, Node: Reporting Bugs, Next: GNU Free Documentation License, Prev: Selecting the Target System, Up: Top
|
File: binutils.info, Node: Reporting Bugs, Next: GNU Free Documentation License, Prev: Selecting the Target System, Up: Top
|
|
|
18 Reporting Bugs
|
18 Reporting Bugs
|
*****************
|
*****************
|
|
|
Your bug reports play an essential role in making the binary utilities
|
Your bug reports play an essential role in making the binary utilities
|
reliable.
|
reliable.
|
|
|
Reporting a bug may help you by bringing a solution to your problem,
|
Reporting a bug may help you by bringing a solution to your problem,
|
or it may not. But in any case the principal function of a bug report
|
or it may not. But in any case the principal function of a bug report
|
is to help the entire community by making the next version of the binary
|
is to help the entire community by making the next version of the binary
|
utilities work better. Bug reports are your contribution to their
|
utilities work better. Bug reports are your contribution to their
|
maintenance.
|
maintenance.
|
|
|
In order for a bug report to serve its purpose, you must include the
|
In order for a bug report to serve its purpose, you must include the
|
information that enables us to fix the bug.
|
information that enables us to fix the bug.
|
|
|
* Menu:
|
* Menu:
|
|
|
* Bug Criteria:: Have you found a bug?
|
* Bug Criteria:: Have you found a bug?
|
* Bug Reporting:: How to report bugs
|
* Bug Reporting:: How to report bugs
|
|
|
|
|
File: binutils.info, Node: Bug Criteria, Next: Bug Reporting, Up: Reporting Bugs
|
File: binutils.info, Node: Bug Criteria, Next: Bug Reporting, Up: Reporting Bugs
|
|
|
18.1 Have You Found a Bug?
|
18.1 Have You Found a Bug?
|
==========================
|
==========================
|
|
|
If you are not sure whether you have found a bug, here are some
|
If you are not sure whether you have found a bug, here are some
|
guidelines:
|
guidelines:
|
|
|
* If a binary utility gets a fatal signal, for any input whatever,
|
* If a binary utility gets a fatal signal, for any input whatever,
|
that is a bug. Reliable utilities never crash.
|
that is a bug. Reliable utilities never crash.
|
|
|
* If a binary utility produces an error message for valid input,
|
* If a binary utility produces an error message for valid input,
|
that is a bug.
|
that is a bug.
|
|
|
* If you are an experienced user of binary utilities, your
|
* If you are an experienced user of binary utilities, your
|
suggestions for improvement are welcome in any case.
|
suggestions for improvement are welcome in any case.
|
|
|
|
|
File: binutils.info, Node: Bug Reporting, Prev: Bug Criteria, Up: Reporting Bugs
|
File: binutils.info, Node: Bug Reporting, Prev: Bug Criteria, Up: Reporting Bugs
|
|
|
18.2 How to Report Bugs
|
18.2 How to Report Bugs
|
=======================
|
=======================
|
|
|
A number of companies and individuals offer support for GNU products.
|
A number of companies and individuals offer support for GNU products.
|
If you obtained the binary utilities from a support organization, we
|
If you obtained the binary utilities from a support organization, we
|
recommend you contact that organization first.
|
recommend you contact that organization first.
|
|
|
You can find contact information for many support companies and
|
You can find contact information for many support companies and
|
individuals in the file `etc/SERVICE' in the GNU Emacs distribution.
|
individuals in the file `etc/SERVICE' in the GNU Emacs distribution.
|
|
|
In any event, we also recommend that you send bug reports for the
|
In any event, we also recommend that you send bug reports for the
|
binary utilities to `http://www.sourceware.org/bugzilla/'.
|
binary utilities to `http://www.sourceware.org/bugzilla/'.
|
|
|
The fundamental principle of reporting bugs usefully is this:
|
The fundamental principle of reporting bugs usefully is this:
|
*report all the facts*. If you are not sure whether to state a fact or
|
*report all the facts*. If you are not sure whether to state a fact or
|
leave it out, state it!
|
leave it out, state it!
|
|
|
Often people omit facts because they think they know what causes the
|
Often people omit facts because they think they know what causes the
|
problem and assume that some details do not matter. Thus, you might
|
problem and assume that some details do not matter. Thus, you might
|
assume that the name of a file you use in an example does not matter.
|
assume that the name of a file you use in an example does not matter.
|
Well, probably it does not, but one cannot be sure. Perhaps the bug is
|
Well, probably it does not, but one cannot be sure. Perhaps the bug is
|
a stray memory reference which happens to fetch from the location where
|
a stray memory reference which happens to fetch from the location where
|
that pathname is stored in memory; perhaps, if the pathname were
|
that pathname is stored in memory; perhaps, if the pathname were
|
different, the contents of that location would fool the utility into
|
different, the contents of that location would fool the utility into
|
doing the right thing despite the bug. Play it safe and give a
|
doing the right thing despite the bug. Play it safe and give a
|
specific, complete example. That is the easiest thing for you to do,
|
specific, complete example. That is the easiest thing for you to do,
|
and the most helpful.
|
and the most helpful.
|
|
|
Keep in mind that the purpose of a bug report is to enable us to fix
|
Keep in mind that the purpose of a bug report is to enable us to fix
|
the bug if it is new to us. Therefore, always write your bug reports
|
the bug if it is new to us. Therefore, always write your bug reports
|
on the assumption that the bug has not been reported previously.
|
on the assumption that the bug has not been reported previously.
|
|
|
Sometimes people give a few sketchy facts and ask, "Does this ring a
|
Sometimes people give a few sketchy facts and ask, "Does this ring a
|
bell?" This cannot help us fix a bug, so it is basically useless. We
|
bell?" This cannot help us fix a bug, so it is basically useless. We
|
respond by asking for enough details to enable us to investigate. You
|
respond by asking for enough details to enable us to investigate. You
|
might as well expedite matters by sending them to begin with.
|
might as well expedite matters by sending them to begin with.
|
|
|
To enable us to fix the bug, you should include all these things:
|
To enable us to fix the bug, you should include all these things:
|
|
|
* The version of the utility. Each utility announces it if you
|
* The version of the utility. Each utility announces it if you
|
start it with the `--version' argument.
|
start it with the `--version' argument.
|
|
|
Without this, we will not know whether there is any point in
|
Without this, we will not know whether there is any point in
|
looking for the bug in the current version of the binary utilities.
|
looking for the bug in the current version of the binary utilities.
|
|
|
* Any patches you may have applied to the source, including any
|
* Any patches you may have applied to the source, including any
|
patches made to the `BFD' library.
|
patches made to the `BFD' library.
|
|
|
* The type of machine you are using, and the operating system name
|
* The type of machine you are using, and the operating system name
|
and version number.
|
and version number.
|
|
|
* What compiler (and its version) was used to compile the
|
* What compiler (and its version) was used to compile the
|
utilities--e.g. "`gcc-2.7'".
|
utilities--e.g. "`gcc-2.7'".
|
|
|
* The command arguments you gave the utility to observe the bug. To
|
* The command arguments you gave the utility to observe the bug. To
|
guarantee you will not omit something important, list them all. A
|
guarantee you will not omit something important, list them all. A
|
copy of the Makefile (or the output from make) is sufficient.
|
copy of the Makefile (or the output from make) is sufficient.
|
|
|
If we were to try to guess the arguments, we would probably guess
|
If we were to try to guess the arguments, we would probably guess
|
wrong and then we might not encounter the bug.
|
wrong and then we might not encounter the bug.
|
|
|
* A complete input file, or set of input files, that will reproduce
|
* A complete input file, or set of input files, that will reproduce
|
the bug. If the utility is reading an object file or files, then
|
the bug. If the utility is reading an object file or files, then
|
it is generally most helpful to send the actual object files.
|
it is generally most helpful to send the actual object files.
|
|
|
If the source files were produced exclusively using GNU programs
|
If the source files were produced exclusively using GNU programs
|
(e.g., `gcc', `gas', and/or the GNU `ld'), then it may be OK to
|
(e.g., `gcc', `gas', and/or the GNU `ld'), then it may be OK to
|
send the source files rather than the object files. In this case,
|
send the source files rather than the object files. In this case,
|
be sure to say exactly what version of `gcc', or whatever, was
|
be sure to say exactly what version of `gcc', or whatever, was
|
used to produce the object files. Also say how `gcc', or
|
used to produce the object files. Also say how `gcc', or
|
whatever, was configured.
|
whatever, was configured.
|
|
|
* A description of what behavior you observe that you believe is
|
* A description of what behavior you observe that you believe is
|
incorrect. For example, "It gets a fatal signal."
|
incorrect. For example, "It gets a fatal signal."
|
|
|
Of course, if the bug is that the utility gets a fatal signal,
|
Of course, if the bug is that the utility gets a fatal signal,
|
then we will certainly notice it. But if the bug is incorrect
|
then we will certainly notice it. But if the bug is incorrect
|
output, we might not notice unless it is glaringly wrong. You
|
output, we might not notice unless it is glaringly wrong. You
|
might as well not give us a chance to make a mistake.
|
might as well not give us a chance to make a mistake.
|
|
|
Even if the problem you experience is a fatal signal, you should
|
Even if the problem you experience is a fatal signal, you should
|
still say so explicitly. Suppose something strange is going on,
|
still say so explicitly. Suppose something strange is going on,
|
such as your copy of the utility is out of sync, or you have
|
such as your copy of the utility is out of sync, or you have
|
encountered a bug in the C library on your system. (This has
|
encountered a bug in the C library on your system. (This has
|
happened!) Your copy might crash and ours would not. If you told
|
happened!) Your copy might crash and ours would not. If you told
|
us to expect a crash, then when ours fails to crash, we would know
|
us to expect a crash, then when ours fails to crash, we would know
|
that the bug was not happening for us. If you had not told us to
|
that the bug was not happening for us. If you had not told us to
|
expect a crash, then we would not be able to draw any conclusion
|
expect a crash, then we would not be able to draw any conclusion
|
from our observations.
|
from our observations.
|
|
|
* If you wish to suggest changes to the source, send us context
|
* If you wish to suggest changes to the source, send us context
|
diffs, as generated by `diff' with the `-u', `-c', or `-p' option.
|
diffs, as generated by `diff' with the `-u', `-c', or `-p' option.
|
Always send diffs from the old file to the new file. If you wish
|
Always send diffs from the old file to the new file. If you wish
|
to discuss something in the `ld' source, refer to it by context,
|
to discuss something in the `ld' source, refer to it by context,
|
not by line number.
|
not by line number.
|
|
|
The line numbers in our development sources will not match those
|
The line numbers in our development sources will not match those
|
in your sources. Your line numbers would convey no useful
|
in your sources. Your line numbers would convey no useful
|
information to us.
|
information to us.
|
|
|
Here are some things that are not necessary:
|
Here are some things that are not necessary:
|
|
|
* A description of the envelope of the bug.
|
* A description of the envelope of the bug.
|
|
|
Often people who encounter a bug spend a lot of time investigating
|
Often people who encounter a bug spend a lot of time investigating
|
which changes to the input file will make the bug go away and which
|
which changes to the input file will make the bug go away and which
|
changes will not affect it.
|
changes will not affect it.
|
|
|
This is often time consuming and not very useful, because the way
|
This is often time consuming and not very useful, because the way
|
we will find the bug is by running a single example under the
|
we will find the bug is by running a single example under the
|
debugger with breakpoints, not by pure deduction from a series of
|
debugger with breakpoints, not by pure deduction from a series of
|
examples. We recommend that you save your time for something else.
|
examples. We recommend that you save your time for something else.
|
|
|
Of course, if you can find a simpler example to report _instead_
|
Of course, if you can find a simpler example to report _instead_
|
of the original one, that is a convenience for us. Errors in the
|
of the original one, that is a convenience for us. Errors in the
|
output will be easier to spot, running under the debugger will take
|
output will be easier to spot, running under the debugger will take
|
less time, and so on.
|
less time, and so on.
|
|
|
However, simplification is not vital; if you do not want to do
|
However, simplification is not vital; if you do not want to do
|
this, report the bug anyway and send us the entire test case you
|
this, report the bug anyway and send us the entire test case you
|
used.
|
used.
|
|
|
* A patch for the bug.
|
* A patch for the bug.
|
|
|
A patch for the bug does help us if it is a good one. But do not
|
A patch for the bug does help us if it is a good one. But do not
|
omit the necessary information, such as the test case, on the
|
omit the necessary information, such as the test case, on the
|
assumption that a patch is all we need. We might see problems
|
assumption that a patch is all we need. We might see problems
|
with your patch and decide to fix the problem another way, or we
|
with your patch and decide to fix the problem another way, or we
|
might not understand it at all.
|
might not understand it at all.
|
|
|
Sometimes with programs as complicated as the binary utilities it
|
Sometimes with programs as complicated as the binary utilities it
|
is very hard to construct an example that will make the program
|
is very hard to construct an example that will make the program
|
follow a certain path through the code. If you do not send us the
|
follow a certain path through the code. If you do not send us the
|
example, we will not be able to construct one, so we will not be
|
example, we will not be able to construct one, so we will not be
|
able to verify that the bug is fixed.
|
able to verify that the bug is fixed.
|
|
|
And if we cannot understand what bug you are trying to fix, or why
|
And if we cannot understand what bug you are trying to fix, or why
|
your patch should be an improvement, we will not install it. A
|
your patch should be an improvement, we will not install it. A
|
test case will help us to understand.
|
test case will help us to understand.
|
|
|
* A guess about what the bug is or what it depends on.
|
* A guess about what the bug is or what it depends on.
|
|
|
Such guesses are usually wrong. Even we cannot guess right about
|
Such guesses are usually wrong. Even we cannot guess right about
|
such things without first using the debugger to find the facts.
|
such things without first using the debugger to find the facts.
|
|
|
|
|
File: binutils.info, Node: GNU Free Documentation License, Next: Binutils Index, Prev: Reporting Bugs, Up: Top
|
File: binutils.info, Node: GNU Free Documentation License, Next: Binutils Index, Prev: Reporting Bugs, Up: Top
|
|
|
Appendix A GNU Free Documentation License
|
Appendix A GNU Free Documentation License
|
*****************************************
|
*****************************************
|
|
|
Version 1.2, November 2002
|
Version 1.2, November 2002
|
|
|
Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
|
Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
|
51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
|
51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
|
|
|
Everyone is permitted to copy and distribute verbatim copies
|
Everyone is permitted to copy and distribute verbatim copies
|
of this license document, but changing it is not allowed.
|
of this license document, but changing it is not allowed.
|
|
|
0. PREAMBLE
|
0. PREAMBLE
|
|
|
The purpose of this License is to make a manual, textbook, or other
|
The purpose of this License is to make a manual, textbook, or other
|
functional and useful document "free" in the sense of freedom: to
|
functional and useful document "free" in the sense of freedom: to
|
assure everyone the effective freedom to copy and redistribute it,
|
assure everyone the effective freedom to copy and redistribute it,
|
with or without modifying it, either commercially or
|
with or without modifying it, either commercially or
|
noncommercially. Secondarily, this License preserves for the
|
noncommercially. Secondarily, this License preserves for the
|
author and publisher a way to get credit for their work, while not
|
author and publisher a way to get credit for their work, while not
|
being considered responsible for modifications made by others.
|
being considered responsible for modifications made by others.
|
|
|
This License is a kind of "copyleft", which means that derivative
|
This License is a kind of "copyleft", which means that derivative
|
works of the document must themselves be free in the same sense.
|
works of the document must themselves be free in the same sense.
|
It complements the GNU General Public License, which is a copyleft
|
It complements the GNU General Public License, which is a copyleft
|
license designed for free software.
|
license designed for free software.
|
|
|
We have designed this License in order to use it for manuals for
|
We have designed this License in order to use it for manuals for
|
free software, because free software needs free documentation: a
|
free software, because free software needs free documentation: a
|
free program should come with manuals providing the same freedoms
|
free program should come with manuals providing the same freedoms
|
that the software does. But this License is not limited to
|
that the software does. But this License is not limited to
|
software manuals; it can be used for any textual work, regardless
|
software manuals; it can be used for any textual work, regardless
|
of subject matter or whether it is published as a printed book.
|
of subject matter or whether it is published as a printed book.
|
We recommend this License principally for works whose purpose is
|
We recommend this License principally for works whose purpose is
|
instruction or reference.
|
instruction or reference.
|
|
|
1. APPLICABILITY AND DEFINITIONS
|
1. APPLICABILITY AND DEFINITIONS
|
|
|
This License applies to any manual or other work, in any medium,
|
This License applies to any manual or other work, in any medium,
|
that contains a notice placed by the copyright holder saying it
|
that contains a notice placed by the copyright holder saying it
|
can be distributed under the terms of this License. Such a notice
|
can be distributed under the terms of this License. Such a notice
|
grants a world-wide, royalty-free license, unlimited in duration,
|
grants a world-wide, royalty-free license, unlimited in duration,
|
to use that work under the conditions stated herein. The
|
to use that work under the conditions stated herein. The
|
"Document", below, refers to any such manual or work. Any member
|
"Document", below, refers to any such manual or work. Any member
|
of the public is a licensee, and is addressed as "you". You
|
of the public is a licensee, and is addressed as "you". You
|
accept the license if you copy, modify or distribute the work in a
|
accept the license if you copy, modify or distribute the work in a
|
way requiring permission under copyright law.
|
way requiring permission under copyright law.
|
|
|
A "Modified Version" of the Document means any work containing the
|
A "Modified Version" of the Document means any work containing the
|
Document or a portion of it, either copied verbatim, or with
|
Document or a portion of it, either copied verbatim, or with
|
modifications and/or translated into another language.
|
modifications and/or translated into another language.
|
|
|
A "Secondary Section" is a named appendix or a front-matter section
|
A "Secondary Section" is a named appendix or a front-matter section
|
of the Document that deals exclusively with the relationship of the
|
of the Document that deals exclusively with the relationship of the
|
publishers or authors of the Document to the Document's overall
|
publishers or authors of the Document to the Document's overall
|
subject (or to related matters) and contains nothing that could
|
subject (or to related matters) and contains nothing that could
|
fall directly within that overall subject. (Thus, if the Document
|
fall directly within that overall subject. (Thus, if the Document
|
is in part a textbook of mathematics, a Secondary Section may not
|
is in part a textbook of mathematics, a Secondary Section may not
|
explain any mathematics.) The relationship could be a matter of
|
explain any mathematics.) The relationship could be a matter of
|
historical connection with the subject or with related matters, or
|
historical connection with the subject or with related matters, or
|
of legal, commercial, philosophical, ethical or political position
|
of legal, commercial, philosophical, ethical or political position
|
regarding them.
|
regarding them.
|
|
|
The "Invariant Sections" are certain Secondary Sections whose
|
The "Invariant Sections" are certain Secondary Sections whose
|
titles are designated, as being those of Invariant Sections, in
|
titles are designated, as being those of Invariant Sections, in
|
the notice that says that the Document is released under this
|
the notice that says that the Document is released under this
|
License. If a section does not fit the above definition of
|
License. If a section does not fit the above definition of
|
Secondary then it is not allowed to be designated as Invariant.
|
Secondary then it is not allowed to be designated as Invariant.
|
The Document may contain zero Invariant Sections. If the Document
|
The Document may contain zero Invariant Sections. If the Document
|
does not identify any Invariant Sections then there are none.
|
does not identify any Invariant Sections then there are none.
|
|
|
The "Cover Texts" are certain short passages of text that are
|
The "Cover Texts" are certain short passages of text that are
|
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
|
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
|
that says that the Document is released under this License. A
|
that says that the Document is released under this License. A
|
Front-Cover Text may be at most 5 words, and a Back-Cover Text may
|
Front-Cover Text may be at most 5 words, and a Back-Cover Text may
|
be at most 25 words.
|
be at most 25 words.
|
|
|
A "Transparent" copy of the Document means a machine-readable copy,
|
A "Transparent" copy of the Document means a machine-readable copy,
|
represented in a format whose specification is available to the
|
represented in a format whose specification is available to the
|
general public, that is suitable for revising the document
|
general public, that is suitable for revising the document
|
straightforwardly with generic text editors or (for images
|
straightforwardly with generic text editors or (for images
|
composed of pixels) generic paint programs or (for drawings) some
|
composed of pixels) generic paint programs or (for drawings) some
|
widely available drawing editor, and that is suitable for input to
|
widely available drawing editor, and that is suitable for input to
|
text formatters or for automatic translation to a variety of
|
text formatters or for automatic translation to a variety of
|
formats suitable for input to text formatters. A copy made in an
|
formats suitable for input to text formatters. A copy made in an
|
otherwise Transparent file format whose markup, or absence of
|
otherwise Transparent file format whose markup, or absence of
|
markup, has been arranged to thwart or discourage subsequent
|
markup, has been arranged to thwart or discourage subsequent
|
modification by readers is not Transparent. An image format is
|
modification by readers is not Transparent. An image format is
|
not Transparent if used for any substantial amount of text. A
|
not Transparent if used for any substantial amount of text. A
|
copy that is not "Transparent" is called "Opaque".
|
copy that is not "Transparent" is called "Opaque".
|
|
|
Examples of suitable formats for Transparent copies include plain
|
Examples of suitable formats for Transparent copies include plain
|
ASCII without markup, Texinfo input format, LaTeX input format,
|
ASCII without markup, Texinfo input format, LaTeX input format,
|
SGML or XML using a publicly available DTD, and
|
SGML or XML using a publicly available DTD, and
|
standard-conforming simple HTML, PostScript or PDF designed for
|
standard-conforming simple HTML, PostScript or PDF designed for
|
human modification. Examples of transparent image formats include
|
human modification. Examples of transparent image formats include
|
PNG, XCF and JPG. Opaque formats include proprietary formats that
|
PNG, XCF and JPG. Opaque formats include proprietary formats that
|
can be read and edited only by proprietary word processors, SGML or
|
can be read and edited only by proprietary word processors, SGML or
|
XML for which the DTD and/or processing tools are not generally
|
XML for which the DTD and/or processing tools are not generally
|
available, and the machine-generated HTML, PostScript or PDF
|
available, and the machine-generated HTML, PostScript or PDF
|
produced by some word processors for output purposes only.
|
produced by some word processors for output purposes only.
|
|
|
The "Title Page" means, for a printed book, the title page itself,
|
The "Title Page" means, for a printed book, the title page itself,
|
plus such following pages as are needed to hold, legibly, the
|
plus such following pages as are needed to hold, legibly, the
|
material this License requires to appear in the title page. For
|
material this License requires to appear in the title page. For
|
works in formats which do not have any title page as such, "Title
|
works in formats which do not have any title page as such, "Title
|
Page" means the text near the most prominent appearance of the
|
Page" means the text near the most prominent appearance of the
|
work's title, preceding the beginning of the body of the text.
|
work's title, preceding the beginning of the body of the text.
|
|
|
A section "Entitled XYZ" means a named subunit of the Document
|
A section "Entitled XYZ" means a named subunit of the Document
|
whose title either is precisely XYZ or contains XYZ in parentheses
|
whose title either is precisely XYZ or contains XYZ in parentheses
|
following text that translates XYZ in another language. (Here XYZ
|
following text that translates XYZ in another language. (Here XYZ
|
stands for a specific section name mentioned below, such as
|
stands for a specific section name mentioned below, such as
|
"Acknowledgements", "Dedications", "Endorsements", or "History".)
|
"Acknowledgements", "Dedications", "Endorsements", or "History".)
|
To "Preserve the Title" of such a section when you modify the
|
To "Preserve the Title" of such a section when you modify the
|
Document means that it remains a section "Entitled XYZ" according
|
Document means that it remains a section "Entitled XYZ" according
|
to this definition.
|
to this definition.
|
|
|
The Document may include Warranty Disclaimers next to the notice
|
The Document may include Warranty Disclaimers next to the notice
|
which states that this License applies to the Document. These
|
which states that this License applies to the Document. These
|
Warranty Disclaimers are considered to be included by reference in
|
Warranty Disclaimers are considered to be included by reference in
|
this License, but only as regards disclaiming warranties: any other
|
this License, but only as regards disclaiming warranties: any other
|
implication that these Warranty Disclaimers may have is void and
|
implication that these Warranty Disclaimers may have is void and
|
has no effect on the meaning of this License.
|
has no effect on the meaning of this License.
|
|
|
2. VERBATIM COPYING
|
2. VERBATIM COPYING
|
|
|
You may copy and distribute the Document in any medium, either
|
You may copy and distribute the Document in any medium, either
|
commercially or noncommercially, provided that this License, the
|
commercially or noncommercially, provided that this License, the
|
copyright notices, and the license notice saying this License
|
copyright notices, and the license notice saying this License
|
applies to the Document are reproduced in all copies, and that you
|
applies to the Document are reproduced in all copies, and that you
|
add no other conditions whatsoever to those of this License. You
|
add no other conditions whatsoever to those of this License. You
|
may not use technical measures to obstruct or control the reading
|
may not use technical measures to obstruct or control the reading
|
or further copying of the copies you make or distribute. However,
|
or further copying of the copies you make or distribute. However,
|
you may accept compensation in exchange for copies. If you
|
you may accept compensation in exchange for copies. If you
|
distribute a large enough number of copies you must also follow
|
distribute a large enough number of copies you must also follow
|
the conditions in section 3.
|
the conditions in section 3.
|
|
|
You may also lend copies, under the same conditions stated above,
|
You may also lend copies, under the same conditions stated above,
|
and you may publicly display copies.
|
and you may publicly display copies.
|
|
|
3. COPYING IN QUANTITY
|
3. COPYING IN QUANTITY
|
|
|
If you publish printed copies (or copies in media that commonly
|
If you publish printed copies (or copies in media that commonly
|
have printed covers) of the Document, numbering more than 100, and
|
have printed covers) of the Document, numbering more than 100, and
|
the Document's license notice requires Cover Texts, you must
|
the Document's license notice requires Cover Texts, you must
|
enclose the copies in covers that carry, clearly and legibly, all
|
enclose the copies in covers that carry, clearly and legibly, all
|
these Cover Texts: Front-Cover Texts on the front cover, and
|
these Cover Texts: Front-Cover Texts on the front cover, and
|
Back-Cover Texts on the back cover. Both covers must also clearly
|
Back-Cover Texts on the back cover. Both covers must also clearly
|
and legibly identify you as the publisher of these copies. The
|
and legibly identify you as the publisher of these copies. The
|
front cover must present the full title with all words of the
|
front cover must present the full title with all words of the
|
title equally prominent and visible. You may add other material
|
title equally prominent and visible. You may add other material
|
on the covers in addition. Copying with changes limited to the
|
on the covers in addition. Copying with changes limited to the
|
covers, as long as they preserve the title of the Document and
|
covers, as long as they preserve the title of the Document and
|
satisfy these conditions, can be treated as verbatim copying in
|
satisfy these conditions, can be treated as verbatim copying in
|
other respects.
|
other respects.
|
|
|
If the required texts for either cover are too voluminous to fit
|
If the required texts for either cover are too voluminous to fit
|
legibly, you should put the first ones listed (as many as fit
|
legibly, you should put the first ones listed (as many as fit
|
reasonably) on the actual cover, and continue the rest onto
|
reasonably) on the actual cover, and continue the rest onto
|
adjacent pages.
|
adjacent pages.
|
|
|
If you publish or distribute Opaque copies of the Document
|
If you publish or distribute Opaque copies of the Document
|
numbering more than 100, you must either include a
|
numbering more than 100, you must either include a
|
machine-readable Transparent copy along with each Opaque copy, or
|
machine-readable Transparent copy along with each Opaque copy, or
|
state in or with each Opaque copy a computer-network location from
|
state in or with each Opaque copy a computer-network location from
|
which the general network-using public has access to download
|
which the general network-using public has access to download
|
using public-standard network protocols a complete Transparent
|
using public-standard network protocols a complete Transparent
|
copy of the Document, free of added material. If you use the
|
copy of the Document, free of added material. If you use the
|
latter option, you must take reasonably prudent steps, when you
|
latter option, you must take reasonably prudent steps, when you
|
begin distribution of Opaque copies in quantity, to ensure that
|
begin distribution of Opaque copies in quantity, to ensure that
|
this Transparent copy will remain thus accessible at the stated
|
this Transparent copy will remain thus accessible at the stated
|
location until at least one year after the last time you
|
location until at least one year after the last time you
|
distribute an Opaque copy (directly or through your agents or
|
distribute an Opaque copy (directly or through your agents or
|
retailers) of that edition to the public.
|
retailers) of that edition to the public.
|
|
|
It is requested, but not required, that you contact the authors of
|
It is requested, but not required, that you contact the authors of
|
the Document well before redistributing any large number of
|
the Document well before redistributing any large number of
|
copies, to give them a chance to provide you with an updated
|
copies, to give them a chance to provide you with an updated
|
version of the Document.
|
version of the Document.
|
|
|
4. MODIFICATIONS
|
4. MODIFICATIONS
|
|
|
You may copy and distribute a Modified Version of the Document
|
You may copy and distribute a Modified Version of the Document
|
under the conditions of sections 2 and 3 above, provided that you
|
under the conditions of sections 2 and 3 above, provided that you
|
release the Modified Version under precisely this License, with
|
release the Modified Version under precisely this License, with
|
the Modified Version filling the role of the Document, thus
|
the Modified Version filling the role of the Document, thus
|
licensing distribution and modification of the Modified Version to
|
licensing distribution and modification of the Modified Version to
|
whoever possesses a copy of it. In addition, you must do these
|
whoever possesses a copy of it. In addition, you must do these
|
things in the Modified Version:
|
things in the Modified Version:
|
|
|
A. Use in the Title Page (and on the covers, if any) a title
|
A. Use in the Title Page (and on the covers, if any) a title
|
distinct from that of the Document, and from those of
|
distinct from that of the Document, and from those of
|
previous versions (which should, if there were any, be listed
|
previous versions (which should, if there were any, be listed
|
in the History section of the Document). You may use the
|
in the History section of the Document). You may use the
|
same title as a previous version if the original publisher of
|
same title as a previous version if the original publisher of
|
that version gives permission.
|
that version gives permission.
|
|
|
B. List on the Title Page, as authors, one or more persons or
|
B. List on the Title Page, as authors, one or more persons or
|
entities responsible for authorship of the modifications in
|
entities responsible for authorship of the modifications in
|
the Modified Version, together with at least five of the
|
the Modified Version, together with at least five of the
|
principal authors of the Document (all of its principal
|
principal authors of the Document (all of its principal
|
authors, if it has fewer than five), unless they release you
|
authors, if it has fewer than five), unless they release you
|
from this requirement.
|
from this requirement.
|
|
|
C. State on the Title page the name of the publisher of the
|
C. State on the Title page the name of the publisher of the
|
Modified Version, as the publisher.
|
Modified Version, as the publisher.
|
|
|
D. Preserve all the copyright notices of the Document.
|
D. Preserve all the copyright notices of the Document.
|
|
|
E. Add an appropriate copyright notice for your modifications
|
E. Add an appropriate copyright notice for your modifications
|
adjacent to the other copyright notices.
|
adjacent to the other copyright notices.
|
|
|
F. Include, immediately after the copyright notices, a license
|
F. Include, immediately after the copyright notices, a license
|
notice giving the public permission to use the Modified
|
notice giving the public permission to use the Modified
|
Version under the terms of this License, in the form shown in
|
Version under the terms of this License, in the form shown in
|
the Addendum below.
|
the Addendum below.
|
|
|
G. Preserve in that license notice the full lists of Invariant
|
G. Preserve in that license notice the full lists of Invariant
|
Sections and required Cover Texts given in the Document's
|
Sections and required Cover Texts given in the Document's
|
license notice.
|
license notice.
|
|
|
H. Include an unaltered copy of this License.
|
H. Include an unaltered copy of this License.
|
|
|
I. Preserve the section Entitled "History", Preserve its Title,
|
I. Preserve the section Entitled "History", Preserve its Title,
|
and add to it an item stating at least the title, year, new
|
and add to it an item stating at least the title, year, new
|
authors, and publisher of the Modified Version as given on
|
authors, and publisher of the Modified Version as given on
|
the Title Page. If there is no section Entitled "History" in
|
the Title Page. If there is no section Entitled "History" in
|
the Document, create one stating the title, year, authors,
|
the Document, create one stating the title, year, authors,
|
and publisher of the Document as given on its Title Page,
|
and publisher of the Document as given on its Title Page,
|
then add an item describing the Modified Version as stated in
|
then add an item describing the Modified Version as stated in
|
the previous sentence.
|
the previous sentence.
|
|
|
J. Preserve the network location, if any, given in the Document
|
J. Preserve the network location, if any, given in the Document
|
for public access to a Transparent copy of the Document, and
|
for public access to a Transparent copy of the Document, and
|
likewise the network locations given in the Document for
|
likewise the network locations given in the Document for
|
previous versions it was based on. These may be placed in
|
previous versions it was based on. These may be placed in
|
the "History" section. You may omit a network location for a
|
the "History" section. You may omit a network location for a
|
work that was published at least four years before the
|
work that was published at least four years before the
|
Document itself, or if the original publisher of the version
|
Document itself, or if the original publisher of the version
|
it refers to gives permission.
|
it refers to gives permission.
|
|
|
K. For any section Entitled "Acknowledgements" or "Dedications",
|
K. For any section Entitled "Acknowledgements" or "Dedications",
|
Preserve the Title of the section, and preserve in the
|
Preserve the Title of the section, and preserve in the
|
section all the substance and tone of each of the contributor
|
section all the substance and tone of each of the contributor
|
acknowledgements and/or dedications given therein.
|
acknowledgements and/or dedications given therein.
|
|
|
L. Preserve all the Invariant Sections of the Document,
|
L. Preserve all the Invariant Sections of the Document,
|
unaltered in their text and in their titles. Section numbers
|
unaltered in their text and in their titles. Section numbers
|
or the equivalent are not considered part of the section
|
or the equivalent are not considered part of the section
|
titles.
|
titles.
|
|
|
M. Delete any section Entitled "Endorsements". Such a section
|
M. Delete any section Entitled "Endorsements". Such a section
|
may not be included in the Modified Version.
|
may not be included in the Modified Version.
|
|
|
N. Do not retitle any existing section to be Entitled
|
N. Do not retitle any existing section to be Entitled
|
"Endorsements" or to conflict in title with any Invariant
|
"Endorsements" or to conflict in title with any Invariant
|
Section.
|
Section.
|
|
|
O. Preserve any Warranty Disclaimers.
|
O. Preserve any Warranty Disclaimers.
|
|
|
If the Modified Version includes new front-matter sections or
|
If the Modified Version includes new front-matter sections or
|
appendices that qualify as Secondary Sections and contain no
|
appendices that qualify as Secondary Sections and contain no
|
material copied from the Document, you may at your option
|
material copied from the Document, you may at your option
|
designate some or all of these sections as invariant. To do this,
|
designate some or all of these sections as invariant. To do this,
|
add their titles to the list of Invariant Sections in the Modified
|
add their titles to the list of Invariant Sections in the Modified
|
Version's license notice. These titles must be distinct from any
|
Version's license notice. These titles must be distinct from any
|
other section titles.
|
other section titles.
|
|
|
You may add a section Entitled "Endorsements", provided it contains
|
You may add a section Entitled "Endorsements", provided it contains
|
nothing but endorsements of your Modified Version by various
|
nothing but endorsements of your Modified Version by various
|
parties--for example, statements of peer review or that the text
|
parties--for example, statements of peer review or that the text
|
has been approved by an organization as the authoritative
|
has been approved by an organization as the authoritative
|
definition of a standard.
|
definition of a standard.
|
|
|
You may add a passage of up to five words as a Front-Cover Text,
|
You may add a passage of up to five words as a Front-Cover Text,
|
and a passage of up to 25 words as a Back-Cover Text, to the end
|
and a passage of up to 25 words as a Back-Cover Text, to the end
|
of the list of Cover Texts in the Modified Version. Only one
|
of the list of Cover Texts in the Modified Version. Only one
|
passage of Front-Cover Text and one of Back-Cover Text may be
|
passage of Front-Cover Text and one of Back-Cover Text may be
|
added by (or through arrangements made by) any one entity. If the
|
added by (or through arrangements made by) any one entity. If the
|
Document already includes a cover text for the same cover,
|
Document already includes a cover text for the same cover,
|
previously added by you or by arrangement made by the same entity
|
previously added by you or by arrangement made by the same entity
|
you are acting on behalf of, you may not add another; but you may
|
you are acting on behalf of, you may not add another; but you may
|
replace the old one, on explicit permission from the previous
|
replace the old one, on explicit permission from the previous
|
publisher that added the old one.
|
publisher that added the old one.
|
|
|
The author(s) and publisher(s) of the Document do not by this
|
The author(s) and publisher(s) of the Document do not by this
|
License give permission to use their names for publicity for or to
|
License give permission to use their names for publicity for or to
|
assert or imply endorsement of any Modified Version.
|
assert or imply endorsement of any Modified Version.
|
|
|
5. COMBINING DOCUMENTS
|
5. COMBINING DOCUMENTS
|
|
|
You may combine the Document with other documents released under
|
You may combine the Document with other documents released under
|
this License, under the terms defined in section 4 above for
|
this License, under the terms defined in section 4 above for
|
modified versions, provided that you include in the combination
|
modified versions, provided that you include in the combination
|
all of the Invariant Sections of all of the original documents,
|
all of the Invariant Sections of all of the original documents,
|
unmodified, and list them all as Invariant Sections of your
|
unmodified, and list them all as Invariant Sections of your
|
combined work in its license notice, and that you preserve all
|
combined work in its license notice, and that you preserve all
|
their Warranty Disclaimers.
|
their Warranty Disclaimers.
|
|
|
The combined work need only contain one copy of this License, and
|
The combined work need only contain one copy of this License, and
|
multiple identical Invariant Sections may be replaced with a single
|
multiple identical Invariant Sections may be replaced with a single
|
copy. If there are multiple Invariant Sections with the same name
|
copy. If there are multiple Invariant Sections with the same name
|
but different contents, make the title of each such section unique
|
but different contents, make the title of each such section unique
|
by adding at the end of it, in parentheses, the name of the
|
by adding at the end of it, in parentheses, the name of the
|
original author or publisher of that section if known, or else a
|
original author or publisher of that section if known, or else a
|
unique number. Make the same adjustment to the section titles in
|
unique number. Make the same adjustment to the section titles in
|
the list of Invariant Sections in the license notice of the
|
the list of Invariant Sections in the license notice of the
|
combined work.
|
combined work.
|
|
|
In the combination, you must combine any sections Entitled
|
In the combination, you must combine any sections Entitled
|
"History" in the various original documents, forming one section
|
"History" in the various original documents, forming one section
|
Entitled "History"; likewise combine any sections Entitled
|
Entitled "History"; likewise combine any sections Entitled
|
"Acknowledgements", and any sections Entitled "Dedications". You
|
"Acknowledgements", and any sections Entitled "Dedications". You
|
must delete all sections Entitled "Endorsements."
|
must delete all sections Entitled "Endorsements."
|
|
|
6. COLLECTIONS OF DOCUMENTS
|
6. COLLECTIONS OF DOCUMENTS
|
|
|
You may make a collection consisting of the Document and other
|
You may make a collection consisting of the Document and other
|
documents released under this License, and replace the individual
|
documents released under this License, and replace the individual
|
copies of this License in the various documents with a single copy
|
copies of this License in the various documents with a single copy
|
that is included in the collection, provided that you follow the
|
that is included in the collection, provided that you follow the
|
rules of this License for verbatim copying of each of the
|
rules of this License for verbatim copying of each of the
|
documents in all other respects.
|
documents in all other respects.
|
|
|
You may extract a single document from such a collection, and
|
You may extract a single document from such a collection, and
|
distribute it individually under this License, provided you insert
|
distribute it individually under this License, provided you insert
|
a copy of this License into the extracted document, and follow
|
a copy of this License into the extracted document, and follow
|
this License in all other respects regarding verbatim copying of
|
this License in all other respects regarding verbatim copying of
|
that document.
|
that document.
|
|
|
7. AGGREGATION WITH INDEPENDENT WORKS
|
7. AGGREGATION WITH INDEPENDENT WORKS
|
|
|
A compilation of the Document or its derivatives with other
|
A compilation of the Document or its derivatives with other
|
separate and independent documents or works, in or on a volume of
|
separate and independent documents or works, in or on a volume of
|
a storage or distribution medium, is called an "aggregate" if the
|
a storage or distribution medium, is called an "aggregate" if the
|
copyright resulting from the compilation is not used to limit the
|
copyright resulting from the compilation is not used to limit the
|
legal rights of the compilation's users beyond what the individual
|
legal rights of the compilation's users beyond what the individual
|
works permit. When the Document is included in an aggregate, this
|
works permit. When the Document is included in an aggregate, this
|
License does not apply to the other works in the aggregate which
|
License does not apply to the other works in the aggregate which
|
are not themselves derivative works of the Document.
|
are not themselves derivative works of the Document.
|
|
|
If the Cover Text requirement of section 3 is applicable to these
|
If the Cover Text requirement of section 3 is applicable to these
|
copies of the Document, then if the Document is less than one half
|
copies of the Document, then if the Document is less than one half
|
of the entire aggregate, the Document's Cover Texts may be placed
|
of the entire aggregate, the Document's Cover Texts may be placed
|
on covers that bracket the Document within the aggregate, or the
|
on covers that bracket the Document within the aggregate, or the
|
electronic equivalent of covers if the Document is in electronic
|
electronic equivalent of covers if the Document is in electronic
|
form. Otherwise they must appear on printed covers that bracket
|
form. Otherwise they must appear on printed covers that bracket
|
the whole aggregate.
|
the whole aggregate.
|
|
|
8. TRANSLATION
|
8. TRANSLATION
|
|
|
Translation is considered a kind of modification, so you may
|
Translation is considered a kind of modification, so you may
|
distribute translations of the Document under the terms of section
|
distribute translations of the Document under the terms of section
|
4. Replacing Invariant Sections with translations requires special
|
4. Replacing Invariant Sections with translations requires special
|
permission from their copyright holders, but you may include
|
permission from their copyright holders, but you may include
|
translations of some or all Invariant Sections in addition to the
|
translations of some or all Invariant Sections in addition to the
|
original versions of these Invariant Sections. You may include a
|
original versions of these Invariant Sections. You may include a
|
translation of this License, and all the license notices in the
|
translation of this License, and all the license notices in the
|
Document, and any Warranty Disclaimers, provided that you also
|
Document, and any Warranty Disclaimers, provided that you also
|
include the original English version of this License and the
|
include the original English version of this License and the
|
original versions of those notices and disclaimers. In case of a
|
original versions of those notices and disclaimers. In case of a
|
disagreement between the translation and the original version of
|
disagreement between the translation and the original version of
|
this License or a notice or disclaimer, the original version will
|
this License or a notice or disclaimer, the original version will
|
prevail.
|
prevail.
|
|
|
If a section in the Document is Entitled "Acknowledgements",
|
If a section in the Document is Entitled "Acknowledgements",
|
"Dedications", or "History", the requirement (section 4) to
|
"Dedications", or "History", the requirement (section 4) to
|
Preserve its Title (section 1) will typically require changing the
|
Preserve its Title (section 1) will typically require changing the
|
actual title.
|
actual title.
|
|
|
9. TERMINATION
|
9. TERMINATION
|
|
|
You may not copy, modify, sublicense, or distribute the Document
|
You may not copy, modify, sublicense, or distribute the Document
|
except as expressly provided for under this License. Any other
|
except as expressly provided for under this License. Any other
|
attempt to copy, modify, sublicense or distribute the Document is
|
attempt to copy, modify, sublicense or distribute the Document is
|
void, and will automatically terminate your rights under this
|
void, and will automatically terminate your rights under this
|
License. However, parties who have received copies, or rights,
|
License. However, parties who have received copies, or rights,
|
from you under this License will not have their licenses
|
from you under this License will not have their licenses
|
terminated so long as such parties remain in full compliance.
|
terminated so long as such parties remain in full compliance.
|
|
|
10. FUTURE REVISIONS OF THIS LICENSE
|
10. FUTURE REVISIONS OF THIS LICENSE
|
|
|
The Free Software Foundation may publish new, revised versions of
|
The Free Software Foundation may publish new, revised versions of
|
the GNU Free Documentation License from time to time. Such new
|
the GNU Free Documentation License from time to time. Such new
|
versions will be similar in spirit to the present version, but may
|
versions will be similar in spirit to the present version, but may
|
differ in detail to address new problems or concerns. See
|
differ in detail to address new problems or concerns. See
|
`http://www.gnu.org/copyleft/'.
|
`http://www.gnu.org/copyleft/'.
|
|
|
Each version of the License is given a distinguishing version
|
Each version of the License is given a distinguishing version
|
number. If the Document specifies that a particular numbered
|
number. If the Document specifies that a particular numbered
|
version of this License "or any later version" applies to it, you
|
version of this License "or any later version" applies to it, you
|
have the option of following the terms and conditions either of
|
have the option of following the terms and conditions either of
|
that specified version or of any later version that has been
|
that specified version or of any later version that has been
|
published (not as a draft) by the Free Software Foundation. If
|
published (not as a draft) by the Free Software Foundation. If
|
the Document does not specify a version number of this License,
|
the Document does not specify a version number of this License,
|
you may choose any version ever published (not as a draft) by the
|
you may choose any version ever published (not as a draft) by the
|
Free Software Foundation.
|
Free Software Foundation.
|
|
|
ADDENDUM: How to use this License for your documents
|
ADDENDUM: How to use this License for your documents
|
====================================================
|
====================================================
|
|
|
To use this License in a document you have written, include a copy of
|
To use this License in a document you have written, include a copy of
|
the License in the document and put the following copyright and license
|
the License in the document and put the following copyright and license
|
notices just after the title page:
|
notices just after the title page:
|
|
|
Copyright (C) YEAR YOUR NAME.
|
Copyright (C) YEAR YOUR NAME.
|
Permission is granted to copy, distribute and/or modify this document
|
Permission is granted to copy, distribute and/or modify this document
|
under the terms of the GNU Free Documentation License, Version 1.2
|
under the terms of the GNU Free Documentation License, Version 1.2
|
or any later version published by the Free Software Foundation;
|
or any later version published by the Free Software Foundation;
|
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
|
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
|
Texts. A copy of the license is included in the section entitled ``GNU
|
Texts. A copy of the license is included in the section entitled ``GNU
|
Free Documentation License''.
|
Free Documentation License''.
|
|
|
If you have Invariant Sections, Front-Cover Texts and Back-Cover
|
If you have Invariant Sections, Front-Cover Texts and Back-Cover
|
Texts, replace the "with...Texts." line with this:
|
Texts, replace the "with...Texts." line with this:
|
|
|
with the Invariant Sections being LIST THEIR TITLES, with
|
with the Invariant Sections being LIST THEIR TITLES, with
|
the Front-Cover Texts being LIST, and with the Back-Cover Texts
|
the Front-Cover Texts being LIST, and with the Back-Cover Texts
|
being LIST.
|
being LIST.
|
|
|
If you have Invariant Sections without Cover Texts, or some other
|
If you have Invariant Sections without Cover Texts, or some other
|
combination of the three, merge those two alternatives to suit the
|
combination of the three, merge those two alternatives to suit the
|
situation.
|
situation.
|
|
|
If your document contains nontrivial examples of program code, we
|
If your document contains nontrivial examples of program code, we
|
recommend releasing these examples in parallel under your choice of
|
recommend releasing these examples in parallel under your choice of
|
free software license, such as the GNU General Public License, to
|
free software license, such as the GNU General Public License, to
|
permit their use in free software.
|
permit their use in free software.
|
|
|
|
|
File: binutils.info, Node: Binutils Index, Prev: GNU Free Documentation License, Up: Top
|
File: binutils.info, Node: Binutils Index, Prev: GNU Free Documentation License, Up: Top
|
|
|
Binutils Index
|
Binutils Index
|
**************
|
**************
|
|
|
|