This brief manual contains documentation for the gnu binary utilities (GNU Binutils) version 2.30.52:
This document is distributed under the terms of the GNU Free Documentation License version 1.3. A copy of the license is included in the section entitled “GNU Free Documentation License”.
ar [-]p[mod] [--plugin name] [--target bfdname] [--output dirname] [relpos] [count] archive [member...] ar -M [ <mri-script ]
The gnu ar program creates, modifies, and extracts from archives. An archive is a single file holding a collection of other files in a structure that makes it possible to retrieve the original individual files (called members of the archive).
The original files' contents, mode (permissions), timestamp, owner, and group are preserved in the archive, and can be restored on extraction.
gnu ar can maintain archives whose members have names of any length; however, depending on how ar is configured on your system, a limit on member-name length may be imposed for compatibility with archive formats maintained with other tools. If it exists, the limit is often 15 characters (typical of formats related to a.out) or 16 characters (typical of formats related to coff).
ar is considered a binary utility because archives of this sort are most often used as libraries holding commonly needed subroutines.
ar creates an index to the symbols defined in relocatable object modules in the archive when you specify the modifier ‘s’. Once created, this index is updated in the archive whenever ar makes a change to its contents (save for the ‘q’ update operation). 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 their placement in the archive.
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 be used to add just the table.
gnu ar can optionally create a thin archive, which contains a symbol index and references to the original copies of the member files of the archive. This is useful for building libraries for use within a local build tree, where the relocatable objects are expected to remain available, and copying the contents of each object would only waste time and space.
An archive can either be thin or it can be normal. It cannot be both at the same time. Once an archive is created its format cannot be changed without first deleting it and then creating a new archive in its place.
Thin archives are also flattened, so that adding one thin archive to another thin archive does not nest it, as would happen with a normal archive. Instead the elements of the first archive are added individually to the second archive.
The paths to the elements of the archive are stored relative to the archive itself.
gnu ar is designed to be compatible with two different facilities. You can control its activity using command-line options, like 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 supplied via standard input, like the MRI “librarian” program.
ar [-X32_64] [-]p[mod] [--plugin name] [--target bfdname] [--output dirname] [relpos] [count] archive [member...]
When you use ar in the Unix style, ar insists on at least two arguments to execute: one keyletter specifying the operation (optionally accompanied by other keyletters specifying modifiers), and the archive name to act on.
Most operations can also accept further member arguments, specifying particular files to operate on.
gnu ar allows you to mix the operation code p and modifier flags mod in any order, within the first command-line argument.
If you wish, you may begin the first command-line argument with a dash.
The p keyletter specifies what operation to execute; it may be any of the following, but you must specify only one of them:
If you specify the ‘v’ modifier, ar lists each module
as it is deleted.
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 more than one member.
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 use the ‘a’, ‘b’, or ‘i’ modifiers to move them to a
specified place instead.
If you specify no member arguments, all the files in the archive are
printed.
The modifiers ‘a’, ‘b’, and ‘i’ do not affect this operation; new members are always placed at the end of the archive.
The modifier ‘v’ makes ar list each file as it is appended.
Since the point of this operation is speed, implementations of ar have the option of not updating the archive's symbol table if one exists. Too many different systems however assume that symbol tables are always up-to-date, so gnu ar will rebuild the table even with a quick append.
Note - gnu ar treats the command ‘qs’ as a
synonym for ‘r’ - replacing already existing files in the
archive and appending new ones at the end.
If one of the files named in member... does not exist, ar displays an error message, and leaves undisturbed any existing members of the archive matching that name.
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 relative to some existing member.
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’ to indicate whether the file was appended (no old member
deleted) or replaced.
If you do not specify a member, all files in the archive are listed.
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 instance; to see them all, you must ask for a complete
listing—in our example, ‘ar t b.a’.
If you do not specify a member, all files in the archive are extracted.
Files cannot be extracted from a thin archive, and there are
restrictions on extracting from archives created with P: The
paths must not be absolute, may not contain ..
, and any
subdirectories in the paths must exist. If it is desired to avoid
these restrictions then used the --output option to specify
an output directory.
A number of modifiers (mod) may immediately follow the p keyletter, to specify variations on an operation's behavior:
If binutils was configured with
--enable-deterministic-archives, then this mode is on by default.
It can be disabled with the ‘U’ modifier, below.
ar rcST archive.a subdir/file1 subdir/file2 file1
will result in the first subdir/file1
being replaced with
file1
from the current directory. Adding P will
prevent this replacement.
This is the default unless binutils was configured with
--enable-deterministic-archives.
The ar program also supports some command-line options which are neither modifiers nor actions, but which do change its behaviour in specific ways:
This option is only available if the toolchain has been built with plugin support enabled.
If --plugin is not provided, but plugin support has been enabled then ar iterates over the files in ${libdir}/bfd-plugins in alphabetic order and the first plugin that claims the object in question is used.
Please note that this plugin search directory is not the one
used by ld's -plugin option. In order to make
ar use the linker plugin it must be copied into the
${libdir}/bfd-plugins directory. For GCC based compilations
the linker plugin is called liblto_plugin.so.0.0.0. For Clang
based compilations it is called LLVMgold.so. The GCC plugin
is always backwards compatible with earlier versions, so it is
sufficient to just copy the newest one.
Note - although the presence of this option does imply a x extraction operation that option must still be included on the command line.
ar -M [ <script ]
If you use the single command-line option ‘-M’ with ar, you can control its operation with a rudimentary command language. This form of ar operates interactively if standard input is coming directly from a terminal. During interactive use, ar prompts for input (the prompt is ‘AR >’), and continues executing even after errors. If you redirect standard input to a script file, no prompts are issued, and ar abandons execution (with a nonzero exit code) on any error.
The ar command language is not designed to be equivalent to the command-line options; in fact, it provides somewhat less control over archives. The only purpose of the command language is to ease the transition to gnu ar for developers who already have scripts written for the MRI “librarian” program.
The syntax for the ar command language is straightforward:
LIST
is the same as list
. In the following descriptions, commands are
shown in upper case for clarity.
Here are the commands you can use in ar scripts, or when using ar interactively. Three of them have special significance:
OPEN
or CREATE
specify a current archive, which is
a temporary file required for most of the other commands.
SAVE
commits the changes so far specified by the script. Prior
to SAVE
, commands affect only the temporary copy of the current
archive.
ADDLIB
archiveADDLIB
archive (
module,
module, ...
module)
Requires prior use of OPEN
or CREATE
.
ADDMOD
member,
member, ...
memberRequires prior use of OPEN
or CREATE
.
CLEAR
SAVE
. May be executed (with no
effect) even if no current archive is specified.
CREATE
archiveSAVE
.
You can overwrite existing archives; similarly, the contents of any
existing file named archive will not be destroyed until SAVE
.
DELETE
module,
module, ...
moduleRequires prior use of OPEN
or CREATE
.
DIRECTORY
archive (
module, ...
module)
DIRECTORY
archive (
module, ...
module)
outputfileVERBOSE
specifies the form of the output: when verbose
output is off, output is like that of ‘ar -t archive
module...’. When verbose output is on, the listing is like
‘ar -tv archive module...’.
Output normally goes to the standard output stream; however, if you
specify outputfile as a final argument, ar directs the
output to that file.
END
0
exit code to indicate successful
completion. This command does not save the output file; if you have
changed the current archive since the last SAVE
command, those
changes are lost.
EXTRACT
module,
module, ...
moduleRequires prior use of OPEN
or CREATE
.
LIST
VERBOSE
. The effect is like ‘ar
tv archive’. (This single command is a gnu ar
enhancement, rather than present for MRI compatibility.)
Requires prior use of OPEN
or CREATE
.
OPEN
archiveSAVE
.
REPLACE
module,
module, ...
moduleREPLACE
arguments) from files in the current working directory.
To execute this command without errors, both the file, and the module in
the current archive, must exist.
Requires prior use of OPEN
or CREATE
.
VERBOSE
DIRECTORY
.
When the flag is on, DIRECTORY
output matches output from
‘ar -tv ’....
SAVE
CREATE
or OPEN
command.
Requires prior use of OPEN
or CREATE
.
nm [-A|-o|--print-file-name] [-a|--debug-syms] [-B|--format=bsd] [-C|--demangle[=style]] [-D|--dynamic] [-fformat|--format=format] [-g|--extern-only] [-h|--help] [-l|--line-numbers] [--inlines] [-n|-v|--numeric-sort] [-P|--portability] [-p|--no-sort] [-r|--reverse-sort] [-S|--print-size] [-s|--print-armap] [-t radix|--radix=radix] [-u|--undefined-only] [-V|--version] [-X 32_64] [--defined-only] [--no-demangle] [--plugin name] [--no-recurse-limit|--recurse-limit]] [--size-sort] [--special-syms] [--synthetic] [--with-symbol-versions] [--target=bfdname] [objfile...]
gnu nm lists the symbols from object files objfile.... If no object files are listed as arguments, nm assumes the file a.out.
For each symbol, nm shows:
u
, v
and w
).
A
B
b
C
D
d
G
g
i
I
N
n
p
R
r
S
s
T
t
U
u
V
v
W
w
-
?
The long and short forms of options, shown here as alternatives, are equivalent.
The default is for this limit to be enabled, but disabling it may be
necessary in order to demangle truly complicated names. Note however
that if the recursion limit is disabled then stack exhaustion is
possible and any bug reports about such an event will be rejected.
bsd
,
sysv
, or posix
. The default is bsd
.
Only the first character of format is significant; it can be
either upper or lower case.
main
inlines
callee1
which inlines callee2
, and address is from
callee2
, the source information for callee1
and main
will also be printed.
bsd
output style.
This option has no effect for object formats that do not record symbol
sizes, unless ‘--size-sort’ is also used in which case a
calculated size is displayed.
If --plugin is not provided, but plugin support has been enabled then nm iterates over the files in ${libdir}/bfd-plugins in alphabetic order and the first plugin that claims the object in question is used.
Please note that this plugin search directory is not the one
used by ld's -plugin option. In order to make
nm use the linker plugin it must be copied into the
${libdir}/bfd-plugins directory. For GCC based compilations
the linker plugin is called liblto_plugin.so.0.0.0. For Clang
based compilations it is called LLVMgold.so. The GCC plugin
is always backwards compatible with earlier versions, so it is
sufficient to just copy the newest one.
bsd
output format is used
the size of the symbol is printed, rather than the value, and
‘-S’ must be used in order both size and value to be printed.
objcopy [-F bfdname|--target=bfdname] [-I bfdname|--input-target=bfdname] [-O bfdname|--output-target=bfdname] [-B bfdarch|--binary-architecture=bfdarch] [-S|--strip-all] [-g|--strip-debug] [--strip-unneeded] [-K symbolname|--keep-symbol=symbolname] [-N symbolname|--strip-symbol=symbolname] [--strip-unneeded-symbol=symbolname] [-G symbolname|--keep-global-symbol=symbolname] [--localize-hidden] [-L symbolname|--localize-symbol=symbolname] [--globalize-symbol=symbolname] [--globalize-symbols=filename] [-W symbolname|--weaken-symbol=symbolname] [-w|--wildcard] [-x|--discard-all] [-X|--discard-locals] [-b byte|--byte=byte] [-i [breadth]|--interleave[=breadth]] [--interleave-width=width] [-j sectionpattern|--only-section=sectionpattern] [-R sectionpattern|--remove-section=sectionpattern] [--keep-section=sectionpattern] [--remove-relocations=sectionpattern] [-p|--preserve-dates] [-D|--enable-deterministic-archives] [-U|--disable-deterministic-archives] [--debugging] [--gap-fill=val] [--pad-to=address] [--set-start=val] [--adjust-start=incr] [--change-addresses=incr] [--change-section-address sectionpattern{=,+,-}val] [--change-section-lma sectionpattern{=,+,-}val] [--change-section-vma sectionpattern{=,+,-}val] [--change-warnings] [--no-change-warnings] [--set-section-flags sectionpattern=flags] [--set-section-alignment sectionpattern=align] [--add-section sectionname=filename] [--dump-section sectionname=filename] [--update-section sectionname=filename] [--rename-section oldname=newname[,flags]] [--long-section-names {enable,disable,keep}] [--change-leading-char] [--remove-leading-char] [--reverse-bytes=num] [--srec-len=ival] [--srec-forceS3] [--redefine-sym old=new] [--redefine-syms=filename] [--weaken] [--keep-symbols=filename] [--strip-symbols=filename] [--strip-unneeded-symbols=filename] [--keep-global-symbols=filename] [--localize-symbols=filename] [--weaken-symbols=filename] [--add-symbol name=[section:]value[,flags]] [--alt-machine-code=index] [--prefix-symbols=string] [--prefix-sections=string] [--prefix-alloc-sections=string] [--add-gnu-debuglink=path-to-file] [--keep-file-symbols] [--only-keep-debug] [--strip-dwo] [--extract-dwo] [--extract-symbol] [--writable-text] [--readonly-text] [--pure] [--impure] [--file-alignment=num] [--heap=size] [--image-base=address] [--section-alignment=num] [--stack=size] [--subsystem=which:major.minor] [--compress-debug-sections] [--decompress-debug-sections] [--elf-stt-common=val] [--merge-notes] [--no-merge-notes] [--verilog-data-width=val] [-v|--verbose] [-V|--version] [--help] [--info] infile [outfile]
The gnu objcopy utility copies the contents of an object file to another. objcopy uses the gnu bfd Library to read and write the object files. It can write the destination object file in a format different from that of the source object file. The exact behavior of objcopy is controlled by command-line options. Note that objcopy should be able to copy a fully linked file between any two formats. However, copying a relocatable object file between any two formats may not work as expected.
objcopy creates temporary files to do its translations and deletes 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 recognize most formats without being told explicitly. See BFD.
objcopy can be used to generate S-records by using an output target of ‘srec’ (e.g., use ‘-O srec’).
objcopy can be used to generate a raw binary file by using an output target of ‘binary’ (e.g., use -O binary). When objcopy generates a raw binary file, it will essentially produce a memory dump of the contents of the input object file. All symbols and relocation information will be discarded. The memory dump will start at the load address of the lowest section copied into the output file.
When generating an S-record or a raw binary file, it may be helpful to use -S to remove sections containing debugging information. In some cases -R will be useful to remove sections which contain information that is not needed by the binary file.
Note—objcopy is not able to change the endianness of its input 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 endianness or which have no endianness (e.g., ‘srec’). (However, see the --reverse-bytes option.)
If the first character of sectionpattern is the exclamation point (!) then matching sections will not be copied, even if earlier use of --only-section on the same command line would otherwise copy it. For example:
--only-section=.text.* --only-section=!.text.foo
will copy all sectinos maching '.text.*' but not the section
'.text.foo'.
If the first character of sectionpattern is the exclamation point (!) then matching sections will not be removed even if an earlier use of --remove-section on the same command line would otherwise remove it. For example:
--remove-section=.text.* --remove-section=!.text.foo
will remove all sections matching the pattern '.text.*', but will not
remove the section '.text.foo'.
--remove-relocations=.text.*
will remove the relocations for all sections matching the pattern '.text.*'.
If the first character of sectionpattern is the exclamation point (!) then matching sections will not have their relocation removed even if an earlier use of --remove-relocations on the same command line would otherwise cause the relocations to be removed. For example:
--remove-relocations=.text.* --remove-relocations=!.text.foo
will remove all relocations for sections matching the pattern
'.text.*', but will not remove relocations for the section
'.text.foo'.
-w -W !foo -W fo*
would cause objcopy to weaken all symbols that start with “fo”
except for the symbol “foo”.
This option is useful for creating files to program rom. It is
typically used with an srec
output target. Note that
objcopy will complain if you do not specify the
--byte option as well.
The default interleave breadth is 4, so with --byte set to 0,
objcopy would copy the first byte out of every four bytes
from the input to the output.
The default value for this option is 1. The value of width plus the byte value set by the --byte option must not exceed the interleave breadth set by the --interleave option.
This option can be used to create images for two 16-bit flashes interleaved
in a 32-bit bus by passing -b 0 -i 4 --interleave-width=2
and -b 2 -i 4 --interleave-width=2 to two objcopy
commands. If the input was '12345678' then the outputs would be
'1256' and '3478' respectively.
If binutils was configured with
--enable-deterministic-archives, then this mode is on by default.
It can be disabled with the ‘-U’ option, below.
This is the default unless binutils was configured with
--enable-deterministic-archives.
Note - it is possible to use --rename-section and
--update-section to both update and rename a section from one
command line. In this case, pass the original section name to
--update-section, and the original and new section names to
--rename-section.
This option is particularly helpful when the input format is binary, since this will always create a section called .data. If for example, you wanted instead to create a section called .rodata containing binary data you could use the following command line to achieve it:
objcopy -I binary -O <output_format> -B <architecture> \ --rename-section .data=.rodata,alloc,load,readonly,data,contents \ <input_binary_file> <output_object_file>
COFF
and PE-COFF
object formats. The default behaviour, ‘keep’,
is to preserve long section names if any are present in the input file.
The ‘enable’ and ‘disable’ options forcibly enable or disable
the use of long section names in the output object; when ‘disable’
is in effect, any long section names in the input object will be truncated.
The ‘enable’ option will only emit long section names if any are
present in the inputs; this is mostly the same as ‘keep’, but it
is left undefined whether the ‘enable’ option might force the
creation of an empty string table in the output file.
This option is used typically in generating ROM images for problematic target systems. For example, on some target boards, the 32-bit words fetched from 8-bit ROMs are re-assembled in little-endian byte order regardless of the CPU byte order. Depending on the programming model, the endianness of the ROM may need to be modified.
Consider a simple file with a section containing the following eight
bytes: 12345678
.
Using ‘--reverse-bytes=2’ for the above example, the bytes in the
output file would be ordered 21436587
.
Using ‘--reverse-bytes=4’ for the above example, the bytes in the
output file would be ordered 43218765
.
By using ‘--reverse-bytes=2’ for the above example, followed by
‘--reverse-bytes=4’ on the output file, the bytes in the second
output file would be ordered 34127856
.
If the debug info file is built in one location but it is going to be installed at a later time into a different location then do not use the path to the installed location. The --add-gnu-debuglink option will fail because the installed file does not exist yet. Instead put the debug info file in the current directory and use the --add-gnu-debuglink option without any directory components, like this:
objcopy --add-gnu-debuglink=foo.debug
At debug time the debugger will attempt to look for the separate debug info file in a set of known locations. The exact set of these locations varies depending upon the distribution being used, but it typically includes:
* The same directory as the executable.
* A sub-directory of the directory containing the executable
* A global debug directory such as /usr/lib/debug.
As long as the debug info file has been installed into one of these
locations before the debugger is run everything should work
correctly.
Note - the section headers of the stripped sections are preserved, including their sizes, but the contents of the section are discarded. The section headers are preserved so that other tools can match up the debuginfo file with the real executable, even if that executable has been relocated to a different address space.
The intention is that this option will be used in conjunction with --add-gnu-debuglink to create a two part executable. One a stripped binary which will occupy less space in RAM and in a distribution and the second a debugging information file which is only needed if debugging abilities are required. The suggested procedure to create these files is as follows:
foo
then...
objcopy --only-keep-debug foo foo.dbg
to
create a file containing the debugging info.
objcopy --strip-debug foo
to create a
stripped executable.
objcopy --add-gnu-debuglink=foo.dbg foo
to add a link to the debugging info into the stripped executable.
Note—the choice of .dbg
as an extension for the debug info
file is arbitrary. Also the --only-keep-debug
step is
optional. You could instead do this:
foo
to foo.full
objcopy --strip-debug foo
objcopy --add-gnu-debuglink=foo.full foo
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 --only-keep-debug switch.
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 debugging
information may be incomplete. Besides the gnu_debuglink feature
currently only supports the presence of one filename containing
debugging information, not multiple filenames on a one-per-object-file
basis.
native
, windows
,
console
, posix
, efi-app
, efi-bsd
,
efi-rtd
, sal-rtd
, and xbox
. You may optionally set
the subsystem version also. Numeric values are also accepted for
which.
[This option is specific to PE targets.]
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 --just-symbols
linker input file.
STT_COMMON
or STT_OBJECT
type.
--elf-stt-common=yes converts common symbol type to
STT_COMMON
. --elf-stt-common=no converts common symbol
type to STT_OBJECT
.
objdump [-a|--archive-headers] [-b bfdname|--target=bfdname] [-C|--demangle[=style] ] [-d|--disassemble[=symbol]] [-D|--disassemble-all] [-z|--disassemble-zeroes] [-EB|-EL|--endian={big | little }] [-f|--file-headers] [-F|--file-offsets] [--file-start-context] [-g|--debugging] [-e|--debugging-tags] [-h|--section-headers|--headers] [-i|--info] [-j section|--section=section] [-l|--line-numbers] [-S|--source] [--source-comment[=text]] [-m machine|--architecture=machine] [-M options|--disassembler-options=options] [-p|--private-headers] [-P options|--private=options] [-r|--reloc] [-R|--dynamic-reloc] [-s|--full-contents] [-W[lLiaprmfFsoRtUuTgAckK]| --dwarf[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links]] [--ctf=section] [-G|--stabs] [-t|--syms] [-T|--dynamic-syms] [-x|--all-headers] [-w|--wide] [--start-address=address] [--stop-address=address] [--prefix-addresses] [--[no-]show-raw-insn] [--adjust-vma=offset] [--dwarf-depth=n] [--dwarf-start=n] [--ctf-parent=section] [--no-recurse-limit|--recurse-limit] [--special-syms] [--prefix=prefix] [--prefix-strip=level] [--insn-width=width] [-V|--version] [-H|--help] objfile...
objdump displays information about one or more object files. The options control what particular information to display. This information is mostly useful to programmers who are working on the compilation tools, as opposed to programmers who just want their program to compile and work.
objfile... are the object files to be examined. When you specify archives, objdump shows information on each of the member object files.
The long and short forms of options, shown here as alternatives, are equivalent. At least one option from the list -a,-d,-D,-e,-f,-g,-G,-h,-H,-p,-P,-r,-R,-s,-S,-t,-T,-V,-x must be given.
For example,
objdump -b oasys -m vax -h fu.o
displays summary information from the section headers (-h) of
fu.o, which is explicitly identified (-m) as a VAX object
file in the format produced by Oasys compilers. You can list the
formats available with the -i option.
See Target Selection, for more information.
The default is for this limit to be enabled, but disabling it may be
necessary in order to demangle truly complicated names. Note however
that if the recursion limit is disabled then stack exhaustion is
possible and any bug reports about such an event will be rejected.
Note if the --dwarf=follow-links option has also been enabled
then any symbol tables in linked debug info files will be read in and
used when disassembling.
This option also has a subtle effect on the disassembly of instructions in code sections. When option -d is in effect objdump will assume that any symbols present in a code section occur on the boundary between instructions and it will refuse to disassemble across such a boundary. When option -D is in effect however this assumption is supressed. This means that it is possible for the output of -d and -D to differ if, for example, data is stored in code sections.
If the target is an ARM architecture this switch also has the effect of forcing the disassembler to decode pieces of data found in code sections as if they were instructions.
Note if the --dwarf=follow-links option has also been enabled
then any symbol tables in linked debug info files will be read in and
used when disassembling.
File segments may be relocated to nonstandard addresses, for example by using the -Ttext, -Tdata, or -Tbss options to ld. However, some object file formats, such as a.out, do not store the starting address of the file segments. In those situations, although ld relocates the sections correctly, using ‘objdump -h’ to list the file section headers cannot show the correct addresses. Instead, it shows the usual addresses, which are implicit for the target.
Note, in some cases it is possible for a section to have both the
READONLY and the NOREAD attributes set. In such cases the NOREAD
attribute takes precedence, but objdump will report both
since the exact setting of the flag bits might be important.
If the target is an ARM architecture then this switch has an
additional effect. It restricts the disassembly to only those
instructions supported by the architecture specified by machine.
If it is necessary to use this switch because the input file does not
contain any architecture information, but it is also desired to
disassemble all the instructions use -marm.
For ARC, dsp controls the printing of DSP instructions, spfp selects the printing of FPX single precision FP instructions, dpfp selects the printing of FPX double precision FP instructions, quarkse_em selects the printing of special QuarkSE-EM instructions, fpuda selects the printing of double precision assist instructions, fpus selects the printing of FPU single precision FP instructions, while fpud selects the printing of FPU double precision FP instructions. Additionally, one can choose to have all the immediates printed in hexadecimal using hex. By default, the short immediates are printed using the decimal representation, while the long immediate values are printed as hexadecimal.
cpu=... allows to enforce a particular ISA when disassembling instructions, overriding the -m value or whatever is in the ELF file. This might be useful to select ARC EM or HS ISA, because architecture is same for those and disassembler relies on private ELF header data to decide if code is for EM or HS. This option might be specified multiple times - only the latest value will be used. Valid values are same as for the assembler -mcpu=... option.
If the target is an ARM architecture then this switch can be used to select which register name set is used during disassembler. Specifying -M reg-names-std (the default) will select the register names as used in ARM's instruction set documentation, but with register 13 called 'sp', register 14 called 'lr' and register 15 called 'pc'. Specifying -M reg-names-apcs will select the name set used by the ARM Procedure Call Standard, whilst specifying -M reg-names-raw will just use ‘r’ followed by the register number.
There are also two variants on the APCS register naming scheme enabled by -M reg-names-atpcs and -M reg-names-special-atpcs which use the ARM/Thumb Procedure Call Standard naming conventions. (Either with the normal register names or the special register names).
This option can also be used for ARM architectures to force the disassembler to interpret all instructions as Thumb instructions by using the switch --disassembler-options=force-thumb. This can be useful when attempting to disassemble thumb code produced by other compilers.
For AArch64 targets this switch can be used to set whether instructions are disassembled as the most general instruction using the -M no-aliases option or whether instruction notes should be generated as comments in the disasssembly using -M notes.
For the x86, some of the options duplicate functions of the -m switch, but allow finer grained control. Multiple selections from the following may be specified as a comma separated string.
x86-64
i386
i8086
intel
att
amd64
intel64
intel-mnemonic
att-mnemonic
intel-mnemonic
implies intel
and
att-mnemonic
implies att
.
addr64
addr32
addr16
data32
data16
x86-64
, i386
or i8086
appear later in the option string.
suffix
For PowerPC, the -M argument raw selects
disasssembly of hardware insns rather than aliases. For example, you
will see rlwinm
rather than clrlwi
, and addi
rather than li
. All of the -m arguments for
gas that select a CPU are supported. These are:
403, 405, 440, 464, 476,
601, 603, 604, 620, 7400,
7410, 7450, 7455, 750cl,
821, 850, 860, a2, booke,
booke32, cell, com, e200z4,
e300, e500, e500mc, e500mc64,
e500x2, e5500, e6500, efs,
power4, power5, power6, power7,
power8, power9, ppc, ppc32,
ppc64, ppc64bridge, ppcps, pwr,
pwr2, pwr4, pwr5, pwr5x,
pwr6, pwr7, pwr8, pwr9,
pwrx, titan, and vle.
32 and 64 modify the default or a prior CPU
selection, disabling and enabling 64-bit insns respectively. In
addition, altivec, any, htm, vsx,
and spe add capabilities to a previous or later CPU
selection. any will disassemble any opcode known to
binutils, but in cases where an opcode has two different meanings or
different arguments, you may not see the disassembly you expect.
If you disassemble without giving a CPU selection, a default will be
chosen from information gleaned by BFD from the object files headers,
but the result again may not be as you expect.
For MIPS, this option controls the printing of instruction mnemonic names and register names in disassembled instructions. Multiple selections from the following may be specified as a comma separated string, and invalid options are ignored:
no-aliases
msa
virt
xpa
gpr-names=
ABIfpr-names=
ABIcp0-names=
ARCHhwr-names=
ARCHrdhwr
instruction) names
as appropriate for the CPU or architecture specified by
ARCH. By default, HWR names are selected according to
the architecture and CPU of the binary being disassembled.
reg-names=
ABIreg-names=
ARCHFor any of the options listed above, ABI or ARCH may be specified as ‘numeric’ to have numbers printed rather than names, for the selected types of registers. You can list the available values of ABI and ARCH using the --help option.
For VAX, you can specify function entry addresses with -M
entry:0xf00ba. You can use this multiple times to properly
disassemble VAX binary files that don't contain symbol tables (like
ROM dumps). In these cases, the function entry mask would otherwise
be decoded as VAX instructions, which would probably lead the rest
of the function being wrongly disassembled.
For XCOFF, the available options are:
header
aout
sections
syms
relocs
lineno,
loader
except
typchk
traceback
toc
ldinfo
Not all object formats support this option. In particular the ELF
format does not use it.
Displays the contents of the DWARF debug sections in the file, if any are present. Compressed debug sections are automatically decompressed (temporarily) before they are displayed. If one or more of the optional letters or words follows the switch then only those type(s) of data will be dumped. The letters and words refer to the following information:
a
=abbrev
A
=addr
c
=cu_index
f
=frames
F
=frame-interp
g
=gdb_index
i
=info
k
=links
K
=follow-links
In addition, when displaying DWARF attributes, if a form is found that
references the separate debug info file, then the referenced contents
will also be displayed.
l
=rawline
L
=decodedline
m
=macro
o
=loc
p
=pubnames
r
=aranges
R
=Ranges
s
=str
t
=pubtype
T
=trace_aranges
u
=trace_abbrev
U
=trace_info
Note: displaying the contents of ‘.debug_static_funcs’,
‘.debug_static_vars’ and ‘debug_weaknames’ sections is not
currently supported.
.debug_info
section to n children.
This is only useful with --debug-dump=info. The default is
to print all DIEs; the special value 0 for n will also have this
effect.
With a non-zero value for n, DIEs at or deeper than n
levels will not be printed. The range for n is zero-based.
If specified, this option will suppress printing of any header information and all DIEs before the DIE numbered n. Only siblings and children of the specified DIE will be printed.
This can be used in conjunction with --dwarf-depth.
.stab
debugging symbol-table entries are carried in an ELF
section. In most other file formats, debugging symbol-table entries are
interleaved with linkage symbols, and are visible in the --syms
output.
[ 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
where the number inside the square brackets is the number of the 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 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 symbol. The last two fields are the symbol's value and its name.
The other common output format, usually seen with ELF based files, looks like this:
00000000 l d .bss 00000000 .bss 00000000 g .text 00000000 fred
Here the first number is the symbol's value (sometimes refered to as its address). The next field is actually a set of characters and spaces indicating the flag bits that are set on the symbol. These characters are described below. Next is the section with which the symbol is associated or *ABS* if the section is absolute (ie not connected with any section), or *UND* if the section is referenced in the file being dumped, but not defined there.
After the section name comes another field, a number, which for common symbols is the alignment and for other symbol is the size. Finally the symbol's name is displayed.
The flag characters are divided into 7 groups as follows:
l
g
u
!
w
C
W
I
i
d
D
F
f
O
The output format is similar to that produced by the --syms
option, except that an extra field is inserted before the symbol's
name, giving the version information associated with the symbol.
If the version is the default version to be used when resolving
unversioned references to the symbol then it's displayed as is,
otherwise it's put into parentheses.
ranlib [--plugin name] [-DhHvVt] archive
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 an archive that is a relocatable object file.
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 allows routines in the library to call each other without regard to their placement in the archive.
The gnu ranlib program is another form of gnu ar; running ranlib is completely equivalent to executing ‘ar -s’. See ar.
If binutils was configured with
--enable-deterministic-archives, then this mode is on by
default. It can be disabled with the ‘-U’ option, described
below.
If binutils was configured without --enable-deterministic-archives, then this mode is on by default.
size [-A|-B|-G|--format=compatibility] [--help] [-d|-o|-x|--radix=number] [--common] [-t|--totals] [--target=bfdname] [-V|--version] [objfile...]
The gnu size utility lists the section sizes and the total size for each of the binary files objfile on its argument list. By default, one line of output is generated for each file or each module if the file is an archive.
objfile... are the files to be examined. If none are
specified, the file a.out
will be used instead.
The command-line options have the following meanings:
Here is an example of the Berkeley (default) format of output from size:
$ size --format=Berkeley ranlib size text data bss dec hex filename 294880 81920 11592 388392 5ed28 ranlib 294880 81920 11888 388688 5ee50 size
The Berkeley style output counts read only data in the text
column, not in the data
column, the dec
and hex
columns both display the sum of the text
, data
, and
bss
columns in decimal and hexadecimal respectively.
The GNU format counts read only data in the data
column, not
the text
column, and only displays the sum of the text
,
data
, and bss
columns once, in the total
column.
The --radix option can be used to change the number base for
all columns. Here is the same data displayed with GNU conventions:
$ size --format=GNU ranlib size text data bss total filename 279880 96920 11592 388392 ranlib 279880 96920 11888 388688 size
This is the same data, but displayed closer to System V conventions:
$ size --format=SysV ranlib size ranlib : section size addr .text 294880 8192 .data 81920 303104 .bss 11592 385024 Total 388392 size : section size addr .text 294880 8192 .data 81920 303104 .bss 11888 385024 Total 388688
strings [-afovV] [-min-len] [-n min-len] [--bytes=min-len] [-t radix] [--radix=radix] [-e encoding] [--encoding=encoding] [-] [--all] [--print-file-name] [-T bfdname] [--target=bfdname] [-w] [--include-all-whitespace] [-s] [--output-separatorsep_string] [--help] [--version] file...
For each file given, gnu strings prints the printable character sequences that are at least 4 characters long (or the number given with the options below) and are followed by an unprintable character.
Depending upon how the strings program was configured it will default to either displaying all the printable sequences that it can find in each file, or only those sequences that are in loadable, initialized data sections. If the file type in unrecognizable, or if strings is reading from stdin then it will always display all of the printable sequences that it can find.
For backwards compatibility any file that occurs after a command-line option of just - will also be scanned in full, regardless of the presence of any -d option.
strings is mainly useful for determining the contents of non-text files.
The - option is position dependent and forces strings to
perform full scans of any file that is mentioned after the -
on the command line, even if the -d option has been
specified.
strip [-F bfdname |--target=bfdname] [-I bfdname |--input-target=bfdname] [-O bfdname |--output-target=bfdname] [-s|--strip-all] [-S|-g|-d|--strip-debug] [--strip-dwo] [-K symbolname|--keep-symbol=symbolname] [-M|--merge-notes][--no-merge-notes] [-N symbolname |--strip-symbol=symbolname] [-w|--wildcard] [-x|--discard-all] [-X |--discard-locals] [-R sectionname |--remove-section=sectionname] [--keep-section=sectionpattern] [--remove-relocations=sectionpattern] [-o file] [-p|--preserve-dates] [-D|--enable-deterministic-archives] [-U|--disable-deterministic-archives] [--keep-file-symbols] [--only-keep-debug] [-v |--verbose] [-V|--version] [--help] [--info] objfile...
gnu strip discards all symbols from object files objfile. The list of object files may include archives. At least one object file must be given.
strip modifies the files named in its argument, rather than writing modified copies under different names.
If the first character of sectionpattern is the exclamation point (!) then matching sections will not be removed even if an earlier use of --remove-section on the same command line would otherwise remove it. For example:
--remove-section=.text.* --remove-section=!.text.foo
will remove all sections matching the pattern '.text.*', but will not
remove the section '.text.foo'.
--remove-relocations=.text.*
will remove the relocations for all sections matching the patter '.text.*'.
If the first character of sectionpattern is the exclamation point (!) then matching sections will not have their relocation removed even if an earlier use of --remove-relocations on the same command line would otherwise cause the relocations to be removed. For example:
--remove-relocations=.text.* --remove-relocations=!.text.foo
will remove all relocations for sections matching the pattern
'.text.*', but will not remove relocations for the section
'.text.foo'.
If binutils was configured with
--enable-deterministic-archives, then this mode is on by default.
It can be disabled with the ‘-U’ option, below.
This is the default unless binutils was configured with
--enable-deterministic-archives.
-w -K !foo -K fo*
would cause strip to only keep symbols that start with the letters
“fo”, but to discard the symbol “foo”.
Note - the section headers of the stripped sections are preserved, including their sizes, but the contents of the section are discarded. The section headers are preserved so that other tools can match up the debuginfo file with the real executable, even if that executable has been relocated to a different address space.
The intention is that this option will be used in conjunction with --add-gnu-debuglink to create a two part executable. One a stripped binary which will occupy less space in RAM and in a distribution and the second a debugging information file which is only needed if debugging abilities are required. The suggested procedure to create these files is as follows:
foo
then...
objcopy --only-keep-debug foo foo.dbg
to
create a file containing the debugging info.
objcopy --strip-debug foo
to create a
stripped executable.
objcopy --add-gnu-debuglink=foo.dbg foo
to add a link to the debugging info into the stripped executable.
Note—the choice of .dbg
as an extension for the debug info
file is arbitrary. Also the --only-keep-debug
step is
optional. You could instead do this:
foo
to foo.full
strip --strip-debug foo
objcopy --add-gnu-debuglink=foo.full foo
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 --only-keep-debug switch.
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 debugging
information may be incomplete. Besides the gnu_debuglink feature
currently only supports the presence of one filename containing
debugging information, not multiple filenames on a one-per-object-file
basis.
c++filt [-_|--strip-underscore] [-n|--no-strip-underscore] [-p|--no-params] [-t|--types] [-i|--no-verbose] [-r|--no-recurse-limit] [-R|--recurse-limit] [-s format|--format=format] [--help] [--version] [symbol...]
The C++ and Java languages provide function overloading, which means that you can write many functions with the same name, providing that each function takes parameters of different types. In order to be able to distinguish these similarly named functions C++ and Java encode them into a low-level assembler name which uniquely identifies each different version. This process is known as mangling. The c++filt 1 program does the inverse mapping: it decodes (demangles) low-level names into user-level names so that they can be read.
Every alphanumeric word (consisting of letters, digits, underscores, 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 name in the output, otherwise the original word is output. In this way you can pass an entire assembler source file, containing mangled names, through c++filt and see the same source file containing demangled names.
You can also use c++filt to decipher individual symbols by passing them on the command line:
c++filt symbol
If no symbol arguments are given, c++filt reads symbol names from the standard input instead. All the results are printed on the standard output. The difference between reading names from the command line versus reading names from the standard input is that command-line arguments are expected to be just mangled names and no checking is performed to separate them from surrounding text. Thus for example:
c++filt -n _Z1fv
will work and demangle the name to “f()” whereas:
c++filt -n _Z1fv,
will not work. (Note the extra comma at the end of the mangled name which makes it invalid). This command however will work:
echo _Z1fv, | c++filt -n
and will display “f(),”, i.e., the demangled name followed by a 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 assembler source file where there might be extra, extraneous characters trailing after a mangled name. For example:
.type _Z1fv, @function
foo
gets the low-level
name _foo
. This option removes the initial underscore. Whether
c++filt removes the underscore by default is target dependent.
The default is for this limit to be enabled, but disabling it may be necessary in order to demangle truly complicated names. Note however that if the recursion limit is disabled then stack exhaustion is possible and any bug reports about such an event will be rejected.
The -r option is a synonym for the
--no-recurse-limit option. The -R option is a
synonym for the --recurse-limit option.
auto
gnu
lucid
arm
hp
edg
gnu-v3
java
gnat
Warning: c++filt is a new utility, and the details of its user interface are subject to change in future releases. In particular, 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,c++filt symbolmay in a future release become
c++filt option symbol
addr2line [-a|--addresses] [-b bfdname|--target=bfdname] [-C|--demangle[=style]] [-r|--no-recurse-limit] [-R|--recurse-limit] [-e filename|--exe=filename] [-f|--functions] [-s|--basename] [-i|--inlines] [-p|--pretty-print] [-j|--section=name] [-H|--help] [-V|--version] [addr addr ...]
addr2line translates addresses into file names and line numbers. Given an address in an executable or an offset in a section of a relocatable object, it uses the debugging information to figure out which file name and line number are associated with it.
The executable or relocatable object to use is specified with the -e option. The default is the file a.out. The section in the relocatable object to use is specified with the -j option.
addr2line has two modes of operation.
In the first, hexadecimal addresses are specified on the command line, and addr2line displays the file name and line number for each address.
In the second, addr2line reads hexadecimal addresses from standard 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 convert dynamically chosen addresses.
The format of the output is ‘FILENAME:LINENO’. By default each input address generates one line of output.
Two options can generate additional lines before each ‘FILENAME:LINENO’ line (in that order).
If the -a option is used then a line with the input address is displayed.
If the -f option is used, then a line with the ‘FUNCTIONNAME’ is displayed. This is the name of the function containing the address.
One option can generate additional lines after the ‘FILENAME:LINENO’ line.
If the -i option is used and the code at the given address is present there because of inlining by the compiler then additional lines are displayed afterwards. One or two extra lines (if the -f option is used) are displayed for each inlined function.
Alternatively if the -p option is used then each input address generates a single, long, output line containing the address, the function name, the file name and the line number. If the -i option has also been used then any inlined functions will be displayed in the same manner, but on separate lines, and prefixed by the text ‘(inlined by)’.
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 not be determined, addr2line will print 0.
The long and short forms of options, shown here as alternatives, are equivalent.
main
inlines
callee1
which inlines callee2
, and address is from
callee2
, the source information for callee1
and main
will also be printed.
The default is for this limit to be enabled, but disabling it may be necessary in order to demangle truly complicated names. Note however that if the recursion limit is disabled then stack exhaustion is possible and any bug reports about such an event will be rejected.
The -r option is a synonym for the --no-recurse-limit option. The -R option is a synonym for the --recurse-limit option.
Note this option is only effective if the -C or --demangle option has been enabled.
windmc may be used to generator Windows message resources.
Warning: windmc is not always built as part of the binary utilities, since it is only useful for Windows targets.
windmc [options] input-file
windmc reads message definitions from an input file (.mc) and translate them into a set of output files. The output files may be of four kinds:
h
rc
bin
dbg
The exact description of these different formats is available in documentation from Microsoft.
When windmc converts from the mc
format to the bin
format, rc
, h
, and optional dbg
it is acting like the
Windows Message Compiler.
bin
files should be in ASCII
format.
bin
filenames should have to be prefixed by the
basename of the source file.
bin
files by zero. By default they are
terminated by CR/LF.
windmc
to generate an OLE2 header
file, using HRESULT definitions. Status codes are used if the flag is not
specified.
rc
script and the generated
bin
files that the resource compiler script includes. The default
is the current directory.
bin
file should be in UTF16
format. This is the default behaviour.
dbg
C include file that maps message id's to the
symbolic name. No such file is generated without specifying the switch.
windres may be used to manipulate Windows resources.
Warning: windres is not always built as part of the binary utilities, since it is only useful for Windows targets.
windres [options] [input-file] [output-file]
windres reads resources from an input file and copies them into an output file. Either file may be in one of three formats:
rc
res
coff
The exact description of these different formats is available in documentation from Microsoft.
When windres converts from the rc
format to the res
format, it is acting like the Windows Resource Compiler. When
windres converts from the res
format to the coff
format, it is acting like the Windows CVTRES
program.
When windres generates an rc
file, the output is similar
but not identical to the format expected for the input. When an input
rc
file refers to an external filename, an output rc
file
will instead include the file contents.
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 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 .o or
.exe will be treated as a coff
file.
If no output file is specified, windres will print the resources
in rc
format to standard output.
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 application. This will make the resources described in the
rc
file available to Windows.
rc
file, it runs it through the C
preprocessor first. This option may be used to specify the preprocessor
to use, including any leading arguments. The default preprocessor
argument is gcc -E -xc-header -DRC_INVOKED
.
rc
file, it runs it through
the C preprocessor first. This option may be used to specify additional
text to be passed to preprocessor on its command line.
This option can be used multiple times to add multiple options to the
preprocessor command line.
rc
file.
windres will pass this to the preprocessor as an -I
option. windres will also search this directory when looking for
files named in the rc
file. If the argument passed to this command
matches any of the supported formats (as described in the -J
option), it will issue a deprecation warning, and behave just like the
-J option. New programs should not use this behaviour. If a
directory happens to match a format, simple prefix it with ‘./’
to disable the backward compatibility.
rc
file.
rc
file.
rc
file.
val should be a hexadecimal prefixed by ‘0x’ or decimal
codepage code. The valid range is from zero up to 0xffff, but the
validity of the codepage is host and configuration dependent.
rc
file.
val should be a hexadecimal language code. The low eight bits are
the language, and the high eight bits are the sublanguage.
YYDEBUG
defined as 1
,
this will turn on parser debugging.
dlltool is used to create the files needed to create dynamic link libraries (DLLs) on systems which understand PE format image files such as Windows. A DLL contains an export table which contains information that the runtime loader needs to resolve references from a referencing program.
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 .o file can contain information in special ‘.drectve’ sections with export information.
Note: dlltool is not always built as part of the binary utilities, since it is only useful for those targets which support DLLs.
dlltool [-d|--input-def def-file-name] [-b|--base-file base-file-name] [-e|--output-exp exports-file-name] [-z|--output-def def-file-name] [-l|--output-lib library-file-name] [-y|--output-delaylib library-file-name] [--export-all-symbols] [--no-export-all-symbols] [--exclude-symbols list] [--no-default-excludes] [-S|--as path-to-assembler] [-f|--as-flags options] [-D|--dllname name] [-m|--machine machine] [-a|--add-indirect] [-U|--add-underscore] [--add-stdcall-underscore] [-k|--kill-at] [-A|--add-stdcall-alias] [-p|--ext-prefix-alias prefix] [-x|--no-idata4] [-c|--no-idata5] [--use-nul-prefixed-import-tables] [-I|--identify library-file-name] [--identify-strict] [-i|--interwork] [-n|--nodelete] [-t|--temp-prefix prefix] [-v|--verbose] [-h|--help] [-V|--version] [--no-leading-underscore] [--leading-underscore] [object-file ...]
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 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 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 be present in one invocation of dlltool.
When creating a DLL, along with the source for the DLL, it is necessary to have three other files. dlltool can help with the creation of these files.
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 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 object files specified on its command line looking for those functions which have been specially marked as being exported and put entries for them in the .def file it creates.
In order to mark a function as being exported from a DLL, it needs to have an -export:<name_of_function> entry in the ‘.drectve’ section of the object file. This can be done in C by using the asm() operator:
asm (".section .drectve"); asm (".ascii \"-export:my_func\""); int my_func (void) { ... }
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 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 dlltool when it is creating or reading in a .def file.
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 (an `import library'). This file can be created by giving the -l option to dlltool when it is creating or reading in a .def file.
If the -y option is specified, dlltool generates a delay-import library that can be used instead of the normal import library to allow a program to link to the dll only as soon as an imported function is called for the first time. The resulting executable will need to be linked to the static delayimp library containing __delayLoadHelper2(), which in turn will import LoadLibraryA and GetProcAddress from kernel32.
dlltool builds the library file by hand, but it builds the exports file by creating temporary files containing assembler statements and 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 option can be used to pass specific flags to that assembler. The -n 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 prevent dlltool from deleting the temporary object files it used to build the library.
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 uses that DLL:
gcc -c dll.c dlltool -e exports.o -l dll.lib dll.o gcc dll.o exports.o -o dll.dll gcc program.o dll.lib -o program
dlltool may also be used to query an existing import library to determine the name of the DLL to which it is associated. See the description of the -I or --identify option.
The command-line options have the following meanings:
This does not change the naming of symbols provided by the import library
to programs linked against it, but only the entries in the import table
(ie the .idata section).
.idata4
section. This is for compatibility
with certain operating systems.
.idata4
and .idata5
by zero an
element. This emulates old gnu import library generation of
dlltool
. By default this option is turned off.
.idata5
section. This is for compatibility
with certain operating systems.
stdout
, the name(s)
of the associated DLL(s). This can be performed in addition to any
other operations indicated by the other options and arguments.
dlltool fails if the import library does not exist or is not
actually an import library. See also --identify-strict.
A .def file contains any number of the following commands:
NAME
name [ ,
base ]
.exe
.
LIBRARY
name [ ,
base ]
.dll
.
Note: If you want to use LIBRARY as name then you need to quote. Otherwise
this will fail due a necessary hack for libtool (see PR binutils/13710 for more
details).
EXPORTS ( ( (
name1 [ =
name2 ] ) | (
name1 =
module-name .
external-name ) ) [ ==
its_name ]
[
integer ] [ NONAME ] [ CONSTANT ] [ DATA ] [ PRIVATE ] ) *
EXPORTS
has to be the last command in .def file, as keywords
are treated - beside LIBRARY
- as simple name-identifiers.
If you want to use LIBRARY as name then you need to quote it.
IMPORTS ( (
internal-name =
module-name .
integer ) | [
internal-name = ]
module-name .
external-name ) [ == )
its_name ] *
IMPORTS
has to be the last command in .def file, as keywords
are treated - beside LIBRARY
- as simple name-identifiers.
If you want to use LIBRARY as name then you need to quote it.
DESCRIPTION
string.rdata
section.
STACKSIZE
number-reserve [,
number-commit ]
HEAPSIZE
number-reserve [,
number-commit ]
--stack
or --heap
number-reserve,number-commit in the output .drectve
section. The linker will see this and act upon it.
CODE
attr +
DATA
attr +
SECTIONS (
section-name attr + ) *
--attr
section-name attr in the output
.drectve
section, where attr is one of READ
,
WRITE
, EXECUTE
or SHARED
. The linker will see
this and act upon it.
readelf [-a|--all] [-h|--file-header] [-l|--program-headers|--segments] [-S|--section-headers|--sections] [-g|--section-groups] [-t|--section-details] [-e|--headers] [-s|--syms|--symbols] [--dyn-syms] [-n|--notes] [-r|--relocs] [-u|--unwind] [-d|--dynamic] [-V|--version-info] [-A|--arch-specific] [-D|--use-dynamic] [-x <number or name>|--hex-dump=<number or name>] [-p <number or name>|--string-dump=<number or name>] [-R <number or name>|--relocated-dump=<number or name>] [-z|--decompress] [-c|--archive-index] [-w[lLiaprmfFsoRtUuTgAckK]| --debug-dump[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links]] [--dwarf-depth=n] [--dwarf-start=n] [--ctf=section] [--ctf-parent=section] [--ctf-symbols=section] [--ctf-strings=section] [-I|--histogram] [-v|--version] [-W|--wide] [-H|--help] elffile...
readelf displays information about one or more ELF format object files. The options control what particular information to display.
elffile... are the object files to be examined. 32-bit and 64-bit ELF files are supported, as are archives containing ELF files.
This program performs a similar function to objdump but it goes 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.
The long and short forms of options, shown here as alternatives, are equivalent. At least one option besides ‘-v’ or ‘-H’ must be given.
Note - this option does not enable --use-dynamic itself, so
if that option is not present on the command line then dynamic symbols
and dynamic relocs will not be displayed.
.ARM.exidx
/ .ARM.extab
) are currently supported. If
support is not yet implemented for your architecture you could try
dumping the contents of the .eh_frames section using the
--debug-dump=frames or --debug-dump=frames-interp
options.
When displaying relocations, this option makes readelf
display the dynamic relocations rather than the static relocations.
Displays the contents of the DWARF debug sections in the file, if any are present. Compressed debug sections are automatically decompressed (temporarily) before they are displayed. If one or more of the optional letters or words follows the switch then only those type(s) of data will be dumped. The letters and words refer to the following information:
a
=abbrev
A
=addr
c
=cu_index
f
=frames
F
=frame-interp
g
=gdb_index
i
=info
k
=links
K
=follow-links
In addition, when displaying DWARF attributes, if a form is found that
references the separate debug info file, then the referenced contents
will also be displayed.
l
=rawline
L
=decodedline
m
=macro
o
=loc
p
=pubnames
r
=aranges
R
=Ranges
s
=str
t
=pubtype
T
=trace_aranges
u
=trace_abbrev
U
=trace_info
Note: displaying the contents of ‘.debug_static_funcs’,
‘.debug_static_vars’ and ‘debug_weaknames’ sections is not
currently supported.
.debug_info
section to n children.
This is only useful with --debug-dump=info. The default is
to print all DIEs; the special value 0 for n will also have this
effect.
With a non-zero value for n, DIEs at or deeper than n
levels will not be printed. The range for n is zero-based.
If specified, this option will suppress printing of any header information and all DIEs before the DIE numbered n. Only siblings and children of the specified DIE will be printed.
This can be used in conjunction with --dwarf-depth.
.symtab
and its linked
string table are used.
If either of --ctf-symbols or --ctf-strings is specified, the
other must be specified as well.
elfedit [--input-mach=machine] [--input-type=type] [--input-osabi=osabi] --output-mach=machine --output-type=type --output-osabi=osabi --enable-x86-feature=feature --disable-x86-feature=feature [-v|--version] [-h|--help] elffile...
elfedit updates the ELF header and program property of ELF files which have the matching ELF machine and file types. The options control how and which fields in the ELF header and program property should be updated.
elffile... are the ELF files to be updated. 32-bit and 64-bit ELF files are supported, as are archives containing ELF files.
The long and short forms of options, shown here as alternatives, are equivalent. At least one of the --output-mach, --output-type, --output-osabi, --enable-x86-feature and --disable-x86-feature options must be given.
The supported ELF machine types are, i386, IAMCU, L1OM,
K1OM and x86-64.
The supported ELF file types are, rel, exec and dyn.
The supported ELF OSABIs are, none, HPUX, NetBSD,
GNU, Linux (alias for GNU),
Solaris, AIX, Irix,
FreeBSD, TRU64, Modesto, OpenBSD, OpenVMS,
NSK, AROS and FenixOS.
Note: --enable-x86-feature and --disable-x86-feature
are available only on hosts with ‘mmap’ support.
The following command-line options are supported by all of the programs described in this manual.
Options in file are separated by whitespace. A whitespace
character may be included in an option by surrounding the entire
option in either single or double quotes. Any character (including a
backslash) may be included by prefixing the character to be included
with a backslash. The file may itself contain additional
@file options; any such options will be processed recursively.
You can specify two aspects of the target system to the gnu binary file utilities, each in several ways:
In the following summaries, the lists of ways to specify values are in order of decreasing precedence. The ways listed first override those listed later.
The commands to list valid values only list the values for which the programs you are running were configured. If they were configured with --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 because some of them can only be configured native (on hosts with the same type as the target system).
A target is an object file format. A given target may be supported for multiple architectures (see Architecture Selection). A target selection may also have variations for different operating systems or architectures.
The command to list valid target values is ‘objdump -i’ (the first column of output contains the relevant information).
Some sample values are: ‘a.out-hp300bsd’, ‘ecoff-littlemips’, ‘a.out-sunos-big’.
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 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 running the shell script config.sub which is included with the sources.
Some sample configuration triplets are: ‘m68k-hp-bsd’, ‘mips-dec-ultrix’, ‘sparc-sun-sunos’.
Ways to specify:
GNUTARGET
Ways to specify:
GNUTARGET
Ways to specify:
GNUTARGET
Ways to specify:
GNUTARGET
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 family from the name of the particular cpu.
The command to list valid architecture values is ‘objdump -i’ (the second column contains the relevant information).
Sample values: ‘m68k:68020’, ‘mips:3000’, ‘sparc’.
Ways to specify:
Ways to specify:
Your bug reports play an essential role in making the binary utilities reliable.
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 is to help the entire community by making the next version of the binary utilities work better. Bug reports are your contribution to their maintenance.
In order for a bug report to serve its purpose, you must include the information that enables us to fix the bug.
If you are not sure whether you have found a bug, here are some guidelines:
A number of companies and individuals offer support for gnu products. If you obtained the binary utilities from a support organization, we recommend you contact that organization first.
You can find contact information for many support companies and individuals in the file etc/SERVICE in the gnu Emacs distribution.
In any event, we also recommend that you send bug reports for the binary utilities to http://www.sourceware.org/bugzilla/.
The fundamental principle of reporting bugs usefully is this: report all the facts. If you are not sure whether to state a fact or leave it out, state it!
Often people omit facts because they think they know what causes the 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. 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 that pathname is stored in memory; perhaps, if the pathname were different, the contents of that location would fool the utility into 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, and the most helpful.
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 on the assumption that the bug has not been reported previously.
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 respond by asking for enough details to enable us to investigate. You might as well expedite matters by sending them to begin with.
To enable us to fix the bug, you should include all these things:
Without this, we will not know whether there is any point in looking for the bug in the current version of the binary utilities.
BFD
library.
gcc-2.7
”.
If we were to try to guess the arguments, we would probably guess wrong and then we might not encounter the bug.
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 send the source files rather than the object files. In this case, be sure to say exactly what version of gcc, or whatever, was used to produce the object files. Also say how gcc, or whatever, was configured.
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 output, we might not notice unless it is glaringly wrong. You might as well not give us a chance to make a mistake.
Even if the problem you experience is a fatal signal, you should still say so explicitly. Suppose something strange is going on, 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 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 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 from our observations.
The line numbers in our development sources will not match those in your sources. Your line numbers would convey no useful information to us.
Here are some things that are not necessary:
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 changes will not affect it.
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 debugger with breakpoints, not by pure deduction from a series of examples. We recommend that you save your time for something else.
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 output will be easier to spot, running under the debugger will take less time, and so on.
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 used.
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 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 might not understand it at all.
Sometimes with programs as complicated as the binary utilities it 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 example, we will not be able to construct one, so we will not be able to verify that the bug is fixed.
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 test case will help us to understand.
Such guesses are usually wrong. Even we cannot guess right about such things without first using the debugger to find the facts.
Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. http://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
The purpose of this License is to make a manual, textbook, or other functional and useful document free in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of “copyleft”, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The “Document”, below, refers to any such manual or work. Any member 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 way requiring permission under copyright law.
A “Modified Version” of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A “Secondary Section” is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The “Invariant Sections” are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The “Cover Texts” are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice 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 be at most 25 words.
A “Transparent” copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not “Transparent” is called “Opaque”.
Examples of suitable formats for Transparent copies include plain ascii without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The “Title Page” means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, “Title Page” means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
The “publisher” means any person or entity that distributes copies of the Document to the public.
A section “Entitled XYZ” means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as “Acknowledgements”, “Dedications”, “Endorsements”, or “History”.) To “Preserve the Title” of such a section when you modify the Document means that it remains a section “Entitled XYZ” according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated 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 release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section Entitled “Endorsements”, provided it contains nothing but endorsements of your Modified Version by various parties—for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
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 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 added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, 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 replace the old one, on explicit permission from the previous publisher that added the old one.
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 assert or imply endorsement of any Modified Version.
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique 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 unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled “History” in the various original documents, forming one section Entitled “History”; likewise combine any sections Entitled “Acknowledgements”, and any sections Entitled “Dedications”. You must delete all sections Entitled “Endorsements.”
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an “aggregate” if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.
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 of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled “Acknowledgements”, “Dedications”, or “History”, the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
You may not copy, modify, sublicense, or distribute the Document except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License.
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it.
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License “or any later version” applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. If the Document specifies that a proxy can decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document.
“Massive Multiauthor Collaboration Site” (or “MMC Site”) means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server. A “Massive Multiauthor Collaboration” (or “MMC”) contained in the site means any set of copyrightable works thus published on the MMC site.
“CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization.
“Incorporate” means to publish or republish a Document, in whole or in part, as part of another Document.
An MMC is “eligible for relicensing” if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008.
The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing.
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 notices just after the title page:
Copyright (C) year your name. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; 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 Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with...Texts.” line with this:
with the Invariant Sections being list their titles, with the Front-Cover Texts being list, and with the Back-Cover Texts being list.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.
--enable-deterministic-archives
: strip--enable-deterministic-archives
: ranlib--enable-deterministic-archives
: objcopy--enable-deterministic-archives
: ar cmdlineaddr2line
: addr2linear
: arc++filt
: c++filtcxxfilt
: c++filtdlltool
: dlltoolelfedit
: elfeditnm
: nmobjdump
: objdumpranlib
: ranlibreadelf
: readelfsize
: sizestrings
: stringsstrip
: strip[1] MS-DOS does not allow + characters in file names, so on MS-DOS this program is named CXXFILT.