1999-05-03 09:29:11 +02:00
|
|
|
\input texinfo @c -*- Texinfo -*-
|
|
|
|
@setfilename binutils.info
|
2007-10-26 14:00:33 +02:00
|
|
|
@settitle @sc{gnu} Binary Utilities
|
|
|
|
@finalout
|
|
|
|
@synindex ky cp
|
2001-03-13 07:43:59 +01:00
|
|
|
|
2005-11-17 02:01:05 +01:00
|
|
|
@c man begin INCLUDE
|
2007-03-15 15:17:20 +01:00
|
|
|
@include bfdver.texi
|
2005-11-17 02:01:05 +01:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2007-05-22 11:16:39 +02:00
|
|
|
@copying
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin COPYRIGHT
|
2019-01-01 11:31:27 +01:00
|
|
|
Copyright @copyright{} 1991-2019 Free Software Foundation, Inc.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
Permission is granted to copy, distribute and/or modify this document
|
2008-11-19 17:22:48 +01:00
|
|
|
under the terms of the GNU Free Documentation License, Version 1.3
|
2001-03-25 22:32:31 +02:00
|
|
|
or any later version published by the Free Software Foundation;
|
|
|
|
with no Invariant Sections, with no Front-Cover Texts, and with no
|
|
|
|
Back-Cover Texts. A copy of the license is included in the
|
2003-02-21 11:30:35 +01:00
|
|
|
section entitled ``GNU Free Documentation License''.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
2007-05-22 11:16:39 +02:00
|
|
|
@end copying
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2007-10-26 14:00:33 +02:00
|
|
|
@dircategory Software development
|
|
|
|
@direntry
|
|
|
|
* Binutils: (binutils). The GNU binary utilities.
|
|
|
|
@end direntry
|
|
|
|
|
|
|
|
@dircategory Individual utilities
|
|
|
|
@direntry
|
|
|
|
* addr2line: (binutils)addr2line. Convert addresses to file and line.
|
|
|
|
* ar: (binutils)ar. Create, modify, and extract from archives.
|
|
|
|
* c++filt: (binutils)c++filt. Filter to demangle encoded C++ symbols.
|
|
|
|
* cxxfilt: (binutils)c++filt. MS-DOS name for c++filt.
|
|
|
|
* dlltool: (binutils)dlltool. Create files needed to build and use DLLs.
|
|
|
|
* nm: (binutils)nm. List symbols from object files.
|
|
|
|
* objcopy: (binutils)objcopy. Copy and translate object files.
|
|
|
|
* objdump: (binutils)objdump. Display information from object files.
|
|
|
|
* ranlib: (binutils)ranlib. Generate index to archive contents.
|
|
|
|
* readelf: (binutils)readelf. Display the contents of ELF format files.
|
|
|
|
* size: (binutils)size. List section sizes and total size.
|
|
|
|
* strings: (binutils)strings. List printable strings from files.
|
|
|
|
* strip: (binutils)strip. Discard symbols.
|
2018-11-06 18:38:33 +01:00
|
|
|
* elfedit: (binutils)elfedit. Update ELF header and property of ELF files.
|
2007-10-26 14:00:33 +02:00
|
|
|
* windmc: (binutils)windmc. Generator for Windows message resources.
|
|
|
|
* windres: (binutils)windres. Manipulate Windows resources.
|
|
|
|
@end direntry
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@titlepage
|
|
|
|
@title The @sc{gnu} Binary Utilities
|
2007-03-22 22:18:34 +01:00
|
|
|
@ifset VERSION_PACKAGE
|
|
|
|
@subtitle @value{VERSION_PACKAGE}
|
|
|
|
@end ifset
|
1999-05-03 09:29:11 +02:00
|
|
|
@subtitle Version @value{VERSION}
|
|
|
|
@sp 1
|
2004-12-08 03:50:40 +01:00
|
|
|
@subtitle @value{UPDATED}
|
1999-05-03 09:29:11 +02:00
|
|
|
@author Roland H. Pesch
|
|
|
|
@author Jeffrey M. Osier
|
|
|
|
@author Cygnus Support
|
|
|
|
@page
|
|
|
|
|
|
|
|
@tex
|
|
|
|
{\parskip=0pt \hfill Cygnus Support\par \hfill
|
2007-10-26 14:00:33 +02:00
|
|
|
Texinfo \texinfoversion\par }
|
1999-05-03 09:29:11 +02:00
|
|
|
@end tex
|
|
|
|
|
|
|
|
@vskip 0pt plus 1filll
|
2007-10-26 14:00:33 +02:00
|
|
|
@insertcopying
|
1999-05-03 09:29:11 +02:00
|
|
|
@end titlepage
|
2007-03-28 11:08:53 +02:00
|
|
|
@contents
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@node Top
|
|
|
|
@top Introduction
|
|
|
|
|
|
|
|
@cindex version
|
2003-02-21 11:30:35 +01:00
|
|
|
This brief manual contains documentation for the @sc{gnu} binary
|
2007-03-22 22:18:34 +01:00
|
|
|
utilities
|
|
|
|
@ifset VERSION_PACKAGE
|
|
|
|
@value{VERSION_PACKAGE}
|
|
|
|
@end ifset
|
|
|
|
version @value{VERSION}:
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@iftex
|
|
|
|
@table @code
|
|
|
|
@item ar
|
|
|
|
Create, modify, and extract from archives
|
|
|
|
|
|
|
|
@item nm
|
|
|
|
List symbols from object files
|
|
|
|
|
|
|
|
@item objcopy
|
|
|
|
Copy and translate object files
|
|
|
|
|
|
|
|
@item objdump
|
|
|
|
Display information from object files
|
|
|
|
|
|
|
|
@item ranlib
|
|
|
|
Generate index to archive contents
|
|
|
|
|
|
|
|
@item readelf
|
|
|
|
Display the contents of ELF format files.
|
|
|
|
|
|
|
|
@item size
|
|
|
|
List file section sizes and total size
|
|
|
|
|
|
|
|
@item strings
|
|
|
|
List printable strings from files
|
|
|
|
|
|
|
|
@item strip
|
|
|
|
Discard symbols
|
|
|
|
|
2010-01-06 17:52:15 +01:00
|
|
|
@item elfedit
|
2018-11-06 18:38:33 +01:00
|
|
|
Update the ELF header and program property of ELF files.
|
2010-01-06 17:52:15 +01:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item c++filt
|
1999-08-08 20:18:11 +02:00
|
|
|
Demangle encoded C++ symbols (on MS-DOS, this program is named
|
|
|
|
@code{cxxfilt})
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item addr2line
|
|
|
|
Convert addresses into file names and line numbers
|
|
|
|
|
|
|
|
@item windres
|
|
|
|
Manipulate Windows resources
|
|
|
|
|
2007-06-19 15:24:33 +02:00
|
|
|
@item windmc
|
2012-08-17 04:43:21 +02:00
|
|
|
Generator for Windows message resources
|
2007-06-19 15:24:33 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item dlltool
|
|
|
|
Create the files needed to build and use Dynamic Link Libraries
|
|
|
|
@end table
|
|
|
|
@end iftex
|
|
|
|
|
2000-11-06 21:27:26 +01:00
|
|
|
This document is distributed under the terms of the GNU Free
|
2008-11-19 17:22:48 +01:00
|
|
|
Documentation License version 1.3. A copy of the license is included
|
|
|
|
in the section entitled ``GNU Free Documentation License''.
|
2000-11-06 21:27:26 +01:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@menu
|
|
|
|
* ar:: Create, modify, and extract from archives
|
|
|
|
* nm:: List symbols from object files
|
|
|
|
* objcopy:: Copy and translate object files
|
|
|
|
* objdump:: Display information from object files
|
|
|
|
* ranlib:: Generate index to archive contents
|
|
|
|
* size:: List section sizes and total size
|
|
|
|
* strings:: List printable strings from files
|
|
|
|
* strip:: Discard symbols
|
|
|
|
* c++filt:: Filter to demangle encoded C++ symbols
|
1999-08-08 20:18:11 +02:00
|
|
|
* cxxfilt: c++filt. MS-DOS name for c++filt
|
1999-05-03 09:29:11 +02:00
|
|
|
* addr2line:: Convert addresses to file and line
|
2007-06-19 15:24:33 +02:00
|
|
|
* windmc:: Generator for Windows message resources
|
2013-01-07 13:11:13 +01:00
|
|
|
* windres:: Manipulate Windows resources
|
1999-05-03 09:29:11 +02:00
|
|
|
* dlltool:: Create files needed to build and use DLLs
|
2013-01-07 13:11:13 +01:00
|
|
|
* readelf:: Display the contents of ELF format files
|
2018-11-06 18:38:33 +01:00
|
|
|
* elfedit:: Update ELF header and property of ELF files
|
2005-10-03 21:37:44 +02:00
|
|
|
* Common Options:: Command-line options for all utilities
|
2007-11-07 12:36:42 +01:00
|
|
|
* Selecting the Target System:: How these utilities determine the target
|
1999-05-03 09:29:11 +02:00
|
|
|
* Reporting Bugs:: Reporting Bugs
|
2000-11-06 21:27:26 +01:00
|
|
|
* GNU Free Documentation License:: GNU Free Documentation License
|
2008-02-26 09:25:46 +01:00
|
|
|
* Binutils Index:: Binutils Index
|
1999-05-03 09:29:11 +02:00
|
|
|
@end menu
|
|
|
|
|
|
|
|
@node ar
|
|
|
|
@chapter ar
|
|
|
|
|
|
|
|
@kindex ar
|
|
|
|
@cindex archives
|
|
|
|
@cindex collections of files
|
2001-03-25 22:32:31 +02:00
|
|
|
|
|
|
|
@c man title ar create, modify, and extract from archives
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2014-03-12 13:00:27 +01:00
|
|
|
ar [-]@var{p}[@var{mod}] [@option{--plugin} @var{name}] [@option{--target} @var{bfdname}] [@var{relpos}] [@var{count}] @var{archive} [@var{member}@dots{}]
|
1999-05-03 09:29:11 +02:00
|
|
|
ar -M [ <mri-script ]
|
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION ar
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
The @sc{gnu} @command{ar} program creates, modifies, and extracts from
|
1999-05-03 09:29:11 +02:00
|
|
|
archives. An @dfn{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 @dfn{members} of the archive).
|
|
|
|
|
|
|
|
The original files' contents, mode (permissions), timestamp, owner, and
|
|
|
|
group are preserved in the archive, and can be restored on
|
2007-06-29 02:34:14 +02:00
|
|
|
extraction.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@cindex name length
|
2001-08-01 17:54:41 +02:00
|
|
|
@sc{gnu} @command{ar} can maintain archives whose members have names of any
|
|
|
|
length; however, depending on how @command{ar} is configured on your
|
1999-05-03 09:29:11 +02:00
|
|
|
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).
|
|
|
|
|
|
|
|
@cindex libraries
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{ar} is considered a binary utility because archives of this sort
|
1999-05-03 09:29:11 +02:00
|
|
|
are most often used as @dfn{libraries} holding commonly needed
|
|
|
|
subroutines.
|
|
|
|
|
|
|
|
@cindex symbol index
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{ar} creates an index to the symbols defined in relocatable
|
1999-05-03 09:29:11 +02:00
|
|
|
object modules in the archive when you specify the modifier @samp{s}.
|
2001-08-01 17:54:41 +02:00
|
|
|
Once created, this index is updated in the archive whenever @command{ar}
|
1999-05-03 09:29:11 +02:00
|
|
|
makes a change to its contents (save for the @samp{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 @samp{nm -s} or @samp{nm --print-armap} to list this index
|
2001-08-01 17:54:41 +02:00
|
|
|
table. If an archive lacks the table, another form of @command{ar} called
|
|
|
|
@command{ranlib} can be used to add just the table.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2008-03-28 07:49:44 +01:00
|
|
|
@cindex thin archives
|
|
|
|
@sc{gnu} @command{ar} can optionally create a @emph{thin} archive,
|
|
|
|
which contains a symbol index and references to the original copies
|
2013-02-15 15:37:39 +01:00
|
|
|
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 @emph{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 @emph{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.
|
|
|
|
|
2008-03-28 07:49:44 +01:00
|
|
|
The paths to the elements of the archive are stored relative to the
|
2015-09-09 15:33:31 +02:00
|
|
|
archive itself.
|
2008-03-28 07:49:44 +01:00
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@cindex compatibility, @command{ar}
|
|
|
|
@cindex @command{ar} compatibility
|
|
|
|
@sc{gnu} @command{ar} is designed to be compatible with two different
|
1999-05-03 09:29:11 +02:00
|
|
|
facilities. You can control its activity using command-line options,
|
2001-08-01 17:54:41 +02:00
|
|
|
like the different varieties of @command{ar} on Unix systems; or, if you
|
|
|
|
specify the single command-line option @option{-M}, you can control it
|
1999-05-03 09:29:11 +02:00
|
|
|
with a script supplied via standard input, like the MRI ``librarian''
|
|
|
|
program.
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@menu
|
2001-08-01 17:54:41 +02:00
|
|
|
* ar cmdline:: Controlling @command{ar} on the command line
|
|
|
|
* ar scripts:: Controlling @command{ar} with a script
|
1999-05-03 09:29:11 +02:00
|
|
|
@end menu
|
|
|
|
|
|
|
|
@page
|
|
|
|
@node ar cmdline
|
2003-02-21 11:30:35 +01:00
|
|
|
@section Controlling @command{ar} on the Command Line
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS ar
|
2014-03-12 13:00:27 +01:00
|
|
|
ar [@option{-X32_64}] [@option{-}]@var{p}[@var{mod}] [@option{--plugin} @var{name}] [@option{--target} @var{bfdname}] [@var{relpos}] [@var{count}] @var{archive} [@var{member}@dots{}]
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@cindex Unix compatibility, @command{ar}
|
|
|
|
When you use @command{ar} in the Unix style, @command{ar} insists on at least two
|
1999-05-03 09:29:11 +02:00
|
|
|
arguments to execute: one keyletter specifying the @emph{operation}
|
|
|
|
(optionally accompanied by other keyletters specifying
|
|
|
|
@emph{modifiers}), and the archive name to act on.
|
|
|
|
|
|
|
|
Most operations can also accept further @var{member} arguments,
|
|
|
|
specifying particular files to operate on.
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin OPTIONS ar
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@sc{gnu} @command{ar} allows you to mix the operation code @var{p} and modifier
|
1999-05-03 09:29:11 +02:00
|
|
|
flags @var{mod} in any order, within the first command-line argument.
|
|
|
|
|
|
|
|
If you wish, you may begin the first command-line argument with a
|
|
|
|
dash.
|
|
|
|
|
|
|
|
@cindex operations on archive
|
|
|
|
The @var{p} keyletter specifies what operation to execute; it may be
|
|
|
|
any of the following, but you must specify only one of them:
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @samp
|
1999-05-03 09:29:11 +02:00
|
|
|
@item d
|
|
|
|
@cindex deleting from archive
|
|
|
|
@emph{Delete} modules from the archive. Specify the names of modules to
|
|
|
|
be deleted as @var{member}@dots{}; the archive is untouched if you
|
|
|
|
specify no files to delete.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
If you specify the @samp{v} modifier, @command{ar} lists each module
|
1999-05-03 09:29:11 +02:00
|
|
|
as it is deleted.
|
|
|
|
|
|
|
|
@item m
|
|
|
|
@cindex moving in archive
|
|
|
|
Use this operation to @emph{move} members in an archive.
|
|
|
|
|
|
|
|
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
|
2007-06-29 02:34:14 +02:00
|
|
|
than one member.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
If no modifiers are used with @code{m}, any members you name in the
|
|
|
|
@var{member} arguments are moved to the @emph{end} of the archive;
|
|
|
|
you can use the @samp{a}, @samp{b}, or @samp{i} modifiers to move them to a
|
|
|
|
specified place instead.
|
|
|
|
|
|
|
|
@item p
|
|
|
|
@cindex printing from archive
|
|
|
|
@emph{Print} the specified members of the archive, to the standard
|
|
|
|
output file. If the @samp{v} modifier is specified, show the member
|
|
|
|
name before copying its contents to standard output.
|
|
|
|
|
|
|
|
If you specify no @var{member} arguments, all the files in the archive are
|
|
|
|
printed.
|
|
|
|
|
|
|
|
@item q
|
|
|
|
@cindex quick append to archive
|
|
|
|
@emph{Quick append}; Historically, add the files @var{member}@dots{} to the end of
|
|
|
|
@var{archive}, without checking for replacement.
|
|
|
|
|
|
|
|
The modifiers @samp{a}, @samp{b}, and @samp{i} do @emph{not} affect this
|
|
|
|
operation; new members are always placed at the end of the archive.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
The modifier @samp{v} makes @command{ar} list each file as it is appended.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2013-08-23 15:37:06 +02:00
|
|
|
Since the point of this operation is speed, implementations of
|
|
|
|
@command{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 @sc{gnu} @command{ar} will
|
|
|
|
rebuild the table even with a quick append.
|
|
|
|
|
2013-08-23 19:06:44 +02:00
|
|
|
Note - @sc{gnu} @command{ar} treats the command @samp{qs} as a
|
2013-08-23 15:37:06 +02:00
|
|
|
synonym for @samp{r} - replacing already existing files in the
|
|
|
|
archive and appending new ones at the end.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item r
|
|
|
|
@cindex replacement in archive
|
|
|
|
Insert the files @var{member}@dots{} into @var{archive} (with
|
|
|
|
@emph{replacement}). This operation differs from @samp{q} in that any
|
|
|
|
previously existing members are deleted if their names match those being
|
|
|
|
added.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
If one of the files named in @var{member}@dots{} does not exist, @command{ar}
|
1999-05-03 09:29:11 +02:00
|
|
|
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 @samp{a}, @samp{b}, or @samp{i} to request
|
|
|
|
placement relative to some existing member.
|
|
|
|
|
|
|
|
The modifier @samp{v} used with this operation elicits a line of
|
|
|
|
output for each file inserted, along with one of the letters @samp{a} or
|
|
|
|
@samp{r} to indicate whether the file was appended (no old member
|
|
|
|
deleted) or replaced.
|
|
|
|
|
2010-10-29 10:47:02 +02:00
|
|
|
@item s
|
|
|
|
@cindex ranlib
|
|
|
|
Add an index to the archive, or update it if it already exists. Note
|
|
|
|
this command is an exception to the rule that there can only be one
|
|
|
|
command letter, as it is possible to use it as either a command or a
|
|
|
|
modifier. In either case it does the same thing.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item t
|
|
|
|
@cindex contents of archive
|
|
|
|
Display a @emph{table} listing the contents of @var{archive}, or those
|
|
|
|
of the files listed in @var{member}@dots{} that are present in the
|
2018-05-30 18:06:26 +02:00
|
|
|
archive. Normally only the member name is shown, but if the modifier
|
|
|
|
@samp{O} is specified, then the corresponding offset of the member is also
|
|
|
|
displayed. Finally, in order to see the modes (permissions), timestamp,
|
|
|
|
owner, group, and size the @samp{v} modifier should be included.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
If you do not specify a @var{member}, all files in the archive
|
|
|
|
are listed.
|
|
|
|
|
|
|
|
@cindex repeated names in archive
|
|
|
|
@cindex name duplication in archive
|
|
|
|
If there is more than one file with the same name (say, @samp{fie}) in
|
|
|
|
an archive (say @samp{b.a}), @samp{ar t b.a fie} lists only the
|
|
|
|
first instance; to see them all, you must ask for a complete
|
|
|
|
listing---in our example, @samp{ar t b.a}.
|
|
|
|
@c WRS only; per Gumby, this is implementation-dependent, and in a more
|
|
|
|
@c recent case in fact works the other way.
|
|
|
|
|
|
|
|
@item x
|
|
|
|
@cindex extract from archive
|
|
|
|
@emph{Extract} members (named @var{member}) from the archive. You can
|
|
|
|
use the @samp{v} modifier with this operation, to request that
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{ar} list each name as it extracts it.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
If you do not specify a @var{member}, all files in the archive
|
|
|
|
are extracted.
|
|
|
|
|
2008-03-28 07:49:44 +01:00
|
|
|
Files cannot be extracted from a thin archive.
|
1999-05-03 09:29:11 +02:00
|
|
|
@end table
|
|
|
|
|
|
|
|
A number of modifiers (@var{mod}) may immediately follow the @var{p}
|
|
|
|
keyletter, to specify variations on an operation's behavior:
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @samp
|
1999-05-03 09:29:11 +02:00
|
|
|
@item a
|
|
|
|
@cindex relative placement in archive
|
|
|
|
Add new files @emph{after} an existing member of the
|
|
|
|
archive. If you use the modifier @samp{a}, the name of an existing archive
|
|
|
|
member must be present as the @var{relpos} argument, before the
|
|
|
|
@var{archive} specification.
|
|
|
|
|
|
|
|
@item b
|
|
|
|
Add new files @emph{before} an existing member of the
|
|
|
|
archive. If you use the modifier @samp{b}, the name of an existing archive
|
|
|
|
member must be present as the @var{relpos} argument, before the
|
|
|
|
@var{archive} specification. (same as @samp{i}).
|
|
|
|
|
|
|
|
@item c
|
|
|
|
@cindex creating archives
|
|
|
|
@emph{Create} the archive. The specified @var{archive} is always
|
|
|
|
created if it did not exist, when you request an update. But a warning is
|
|
|
|
issued unless you specify in advance that you expect to create it, by
|
|
|
|
using this modifier.
|
|
|
|
|
2009-03-11 05:36:40 +01:00
|
|
|
@item D
|
|
|
|
@cindex deterministic archives
|
2011-12-21 20:39:11 +01:00
|
|
|
@kindex --enable-deterministic-archives
|
2009-03-11 05:36:40 +01:00
|
|
|
Operate in @emph{deterministic} mode. When adding files and the archive
|
|
|
|
index use zero for UIDs, GIDs, timestamps, and use consistent file modes
|
|
|
|
for all files. When this option is used, if @command{ar} is used with
|
|
|
|
identical options and identical input files, multiple runs will create
|
|
|
|
identical output files regardless of the input files' owners, groups,
|
|
|
|
file modes, or modification times.
|
|
|
|
|
2011-12-21 20:39:11 +01:00
|
|
|
If @file{binutils} was configured with
|
|
|
|
@option{--enable-deterministic-archives}, then this mode is on by default.
|
|
|
|
It can be disabled with the @samp{U} modifier, below.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item f
|
2001-08-01 17:54:41 +02:00
|
|
|
Truncate names in the archive. @sc{gnu} @command{ar} will normally permit file
|
1999-05-03 09:29:11 +02:00
|
|
|
names of any length. This will cause it to create archives which are
|
2001-08-01 17:54:41 +02:00
|
|
|
not compatible with the native @command{ar} program on some systems. If
|
1999-05-03 09:29:11 +02:00
|
|
|
this is a concern, the @samp{f} modifier may be used to truncate file
|
|
|
|
names when putting them in the archive.
|
|
|
|
|
|
|
|
@item i
|
|
|
|
Insert new files @emph{before} an existing member of the
|
|
|
|
archive. If you use the modifier @samp{i}, the name of an existing archive
|
|
|
|
member must be present as the @var{relpos} argument, before the
|
|
|
|
@var{archive} specification. (same as @samp{b}).
|
|
|
|
|
|
|
|
@item l
|
|
|
|
This modifier is accepted but not used.
|
|
|
|
@c whaffor ar l modifier??? presumably compat; with
|
2007-06-29 02:34:14 +02:00
|
|
|
@c what???---doc@@cygnus.com, 25jan91
|
1999-05-03 09:29:11 +02:00
|
|
|
|
1999-09-12 20:14:07 +02:00
|
|
|
@item N
|
|
|
|
Uses the @var{count} parameter. This is used if there are multiple
|
|
|
|
entries in the archive with the same name. Extract or delete instance
|
|
|
|
@var{count} of the given name from the archive.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item o
|
|
|
|
@cindex dates in archive
|
|
|
|
Preserve the @emph{original} dates of members when extracting them. If
|
|
|
|
you do not specify this modifier, files extracted from the archive
|
|
|
|
are stamped with the time of extraction.
|
|
|
|
|
2018-05-30 18:06:26 +02:00
|
|
|
@item O
|
|
|
|
@cindex offsets of files
|
|
|
|
Display member offsets inside the archive. Use together with the @samp{t}
|
|
|
|
option.
|
|
|
|
|
1999-09-12 20:14:07 +02:00
|
|
|
@item P
|
|
|
|
Use the full path name when matching names in the archive. @sc{gnu}
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{ar} can not create an archive with a full path name (such archives
|
2019-03-05 18:32:35 +01:00
|
|
|
are not POSIX compliant), but other archive creators can. This option
|
2001-08-01 17:54:41 +02:00
|
|
|
will cause @sc{gnu} @command{ar} to match file names using a complete path
|
1999-09-12 20:14:07 +02:00
|
|
|
name, which can be convenient when extracting a single file from an
|
|
|
|
archive created by another tool.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item s
|
|
|
|
@cindex writing archive index
|
|
|
|
Write an object-file index into the archive, or update an existing one,
|
|
|
|
even if no other change is made to the archive. You may use this modifier
|
|
|
|
flag either with any operation, or alone. Running @samp{ar s} on an
|
|
|
|
archive is equivalent to running @samp{ranlib} on it.
|
|
|
|
|
|
|
|
@item S
|
|
|
|
@cindex not writing archive index
|
|
|
|
Do not generate an archive symbol table. This can speed up building a
|
|
|
|
large library in several steps. The resulting archive can not be used
|
|
|
|
with the linker. In order to build a symbol table, you must omit the
|
|
|
|
@samp{S} modifier on the last execution of @samp{ar}, or you must run
|
|
|
|
@samp{ranlib} on the archive.
|
|
|
|
|
2008-03-28 07:49:44 +01:00
|
|
|
@item T
|
|
|
|
@cindex creating thin archive
|
|
|
|
Make the specified @var{archive} a @emph{thin} archive. If it already
|
|
|
|
exists and is a regular archive, the existing members must be present
|
|
|
|
in the same directory as @var{archive}.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item u
|
|
|
|
@cindex updating an archive
|
|
|
|
Normally, @samp{ar r}@dots{} inserts all files
|
|
|
|
listed into the archive. If you would like to insert @emph{only} those
|
|
|
|
of the files you list that are newer than existing members of the same
|
|
|
|
names, use this modifier. The @samp{u} modifier is allowed only for the
|
|
|
|
operation @samp{r} (replace). In particular, the combination @samp{qu} is
|
|
|
|
not allowed, since checking the timestamps would lose any speed
|
|
|
|
advantage from the operation @samp{q}.
|
|
|
|
|
2011-12-21 20:39:11 +01:00
|
|
|
@item U
|
|
|
|
@cindex deterministic archives
|
|
|
|
@kindex --enable-deterministic-archives
|
|
|
|
Do @emph{not} operate in @emph{deterministic} mode. This is the inverse
|
|
|
|
of the @samp{D} modifier, above: added files and the archive index will
|
|
|
|
get their actual UID, GID, timestamp, and file mode values.
|
|
|
|
|
|
|
|
This is the default unless @file{binutils} was configured with
|
|
|
|
@option{--enable-deterministic-archives}.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item v
|
|
|
|
This modifier requests the @emph{verbose} version of an operation. Many
|
|
|
|
operations display additional information, such as filenames processed,
|
|
|
|
when the modifier @samp{v} is appended.
|
|
|
|
|
|
|
|
@item V
|
2001-08-01 17:54:41 +02:00
|
|
|
This modifier shows the version number of @command{ar}.
|
1999-05-03 09:29:11 +02:00
|
|
|
@end table
|
|
|
|
|
2018-07-02 12:18:24 +02:00
|
|
|
The @command{ar} program also supports some command-line options which
|
2017-01-27 14:20:24 +01:00
|
|
|
are neither modifiers nor actions, but which do change its behaviour
|
|
|
|
in specific ways:
|
|
|
|
|
|
|
|
@table @samp
|
|
|
|
@item --help
|
2018-07-02 12:18:24 +02:00
|
|
|
Displays the list of command-line options supported by @command{ar}
|
2017-01-27 14:20:24 +01:00
|
|
|
and then exits.
|
|
|
|
|
|
|
|
@item --version
|
|
|
|
Displays the version information of @command{ar} and then exits.
|
|
|
|
|
|
|
|
@item -X32_64
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{ar} ignores an initial option spelt @samp{-X32_64}, for
|
2000-07-27 03:39:45 +02:00
|
|
|
compatibility with AIX. The behaviour produced by this option is the
|
2017-01-27 14:20:24 +01:00
|
|
|
default for @sc{gnu} @command{ar}. @command{ar} does not support any
|
|
|
|
of the other @samp{-X} options; in particular, it does not support
|
|
|
|
@option{-X32} which is the default for AIX @command{ar}.
|
2000-07-27 03:39:45 +02:00
|
|
|
|
2017-01-27 14:20:24 +01:00
|
|
|
@item --plugin @var{name}
|
|
|
|
@cindex plugins
|
2018-07-02 12:18:24 +02:00
|
|
|
The optional command-line switch @option{--plugin @var{name}} causes
|
2009-05-26 16:12:03 +02:00
|
|
|
@command{ar} to load the plugin called @var{name} which adds support
|
2017-01-27 14:20:24 +01:00
|
|
|
for more file formats, including object files with link-time
|
|
|
|
optimization information.
|
|
|
|
|
|
|
|
This option is only available if the toolchain has been built with
|
|
|
|
plugin support enabled.
|
|
|
|
|
|
|
|
If @option{--plugin} is not provided, but plugin support has been
|
|
|
|
enabled then @command{ar} iterates over the files in
|
|
|
|
@file{$@{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 @emph{not} the one
|
|
|
|
used by @command{ld}'s @option{-plugin} option. In order to make
|
|
|
|
@command{ar} use the linker plugin it must be copied into the
|
|
|
|
@file{$@{libdir@}/bfd-plugins} directory. For GCC based compilations
|
|
|
|
the linker plugin is called @file{liblto_plugin.so.0.0.0}. For Clang
|
|
|
|
based compilations it is called @file{LLVMgold.so}. The GCC plugin
|
|
|
|
is always backwards compatible with earlier versions, so it is
|
|
|
|
sufficient to just copy the newest one.
|
|
|
|
|
|
|
|
@item --target @var{target}
|
2018-07-02 12:18:24 +02:00
|
|
|
The optional command-line switch @option{--target @var{bfdname}}
|
2011-07-01 17:02:21 +02:00
|
|
|
specifies that the archive members are in an object code format
|
|
|
|
different from your system's default format. See
|
|
|
|
@xref{Target Selection}, for more information.
|
2017-01-27 14:20:24 +01:00
|
|
|
@end table
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO ar
|
|
|
|
nm(1), ranlib(1), and the Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@node ar scripts
|
2003-02-21 11:30:35 +01:00
|
|
|
@section Controlling @command{ar} with a Script
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@smallexample
|
|
|
|
ar -M [ <@var{script} ]
|
|
|
|
@end smallexample
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@cindex MRI compatibility, @command{ar}
|
|
|
|
@cindex scripts, @command{ar}
|
|
|
|
If you use the single command-line option @samp{-M} with @command{ar}, you
|
1999-05-03 09:29:11 +02:00
|
|
|
can control its operation with a rudimentary command language. This
|
2001-08-01 17:54:41 +02:00
|
|
|
form of @command{ar} operates interactively if standard input is coming
|
|
|
|
directly from a terminal. During interactive use, @command{ar} prompts for
|
1999-05-03 09:29:11 +02:00
|
|
|
input (the prompt is @samp{AR >}), and continues executing even after
|
|
|
|
errors. If you redirect standard input to a script file, no prompts are
|
2001-08-01 17:54:41 +02:00
|
|
|
issued, and @command{ar} abandons execution (with a nonzero exit code)
|
1999-05-03 09:29:11 +02:00
|
|
|
on any error.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
The @command{ar} command language is @emph{not} designed to be equivalent
|
1999-05-03 09:29:11 +02:00
|
|
|
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
|
2001-08-01 17:54:41 +02:00
|
|
|
transition to @sc{gnu} @command{ar} for developers who already have scripts
|
1999-05-03 09:29:11 +02:00
|
|
|
written for the MRI ``librarian'' program.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
The syntax for the @command{ar} command language is straightforward:
|
1999-05-03 09:29:11 +02:00
|
|
|
@itemize @bullet
|
|
|
|
@item
|
|
|
|
commands are recognized in upper or lower case; for example, @code{LIST}
|
|
|
|
is the same as @code{list}. In the following descriptions, commands are
|
|
|
|
shown in upper case for clarity.
|
|
|
|
|
|
|
|
@item
|
|
|
|
a single command may appear on each line; it is the first word on the
|
|
|
|
line.
|
|
|
|
|
|
|
|
@item
|
|
|
|
empty lines are allowed, and have no effect.
|
|
|
|
|
|
|
|
@item
|
|
|
|
comments are allowed; text after either of the characters @samp{*}
|
|
|
|
or @samp{;} is ignored.
|
|
|
|
|
|
|
|
@item
|
2001-08-01 17:54:41 +02:00
|
|
|
Whenever you use a list of names as part of the argument to an @command{ar}
|
1999-05-03 09:29:11 +02:00
|
|
|
command, you can separate the individual names with either commas or
|
|
|
|
blanks. Commas are shown in the explanations below, for clarity.
|
|
|
|
|
|
|
|
@item
|
|
|
|
@samp{+} is used as a line continuation character; if @samp{+} appears
|
|
|
|
at the end of a line, the text on the following line is considered part
|
|
|
|
of the current command.
|
|
|
|
@end itemize
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
Here are the commands you can use in @command{ar} scripts, or when using
|
|
|
|
@command{ar} interactively. Three of them have special significance:
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@code{OPEN} or @code{CREATE} specify a @dfn{current archive}, which is
|
|
|
|
a temporary file required for most of the other commands.
|
|
|
|
|
|
|
|
@code{SAVE} commits the changes so far specified by the script. Prior
|
|
|
|
to @code{SAVE}, commands affect only the temporary copy of the current
|
|
|
|
archive.
|
|
|
|
|
|
|
|
@table @code
|
2007-06-29 02:34:14 +02:00
|
|
|
@item ADDLIB @var{archive}
|
1999-05-03 09:29:11 +02:00
|
|
|
@itemx ADDLIB @var{archive} (@var{module}, @var{module}, @dots{} @var{module})
|
|
|
|
Add all the contents of @var{archive} (or, if specified, each named
|
|
|
|
@var{module} from @var{archive}) to the current archive.
|
|
|
|
|
|
|
|
Requires prior use of @code{OPEN} or @code{CREATE}.
|
|
|
|
|
|
|
|
@item ADDMOD @var{member}, @var{member}, @dots{} @var{member}
|
|
|
|
@c FIXME! w/Replacement?? If so, like "ar r @var{archive} @var{names}"
|
|
|
|
@c else like "ar q..."
|
|
|
|
Add each named @var{member} as a module in the current archive.
|
|
|
|
|
|
|
|
Requires prior use of @code{OPEN} or @code{CREATE}.
|
|
|
|
|
|
|
|
@item CLEAR
|
|
|
|
Discard the contents of the current archive, canceling the effect of
|
|
|
|
any operations since the last @code{SAVE}. May be executed (with no
|
|
|
|
effect) even if no current archive is specified.
|
|
|
|
|
|
|
|
@item CREATE @var{archive}
|
|
|
|
Creates an archive, and makes it the current archive (required for many
|
|
|
|
other commands). The new archive is created with a temporary name; it
|
|
|
|
is not actually saved as @var{archive} until you use @code{SAVE}.
|
|
|
|
You can overwrite existing archives; similarly, the contents of any
|
|
|
|
existing file named @var{archive} will not be destroyed until @code{SAVE}.
|
|
|
|
|
|
|
|
@item DELETE @var{module}, @var{module}, @dots{} @var{module}
|
|
|
|
Delete each listed @var{module} from the current archive; equivalent to
|
|
|
|
@samp{ar -d @var{archive} @var{module} @dots{} @var{module}}.
|
|
|
|
|
|
|
|
Requires prior use of @code{OPEN} or @code{CREATE}.
|
|
|
|
|
|
|
|
@item DIRECTORY @var{archive} (@var{module}, @dots{} @var{module})
|
|
|
|
@itemx DIRECTORY @var{archive} (@var{module}, @dots{} @var{module}) @var{outputfile}
|
|
|
|
List each named @var{module} present in @var{archive}. The separate
|
|
|
|
command @code{VERBOSE} specifies the form of the output: when verbose
|
|
|
|
output is off, output is like that of @samp{ar -t @var{archive}
|
|
|
|
@var{module}@dots{}}. When verbose output is on, the listing is like
|
|
|
|
@samp{ar -tv @var{archive} @var{module}@dots{}}.
|
|
|
|
|
|
|
|
Output normally goes to the standard output stream; however, if you
|
2001-08-01 17:54:41 +02:00
|
|
|
specify @var{outputfile} as a final argument, @command{ar} directs the
|
1999-05-03 09:29:11 +02:00
|
|
|
output to that file.
|
|
|
|
|
|
|
|
@item END
|
2001-08-01 17:54:41 +02:00
|
|
|
Exit from @command{ar}, with a @code{0} exit code to indicate successful
|
1999-05-03 09:29:11 +02:00
|
|
|
completion. This command does not save the output file; if you have
|
|
|
|
changed the current archive since the last @code{SAVE} command, those
|
|
|
|
changes are lost.
|
|
|
|
|
|
|
|
@item EXTRACT @var{module}, @var{module}, @dots{} @var{module}
|
|
|
|
Extract each named @var{module} from the current archive, writing them
|
|
|
|
into the current directory as separate files. Equivalent to @samp{ar -x
|
|
|
|
@var{archive} @var{module}@dots{}}.
|
|
|
|
|
|
|
|
Requires prior use of @code{OPEN} or @code{CREATE}.
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c FIXME Tokens but no commands???
|
|
|
|
@item FULLDIR
|
|
|
|
|
|
|
|
@item HELP
|
|
|
|
@end ignore
|
|
|
|
|
|
|
|
@item LIST
|
|
|
|
Display full contents of the current archive, in ``verbose'' style
|
|
|
|
regardless of the state of @code{VERBOSE}. The effect is like @samp{ar
|
2001-08-01 17:54:41 +02:00
|
|
|
tv @var{archive}}. (This single command is a @sc{gnu} @command{ar}
|
1999-05-03 09:29:11 +02:00
|
|
|
enhancement, rather than present for MRI compatibility.)
|
|
|
|
|
|
|
|
Requires prior use of @code{OPEN} or @code{CREATE}.
|
|
|
|
|
|
|
|
@item OPEN @var{archive}
|
|
|
|
Opens an existing archive for use as the current archive (required for
|
|
|
|
many other commands). Any changes as the result of subsequent commands
|
|
|
|
will not actually affect @var{archive} until you next use @code{SAVE}.
|
|
|
|
|
|
|
|
@item REPLACE @var{module}, @var{module}, @dots{} @var{module}
|
|
|
|
In the current archive, replace each existing @var{module} (named in
|
|
|
|
the @code{REPLACE} arguments) from files in the current working directory.
|
|
|
|
To execute this command without errors, both the file, and the module in
|
2007-06-29 02:34:14 +02:00
|
|
|
the current archive, must exist.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
Requires prior use of @code{OPEN} or @code{CREATE}.
|
|
|
|
|
|
|
|
@item VERBOSE
|
|
|
|
Toggle an internal flag governing the output from @code{DIRECTORY}.
|
|
|
|
When the flag is on, @code{DIRECTORY} output matches output from
|
|
|
|
@samp{ar -tv }@dots{}.
|
|
|
|
|
|
|
|
@item SAVE
|
|
|
|
Commit your changes to the current archive, and actually save it as a
|
|
|
|
file with the name specified in the last @code{CREATE} or @code{OPEN}
|
2007-06-29 02:34:14 +02:00
|
|
|
command.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
Requires prior use of @code{OPEN} or @code{CREATE}.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@iftex
|
|
|
|
@node ld
|
|
|
|
@chapter ld
|
|
|
|
@cindex linker
|
|
|
|
@kindex ld
|
2001-08-01 17:54:41 +02:00
|
|
|
The @sc{gnu} linker @command{ld} is now described in a separate manual.
|
1999-05-03 09:29:11 +02:00
|
|
|
@xref{Top,, Overview,, Using LD: the @sc{gnu} linker}.
|
|
|
|
@end iftex
|
|
|
|
|
|
|
|
@node nm
|
|
|
|
@chapter nm
|
|
|
|
@cindex symbols
|
|
|
|
@kindex nm
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man title nm list symbols from object files
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS nm
|
2012-09-06 17:41:30 +02:00
|
|
|
nm [@option{-A}|@option{-o}|@option{--print-file-name}] [@option{-a}|@option{--debug-syms}]
|
|
|
|
[@option{-B}|@option{--format=bsd}] [@option{-C}|@option{--demangle}[=@var{style}]]
|
|
|
|
[@option{-D}|@option{--dynamic}] [@option{-f}@var{format}|@option{--format=}@var{format}]
|
|
|
|
[@option{-g}|@option{--extern-only}] [@option{-h}|@option{--help}]
|
2017-03-21 14:05:19 +01:00
|
|
|
[@option{-l}|@option{--line-numbers}] [@option{--inlines}]
|
|
|
|
[@option{-n}|@option{-v}|@option{--numeric-sort}]
|
2012-09-06 17:41:30 +02:00
|
|
|
[@option{-P}|@option{--portability}] [@option{-p}|@option{--no-sort}]
|
|
|
|
[@option{-r}|@option{--reverse-sort}] [@option{-S}|@option{--print-size}]
|
|
|
|
[@option{-s}|@option{--print-armap}] [@option{-t} @var{radix}|@option{--radix=}@var{radix}]
|
|
|
|
[@option{-u}|@option{--undefined-only}] [@option{-V}|@option{--version}]
|
|
|
|
[@option{-X 32_64}] [@option{--defined-only}] [@option{--no-demangle}]
|
2018-12-07 12:32:55 +01:00
|
|
|
[@option{--plugin} @var{name}]
|
|
|
|
[@option{--no-recurse-limit}|@option{--recurse-limit}]]
|
|
|
|
[@option{--size-sort}] [@option{--special-syms}]
|
2016-11-11 12:49:45 +01:00
|
|
|
[@option{--synthetic}] [@option{--with-symbol-versions}] [@option{--target=}@var{bfdname}]
|
2012-09-06 17:41:30 +02:00
|
|
|
[@var{objfile}@dots{}]
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION nm
|
2001-08-01 17:54:41 +02:00
|
|
|
@sc{gnu} @command{nm} lists the symbols from object files @var{objfile}@dots{}.
|
|
|
|
If no object files are listed as arguments, @command{nm} assumes the file
|
1999-05-03 09:29:11 +02:00
|
|
|
@file{a.out}.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
For each symbol, @command{nm} shows:
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@itemize @bullet
|
|
|
|
@item
|
|
|
|
The symbol value, in the radix selected by options (see below), or
|
|
|
|
hexadecimal by default.
|
|
|
|
|
|
|
|
@item
|
|
|
|
The symbol type. At least the following types are used; others are, as
|
|
|
|
well, depending on the object file format. If lowercase, the symbol is
|
2011-05-18 18:35:03 +02:00
|
|
|
usually local; if uppercase, the symbol is global (external). There
|
|
|
|
are however a few lowercase symbols that are shown for special global
|
|
|
|
symbols (@code{u}, @code{v} and @code{w}).
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@c Some more detail on exactly what these symbol types are used for
|
|
|
|
@c would be nice.
|
|
|
|
@table @code
|
|
|
|
@item A
|
|
|
|
The symbol's value is absolute, and will not be changed by further
|
|
|
|
linking.
|
|
|
|
|
|
|
|
@item B
|
2007-09-17 11:58:27 +02:00
|
|
|
@itemx b
|
2018-01-30 18:22:41 +01:00
|
|
|
The symbol is in the BSS data section. This section typically
|
|
|
|
contains zero-initialized or uninitialized data, although the exact
|
|
|
|
behavior is system dependent.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item C
|
|
|
|
The symbol is common. Common symbols are uninitialized data. When
|
|
|
|
linking, multiple common symbols may appear with the same name. If the
|
|
|
|
symbol is defined anywhere, the common symbols are treated as undefined
|
2001-03-25 22:32:31 +02:00
|
|
|
references.
|
|
|
|
@ifclear man
|
|
|
|
For more details on common symbols, see the discussion of
|
1999-05-03 09:29:11 +02:00
|
|
|
--warn-common in @ref{Options,,Linker options,ld.info,The GNU linker}.
|
2001-03-26 09:02:59 +02:00
|
|
|
@end ifclear
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item D
|
2007-09-17 11:58:27 +02:00
|
|
|
@itemx d
|
1999-05-03 09:29:11 +02:00
|
|
|
The symbol is in the initialized data section.
|
|
|
|
|
|
|
|
@item G
|
2007-09-17 11:58:27 +02:00
|
|
|
@itemx g
|
1999-05-03 09:29:11 +02:00
|
|
|
The symbol is in an initialized data section for small objects. Some
|
|
|
|
object file formats permit more efficient access to small data objects,
|
|
|
|
such as a global int variable as opposed to a large global array.
|
|
|
|
|
2007-09-17 11:58:27 +02:00
|
|
|
@item i
|
2009-07-23 15:00:30 +02:00
|
|
|
For PE format files this indicates that the symbol is in a section
|
|
|
|
specific to the implementation of DLLs. For ELF format files this
|
|
|
|
indicates that the symbol is an indirect function. This is a GNU
|
|
|
|
extension to the standard set of ELF symbol types. It indicates a
|
|
|
|
symbol which if referenced by a relocation does not evaluate to its
|
|
|
|
address, but instead must be invoked at runtime. The runtime
|
|
|
|
execution will then return the value to be used in the relocation.
|
2007-09-17 11:58:27 +02:00
|
|
|
|
2013-08-23 16:12:39 +02:00
|
|
|
@item I
|
|
|
|
The symbol is an indirect reference to another symbol.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item N
|
|
|
|
The symbol is a debugging symbol.
|
|
|
|
|
2019-08-15 16:23:18 +02:00
|
|
|
@item n
|
|
|
|
The symbol is in the read-only data section.
|
|
|
|
|
2007-09-17 11:58:27 +02:00
|
|
|
@item p
|
2019-08-15 16:23:18 +02:00
|
|
|
The symbol is in a stack unwind section.
|
2007-09-17 11:58:27 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item R
|
2007-09-17 11:58:27 +02:00
|
|
|
@itemx r
|
1999-05-03 09:29:11 +02:00
|
|
|
The symbol is in a read only data section.
|
|
|
|
|
|
|
|
@item S
|
2007-09-17 11:58:27 +02:00
|
|
|
@itemx s
|
2018-01-30 18:22:41 +01:00
|
|
|
The symbol is in an uninitialized or zero-initialized data section
|
|
|
|
for small objects.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item T
|
2007-09-17 11:58:27 +02:00
|
|
|
@itemx t
|
1999-05-03 09:29:11 +02:00
|
|
|
The symbol is in the text (code) section.
|
|
|
|
|
|
|
|
@item U
|
|
|
|
The symbol is undefined.
|
|
|
|
|
2009-07-23 15:00:30 +02:00
|
|
|
@item u
|
|
|
|
The symbol is a unique global symbol. This is a GNU extension to the
|
|
|
|
standard set of ELF symbol bindings. For such a symbol the dynamic linker
|
|
|
|
will make sure that in the entire process there is just one symbol with
|
|
|
|
this name and type in use.
|
|
|
|
|
2000-01-28 02:06:37 +01:00
|
|
|
@item V
|
2007-09-17 11:58:27 +02:00
|
|
|
@itemx v
|
2000-01-28 02:06:37 +01:00
|
|
|
The symbol is a weak object. When a weak defined symbol is linked with
|
|
|
|
a normal defined symbol, the normal defined symbol is used with no error.
|
|
|
|
When a weak undefined symbol is linked and the symbol is not defined,
|
2007-09-17 11:58:27 +02:00
|
|
|
the value of the weak symbol becomes zero with no error. On some
|
|
|
|
systems, uppercase indicates that a default value has been specified.
|
2000-01-28 02:06:37 +01:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item W
|
2007-09-17 11:58:27 +02:00
|
|
|
@itemx w
|
2000-01-28 02:06:37 +01:00
|
|
|
The symbol is a weak symbol that has not been specifically tagged as a
|
|
|
|
weak object symbol. When a weak defined symbol is linked with a normal
|
|
|
|
defined symbol, the normal defined symbol is used with no error.
|
|
|
|
When a weak undefined symbol is linked and the symbol is not defined,
|
2004-07-03 18:07:51 +02:00
|
|
|
the value of the symbol is determined in a system-specific manner without
|
2007-06-29 02:34:14 +02:00
|
|
|
error. On some systems, uppercase indicates that a default value has been
|
2004-11-08 09:12:53 +01:00
|
|
|
specified.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -
|
|
|
|
The symbol is a stabs symbol in an a.out object file. In this case, the
|
|
|
|
next values printed are the stabs other field, the stabs desc field, and
|
2001-08-01 17:54:41 +02:00
|
|
|
the stab type. Stabs symbols are used to hold debugging information.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item ?
|
|
|
|
The symbol type is unknown, or object file format specific.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item
|
|
|
|
The symbol name.
|
|
|
|
@end itemize
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS nm
|
1999-05-03 09:29:11 +02:00
|
|
|
The long and short forms of options, shown here as alternatives, are
|
|
|
|
equivalent.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @env
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -A
|
|
|
|
@itemx -o
|
2007-06-29 02:34:14 +02:00
|
|
|
@itemx --print-file-name
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex input file name
|
|
|
|
@cindex file name
|
|
|
|
@cindex source file name
|
1999-10-08 15:56:33 +02:00
|
|
|
Precede each symbol by the name of the input file (or archive member)
|
1999-05-03 09:29:11 +02:00
|
|
|
in which it was found, rather than identifying the input file once only,
|
|
|
|
before all of its symbols.
|
|
|
|
|
|
|
|
@item -a
|
2007-06-29 02:34:14 +02:00
|
|
|
@itemx --debug-syms
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex debugging symbols
|
|
|
|
Display all symbols, even debugger-only symbols; normally these are not
|
|
|
|
listed.
|
|
|
|
|
|
|
|
@item -B
|
2001-08-01 17:54:41 +02:00
|
|
|
@cindex @command{nm} format
|
|
|
|
@cindex @command{nm} compatibility
|
|
|
|
The same as @option{--format=bsd} (for compatibility with the MIPS @command{nm}).
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -C
|
2000-07-20 20:02:56 +02:00
|
|
|
@itemx --demangle[=@var{style}]
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex demangling in nm
|
|
|
|
Decode (@dfn{demangle}) low-level symbol names into user-level names.
|
|
|
|
Besides removing any initial underscore prepended by the system, this
|
2000-07-20 20:02:56 +02:00
|
|
|
makes C++ function names readable. Different compilers have different
|
2007-06-29 02:34:14 +02:00
|
|
|
mangling styles. The optional demangling style argument can be used to
|
|
|
|
choose an appropriate demangling style for your compiler. @xref{c++filt},
|
2000-07-20 20:02:56 +02:00
|
|
|
for more information on demangling.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --no-demangle
|
|
|
|
Do not demangle low-level symbol names. This is the default.
|
|
|
|
|
2018-12-07 12:32:55 +01:00
|
|
|
@item --recurse-limit
|
|
|
|
@itemx --no-recurse-limit
|
|
|
|
@itemx --recursion-limit
|
|
|
|
@itemx --no-recursion-limit
|
|
|
|
Enables or disables a limit on the amount of recursion performed
|
|
|
|
whilst demangling strings. Since the name mangling formats allow for
|
|
|
|
an inifinite level of recursion it is possible to create strings whose
|
|
|
|
decoding will exhaust the amount of stack space available on the host
|
|
|
|
machine, triggering a memory fault. The limit tries to prevent this
|
2018-12-11 13:01:15 +01:00
|
|
|
from happening by restricting recursion to 2048 levels of nesting.
|
2018-12-07 12:32:55 +01:00
|
|
|
|
|
|
|
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.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -D
|
|
|
|
@itemx --dynamic
|
|
|
|
@cindex dynamic symbols
|
|
|
|
Display the dynamic symbols rather than the normal symbols. This is
|
|
|
|
only meaningful for dynamic objects, such as certain types of shared
|
|
|
|
libraries.
|
|
|
|
|
|
|
|
@item -f @var{format}
|
|
|
|
@itemx --format=@var{format}
|
2001-08-01 17:54:41 +02:00
|
|
|
@cindex @command{nm} format
|
|
|
|
@cindex @command{nm} compatibility
|
1999-05-03 09:29:11 +02:00
|
|
|
Use the output format @var{format}, which can be @code{bsd},
|
|
|
|
@code{sysv}, or @code{posix}. The default is @code{bsd}.
|
|
|
|
Only the first character of @var{format} is significant; it can be
|
|
|
|
either upper or lower case.
|
|
|
|
|
|
|
|
@item -g
|
2007-06-29 02:34:14 +02:00
|
|
|
@itemx --extern-only
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex external symbols
|
|
|
|
Display only external symbols.
|
|
|
|
|
2012-09-06 17:41:30 +02:00
|
|
|
@item -h
|
|
|
|
@itemx --help
|
|
|
|
Show a summary of the options to @command{nm} and exit.
|
2009-05-26 16:12:03 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -l
|
|
|
|
@itemx --line-numbers
|
|
|
|
@cindex symbol line numbers
|
|
|
|
For each symbol, use debugging information to try to find a filename and
|
|
|
|
line number. For a defined symbol, look for the line number of the
|
|
|
|
address of the symbol. For an undefined symbol, look for the line
|
|
|
|
number of a relocation entry which refers to the symbol. If line number
|
|
|
|
information can be found, print it after the other symbol information.
|
|
|
|
|
2017-03-21 14:05:19 +01:00
|
|
|
@item --inlines
|
|
|
|
@cindex objdump inlines
|
|
|
|
When option @option{-l} is active, if the address belongs to a
|
|
|
|
function that was inlined, then this option causes the source
|
|
|
|
information for all enclosing scopes back to the first non-inlined
|
|
|
|
function to be printed as well. For example, if @code{main} inlines
|
|
|
|
@code{callee1} which inlines @code{callee2}, and address is from
|
|
|
|
@code{callee2}, the source information for @code{callee1} and @code{main}
|
|
|
|
will also be printed.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -n
|
|
|
|
@itemx -v
|
2007-06-29 02:34:14 +02:00
|
|
|
@itemx --numeric-sort
|
1999-05-03 09:29:11 +02:00
|
|
|
Sort symbols numerically by their addresses, rather than alphabetically
|
2007-06-29 02:34:14 +02:00
|
|
|
by their names.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -p
|
2007-06-29 02:34:14 +02:00
|
|
|
@itemx --no-sort
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex sorting symbols
|
|
|
|
Do not bother to sort the symbols in any order; print them in the order
|
|
|
|
encountered.
|
|
|
|
|
|
|
|
@item -P
|
|
|
|
@itemx --portability
|
|
|
|
Use the POSIX.2 standard output format instead of the default format.
|
|
|
|
Equivalent to @samp{-f posix}.
|
|
|
|
|
2012-09-06 17:41:30 +02:00
|
|
|
@item -r
|
|
|
|
@itemx --reverse-sort
|
|
|
|
Reverse the order of the sort (whether numeric or alphabetic); let the
|
|
|
|
last come first.
|
|
|
|
|
2002-06-15 20:40:26 +02:00
|
|
|
@item -S
|
|
|
|
@itemx --print-size
|
2009-06-01 03:50:45 +02:00
|
|
|
Print both value and size of defined symbols for the @code{bsd} output style.
|
|
|
|
This option has no effect for object formats that do not record symbol
|
|
|
|
sizes, unless @samp{--size-sort} is also used in which case a
|
|
|
|
calculated size is displayed.
|
2002-06-15 20:40:26 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -s
|
|
|
|
@itemx --print-armap
|
|
|
|
@cindex symbol index, listing
|
|
|
|
When listing symbols from archive members, include the index: a mapping
|
2001-08-01 17:54:41 +02:00
|
|
|
(stored in the archive by @command{ar} or @command{ranlib}) of which modules
|
1999-05-03 09:29:11 +02:00
|
|
|
contain definitions for which names.
|
|
|
|
|
2012-09-06 17:41:30 +02:00
|
|
|
@item -t @var{radix}
|
|
|
|
@itemx --radix=@var{radix}
|
|
|
|
Use @var{radix} as the radix for printing the symbol values. It must be
|
|
|
|
@samp{d} for decimal, @samp{o} for octal, or @samp{x} for hexadecimal.
|
|
|
|
|
|
|
|
@item -u
|
|
|
|
@itemx --undefined-only
|
|
|
|
@cindex external symbols
|
|
|
|
@cindex undefined symbols
|
|
|
|
Display only undefined symbols (those external to each object file).
|
|
|
|
|
|
|
|
@item -V
|
|
|
|
@itemx --version
|
|
|
|
Show the version number of @command{nm} and exit.
|
|
|
|
|
|
|
|
@item -X
|
|
|
|
This option is ignored for compatibility with the AIX version of
|
|
|
|
@command{nm}. It takes one parameter which must be the string
|
|
|
|
@option{32_64}. The default mode of AIX @command{nm} corresponds
|
|
|
|
to @option{-X 32}, which is not supported by @sc{gnu} @command{nm}.
|
|
|
|
|
|
|
|
@item --defined-only
|
|
|
|
@cindex external symbols
|
|
|
|
@cindex undefined symbols
|
|
|
|
Display only defined symbols for each object file.
|
|
|
|
|
|
|
|
@item --plugin @var{name}
|
2017-01-27 14:20:24 +01:00
|
|
|
@cindex plugins
|
2012-09-06 17:41:30 +02:00
|
|
|
Load the plugin called @var{name} to add support for extra target
|
|
|
|
types. This option is only available if the toolchain has been built
|
|
|
|
with plugin support enabled.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2017-01-27 14:20:24 +01:00
|
|
|
If @option{--plugin} is not provided, but plugin support has been
|
|
|
|
enabled then @command{nm} iterates over the files in
|
|
|
|
@file{$@{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 @emph{not} the one
|
|
|
|
used by @command{ld}'s @option{-plugin} option. In order to make
|
|
|
|
@command{nm} use the linker plugin it must be copied into the
|
|
|
|
@file{$@{libdir@}/bfd-plugins} directory. For GCC based compilations
|
|
|
|
the linker plugin is called @file{liblto_plugin.so.0.0.0}. For Clang
|
|
|
|
based compilations it is called @file{LLVMgold.so}. The GCC plugin
|
|
|
|
is always backwards compatible with earlier versions, so it is
|
|
|
|
sufficient to just copy the newest one.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --size-sort
|
2016-04-29 14:22:51 +02:00
|
|
|
Sort symbols by size. For ELF objects symbol sizes are read from the
|
|
|
|
ELF, for other object types the symbol sizes are computed as the
|
|
|
|
difference between the value of the symbol and the value of the symbol
|
|
|
|
with the next higher value. If the @code{bsd} output format is used
|
|
|
|
the size of the symbol is printed, rather than the value, and
|
|
|
|
@samp{-S} must be used in order both size and value to be printed.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2004-10-08 16:54:04 +02:00
|
|
|
@item --special-syms
|
|
|
|
Display symbols which have a target-specific special meaning. These
|
|
|
|
symbols are usually used by the target for some special processing and
|
2013-08-23 16:22:39 +02:00
|
|
|
are not normally helpful when included in the normal symbol lists.
|
|
|
|
For example for ARM targets this option would skip the mapping symbols
|
|
|
|
used to mark transitions between ARM code, THUMB code and data.
|
2004-10-08 16:54:04 +02:00
|
|
|
|
2012-09-06 17:41:30 +02:00
|
|
|
@item --synthetic
|
|
|
|
Include synthetic symbols in the output. These are special symbols
|
|
|
|
created by the linker for various purposes. They are not shown by
|
|
|
|
default since they are not part of the binary's original source code.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2016-11-11 12:49:45 +01:00
|
|
|
@item --with-symbol-versions
|
|
|
|
Enables the display of symbol version information if any exists. The
|
|
|
|
version string is displayed as a suffix to the symbol name, preceeded by
|
|
|
|
an @@ character. For example @samp{foo@@VER_1}. If the version is
|
|
|
|
the default version to be used when resolving unversioned references
|
|
|
|
to the symbol then it is displayed as a suffix preceeded by two @@
|
|
|
|
characters. For example @samp{foo@@@@VER_2}.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --target=@var{bfdname}
|
|
|
|
@cindex object code format
|
|
|
|
Specify an object code format other than your system's default format.
|
|
|
|
@xref{Target Selection}, for more information.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO nm
|
|
|
|
ar(1), objdump(1), ranlib(1), and the Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@node objcopy
|
|
|
|
@chapter objcopy
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man title objcopy copy and translate object files
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS objcopy
|
2001-08-01 17:54:41 +02:00
|
|
|
objcopy [@option{-F} @var{bfdname}|@option{--target=}@var{bfdname}]
|
|
|
|
[@option{-I} @var{bfdname}|@option{--input-target=}@var{bfdname}]
|
|
|
|
[@option{-O} @var{bfdname}|@option{--output-target=}@var{bfdname}]
|
|
|
|
[@option{-B} @var{bfdarch}|@option{--binary-architecture=}@var{bfdarch}]
|
2003-06-12 09:23:31 +02:00
|
|
|
[@option{-S}|@option{--strip-all}]
|
|
|
|
[@option{-g}|@option{--strip-debug}]
|
2017-12-01 08:10:55 +01:00
|
|
|
[@option{--strip-unneeded}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-K} @var{symbolname}|@option{--keep-symbol=}@var{symbolname}]
|
|
|
|
[@option{-N} @var{symbolname}|@option{--strip-symbol=}@var{symbolname}]
|
2004-12-16 14:16:33 +01:00
|
|
|
[@option{--strip-unneeded-symbol=}@var{symbolname}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-G} @var{symbolname}|@option{--keep-global-symbol=}@var{symbolname}]
|
2006-06-23 18:23:09 +02:00
|
|
|
[@option{--localize-hidden}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-L} @var{symbolname}|@option{--localize-symbol=}@var{symbolname}]
|
2005-03-15 18:45:19 +01:00
|
|
|
[@option{--globalize-symbol=}@var{symbolname}]
|
2018-10-11 12:38:10 +02:00
|
|
|
[@option{--globalize-symbols=}@var{filename}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-W} @var{symbolname}|@option{--weaken-symbol=}@var{symbolname}]
|
2003-11-11 18:50:26 +01:00
|
|
|
[@option{-w}|@option{--wildcard}]
|
2003-06-12 09:23:31 +02:00
|
|
|
[@option{-x}|@option{--discard-all}]
|
|
|
|
[@option{-X}|@option{--discard-locals}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-b} @var{byte}|@option{--byte=}@var{byte}]
|
2010-09-10 14:11:28 +02:00
|
|
|
[@option{-i} [@var{breadth}]|@option{--interleave}[=@var{breadth}]]
|
|
|
|
[@option{--interleave-width=}@var{width}]
|
2013-02-15 10:32:31 +01:00
|
|
|
[@option{-j} @var{sectionpattern}|@option{--only-section=}@var{sectionpattern}]
|
|
|
|
[@option{-R} @var{sectionpattern}|@option{--remove-section=}@var{sectionpattern}]
|
objcopy/strip: Add option --remove-relocations=SECTIONPATTERN
The objcopy and strip tools make use of the bfd library to manipulate
the state of the input file (to produce an output file). Within the
input file (for ELF at least), relocations are held within a section,
and so, if the user wanted to remove the relocations, but keep the
section to which the relocations would have been applied, it is tempting
to think that specifying the name of a relocation section to objcopy's
--remove-section option might do what you want, for example:
objcopy --remove-section=.rela.text input.elf output.elf
However, this does not work. The reason is that when the input file is
loaded, relocations are not managed as sections, but are, instead,
loaded as data associated with the section to which the relocations
would be applied. In our example above the relocations in '.rela.text'
are held as data on the section '.text' once 'input.elf' is loaded.
One task that objcopy and strip do is copy the relocations from the
input file to the output file if the section is also being copied from
the input file to the output file.
This commit adds a new command line option for objcopy and strip,
--remove-relocations, which can be used to remove the relocations, while
keeping the section that the relocations would have been applied to, for
example:
objcopy --remove-relocations=.text input.elf output.elf
in this case the section '.text' will appear in both 'input.elf' and
'output.elf', but any relocations in 'input.elf' that apply to '.text'
will not be present in 'output.elf'.
I have also added a special case to the handling of --remove-section
that spots if a user tries to remove a relocation section (currently
this is done by spotting the '.rela.' or '.rel.' prefix) and forwards
the request to --remove-relocations.
As with --remove-section and --only-section the --remove-relocations
option supports the '!' prefix on the section-patterns it takes to allow
for sections to be specifically not matched.
There are tests for all the new functionality.
binutils/ChangeLog:
* doc/binutils.texi (objcopy): Document 'remove-relocations'.
(strip): Likewise.
* objcopy.c (SECTION_CONTEXT_REMOVE_RELOCS): Define.
(enum command_line_switch): Add 'OPTION_REMOVE_RELOCS'.
(struct option strip_options): Add 'remove-relocations'.
(struct option copy_options): Likewise.
(copy_usage): Likewise.
(strip_usage): Likewise.
(handle_remove_relocations_option): New function.
(discard_relocations): New function.
(handle_remove_section_option): New function.
(copy_relocations_in_section): Use discard_relocations.
(strip_main): Use handle_remove_section_option for
'remove-section', and handle 'remove-relocations' option.
(copy_main): Likewise.
* testsuite/binutils-all/objcopy.exp: Run new tests.
* testsuite/binutils-all/remove-relocs-01.d: New file.
* testsuite/binutils-all/remove-relocs-01.s: New file.
* testsuite/binutils-all/remove-relocs-02.d: New file.
* testsuite/binutils-all/remove-relocs-03.d: New file.
* testsuite/binutils-all/remove-relocs-04.d: New file.
* testsuite/binutils-all/remove-relocs-05.d: New file.
* testsuite/binutils-all/remove-relocs-06.d: New file.
2015-08-21 21:08:26 +02:00
|
|
|
[@option{--remove-relocations=}@var{sectionpattern}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-p}|@option{--preserve-dates}]
|
2012-04-25 19:50:14 +02:00
|
|
|
[@option{-D}|@option{--enable-deterministic-archives}]
|
2013-01-07 18:40:59 +01:00
|
|
|
[@option{-U}|@option{--disable-deterministic-archives}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{--debugging}]
|
2003-06-12 09:23:31 +02:00
|
|
|
[@option{--gap-fill=}@var{val}]
|
|
|
|
[@option{--pad-to=}@var{address}]
|
|
|
|
[@option{--set-start=}@var{val}]
|
|
|
|
[@option{--adjust-start=}@var{incr}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{--change-addresses=}@var{incr}]
|
2013-02-15 10:32:31 +01:00
|
|
|
[@option{--change-section-address} @var{sectionpattern}@{=,+,-@}@var{val}]
|
|
|
|
[@option{--change-section-lma} @var{sectionpattern}@{=,+,-@}@var{val}]
|
|
|
|
[@option{--change-section-vma} @var{sectionpattern}@{=,+,-@}@var{val}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{--change-warnings}] [@option{--no-change-warnings}]
|
2013-02-15 10:32:31 +01:00
|
|
|
[@option{--set-section-flags} @var{sectionpattern}=@var{flags}]
|
2019-08-28 13:33:41 +02:00
|
|
|
[@option{--set-section-alignment} @var{sectionpattern}=@var{align}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{--add-section} @var{sectionname}=@var{filename}]
|
2013-12-31 10:52:24 +01:00
|
|
|
[@option{--dump-section} @var{sectionname}=@var{filename}]
|
2015-02-13 18:04:42 +01:00
|
|
|
[@option{--update-section} @var{sectionname}=@var{filename}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{--rename-section} @var{oldname}=@var{newname}[,@var{flags}]]
|
2009-04-14 11:47:44 +02:00
|
|
|
[@option{--long-section-names} @{enable,disable,keep@}]
|
2003-06-12 09:23:31 +02:00
|
|
|
[@option{--change-leading-char}] [@option{--remove-leading-char}]
|
2007-04-23 12:59:07 +02:00
|
|
|
[@option{--reverse-bytes=}@var{num}]
|
2003-06-12 09:23:31 +02:00
|
|
|
[@option{--srec-len=}@var{ival}] [@option{--srec-forceS3}]
|
|
|
|
[@option{--redefine-sym} @var{old}=@var{new}]
|
|
|
|
[@option{--redefine-syms=}@var{filename}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{--weaken}]
|
|
|
|
[@option{--keep-symbols=}@var{filename}]
|
|
|
|
[@option{--strip-symbols=}@var{filename}]
|
2004-12-16 14:16:33 +01:00
|
|
|
[@option{--strip-unneeded-symbols=}@var{filename}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{--keep-global-symbols=}@var{filename}]
|
|
|
|
[@option{--localize-symbols=}@var{filename}]
|
|
|
|
[@option{--weaken-symbols=}@var{filename}]
|
2018-02-20 14:33:15 +01:00
|
|
|
[@option{--add-symbol} @var{name}=[@var{section}:]@var{value}[,@var{flags}]]
|
2002-12-14 22:17:41 +01:00
|
|
|
[@option{--alt-machine-code=}@var{index}]
|
|
|
|
[@option{--prefix-symbols=}@var{string}]
|
|
|
|
[@option{--prefix-sections=}@var{string}]
|
|
|
|
[@option{--prefix-alloc-sections=}@var{string}]
|
2003-06-26 10:14:10 +02:00
|
|
|
[@option{--add-gnu-debuglink=}@var{path-to-file}]
|
2005-11-15 09:33:38 +01:00
|
|
|
[@option{--keep-file-symbols}]
|
2003-06-26 10:14:10 +02:00
|
|
|
[@option{--only-keep-debug}]
|
2012-05-08 19:49:36 +02:00
|
|
|
[@option{--strip-dwo}]
|
|
|
|
[@option{--extract-dwo}]
|
2007-03-01 17:39:42 +01:00
|
|
|
[@option{--extract-symbol}]
|
2003-12-23 14:01:11 +01:00
|
|
|
[@option{--writable-text}]
|
|
|
|
[@option{--readonly-text}]
|
|
|
|
[@option{--pure}]
|
|
|
|
[@option{--impure}]
|
bfd/
2009-04-17 H.J. Lu <hongjiu.lu@intel.com>
PR binutils/10074
* coffcode.h (bfd_pei_p): New.
* config.bfd: Remove bfd_efi_bsdrv_ia32_vec,
bfd_efi_rtdrv_ia32_vec, bfd_efi_bsdrv_x86_64_vec,
bfd_efi_rtdrv_x86_64_vec, bfd_efi_bsdrv_ia64_vec and
bfd_efi_rtdrv_ia64_vec. Replace bfd_efi_app_ia32_vec,
bfd_efi_app_x86_64_vec and bfd_efi_app_ia64_vec with
i386pei_vec, x86_64pei_vec and bfd_pei_ia64_vec, respectively.
* configure.in: Remove bfd_efi_bsdrv_ia32_vec,
bfd_efi_rtdrv_ia32_vec, bfd_efi_bsdrv_x86_64_vec,
bfd_efi_rtdrv_x86_64_vec,
bfd_efi_bsdrv_ia64_vec and bfd_efi_rtdrv_ia64_vec. Replace
bfd_efi_ia64_vec with bfd_pei_ia64_vec.
* targets.c: Likewise.
* configure: Regenerated.
* libcoff.h: Likewise.
* Makefile.in: Likewise.
* efi-app-ia32.c: Removed.
* efi-app-x86_64.c: Likewise.
* efi-bsdrv-ia32.c: Likewise.
* efi-bsdrv-ia64.c: Likewise.
* efi-bsdrv-x86_64.c: Likewise.
* efi-rtdrv-ia32.c: Likewise.
* efi-rtdrv-ia64.c: Likewise.
* efi-rtdrv-x86_64.c: Likewise.
* efi-rtdrv-ia32.c: Likewise.
* efi-app-ia64.c: Moved to ...
* pei-ia64.c: This.
(TARGET_SYM): Set to bfd_pei_ia64_vec.
(TARGET_NAME): Set to pei-ia64.
* libpei.h (bfd_target_pei_p): Removed.
(bfd_target_pei_arch): Likewise.
(bfd_target_efi_app_p): Likewise.
(bfd_target_efi_app_arch): Likewise.
(bfd_target_efi_bsdrv_p): Likewise.
(bfd_target_efi_bsdrv_arch): Likewise.
(bfd_target_efi_rtdrv_p): Likewise.
(bfd_target_efi_rtdrv_arch): Likewise.
(bfd_pe_executable_p): Likewise.
* Makefile.am (BFD32_BACKENDS): Remove efi-app-ia32.lo,
efi-bsdrv-ia32.lo and efi-rtdrv-ia32.lo.
(BFD32_BACKENDS_CFILES): Remove efi-app-ia32.c, efi-bsdrv-ia32.c
and efi-rtdrv-ia32.c.
(BFD64_BACKENDS): Remove efi-app-ia64.lo, efi-bsdrv-ia64.lo,
efi-rtdrv-ia64.lo, efi-app-x86_64.lo, efi-bsdrv-x86_64.lo and
efi-rtdrv-x86_64.lo. Add pei-ia64.lo.
(BFD64_BACKENDS_CFILES): Remove efi-app-ia64.c, efi-bsdrv-ia64.c,
efi-rtdrv-ia64.c, efi-app-x86_64.c, efi-bsdrv-x86_64.c and
efi-rtdrv-x86_64.c. Add pei-ia64.c.
(efi-app-ia64.lo): Removed.
(efi-bsdrv-ia32.lo): Likewise.
(efi-rtdrv-ia32.lo): Likewise.
(efi-app-ia64.lo): Likewise.
(efi-bsdrv-ia64.lo): Likewise.
(efi-rtdrv-ia64.lo): Likewise.
(efi-app-x86_64.lo): Likewise.
(efi-bsdrv-x86_64.lo): Likewise.
(efi-rtdrv-x86_64.lo): Likewise.
(pei-ia64.lo): New.
* peicode.h (coff_swap_scnhdr_in): Replace bfd_pe_executable_p
with bfd_pei_p.
(arch_type): Removed.
(pe_arch): Likewise.
(pe_bfd_object_p): Just return coff_object_p.
* peXXigen.c (_bfd_XXi_swap_scnhdr_out): Replace
bfd_pe_executable_p with bfd_pei_p.
binutils/
2009-04-17 H.J. Lu <hongjiu.lu@intel.com>
PR binutils/10074
* objcopy.c: Include coff/i386.h and coff/pe.h.
(pe_file_alignment): New.
(pe_heap_commit): Likewise.
(pe_heap_reserve): Likewise.
(pe_image_base): Likewise.
(pe_section_alignment): Likewise.
(pe_stack_commit): Likewise.
(pe_stack_reserve): Likewise.
(pe_subsystem): Likewise.
(pe_major_subsystem_version): Likewise.
(pe_minor_subsystem_version): Likewise.
(set_pe_subsystem): Likewise.
(convert_efi_target): Likewise.
(command_line_switch): Add OPTION_FILE_ALIGNMENT,
OPTION_HEAP, OPTION_IMAGE_BASE, OPTION_SECTION_ALIGNMENT,
OPTION_STACK and OPTION_SUBSYSTEM.
(copy_options): Likewise.
(copy_usage): Add --file-alignment, --heap, --image-base,
--section-alignment, --stack and --subsystem.
(copy_object): Set up PE parameters.
(copy_main): Process Add OPTION_FILE_ALIGNMENT,
OPTION_HEAP, OPTION_IMAGE_BASE, OPTION_SECTION_ALIGNMENT,
OPTION_STACK and OPTION_SUBSYSTEM. Convert EFI target to
PEI target.
* NEWS: Mention --file-alignment, --heap, --image-base,
--section-alignment, --stack and --subsystem command line
options for objcopy.
* doc/binutils.texi: Document --file-alignment, --heap,
--image-base, --section-alignment, --stack and --subsystem
command line options for objcopy.
2009-04-17 15:46:18 +02:00
|
|
|
[@option{--file-alignment=}@var{num}]
|
|
|
|
[@option{--heap=}@var{size}]
|
|
|
|
[@option{--image-base=}@var{address}]
|
|
|
|
[@option{--section-alignment=}@var{num}]
|
|
|
|
[@option{--stack=}@var{size}]
|
|
|
|
[@option{--subsystem=}@var{which}:@var{major}.@var{minor}]
|
2010-10-29 14:10:39 +02:00
|
|
|
[@option{--compress-debug-sections}]
|
|
|
|
[@option{--decompress-debug-sections}]
|
Properly implement STT_COMMON
The BFD configure option, --enable-elf-stt-common, can't be to used to
verify STT_COMMON implementation with the normal binutils build. Instead,
this patch removes it from BFD. It adds --elf-stt-common=[no|yes] to ELF
assembler/objcopy and adds -z common/-z nocommon to ld.
A configure option, --enable-elf-stt-common, is added to gas to specify
whether ELF assembler should generate common symbols with the STT_COMMON
type by default.
Since BSF_KEEP_G is never used, it is renamed to BSF_ELF_COMMON for ELF
common symbols.
bfd/
PR ld/19645
* bfd.c (bfd): Change flags to 20 bits.
(BFD_CONVERT_ELF_COMMON): New.
(BFD_USE_ELF_STT_COMMON): Likewise.
(BFD_FLAGS_SAVED): Add BFD_CONVERT_ELF_COMMON and
BFD_USE_ELF_STT_COMMON.
(BFD_FLAGS_FOR_BFD_USE_MASK): Likewise.
* configure.ac: Remove --enable-elf-stt-common.
* elf.c (swap_out_syms): Choose STT_COMMON or STT_OBJECT for
common symbol depending on BFD_CONVERT_ELF_COMMON and
BFD_USE_ELF_STT_COMMON.
* elfcode.h (elf_slurp_symbol_table): Set BSF_ELF_COMMON for
STT_COMMON.
* elflink.c (bfd_elf_link_mark_dynamic_symbol): Also check
STT_COMMON.
(elf_link_convert_common_type): New function.
(elf_link_output_extsym): Choose STT_COMMON or STT_OBJECT for
common symbol depending on BFD_CONVERT_ELF_COMMON and
BFD_USE_ELF_STT_COMMON. Set sym.st_info after sym.st_shndx.
* elfxx-target.h (TARGET_BIG_SYM): Add BFD_CONVERT_ELF_COMMON
and BFD_USE_ELF_STT_COMMON to object_flags.
(TARGET_LITTLE_SYM): Likewise.
* syms.c (BSF_KEEP_G): Renamed to ...
(BSF_ELF_COMMON): This.
* bfd-in2.h: Regenerated.
* config.in: Likewise.
* configure: Likewise.
binutils/
PR ld/19645
* NEWS: Mention --elf-stt-common= for objcopy.
* doc/binutils.texi: Document --elf-stt-common= for objcopy.
* objcopy.c (do_elf_stt_common): New.
(command_line_switch): Add OPTION_ELF_STT_COMMON.
(copy_options): Add --elf-stt-common=.
(copy_usage): Add --elf-stt-common=.
(copy_object): Also check do_elf_stt_common for ELF targets.
(copy_file): Handle do_elf_stt_common.
(copy_main): Handle OPTION_ELF_STT_COMMON.
* readelf.c (apply_relocations): Support STT_COMMON.
* testsuite/binutils-all/common-1.s: New file.
* testsuite/binutils-all/common-1a.d: Likewise.
* testsuite/binutils-all/common-1b.d: Likewise.
* testsuite/binutils-all/common-1c.d: Likewise.
* testsuite/binutils-all/common-1d.d: Likewise.
* testsuite/binutils-all/common-1e.d: Likewise.
* testsuite/binutils-all/common-1f.d: Likewise.
* testsuite/binutils-all/common-2.s: Likewise.
* testsuite/binutils-all/common-2a.d: Likewise.
* testsuite/binutils-all/common-2b.d: Likewise.
* testsuite/binutils-all/common-2c.d: Likewise.
* testsuite/binutils-all/common-2d.d: Likewise.
* testsuite/binutils-all/common-2e.d: Likewise.
* testsuite/binutils-all/common-2f.d: Likewise.
* testsuite/binutils-all/objcopy.exp
(objcopy_test_elf_common_symbols): New proc.
Run objcopy_test_elf_common_symbols for ELF targets
gas/
PR ld/19645
* NEWS: Mention --enable-elf-stt-common and --elf-stt-common=
for ELF assemblers.
* as.c (flag_use_elf_stt_common): New.
(show_usage): Add --elf-stt-common=.
(option_values): Add OPTION_ELF_STT_COMMON.
(std_longopts): Add --elf-stt-common=.
(parse_args): Handle --elf-stt-common=.
* as.h (flag_use_elf_stt_common): New.
* config.in: Regenerated.
* configure: Likewise.
* configure.ac: Add --enable-elf-stt-common and define
DEFAULT_GENERATE_ELF_STT_COMMON.
* gas/write.c (write_object_file): Set BFD_CONVERT_ELF_COMMON
and BFD_USE_ELF_STT_COMMON if flag_use_elf_stt_common is set.
* doc/as.texinfo: Document --elf-stt-common=.
* testsuite/gas/elf/common3.s: New file.
* testsuite/gas/elf/common3a.d: Likewise.
* testsuite/gas/elf/common3b.d: Likewise.
* testsuite/gas/elf/common4.s: Likewise.
* testsuite/gas/elf/common4a.d: Likewise.
* testsuite/gas/elf/common4b.d: Likewise.
* testsuite/gas/i386/dw2-compress-3b.d: Likewise.
* testsuite/gas/i386/dw2-compressed-3b.d: Likewise.
* testsuite/gas/elf/elf.exp: Run common3a, common3b, common4a
and common4b.
* testsuite/gas/i386/dw2-compress-3.d: Renamed to ...
* testsuite/gas/i386/dw2-compress-3a.d: This. Pass
--elf-stt-common=no to as.
* testsuite/gas/i386/dw2-compressed-3.d: Renamed to ...
* testsuite/gas/i386/dw2-compressed-3a.d: This. Pass
--elf-stt-common=no to as.
* testsuite/gas/i386/i386.exp: Run dw2-compress-3a,
dw2-compress-3b, dw2-compressed-3a and dw2-compressed-3b instead
of dw2-compress-3 and dw2-compressed-3.
include/
PR ld/19645
* bfdlink.h (bfd_link_elf_stt_common): New enum.
(bfd_link_info): Add elf_stt_common.
ld/
PR ld/19645
* NEWS: Mention -z common/-z nocommon for ELF targets.
* emultempl/elf32.em (gld${EMULATION_NAME}_handle_option): Handle
-z common and -z nocommon.
* ld.texinfo: Document -z common/-z nocommon.
* lexsup.c (elf_shlib_list_options): Add -z common/-z nocommon.
* testsuite/ld-elf/tls_common.exp: Test --elf-stt-common=no and
--elf-stt-common=yes with assembler.
* testsuite/ld-elfcomm/common-1.s: New file.
* testsuite/ld-elfcomm/common-1a.d: Likewise.
* testsuite/ld-elfcomm/common-1b.d: Likewise.
* testsuite/ld-elfcomm/common-1c.d: Likewise.
* testsuite/ld-elfcomm/common-1d.d: Likewise.
* testsuite/ld-elfcomm/common-1e.d: Likewise.
* testsuite/ld-elfcomm/common-1f.d: Likewise.
* testsuite/ld-elfcomm/common-2.s: Likewise.
* testsuite/ld-elfcomm/common-2a.d: Likewise.
* testsuite/ld-elfcomm/common-2b.d: Likewise.
* testsuite/ld-elfcomm/common-2c.d: Likewise.
* testsuite/ld-elfcomm/common-2d.d: Likewise.
* testsuite/ld-elfcomm/common-2e.d: Likewise.
* testsuite/ld-elfcomm/common-2f.d: Likewise.
* testsuite/ld-elfcomm/common-3a.rd: Likewise.
* testsuite/ld-elfcomm/common-3b.rd: Likewise.
* testsuite/ld-i386/pr19645.d: Likewise.
* testsuite/ld-i386/pr19645.s: Likewise.
* testsuite/ld-x86-64/largecomm-1.s: Likewise.
* testsuite/ld-x86-64/largecomm-1a.d: Likewise.
* testsuite/ld-x86-64/largecomm-1b.d: Likewise.
* testsuite/ld-x86-64/largecomm-1c.d: Likewise.
* testsuite/ld-x86-64/largecomm-1d.d: Likewise.
* testsuite/ld-x86-64/largecomm-1e.d: Likewise.
* testsuite/ld-x86-64/largecomm-1f.d: Likewise.
* testsuite/ld-x86-64/pr19645.d: Likewise.
* testsuite/ld-x86-64/pr19645.s: Likewise.
* testsuite/ld-elfcomm/elfcomm.exp: Test --elf-stt-common=yes
with assembler.
(assembler_generates_commons): Removed.
Run -z common/-z nocommon tests. Run *.d tests.
* testsuite/ld-i386/i386.exp: Run pr19645.
* testsuite/ld-x86-64/x86-64.exp: Likewise.
* testsuite/ld-x86-64/dwarfreloc.exp: Test --elf-stt-common with
assembler. Test STT_COMMON with readelf.
2016-02-22 18:18:52 +01:00
|
|
|
[@option{--elf-stt-common=@var{val}}]
|
2017-03-01 12:09:46 +01:00
|
|
|
[@option{--merge-notes}]
|
2017-04-13 15:50:56 +02:00
|
|
|
[@option{--no-merge-notes}]
|
2019-05-14 11:40:04 +02:00
|
|
|
[@option{--verilog-data-width=@var{val}}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-v}|@option{--verbose}]
|
2007-06-29 02:34:14 +02:00
|
|
|
[@option{-V}|@option{--version}]
|
2003-03-24 17:11:46 +01:00
|
|
|
[@option{--help}] [@option{--info}]
|
1999-05-03 09:29:11 +02:00
|
|
|
@var{infile} [@var{outfile}]
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION objcopy
|
2001-08-01 17:54:41 +02:00
|
|
|
The @sc{gnu} @command{objcopy} utility copies the contents of an object
|
|
|
|
file to another. @command{objcopy} uses the @sc{gnu} @sc{bfd} Library to
|
1999-05-03 09:29:11 +02:00
|
|
|
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
|
2001-08-01 17:54:41 +02:00
|
|
|
exact behavior of @command{objcopy} is controlled by command-line options.
|
|
|
|
Note that @command{objcopy} should be able to copy a fully linked file
|
2000-06-15 21:34:44 +02:00
|
|
|
between any two formats. However, copying a relocatable object file
|
|
|
|
between any two formats may not work as expected.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{objcopy} creates temporary files to do its translations and
|
|
|
|
deletes them afterward. @command{objcopy} uses @sc{bfd} to do all its
|
1999-05-03 09:29:11 +02:00
|
|
|
translation work; it has access to all the formats described in @sc{bfd}
|
|
|
|
and thus is able to recognize most formats without being told
|
|
|
|
explicitly. @xref{BFD,,BFD,ld.info,Using LD}.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{objcopy} can be used to generate S-records by using an output
|
1999-05-03 09:29:11 +02:00
|
|
|
target of @samp{srec} (e.g., use @samp{-O srec}).
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{objcopy} can be used to generate a raw binary file by using an
|
|
|
|
output target of @samp{binary} (e.g., use @option{-O binary}). When
|
|
|
|
@command{objcopy} generates a raw binary file, it will essentially produce
|
1999-05-03 09:29:11 +02:00
|
|
|
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
|
2001-08-01 17:54:41 +02:00
|
|
|
use @option{-S} to remove sections containing debugging information. In
|
|
|
|
some cases @option{-R} will be useful to remove sections which contain
|
1999-10-08 15:56:33 +02:00
|
|
|
information that is not needed by the binary file.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2003-02-21 11:30:35 +01:00
|
|
|
Note---@command{objcopy} is not able to change the endianness of its input
|
|
|
|
files. If the input format has an endianness (some formats do not),
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{objcopy} can only copy the inputs into file formats that have the
|
2003-02-21 11:30:35 +01:00
|
|
|
same endianness or which have no endianness (e.g., @samp{srec}).
|
2007-04-23 12:59:07 +02:00
|
|
|
(However, see the @option{--reverse-bytes} option.)
|
2001-01-18 01:18:50 +01:00
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS objcopy
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @env
|
1999-05-03 09:29:11 +02:00
|
|
|
@item @var{infile}
|
|
|
|
@itemx @var{outfile}
|
1999-10-08 15:56:33 +02:00
|
|
|
The input and output files, respectively.
|
2001-08-01 17:54:41 +02:00
|
|
|
If you do not specify @var{outfile}, @command{objcopy} creates a
|
1999-05-03 09:29:11 +02:00
|
|
|
temporary file and destructively renames the result with
|
|
|
|
the name of @var{infile}.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@item -I @var{bfdname}
|
1999-05-03 09:29:11 +02:00
|
|
|
@itemx --input-target=@var{bfdname}
|
|
|
|
Consider the source file's object format to be @var{bfdname}, rather than
|
|
|
|
attempting to deduce it. @xref{Target Selection}, for more information.
|
|
|
|
|
|
|
|
@item -O @var{bfdname}
|
|
|
|
@itemx --output-target=@var{bfdname}
|
|
|
|
Write the output file using the object format @var{bfdname}.
|
|
|
|
@xref{Target Selection}, for more information.
|
|
|
|
|
|
|
|
@item -F @var{bfdname}
|
|
|
|
@itemx --target=@var{bfdname}
|
|
|
|
Use @var{bfdname} as the object format for both the input and the output
|
|
|
|
file; i.e., simply transfer data from source to destination with no
|
|
|
|
translation. @xref{Target Selection}, for more information.
|
|
|
|
|
2001-03-13 01:08:35 +01:00
|
|
|
@item -B @var{bfdarch}
|
|
|
|
@itemx --binary-architecture=@var{bfdarch}
|
2009-09-11 13:16:19 +02:00
|
|
|
Useful when transforming a architecture-less input file into an object file.
|
|
|
|
In this case the output architecture can be set to @var{bfdarch}. This
|
|
|
|
option will be ignored if the input file has a known @var{bfdarch}. You
|
2001-03-13 01:08:35 +01:00
|
|
|
can access this binary data inside a program by referencing the special
|
|
|
|
symbols that are created by the conversion process. These symbols are
|
|
|
|
called _binary_@var{objfile}_start, _binary_@var{objfile}_end and
|
|
|
|
_binary_@var{objfile}_size. e.g. you can transform a picture file into
|
2007-06-29 02:34:14 +02:00
|
|
|
an object file and then access it in your code using these symbols.
|
2001-03-13 01:08:35 +01:00
|
|
|
|
2013-02-15 10:32:31 +01:00
|
|
|
@item -j @var{sectionpattern}
|
|
|
|
@itemx --only-section=@var{sectionpattern}
|
|
|
|
Copy only the indicated sections from the input file to the output file.
|
1999-06-12 17:42:04 +02:00
|
|
|
This option may be given more than once. Note that using this option
|
2013-02-15 10:32:31 +01:00
|
|
|
inappropriately may make the output file unusable. Wildcard
|
|
|
|
characters are accepted in @var{sectionpattern}.
|
1999-06-12 17:42:04 +02:00
|
|
|
|
2015-08-24 14:02:39 +02:00
|
|
|
If the first character of @var{sectionpattern} is the exclamation
|
|
|
|
point (!) then matching sections will not be copied, even if earlier
|
|
|
|
use of @option{--only-section} on the same command line would
|
|
|
|
otherwise copy it. For example:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
--only-section=.text.* --only-section=!.text.foo
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
will copy all sectinos maching '.text.*' but not the section
|
|
|
|
'.text.foo'.
|
|
|
|
|
2013-02-15 10:32:31 +01:00
|
|
|
@item -R @var{sectionpattern}
|
|
|
|
@itemx --remove-section=@var{sectionpattern}
|
|
|
|
Remove any section matching @var{sectionpattern} from the output file.
|
|
|
|
This option may be given more than once. Note that using this option
|
|
|
|
inappropriately may make the output file unusable. Wildcard
|
|
|
|
characters are accepted in @var{sectionpattern}. Using both the
|
|
|
|
@option{-j} and @option{-R} options together results in undefined
|
|
|
|
behaviour.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2015-08-24 14:02:39 +02:00
|
|
|
If the first character of @var{sectionpattern} is the exclamation
|
|
|
|
point (!) then matching sections will not be removed even if an
|
|
|
|
earlier use of @option{--remove-section} on the same command line
|
|
|
|
would otherwise remove it. For example:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
--remove-section=.text.* --remove-section=!.text.foo
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
will remove all sections matching the pattern '.text.*', but will not
|
|
|
|
remove the section '.text.foo'.
|
|
|
|
|
objcopy/strip: Add option --remove-relocations=SECTIONPATTERN
The objcopy and strip tools make use of the bfd library to manipulate
the state of the input file (to produce an output file). Within the
input file (for ELF at least), relocations are held within a section,
and so, if the user wanted to remove the relocations, but keep the
section to which the relocations would have been applied, it is tempting
to think that specifying the name of a relocation section to objcopy's
--remove-section option might do what you want, for example:
objcopy --remove-section=.rela.text input.elf output.elf
However, this does not work. The reason is that when the input file is
loaded, relocations are not managed as sections, but are, instead,
loaded as data associated with the section to which the relocations
would be applied. In our example above the relocations in '.rela.text'
are held as data on the section '.text' once 'input.elf' is loaded.
One task that objcopy and strip do is copy the relocations from the
input file to the output file if the section is also being copied from
the input file to the output file.
This commit adds a new command line option for objcopy and strip,
--remove-relocations, which can be used to remove the relocations, while
keeping the section that the relocations would have been applied to, for
example:
objcopy --remove-relocations=.text input.elf output.elf
in this case the section '.text' will appear in both 'input.elf' and
'output.elf', but any relocations in 'input.elf' that apply to '.text'
will not be present in 'output.elf'.
I have also added a special case to the handling of --remove-section
that spots if a user tries to remove a relocation section (currently
this is done by spotting the '.rela.' or '.rel.' prefix) and forwards
the request to --remove-relocations.
As with --remove-section and --only-section the --remove-relocations
option supports the '!' prefix on the section-patterns it takes to allow
for sections to be specifically not matched.
There are tests for all the new functionality.
binutils/ChangeLog:
* doc/binutils.texi (objcopy): Document 'remove-relocations'.
(strip): Likewise.
* objcopy.c (SECTION_CONTEXT_REMOVE_RELOCS): Define.
(enum command_line_switch): Add 'OPTION_REMOVE_RELOCS'.
(struct option strip_options): Add 'remove-relocations'.
(struct option copy_options): Likewise.
(copy_usage): Likewise.
(strip_usage): Likewise.
(handle_remove_relocations_option): New function.
(discard_relocations): New function.
(handle_remove_section_option): New function.
(copy_relocations_in_section): Use discard_relocations.
(strip_main): Use handle_remove_section_option for
'remove-section', and handle 'remove-relocations' option.
(copy_main): Likewise.
* testsuite/binutils-all/objcopy.exp: Run new tests.
* testsuite/binutils-all/remove-relocs-01.d: New file.
* testsuite/binutils-all/remove-relocs-01.s: New file.
* testsuite/binutils-all/remove-relocs-02.d: New file.
* testsuite/binutils-all/remove-relocs-03.d: New file.
* testsuite/binutils-all/remove-relocs-04.d: New file.
* testsuite/binutils-all/remove-relocs-05.d: New file.
* testsuite/binutils-all/remove-relocs-06.d: New file.
2015-08-21 21:08:26 +02:00
|
|
|
@item --remove-relocations=@var{sectionpattern}
|
2018-09-10 04:27:08 +02:00
|
|
|
Remove non-dynamic relocations from the output file for any section
|
|
|
|
matching @var{sectionpattern}. This option may be given more than
|
|
|
|
once. Note that using this option inappropriately may make the output
|
|
|
|
file unusable, and attempting to remove a dynamic relocation section
|
|
|
|
such as @samp{.rela.plt} from an executable or shared library with
|
|
|
|
@option{--remove-relocations=.plt} will not work. Wildcard characters
|
|
|
|
are accepted in @var{sectionpattern}.
|
objcopy/strip: Add option --remove-relocations=SECTIONPATTERN
The objcopy and strip tools make use of the bfd library to manipulate
the state of the input file (to produce an output file). Within the
input file (for ELF at least), relocations are held within a section,
and so, if the user wanted to remove the relocations, but keep the
section to which the relocations would have been applied, it is tempting
to think that specifying the name of a relocation section to objcopy's
--remove-section option might do what you want, for example:
objcopy --remove-section=.rela.text input.elf output.elf
However, this does not work. The reason is that when the input file is
loaded, relocations are not managed as sections, but are, instead,
loaded as data associated with the section to which the relocations
would be applied. In our example above the relocations in '.rela.text'
are held as data on the section '.text' once 'input.elf' is loaded.
One task that objcopy and strip do is copy the relocations from the
input file to the output file if the section is also being copied from
the input file to the output file.
This commit adds a new command line option for objcopy and strip,
--remove-relocations, which can be used to remove the relocations, while
keeping the section that the relocations would have been applied to, for
example:
objcopy --remove-relocations=.text input.elf output.elf
in this case the section '.text' will appear in both 'input.elf' and
'output.elf', but any relocations in 'input.elf' that apply to '.text'
will not be present in 'output.elf'.
I have also added a special case to the handling of --remove-section
that spots if a user tries to remove a relocation section (currently
this is done by spotting the '.rela.' or '.rel.' prefix) and forwards
the request to --remove-relocations.
As with --remove-section and --only-section the --remove-relocations
option supports the '!' prefix on the section-patterns it takes to allow
for sections to be specifically not matched.
There are tests for all the new functionality.
binutils/ChangeLog:
* doc/binutils.texi (objcopy): Document 'remove-relocations'.
(strip): Likewise.
* objcopy.c (SECTION_CONTEXT_REMOVE_RELOCS): Define.
(enum command_line_switch): Add 'OPTION_REMOVE_RELOCS'.
(struct option strip_options): Add 'remove-relocations'.
(struct option copy_options): Likewise.
(copy_usage): Likewise.
(strip_usage): Likewise.
(handle_remove_relocations_option): New function.
(discard_relocations): New function.
(handle_remove_section_option): New function.
(copy_relocations_in_section): Use discard_relocations.
(strip_main): Use handle_remove_section_option for
'remove-section', and handle 'remove-relocations' option.
(copy_main): Likewise.
* testsuite/binutils-all/objcopy.exp: Run new tests.
* testsuite/binutils-all/remove-relocs-01.d: New file.
* testsuite/binutils-all/remove-relocs-01.s: New file.
* testsuite/binutils-all/remove-relocs-02.d: New file.
* testsuite/binutils-all/remove-relocs-03.d: New file.
* testsuite/binutils-all/remove-relocs-04.d: New file.
* testsuite/binutils-all/remove-relocs-05.d: New file.
* testsuite/binutils-all/remove-relocs-06.d: New file.
2015-08-21 21:08:26 +02:00
|
|
|
For example:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
--remove-relocations=.text.*
|
|
|
|
@end smallexample
|
|
|
|
|
2018-09-10 04:27:08 +02:00
|
|
|
will remove the relocations for all sections matching the pattern
|
objcopy/strip: Add option --remove-relocations=SECTIONPATTERN
The objcopy and strip tools make use of the bfd library to manipulate
the state of the input file (to produce an output file). Within the
input file (for ELF at least), relocations are held within a section,
and so, if the user wanted to remove the relocations, but keep the
section to which the relocations would have been applied, it is tempting
to think that specifying the name of a relocation section to objcopy's
--remove-section option might do what you want, for example:
objcopy --remove-section=.rela.text input.elf output.elf
However, this does not work. The reason is that when the input file is
loaded, relocations are not managed as sections, but are, instead,
loaded as data associated with the section to which the relocations
would be applied. In our example above the relocations in '.rela.text'
are held as data on the section '.text' once 'input.elf' is loaded.
One task that objcopy and strip do is copy the relocations from the
input file to the output file if the section is also being copied from
the input file to the output file.
This commit adds a new command line option for objcopy and strip,
--remove-relocations, which can be used to remove the relocations, while
keeping the section that the relocations would have been applied to, for
example:
objcopy --remove-relocations=.text input.elf output.elf
in this case the section '.text' will appear in both 'input.elf' and
'output.elf', but any relocations in 'input.elf' that apply to '.text'
will not be present in 'output.elf'.
I have also added a special case to the handling of --remove-section
that spots if a user tries to remove a relocation section (currently
this is done by spotting the '.rela.' or '.rel.' prefix) and forwards
the request to --remove-relocations.
As with --remove-section and --only-section the --remove-relocations
option supports the '!' prefix on the section-patterns it takes to allow
for sections to be specifically not matched.
There are tests for all the new functionality.
binutils/ChangeLog:
* doc/binutils.texi (objcopy): Document 'remove-relocations'.
(strip): Likewise.
* objcopy.c (SECTION_CONTEXT_REMOVE_RELOCS): Define.
(enum command_line_switch): Add 'OPTION_REMOVE_RELOCS'.
(struct option strip_options): Add 'remove-relocations'.
(struct option copy_options): Likewise.
(copy_usage): Likewise.
(strip_usage): Likewise.
(handle_remove_relocations_option): New function.
(discard_relocations): New function.
(handle_remove_section_option): New function.
(copy_relocations_in_section): Use discard_relocations.
(strip_main): Use handle_remove_section_option for
'remove-section', and handle 'remove-relocations' option.
(copy_main): Likewise.
* testsuite/binutils-all/objcopy.exp: Run new tests.
* testsuite/binutils-all/remove-relocs-01.d: New file.
* testsuite/binutils-all/remove-relocs-01.s: New file.
* testsuite/binutils-all/remove-relocs-02.d: New file.
* testsuite/binutils-all/remove-relocs-03.d: New file.
* testsuite/binutils-all/remove-relocs-04.d: New file.
* testsuite/binutils-all/remove-relocs-05.d: New file.
* testsuite/binutils-all/remove-relocs-06.d: New file.
2015-08-21 21:08:26 +02:00
|
|
|
'.text.*'.
|
|
|
|
|
|
|
|
If the first character of @var{sectionpattern} is the exclamation
|
|
|
|
point (!) then matching sections will not have their relocation
|
|
|
|
removed even if an earlier use of @option{--remove-relocations} on the
|
|
|
|
same command line would otherwise cause the relocations to be removed.
|
|
|
|
For example:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
--remove-relocations=.text.* --remove-relocations=!.text.foo
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
will remove all relocations for sections matching the pattern
|
|
|
|
'.text.*', but will not remove relocations for the section
|
|
|
|
'.text.foo'.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -S
|
|
|
|
@itemx --strip-all
|
|
|
|
Do not copy relocation and symbol information from the source file.
|
|
|
|
|
|
|
|
@item -g
|
|
|
|
@itemx --strip-debug
|
2003-06-12 09:23:31 +02:00
|
|
|
Do not copy debugging symbols or sections from the source file.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --strip-unneeded
|
|
|
|
Strip all symbols that are not needed for relocation processing.
|
|
|
|
|
|
|
|
@item -K @var{symbolname}
|
|
|
|
@itemx --keep-symbol=@var{symbolname}
|
2005-04-25 11:23:24 +02:00
|
|
|
When stripping symbols, keep symbol @var{symbolname} even if it would
|
|
|
|
normally be stripped. This option may be given more than once.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -N @var{symbolname}
|
|
|
|
@itemx --strip-symbol=@var{symbolname}
|
|
|
|
Do not copy symbol @var{symbolname} from the source file. This option
|
|
|
|
may be given more than once.
|
|
|
|
|
2004-12-16 14:16:33 +01:00
|
|
|
@item --strip-unneeded-symbol=@var{symbolname}
|
|
|
|
Do not copy symbol @var{symbolname} from the source file unless it is needed
|
|
|
|
by a relocation. This option may be given more than once.
|
|
|
|
|
2001-05-30 12:46:28 +02:00
|
|
|
@item -G @var{symbolname}
|
|
|
|
@itemx --keep-global-symbol=@var{symbolname}
|
|
|
|
Keep only symbol @var{symbolname} global. Make all other symbols local
|
|
|
|
to the file, so that they are not visible externally. This option may
|
2018-10-11 12:38:10 +02:00
|
|
|
be given more than once. Note: this option cannot be used in
|
|
|
|
conjunction with the @option{--globalize-symbol} or
|
|
|
|
@option{--globalize-symbols} options.
|
2001-05-30 12:46:28 +02:00
|
|
|
|
2006-06-23 18:23:09 +02:00
|
|
|
@item --localize-hidden
|
|
|
|
In an ELF object, mark all symbols that have hidden or internal visibility
|
|
|
|
as local. This option applies on top of symbol-specific localization options
|
|
|
|
such as @option{-L}.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -L @var{symbolname}
|
|
|
|
@itemx --localize-symbol=@var{symbolname}
|
2016-07-20 10:41:10 +02:00
|
|
|
Convert a global or weak symbol called @var{symbolname} into a local
|
|
|
|
symbol, so that it is not visible externally. This option may be
|
|
|
|
given more than once. Note - unique symbols are not converted.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -W @var{symbolname}
|
|
|
|
@itemx --weaken-symbol=@var{symbolname}
|
|
|
|
Make symbol @var{symbolname} weak. This option may be given more than once.
|
|
|
|
|
2005-03-15 18:45:19 +01:00
|
|
|
@item --globalize-symbol=@var{symbolname}
|
|
|
|
Give symbol @var{symbolname} global scoping so that it is visible
|
|
|
|
outside of the file in which it is defined. This option may be given
|
2018-10-11 12:38:10 +02:00
|
|
|
more than once. Note: this option cannot be used in conjunction with
|
|
|
|
the @option{-G} or @option{--keep-global-symbol} options.
|
2005-03-15 18:45:19 +01:00
|
|
|
|
2003-11-11 18:50:26 +01:00
|
|
|
@item -w
|
|
|
|
@itemx --wildcard
|
|
|
|
Permit regular expressions in @var{symbolname}s used in other command
|
|
|
|
line options. The question mark (?), asterisk (*), backslash (\) and
|
|
|
|
square brackets ([]) operators can be used anywhere in the symbol
|
|
|
|
name. If the first character of the symbol name is the exclamation
|
|
|
|
point (!) then the sense of the switch is reversed for that symbol.
|
|
|
|
For example:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
-w -W !foo -W fo*
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
would cause objcopy to weaken all symbols that start with ``fo''
|
|
|
|
except for the symbol ``foo''.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -x
|
|
|
|
@itemx --discard-all
|
|
|
|
Do not copy non-global symbols from the source file.
|
|
|
|
@c FIXME any reason to prefer "non-global" to "local" here?
|
|
|
|
|
|
|
|
@item -X
|
|
|
|
@itemx --discard-locals
|
|
|
|
Do not copy compiler-generated local symbols.
|
|
|
|
(These usually start with @samp{L} or @samp{.}.)
|
|
|
|
|
|
|
|
@item -b @var{byte}
|
|
|
|
@itemx --byte=@var{byte}
|
2010-09-10 14:11:28 +02:00
|
|
|
If interleaving has been enabled via the @option{--interleave} option
|
|
|
|
then start the range of bytes to keep at the @var{byte}th byte.
|
|
|
|
@var{byte} can be in the range from 0 to @var{breadth}-1, where
|
|
|
|
@var{breadth} is the value given by the @option{--interleave} option.
|
|
|
|
|
|
|
|
@item -i [@var{breadth}]
|
|
|
|
@itemx --interleave[=@var{breadth}]
|
|
|
|
Only copy a range out of every @var{breadth} bytes. (Header data is
|
|
|
|
not affected). Select which byte in the range begins the copy with
|
|
|
|
the @option{--byte} option. Select the width of the range with the
|
|
|
|
@option{--interleave-width} option.
|
|
|
|
|
|
|
|
This option is useful for creating files to program @sc{rom}. It is
|
|
|
|
typically used with an @code{srec} output target. Note that
|
|
|
|
@command{objcopy} will complain if you do not specify the
|
|
|
|
@option{--byte} option as well.
|
|
|
|
|
|
|
|
The default interleave breadth is 4, so with @option{--byte} set to 0,
|
|
|
|
@command{objcopy} would copy the first byte out of every four bytes
|
|
|
|
from the input to the output.
|
|
|
|
|
|
|
|
@item --interleave-width=@var{width}
|
|
|
|
When used with the @option{--interleave} option, copy @var{width}
|
|
|
|
bytes at a time. The start of the range of bytes to be copied is set
|
|
|
|
by the @option{--byte} option, and the extent of the range is set with
|
|
|
|
the @option{--interleave} option.
|
|
|
|
|
|
|
|
The default value for this option is 1. The value of @var{width} plus
|
|
|
|
the @var{byte} value set by the @option{--byte} option must not exceed
|
|
|
|
the interleave breadth set by the @option{--interleave} option.
|
|
|
|
|
|
|
|
This option can be used to create images for two 16-bit flashes interleaved
|
|
|
|
in a 32-bit bus by passing @option{-b 0 -i 4 --interleave-width=2}
|
|
|
|
and @option{-b 2 -i 4 --interleave-width=2} to two @command{objcopy}
|
|
|
|
commands. If the input was '12345678' then the outputs would be
|
|
|
|
'1256' and '3478' respectively.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -p
|
|
|
|
@itemx --preserve-dates
|
|
|
|
Set the access and modification dates of the output file to be the same
|
|
|
|
as those of the input file.
|
|
|
|
|
2012-04-25 19:50:14 +02:00
|
|
|
@item -D
|
|
|
|
@itemx --enable-deterministic-archives
|
2013-01-07 18:40:59 +01:00
|
|
|
@cindex deterministic archives
|
|
|
|
@kindex --enable-deterministic-archives
|
2012-04-25 19:50:14 +02:00
|
|
|
Operate in @emph{deterministic} mode. When copying archive members
|
|
|
|
and writing the archive index, use zero for UIDs, GIDs, timestamps,
|
|
|
|
and use consistent file modes for all files.
|
|
|
|
|
2013-01-07 18:40:59 +01:00
|
|
|
If @file{binutils} was configured with
|
|
|
|
@option{--enable-deterministic-archives}, then this mode is on by default.
|
|
|
|
It can be disabled with the @samp{-U} option, below.
|
|
|
|
|
|
|
|
@item -U
|
|
|
|
@itemx --disable-deterministic-archives
|
|
|
|
@cindex deterministic archives
|
|
|
|
@kindex --enable-deterministic-archives
|
|
|
|
Do @emph{not} operate in @emph{deterministic} mode. This is the
|
|
|
|
inverse of the @option{-D} option, above: when copying archive members
|
|
|
|
and writing the archive index, use their actual UID, GID, timestamp,
|
|
|
|
and file mode values.
|
|
|
|
|
|
|
|
This is the default unless @file{binutils} was configured with
|
|
|
|
@option{--enable-deterministic-archives}.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --debugging
|
|
|
|
Convert debugging information, if possible. This is not the default
|
|
|
|
because only certain debugging formats are supported, and the
|
|
|
|
conversion process can be time consuming.
|
|
|
|
|
|
|
|
@item --gap-fill @var{val}
|
|
|
|
Fill gaps between sections with @var{val}. This operation applies to
|
|
|
|
the @emph{load address} (LMA) of the sections. It is done by increasing
|
|
|
|
the size of the section with the lower address, and filling in the extra
|
|
|
|
space created with @var{val}.
|
|
|
|
|
|
|
|
@item --pad-to @var{address}
|
|
|
|
Pad the output file up to the load address @var{address}. This is
|
|
|
|
done by increasing the size of the last section. The extra space is
|
2001-08-01 17:54:41 +02:00
|
|
|
filled in with the value specified by @option{--gap-fill} (default zero).
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --set-start @var{val}
|
1999-10-08 15:56:33 +02:00
|
|
|
Set the start address of the new file to @var{val}. Not all object file
|
1999-05-03 09:29:11 +02:00
|
|
|
formats support setting the start address.
|
|
|
|
|
|
|
|
@item --change-start @var{incr}
|
|
|
|
@itemx --adjust-start @var{incr}
|
|
|
|
@cindex changing start address
|
|
|
|
Change the start address by adding @var{incr}. Not all object file
|
|
|
|
formats support setting the start address.
|
|
|
|
|
|
|
|
@item --change-addresses @var{incr}
|
|
|
|
@itemx --adjust-vma @var{incr}
|
|
|
|
@cindex changing object addresses
|
|
|
|
Change the VMA and LMA addresses of all sections, as well as the start
|
|
|
|
address, by adding @var{incr}. Some object file formats do not permit
|
|
|
|
section addresses to be changed arbitrarily. Note that this does not
|
|
|
|
relocate the sections; if the program expects sections to be loaded at a
|
|
|
|
certain address, and this option is used to change the sections such
|
2007-06-29 02:34:14 +02:00
|
|
|
that they are loaded at a different address, the program may fail.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2013-02-15 10:32:31 +01:00
|
|
|
@item --change-section-address @var{sectionpattern}@{=,+,-@}@var{val}
|
|
|
|
@itemx --adjust-section-vma @var{sectionpattern}@{=,+,-@}@var{val}
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex changing section address
|
2013-02-15 10:32:31 +01:00
|
|
|
Set or change both the VMA address and the LMA address of any section
|
|
|
|
matching @var{sectionpattern}. If @samp{=} is used, the section
|
|
|
|
address is set to @var{val}. Otherwise, @var{val} is added to or
|
|
|
|
subtracted from the section address. See the comments under
|
|
|
|
@option{--change-addresses}, above. If @var{sectionpattern} does not
|
|
|
|
match any sections in the input file, a warning will be issued, unless
|
|
|
|
@option{--no-change-warnings} is used.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2013-02-15 10:32:31 +01:00
|
|
|
@item --change-section-lma @var{sectionpattern}@{=,+,-@}@var{val}
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex changing section LMA
|
2013-02-15 10:32:31 +01:00
|
|
|
Set or change the LMA address of any sections matching
|
|
|
|
@var{sectionpattern}. The LMA address is the address where the
|
|
|
|
section will be loaded into memory at program load time. Normally
|
|
|
|
this is the same as the VMA address, which is the address of the
|
|
|
|
section at program run time, but on some systems, especially those
|
|
|
|
where a program is held in ROM, the two can be different. If @samp{=}
|
|
|
|
is used, the section address is set to @var{val}. Otherwise,
|
|
|
|
@var{val} is added to or subtracted from the section address. See the
|
|
|
|
comments under @option{--change-addresses}, above. If
|
|
|
|
@var{sectionpattern} does not match any sections in the input file, a
|
|
|
|
warning will be issued, unless @option{--no-change-warnings} is used.
|
|
|
|
|
|
|
|
@item --change-section-vma @var{sectionpattern}@{=,+,-@}@var{val}
|
|
|
|
@cindex changing section VMA
|
|
|
|
Set or change the VMA address of any section matching
|
|
|
|
@var{sectionpattern}. The VMA address is the address where the
|
|
|
|
section will be located once the program has started executing.
|
|
|
|
Normally this is the same as the LMA address, which is the address
|
|
|
|
where the section will be loaded into memory, but on some systems,
|
1999-05-03 09:29:11 +02:00
|
|
|
especially those where a program is held in ROM, the two can be
|
|
|
|
different. If @samp{=} is used, the section address is set to
|
|
|
|
@var{val}. Otherwise, @var{val} is added to or subtracted from the
|
2001-08-01 17:54:41 +02:00
|
|
|
section address. See the comments under @option{--change-addresses},
|
2013-02-15 10:32:31 +01:00
|
|
|
above. If @var{sectionpattern} does not match any sections in the
|
|
|
|
input file, a warning will be issued, unless
|
2007-06-29 02:34:14 +02:00
|
|
|
@option{--no-change-warnings} is used.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --change-warnings
|
|
|
|
@itemx --adjust-warnings
|
2001-08-01 17:54:41 +02:00
|
|
|
If @option{--change-section-address} or @option{--change-section-lma} or
|
2013-02-15 10:32:31 +01:00
|
|
|
@option{--change-section-vma} is used, and the section pattern does not
|
|
|
|
match any sections, issue a warning. This is the default.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --no-change-warnings
|
|
|
|
@itemx --no-adjust-warnings
|
2001-08-01 17:54:41 +02:00
|
|
|
Do not issue a warning if @option{--change-section-address} or
|
|
|
|
@option{--adjust-section-lma} or @option{--adjust-section-vma} is used, even
|
2013-02-15 10:32:31 +01:00
|
|
|
if the section pattern does not match any sections.
|
|
|
|
|
|
|
|
@item --set-section-flags @var{sectionpattern}=@var{flags}
|
|
|
|
Set the flags for any sections matching @var{sectionpattern}. The
|
|
|
|
@var{flags} argument is a comma separated string of flag names. The
|
|
|
|
recognized names are @samp{alloc}, @samp{contents}, @samp{load},
|
|
|
|
@samp{noload}, @samp{readonly}, @samp{code}, @samp{data}, @samp{rom},
|
|
|
|
@samp{share}, and @samp{debug}. You can set the @samp{contents} flag
|
|
|
|
for a section which does not have contents, but it is not meaningful
|
|
|
|
to clear the @samp{contents} flag of a section which does have
|
|
|
|
contents--just remove the section instead. Not all flags are
|
|
|
|
meaningful for all object file formats.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2019-08-28 13:33:41 +02:00
|
|
|
@item --set-section-alignment @var{sectionpattern}=@var{align}
|
|
|
|
Set the alignment for any sections matching @var{sectionpattern}. @var{align}
|
|
|
|
specifies the alignment as the exponent for the power of two, i.e. the
|
|
|
|
alignment in bytes will be 2^@var{align}.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --add-section @var{sectionname}=@var{filename}
|
|
|
|
Add a new section named @var{sectionname} while copying the file. The
|
|
|
|
contents of the new section are taken from the file @var{filename}. The
|
|
|
|
size of the section will be the size of the file. This option only
|
|
|
|
works on file formats which can support sections with arbitrary names.
|
2013-12-31 10:52:24 +01:00
|
|
|
Note - it may be necessary to use the @option{--set-section-flags}
|
|
|
|
option to set the attributes of the newly created section.
|
|
|
|
|
|
|
|
@item --dump-section @var{sectionname}=@var{filename}
|
|
|
|
Place the contents of section named @var{sectionname} into the file
|
|
|
|
@var{filename}, overwriting any contents that may have been there
|
|
|
|
previously. This option is the inverse of @option{--add-section}.
|
|
|
|
This option is similar to the @option{--only-section} option except
|
|
|
|
that it does not create a formatted file, it just dumps the contents
|
|
|
|
as raw binary data, without applying any relocations. The option can
|
|
|
|
be specified more than once.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2015-02-13 18:04:42 +01:00
|
|
|
@item --update-section @var{sectionname}=@var{filename}
|
|
|
|
Replace the existing contents of a section named @var{sectionname}
|
|
|
|
with the contents of file @var{filename}. The size of the section
|
|
|
|
will be adjusted to the size of the file. The section flags for
|
|
|
|
@var{sectionname} will be unchanged. For ELF format files the section
|
|
|
|
to segment mapping will also remain unchanged, something which is not
|
|
|
|
possible using @option{--remove-section} followed by
|
|
|
|
@option{--add-section}. The option can be specified more than once.
|
|
|
|
|
|
|
|
Note - it is possible to use @option{--rename-section} and
|
|
|
|
@option{--update-section} to both update and rename a section from one
|
|
|
|
command line. In this case, pass the original section name to
|
|
|
|
@option{--update-section}, and the original and new section names to
|
|
|
|
@option{--rename-section}.
|
|
|
|
|
2015-10-21 16:16:35 +02:00
|
|
|
@item --add-symbol @var{name}=[@var{section}:]@var{value}[,@var{flags}]
|
|
|
|
Add a new symbol named @var{name} while copying the file. This option may be
|
|
|
|
specified multiple times. If the @var{section} is given, the symbol will be
|
|
|
|
associated with and relative to that section, otherwise it will be an ABS
|
|
|
|
symbol. Specifying an undefined section will result in a fatal error. There
|
|
|
|
is no check for the value, it will be taken as specified. Symbol flags can
|
|
|
|
be specified and not all flags will be meaningful for all object file
|
|
|
|
formats. By default, the symbol will be global. The special flag
|
|
|
|
'before=@var{othersym}' will insert the new symbol in front of the specified
|
|
|
|
@var{othersym}, otherwise the symbol(s) will be added at the end of the
|
|
|
|
symbol table in the order they appear.
|
|
|
|
|
2001-07-31 15:49:39 +02:00
|
|
|
@item --rename-section @var{oldname}=@var{newname}[,@var{flags}]
|
|
|
|
Rename a section from @var{oldname} to @var{newname}, optionally
|
|
|
|
changing the section's flags to @var{flags} in the process. This has
|
2018-01-22 22:05:56 +01:00
|
|
|
the advantage over using a linker script to perform the rename in that
|
2001-07-31 15:49:39 +02:00
|
|
|
the output stays as an object file and does not become a linked
|
|
|
|
executable.
|
|
|
|
|
|
|
|
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:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
objcopy -I binary -O <output_format> -B <architecture> \
|
|
|
|
--rename-section .data=.rodata,alloc,load,readonly,data,contents \
|
|
|
|
<input_binary_file> <output_object_file>
|
|
|
|
@end smallexample
|
|
|
|
|
2009-04-14 11:47:44 +02:00
|
|
|
@item --long-section-names @{enable,disable,keep@}
|
|
|
|
Controls the handling of long section names when processing @code{COFF}
|
|
|
|
and @code{PE-COFF} object formats. The default behaviour, @samp{keep},
|
|
|
|
is to preserve long section names if any are present in the input file.
|
|
|
|
The @samp{enable} and @samp{disable} options forcibly enable or disable
|
|
|
|
the use of long section names in the output object; when @samp{disable}
|
|
|
|
is in effect, any long section names in the input object will be truncated.
|
|
|
|
The @samp{enable} option will only emit long section names if any are
|
|
|
|
present in the inputs; this is mostly the same as @samp{keep}, but it
|
2011-11-29 19:07:41 +01:00
|
|
|
is left undefined whether the @samp{enable} option might force the
|
2009-04-14 11:47:44 +02:00
|
|
|
creation of an empty string table in the output file.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --change-leading-char
|
|
|
|
Some object file formats use special characters at the start of
|
|
|
|
symbols. The most common such character is underscore, which compilers
|
2001-08-01 17:54:41 +02:00
|
|
|
often add before every symbol. This option tells @command{objcopy} to
|
1999-05-03 09:29:11 +02:00
|
|
|
change the leading character of every symbol when it converts between
|
|
|
|
object file formats. If the object file formats use the same leading
|
|
|
|
character, this option has no effect. Otherwise, it will add a
|
|
|
|
character, or remove a character, or change a character, as
|
|
|
|
appropriate.
|
|
|
|
|
|
|
|
@item --remove-leading-char
|
|
|
|
If the first character of a global symbol is a special symbol leading
|
|
|
|
character used by the object file format, remove the character. The
|
|
|
|
most common symbol leading character is underscore. This option will
|
|
|
|
remove a leading underscore from all global symbols. This can be useful
|
|
|
|
if you want to link together objects of different file formats with
|
|
|
|
different conventions for symbol names. This is different from
|
2001-08-01 17:54:41 +02:00
|
|
|
@option{--change-leading-char} because it always changes the symbol name
|
1999-05-03 09:29:11 +02:00
|
|
|
when appropriate, regardless of the object file format of the output
|
|
|
|
file.
|
|
|
|
|
2007-04-23 12:59:07 +02:00
|
|
|
@item --reverse-bytes=@var{num}
|
|
|
|
Reverse the bytes in a section with output contents. A section length must
|
|
|
|
be evenly divisible by the value given in order for the swap to be able to
|
|
|
|
take place. Reversing takes place before the interleaving is performed.
|
|
|
|
|
|
|
|
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: @code{12345678}.
|
|
|
|
|
|
|
|
Using @samp{--reverse-bytes=2} for the above example, the bytes in the
|
|
|
|
output file would be ordered @code{21436587}.
|
|
|
|
|
|
|
|
Using @samp{--reverse-bytes=4} for the above example, the bytes in the
|
|
|
|
output file would be ordered @code{43218765}.
|
|
|
|
|
|
|
|
By using @samp{--reverse-bytes=2} for the above example, followed by
|
|
|
|
@samp{--reverse-bytes=4} on the output file, the bytes in the second
|
|
|
|
output file would be ordered @code{34127856}.
|
|
|
|
|
2000-11-03 02:47:13 +01:00
|
|
|
@item --srec-len=@var{ival}
|
|
|
|
Meaningful only for srec output. Set the maximum length of the Srecords
|
|
|
|
being produced to @var{ival}. This length covers both address, data and
|
|
|
|
crc fields.
|
|
|
|
|
|
|
|
@item --srec-forceS3
|
2007-06-29 02:34:14 +02:00
|
|
|
Meaningful only for srec output. Avoid generation of S1/S2 records,
|
2000-11-03 02:47:13 +01:00
|
|
|
creating S3-only record format.
|
|
|
|
|
2000-04-05 05:43:56 +02:00
|
|
|
@item --redefine-sym @var{old}=@var{new}
|
|
|
|
Change the name of a symbol @var{old}, to @var{new}. This can be useful
|
|
|
|
when one is trying link two things together for which you have no
|
|
|
|
source, and there are name collisions.
|
|
|
|
|
2003-06-02 16:45:13 +02:00
|
|
|
@item --redefine-syms=@var{filename}
|
|
|
|
Apply @option{--redefine-sym} to each symbol pair "@var{old} @var{new}"
|
|
|
|
listed in the file @var{filename}. @var{filename} is simply a flat file,
|
|
|
|
with one symbol pair per line. Line comments may be introduced by the hash
|
|
|
|
character. This option may be given more than once.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --weaken
|
|
|
|
Change all global symbols in the file to be weak. This can be useful
|
|
|
|
when building an object which will be linked against other objects using
|
2001-08-01 17:54:41 +02:00
|
|
|
the @option{-R} option to the linker. This option is only effective when
|
1999-05-03 09:29:11 +02:00
|
|
|
using an object file format which supports weak symbols.
|
|
|
|
|
2001-05-30 12:46:28 +02:00
|
|
|
@item --keep-symbols=@var{filename}
|
2001-08-01 17:54:41 +02:00
|
|
|
Apply @option{--keep-symbol} option to each symbol listed in the file
|
2001-05-30 12:46:28 +02:00
|
|
|
@var{filename}. @var{filename} is simply a flat file, with one symbol
|
|
|
|
name per line. Line comments may be introduced by the hash character.
|
|
|
|
This option may be given more than once.
|
|
|
|
|
|
|
|
@item --strip-symbols=@var{filename}
|
2001-08-01 17:54:41 +02:00
|
|
|
Apply @option{--strip-symbol} option to each symbol listed in the file
|
2001-05-30 12:46:28 +02:00
|
|
|
@var{filename}. @var{filename} is simply a flat file, with one symbol
|
|
|
|
name per line. Line comments may be introduced by the hash character.
|
|
|
|
This option may be given more than once.
|
|
|
|
|
2004-12-16 14:16:33 +01:00
|
|
|
@item --strip-unneeded-symbols=@var{filename}
|
|
|
|
Apply @option{--strip-unneeded-symbol} option to each symbol listed in
|
|
|
|
the file @var{filename}. @var{filename} is simply a flat file, with one
|
|
|
|
symbol name per line. Line comments may be introduced by the hash
|
|
|
|
character. This option may be given more than once.
|
|
|
|
|
2001-05-30 12:46:28 +02:00
|
|
|
@item --keep-global-symbols=@var{filename}
|
2001-08-01 17:54:41 +02:00
|
|
|
Apply @option{--keep-global-symbol} option to each symbol listed in the
|
2001-05-30 12:46:28 +02:00
|
|
|
file @var{filename}. @var{filename} is simply a flat file, with one
|
|
|
|
symbol name per line. Line comments may be introduced by the hash
|
|
|
|
character. This option may be given more than once.
|
|
|
|
|
|
|
|
@item --localize-symbols=@var{filename}
|
2001-08-01 17:54:41 +02:00
|
|
|
Apply @option{--localize-symbol} option to each symbol listed in the file
|
2001-05-30 12:46:28 +02:00
|
|
|
@var{filename}. @var{filename} is simply a flat file, with one symbol
|
|
|
|
name per line. Line comments may be introduced by the hash character.
|
|
|
|
This option may be given more than once.
|
|
|
|
|
2005-03-15 18:45:19 +01:00
|
|
|
@item --globalize-symbols=@var{filename}
|
|
|
|
Apply @option{--globalize-symbol} option to each symbol listed in the file
|
|
|
|
@var{filename}. @var{filename} is simply a flat file, with one symbol
|
|
|
|
name per line. Line comments may be introduced by the hash character.
|
2018-10-11 12:38:10 +02:00
|
|
|
This option may be given more than once. Note: this option cannot be
|
|
|
|
used in conjunction with the @option{-G} or @option{--keep-global-symbol}
|
|
|
|
options.
|
2005-03-15 18:45:19 +01:00
|
|
|
|
2001-05-30 12:46:28 +02:00
|
|
|
@item --weaken-symbols=@var{filename}
|
2001-08-01 17:54:41 +02:00
|
|
|
Apply @option{--weaken-symbol} option to each symbol listed in the file
|
2001-05-30 12:46:28 +02:00
|
|
|
@var{filename}. @var{filename} is simply a flat file, with one symbol
|
|
|
|
name per line. Line comments may be introduced by the hash character.
|
|
|
|
This option may be given more than once.
|
|
|
|
|
2001-08-24 15:56:11 +02:00
|
|
|
@item --alt-machine-code=@var{index}
|
|
|
|
If the output architecture has alternate machine codes, use the
|
|
|
|
@var{index}th code instead of the default one. This is useful in case
|
2007-06-29 02:34:14 +02:00
|
|
|
a machine is assigned an official code and the tool-chain adopts the
|
2001-08-24 15:56:11 +02:00
|
|
|
new code, but other applications still depend on the original code
|
2006-02-28 17:09:01 +01:00
|
|
|
being used. For ELF based architectures if the @var{index}
|
|
|
|
alternative does not exist then the value is treated as an absolute
|
|
|
|
number to be stored in the e_machine field of the ELF header.
|
2001-08-24 15:56:11 +02:00
|
|
|
|
2003-12-23 14:01:11 +01:00
|
|
|
@item --writable-text
|
|
|
|
Mark the output text as writable. This option isn't meaningful for all
|
|
|
|
object file formats.
|
|
|
|
|
|
|
|
@item --readonly-text
|
|
|
|
Make the output text write protected. This option isn't meaningful for all
|
|
|
|
object file formats.
|
|
|
|
|
|
|
|
@item --pure
|
|
|
|
Mark the output file as demand paged. This option isn't meaningful for all
|
|
|
|
object file formats.
|
|
|
|
|
|
|
|
@item --impure
|
|
|
|
Mark the output file as impure. This option isn't meaningful for all
|
|
|
|
object file formats.
|
|
|
|
|
2002-12-13 14:19:44 +01:00
|
|
|
@item --prefix-symbols=@var{string}
|
|
|
|
Prefix all symbols in the output file with @var{string}.
|
|
|
|
|
|
|
|
@item --prefix-sections=@var{string}
|
|
|
|
Prefix all section names in the output file with @var{string}.
|
|
|
|
|
|
|
|
@item --prefix-alloc-sections=@var{string}
|
|
|
|
Prefix all the names of all allocated sections in the output file with
|
|
|
|
@var{string}.
|
|
|
|
|
2003-06-26 10:14:10 +02:00
|
|
|
@item --add-gnu-debuglink=@var{path-to-file}
|
2015-03-05 17:45:15 +01:00
|
|
|
Creates a .gnu_debuglink section which contains a reference to
|
|
|
|
@var{path-to-file} and adds it to the output file. Note: the file at
|
|
|
|
@var{path-to-file} must exist. Part of the process of adding the
|
|
|
|
.gnu_debuglink section involves embedding a checksum of the contents
|
|
|
|
of the debug info file into the section.
|
|
|
|
|
|
|
|
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 @option{--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
|
|
|
|
@option{--add-gnu-debuglink} option without any directory components,
|
|
|
|
like this:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
objcopy --add-gnu-debuglink=foo.debug
|
|
|
|
@end smallexample
|
2019-05-14 11:40:04 +02:00
|
|
|
|
2015-03-05 17:45:15 +01:00
|
|
|
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:
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
|
|
|
|
@item * The same directory as the executable.
|
|
|
|
|
|
|
|
@item * A sub-directory of the directory containing the executable
|
|
|
|
called .debug
|
|
|
|
|
|
|
|
@item * A global debug directory such as /usr/lib/debug.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
As long as the debug info file has been installed into one of these
|
|
|
|
locations before the debugger is run everything should work
|
|
|
|
correctly.
|
2003-06-26 10:14:10 +02:00
|
|
|
|
2005-11-15 09:33:38 +01:00
|
|
|
@item --keep-file-symbols
|
|
|
|
When stripping a file, perhaps with @option{--strip-debug} or
|
|
|
|
@option{--strip-unneeded}, retain any symbols specifying source file names,
|
|
|
|
which would otherwise get stripped.
|
|
|
|
|
2003-06-26 10:14:10 +02:00
|
|
|
@item --only-keep-debug
|
2005-05-01 18:02:56 +02:00
|
|
|
Strip a file, removing contents of any sections that would not be
|
|
|
|
stripped by @option{--strip-debug} and leaving the debugging sections
|
2007-06-29 02:34:14 +02:00
|
|
|
intact. In ELF files, this preserves all note sections in the output.
|
2003-06-26 10:14:10 +02:00
|
|
|
|
2015-08-05 17:16:39 +02:00
|
|
|
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.
|
|
|
|
|
2003-06-26 10:14:10 +02:00
|
|
|
The intention is that this option will be used in conjunction with
|
|
|
|
@option{--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:
|
|
|
|
|
2009-08-27 16:58:08 +02:00
|
|
|
@enumerate
|
2018-06-26 13:56:23 +02:00
|
|
|
@item Link the executable as normal. Assuming that it is called
|
2009-08-27 16:58:08 +02:00
|
|
|
@code{foo} then...
|
|
|
|
@item Run @code{objcopy --only-keep-debug foo foo.dbg} to
|
|
|
|
create a file containing the debugging info.
|
|
|
|
@item Run @code{objcopy --strip-debug foo} to create a
|
|
|
|
stripped executable.
|
|
|
|
@item Run @code{objcopy --add-gnu-debuglink=foo.dbg foo}
|
|
|
|
to add a link to the debugging info into the stripped executable.
|
|
|
|
@end enumerate
|
|
|
|
|
|
|
|
Note---the choice of @code{.dbg} as an extension for the debug info
|
|
|
|
file is arbitrary. Also the @code{--only-keep-debug} step is
|
|
|
|
optional. You could instead do this:
|
|
|
|
|
|
|
|
@enumerate
|
|
|
|
@item Link the executable as normal.
|
|
|
|
@item Copy @code{foo} to @code{foo.full}
|
|
|
|
@item Run @code{objcopy --strip-debug foo}
|
|
|
|
@item Run @code{objcopy --add-gnu-debuglink=foo.full foo}
|
|
|
|
@end enumerate
|
|
|
|
|
|
|
|
i.e., the file pointed to by the @option{--add-gnu-debuglink} can be the
|
|
|
|
full executable. It does not have to be a file created by the
|
|
|
|
@option{--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.
|
|
|
|
|
2012-05-08 19:49:36 +02:00
|
|
|
@item --strip-dwo
|
|
|
|
Remove the contents of all DWARF .dwo sections, leaving the
|
|
|
|
remaining debugging sections and all symbols intact.
|
|
|
|
This option is intended for use by the compiler as part of
|
|
|
|
the @option{-gsplit-dwarf} option, which splits debug information
|
|
|
|
between the .o file and a separate .dwo file. The compiler
|
|
|
|
generates all debug information in the same file, then uses
|
|
|
|
the @option{--extract-dwo} option to copy the .dwo sections to
|
|
|
|
the .dwo file, then the @option{--strip-dwo} option to remove
|
|
|
|
those sections from the original .o file.
|
|
|
|
|
|
|
|
@item --extract-dwo
|
|
|
|
Extract the contents of all DWARF .dwo sections. See the
|
|
|
|
@option{--strip-dwo} option for more information.
|
|
|
|
|
bfd/
2009-04-17 H.J. Lu <hongjiu.lu@intel.com>
PR binutils/10074
* coffcode.h (bfd_pei_p): New.
* config.bfd: Remove bfd_efi_bsdrv_ia32_vec,
bfd_efi_rtdrv_ia32_vec, bfd_efi_bsdrv_x86_64_vec,
bfd_efi_rtdrv_x86_64_vec, bfd_efi_bsdrv_ia64_vec and
bfd_efi_rtdrv_ia64_vec. Replace bfd_efi_app_ia32_vec,
bfd_efi_app_x86_64_vec and bfd_efi_app_ia64_vec with
i386pei_vec, x86_64pei_vec and bfd_pei_ia64_vec, respectively.
* configure.in: Remove bfd_efi_bsdrv_ia32_vec,
bfd_efi_rtdrv_ia32_vec, bfd_efi_bsdrv_x86_64_vec,
bfd_efi_rtdrv_x86_64_vec,
bfd_efi_bsdrv_ia64_vec and bfd_efi_rtdrv_ia64_vec. Replace
bfd_efi_ia64_vec with bfd_pei_ia64_vec.
* targets.c: Likewise.
* configure: Regenerated.
* libcoff.h: Likewise.
* Makefile.in: Likewise.
* efi-app-ia32.c: Removed.
* efi-app-x86_64.c: Likewise.
* efi-bsdrv-ia32.c: Likewise.
* efi-bsdrv-ia64.c: Likewise.
* efi-bsdrv-x86_64.c: Likewise.
* efi-rtdrv-ia32.c: Likewise.
* efi-rtdrv-ia64.c: Likewise.
* efi-rtdrv-x86_64.c: Likewise.
* efi-rtdrv-ia32.c: Likewise.
* efi-app-ia64.c: Moved to ...
* pei-ia64.c: This.
(TARGET_SYM): Set to bfd_pei_ia64_vec.
(TARGET_NAME): Set to pei-ia64.
* libpei.h (bfd_target_pei_p): Removed.
(bfd_target_pei_arch): Likewise.
(bfd_target_efi_app_p): Likewise.
(bfd_target_efi_app_arch): Likewise.
(bfd_target_efi_bsdrv_p): Likewise.
(bfd_target_efi_bsdrv_arch): Likewise.
(bfd_target_efi_rtdrv_p): Likewise.
(bfd_target_efi_rtdrv_arch): Likewise.
(bfd_pe_executable_p): Likewise.
* Makefile.am (BFD32_BACKENDS): Remove efi-app-ia32.lo,
efi-bsdrv-ia32.lo and efi-rtdrv-ia32.lo.
(BFD32_BACKENDS_CFILES): Remove efi-app-ia32.c, efi-bsdrv-ia32.c
and efi-rtdrv-ia32.c.
(BFD64_BACKENDS): Remove efi-app-ia64.lo, efi-bsdrv-ia64.lo,
efi-rtdrv-ia64.lo, efi-app-x86_64.lo, efi-bsdrv-x86_64.lo and
efi-rtdrv-x86_64.lo. Add pei-ia64.lo.
(BFD64_BACKENDS_CFILES): Remove efi-app-ia64.c, efi-bsdrv-ia64.c,
efi-rtdrv-ia64.c, efi-app-x86_64.c, efi-bsdrv-x86_64.c and
efi-rtdrv-x86_64.c. Add pei-ia64.c.
(efi-app-ia64.lo): Removed.
(efi-bsdrv-ia32.lo): Likewise.
(efi-rtdrv-ia32.lo): Likewise.
(efi-app-ia64.lo): Likewise.
(efi-bsdrv-ia64.lo): Likewise.
(efi-rtdrv-ia64.lo): Likewise.
(efi-app-x86_64.lo): Likewise.
(efi-bsdrv-x86_64.lo): Likewise.
(efi-rtdrv-x86_64.lo): Likewise.
(pei-ia64.lo): New.
* peicode.h (coff_swap_scnhdr_in): Replace bfd_pe_executable_p
with bfd_pei_p.
(arch_type): Removed.
(pe_arch): Likewise.
(pe_bfd_object_p): Just return coff_object_p.
* peXXigen.c (_bfd_XXi_swap_scnhdr_out): Replace
bfd_pe_executable_p with bfd_pei_p.
binutils/
2009-04-17 H.J. Lu <hongjiu.lu@intel.com>
PR binutils/10074
* objcopy.c: Include coff/i386.h and coff/pe.h.
(pe_file_alignment): New.
(pe_heap_commit): Likewise.
(pe_heap_reserve): Likewise.
(pe_image_base): Likewise.
(pe_section_alignment): Likewise.
(pe_stack_commit): Likewise.
(pe_stack_reserve): Likewise.
(pe_subsystem): Likewise.
(pe_major_subsystem_version): Likewise.
(pe_minor_subsystem_version): Likewise.
(set_pe_subsystem): Likewise.
(convert_efi_target): Likewise.
(command_line_switch): Add OPTION_FILE_ALIGNMENT,
OPTION_HEAP, OPTION_IMAGE_BASE, OPTION_SECTION_ALIGNMENT,
OPTION_STACK and OPTION_SUBSYSTEM.
(copy_options): Likewise.
(copy_usage): Add --file-alignment, --heap, --image-base,
--section-alignment, --stack and --subsystem.
(copy_object): Set up PE parameters.
(copy_main): Process Add OPTION_FILE_ALIGNMENT,
OPTION_HEAP, OPTION_IMAGE_BASE, OPTION_SECTION_ALIGNMENT,
OPTION_STACK and OPTION_SUBSYSTEM. Convert EFI target to
PEI target.
* NEWS: Mention --file-alignment, --heap, --image-base,
--section-alignment, --stack and --subsystem command line
options for objcopy.
* doc/binutils.texi: Document --file-alignment, --heap,
--image-base, --section-alignment, --stack and --subsystem
command line options for objcopy.
2009-04-17 15:46:18 +02:00
|
|
|
@item --file-alignment @var{num}
|
|
|
|
Specify the file alignment. Sections in the file will always begin at
|
|
|
|
file offsets which are multiples of this number. This defaults to
|
|
|
|
512.
|
|
|
|
[This option is specific to PE targets.]
|
|
|
|
|
|
|
|
@item --heap @var{reserve}
|
|
|
|
@itemx --heap @var{reserve},@var{commit}
|
|
|
|
Specify the number of bytes of memory to reserve (and optionally commit)
|
|
|
|
to be used as heap for this program.
|
|
|
|
[This option is specific to PE targets.]
|
|
|
|
|
|
|
|
@item --image-base @var{value}
|
|
|
|
Use @var{value} as the base address of your program or dll. This is
|
|
|
|
the lowest memory location that will be used when your program or dll
|
|
|
|
is loaded. To reduce the need to relocate and improve performance of
|
|
|
|
your dlls, each should have a unique base address and not overlap any
|
|
|
|
other dlls. The default is 0x400000 for executables, and 0x10000000
|
|
|
|
for dlls.
|
|
|
|
[This option is specific to PE targets.]
|
|
|
|
|
|
|
|
@item --section-alignment @var{num}
|
2019-08-28 13:33:41 +02:00
|
|
|
Sets the section alignment field in the PE header. Sections in memory
|
|
|
|
will always begin at addresses which are a multiple of this number.
|
|
|
|
Defaults to 0x1000.
|
bfd/
2009-04-17 H.J. Lu <hongjiu.lu@intel.com>
PR binutils/10074
* coffcode.h (bfd_pei_p): New.
* config.bfd: Remove bfd_efi_bsdrv_ia32_vec,
bfd_efi_rtdrv_ia32_vec, bfd_efi_bsdrv_x86_64_vec,
bfd_efi_rtdrv_x86_64_vec, bfd_efi_bsdrv_ia64_vec and
bfd_efi_rtdrv_ia64_vec. Replace bfd_efi_app_ia32_vec,
bfd_efi_app_x86_64_vec and bfd_efi_app_ia64_vec with
i386pei_vec, x86_64pei_vec and bfd_pei_ia64_vec, respectively.
* configure.in: Remove bfd_efi_bsdrv_ia32_vec,
bfd_efi_rtdrv_ia32_vec, bfd_efi_bsdrv_x86_64_vec,
bfd_efi_rtdrv_x86_64_vec,
bfd_efi_bsdrv_ia64_vec and bfd_efi_rtdrv_ia64_vec. Replace
bfd_efi_ia64_vec with bfd_pei_ia64_vec.
* targets.c: Likewise.
* configure: Regenerated.
* libcoff.h: Likewise.
* Makefile.in: Likewise.
* efi-app-ia32.c: Removed.
* efi-app-x86_64.c: Likewise.
* efi-bsdrv-ia32.c: Likewise.
* efi-bsdrv-ia64.c: Likewise.
* efi-bsdrv-x86_64.c: Likewise.
* efi-rtdrv-ia32.c: Likewise.
* efi-rtdrv-ia64.c: Likewise.
* efi-rtdrv-x86_64.c: Likewise.
* efi-rtdrv-ia32.c: Likewise.
* efi-app-ia64.c: Moved to ...
* pei-ia64.c: This.
(TARGET_SYM): Set to bfd_pei_ia64_vec.
(TARGET_NAME): Set to pei-ia64.
* libpei.h (bfd_target_pei_p): Removed.
(bfd_target_pei_arch): Likewise.
(bfd_target_efi_app_p): Likewise.
(bfd_target_efi_app_arch): Likewise.
(bfd_target_efi_bsdrv_p): Likewise.
(bfd_target_efi_bsdrv_arch): Likewise.
(bfd_target_efi_rtdrv_p): Likewise.
(bfd_target_efi_rtdrv_arch): Likewise.
(bfd_pe_executable_p): Likewise.
* Makefile.am (BFD32_BACKENDS): Remove efi-app-ia32.lo,
efi-bsdrv-ia32.lo and efi-rtdrv-ia32.lo.
(BFD32_BACKENDS_CFILES): Remove efi-app-ia32.c, efi-bsdrv-ia32.c
and efi-rtdrv-ia32.c.
(BFD64_BACKENDS): Remove efi-app-ia64.lo, efi-bsdrv-ia64.lo,
efi-rtdrv-ia64.lo, efi-app-x86_64.lo, efi-bsdrv-x86_64.lo and
efi-rtdrv-x86_64.lo. Add pei-ia64.lo.
(BFD64_BACKENDS_CFILES): Remove efi-app-ia64.c, efi-bsdrv-ia64.c,
efi-rtdrv-ia64.c, efi-app-x86_64.c, efi-bsdrv-x86_64.c and
efi-rtdrv-x86_64.c. Add pei-ia64.c.
(efi-app-ia64.lo): Removed.
(efi-bsdrv-ia32.lo): Likewise.
(efi-rtdrv-ia32.lo): Likewise.
(efi-app-ia64.lo): Likewise.
(efi-bsdrv-ia64.lo): Likewise.
(efi-rtdrv-ia64.lo): Likewise.
(efi-app-x86_64.lo): Likewise.
(efi-bsdrv-x86_64.lo): Likewise.
(efi-rtdrv-x86_64.lo): Likewise.
(pei-ia64.lo): New.
* peicode.h (coff_swap_scnhdr_in): Replace bfd_pe_executable_p
with bfd_pei_p.
(arch_type): Removed.
(pe_arch): Likewise.
(pe_bfd_object_p): Just return coff_object_p.
* peXXigen.c (_bfd_XXi_swap_scnhdr_out): Replace
bfd_pe_executable_p with bfd_pei_p.
binutils/
2009-04-17 H.J. Lu <hongjiu.lu@intel.com>
PR binutils/10074
* objcopy.c: Include coff/i386.h and coff/pe.h.
(pe_file_alignment): New.
(pe_heap_commit): Likewise.
(pe_heap_reserve): Likewise.
(pe_image_base): Likewise.
(pe_section_alignment): Likewise.
(pe_stack_commit): Likewise.
(pe_stack_reserve): Likewise.
(pe_subsystem): Likewise.
(pe_major_subsystem_version): Likewise.
(pe_minor_subsystem_version): Likewise.
(set_pe_subsystem): Likewise.
(convert_efi_target): Likewise.
(command_line_switch): Add OPTION_FILE_ALIGNMENT,
OPTION_HEAP, OPTION_IMAGE_BASE, OPTION_SECTION_ALIGNMENT,
OPTION_STACK and OPTION_SUBSYSTEM.
(copy_options): Likewise.
(copy_usage): Add --file-alignment, --heap, --image-base,
--section-alignment, --stack and --subsystem.
(copy_object): Set up PE parameters.
(copy_main): Process Add OPTION_FILE_ALIGNMENT,
OPTION_HEAP, OPTION_IMAGE_BASE, OPTION_SECTION_ALIGNMENT,
OPTION_STACK and OPTION_SUBSYSTEM. Convert EFI target to
PEI target.
* NEWS: Mention --file-alignment, --heap, --image-base,
--section-alignment, --stack and --subsystem command line
options for objcopy.
* doc/binutils.texi: Document --file-alignment, --heap,
--image-base, --section-alignment, --stack and --subsystem
command line options for objcopy.
2009-04-17 15:46:18 +02:00
|
|
|
[This option is specific to PE targets.]
|
|
|
|
|
|
|
|
@item --stack @var{reserve}
|
|
|
|
@itemx --stack @var{reserve},@var{commit}
|
|
|
|
Specify the number of bytes of memory to reserve (and optionally commit)
|
|
|
|
to be used as stack for this program.
|
|
|
|
[This option is specific to PE targets.]
|
|
|
|
|
|
|
|
@item --subsystem @var{which}
|
|
|
|
@itemx --subsystem @var{which}:@var{major}
|
|
|
|
@itemx --subsystem @var{which}:@var{major}.@var{minor}
|
|
|
|
Specifies the subsystem under which your program will execute. The
|
|
|
|
legal values for @var{which} are @code{native}, @code{windows},
|
|
|
|
@code{console}, @code{posix}, @code{efi-app}, @code{efi-bsd},
|
2009-04-17 17:03:48 +02:00
|
|
|
@code{efi-rtd}, @code{sal-rtd}, and @code{xbox}. You may optionally set
|
bfd/
2009-04-17 H.J. Lu <hongjiu.lu@intel.com>
PR binutils/10074
* coffcode.h (bfd_pei_p): New.
* config.bfd: Remove bfd_efi_bsdrv_ia32_vec,
bfd_efi_rtdrv_ia32_vec, bfd_efi_bsdrv_x86_64_vec,
bfd_efi_rtdrv_x86_64_vec, bfd_efi_bsdrv_ia64_vec and
bfd_efi_rtdrv_ia64_vec. Replace bfd_efi_app_ia32_vec,
bfd_efi_app_x86_64_vec and bfd_efi_app_ia64_vec with
i386pei_vec, x86_64pei_vec and bfd_pei_ia64_vec, respectively.
* configure.in: Remove bfd_efi_bsdrv_ia32_vec,
bfd_efi_rtdrv_ia32_vec, bfd_efi_bsdrv_x86_64_vec,
bfd_efi_rtdrv_x86_64_vec,
bfd_efi_bsdrv_ia64_vec and bfd_efi_rtdrv_ia64_vec. Replace
bfd_efi_ia64_vec with bfd_pei_ia64_vec.
* targets.c: Likewise.
* configure: Regenerated.
* libcoff.h: Likewise.
* Makefile.in: Likewise.
* efi-app-ia32.c: Removed.
* efi-app-x86_64.c: Likewise.
* efi-bsdrv-ia32.c: Likewise.
* efi-bsdrv-ia64.c: Likewise.
* efi-bsdrv-x86_64.c: Likewise.
* efi-rtdrv-ia32.c: Likewise.
* efi-rtdrv-ia64.c: Likewise.
* efi-rtdrv-x86_64.c: Likewise.
* efi-rtdrv-ia32.c: Likewise.
* efi-app-ia64.c: Moved to ...
* pei-ia64.c: This.
(TARGET_SYM): Set to bfd_pei_ia64_vec.
(TARGET_NAME): Set to pei-ia64.
* libpei.h (bfd_target_pei_p): Removed.
(bfd_target_pei_arch): Likewise.
(bfd_target_efi_app_p): Likewise.
(bfd_target_efi_app_arch): Likewise.
(bfd_target_efi_bsdrv_p): Likewise.
(bfd_target_efi_bsdrv_arch): Likewise.
(bfd_target_efi_rtdrv_p): Likewise.
(bfd_target_efi_rtdrv_arch): Likewise.
(bfd_pe_executable_p): Likewise.
* Makefile.am (BFD32_BACKENDS): Remove efi-app-ia32.lo,
efi-bsdrv-ia32.lo and efi-rtdrv-ia32.lo.
(BFD32_BACKENDS_CFILES): Remove efi-app-ia32.c, efi-bsdrv-ia32.c
and efi-rtdrv-ia32.c.
(BFD64_BACKENDS): Remove efi-app-ia64.lo, efi-bsdrv-ia64.lo,
efi-rtdrv-ia64.lo, efi-app-x86_64.lo, efi-bsdrv-x86_64.lo and
efi-rtdrv-x86_64.lo. Add pei-ia64.lo.
(BFD64_BACKENDS_CFILES): Remove efi-app-ia64.c, efi-bsdrv-ia64.c,
efi-rtdrv-ia64.c, efi-app-x86_64.c, efi-bsdrv-x86_64.c and
efi-rtdrv-x86_64.c. Add pei-ia64.c.
(efi-app-ia64.lo): Removed.
(efi-bsdrv-ia32.lo): Likewise.
(efi-rtdrv-ia32.lo): Likewise.
(efi-app-ia64.lo): Likewise.
(efi-bsdrv-ia64.lo): Likewise.
(efi-rtdrv-ia64.lo): Likewise.
(efi-app-x86_64.lo): Likewise.
(efi-bsdrv-x86_64.lo): Likewise.
(efi-rtdrv-x86_64.lo): Likewise.
(pei-ia64.lo): New.
* peicode.h (coff_swap_scnhdr_in): Replace bfd_pe_executable_p
with bfd_pei_p.
(arch_type): Removed.
(pe_arch): Likewise.
(pe_bfd_object_p): Just return coff_object_p.
* peXXigen.c (_bfd_XXi_swap_scnhdr_out): Replace
bfd_pe_executable_p with bfd_pei_p.
binutils/
2009-04-17 H.J. Lu <hongjiu.lu@intel.com>
PR binutils/10074
* objcopy.c: Include coff/i386.h and coff/pe.h.
(pe_file_alignment): New.
(pe_heap_commit): Likewise.
(pe_heap_reserve): Likewise.
(pe_image_base): Likewise.
(pe_section_alignment): Likewise.
(pe_stack_commit): Likewise.
(pe_stack_reserve): Likewise.
(pe_subsystem): Likewise.
(pe_major_subsystem_version): Likewise.
(pe_minor_subsystem_version): Likewise.
(set_pe_subsystem): Likewise.
(convert_efi_target): Likewise.
(command_line_switch): Add OPTION_FILE_ALIGNMENT,
OPTION_HEAP, OPTION_IMAGE_BASE, OPTION_SECTION_ALIGNMENT,
OPTION_STACK and OPTION_SUBSYSTEM.
(copy_options): Likewise.
(copy_usage): Add --file-alignment, --heap, --image-base,
--section-alignment, --stack and --subsystem.
(copy_object): Set up PE parameters.
(copy_main): Process Add OPTION_FILE_ALIGNMENT,
OPTION_HEAP, OPTION_IMAGE_BASE, OPTION_SECTION_ALIGNMENT,
OPTION_STACK and OPTION_SUBSYSTEM. Convert EFI target to
PEI target.
* NEWS: Mention --file-alignment, --heap, --image-base,
--section-alignment, --stack and --subsystem command line
options for objcopy.
* doc/binutils.texi: Document --file-alignment, --heap,
--image-base, --section-alignment, --stack and --subsystem
command line options for objcopy.
2009-04-17 15:46:18 +02:00
|
|
|
the subsystem version also. Numeric values are also accepted for
|
|
|
|
@var{which}.
|
|
|
|
[This option is specific to PE targets.]
|
|
|
|
|
2007-03-01 17:39:42 +01:00
|
|
|
@item --extract-symbol
|
|
|
|
Keep the file's section flags and symbols but remove all section data.
|
|
|
|
Specifically, the option:
|
|
|
|
|
|
|
|
@itemize
|
|
|
|
@item removes the contents of all sections;
|
|
|
|
@item sets the size of every section to zero; and
|
|
|
|
@item sets the file's start address to zero.
|
|
|
|
@end itemize
|
2007-06-29 02:34:14 +02:00
|
|
|
|
2007-03-01 17:39:42 +01:00
|
|
|
This option is used to build a @file{.sym} file for a VxWorks kernel.
|
|
|
|
It can also be a useful way of reducing the size of a @option{--just-symbols}
|
|
|
|
linker input file.
|
|
|
|
|
2010-10-29 14:10:39 +02:00
|
|
|
@item --compress-debug-sections
|
2015-07-14 19:25:52 +02:00
|
|
|
Compress DWARF debug sections using zlib with SHF_COMPRESSED from the
|
|
|
|
ELF ABI. Note - if compression would actually make a section
|
|
|
|
@emph{larger}, then it is not compressed.
|
2010-10-29 14:10:39 +02:00
|
|
|
|
2015-04-08 16:53:54 +02:00
|
|
|
@item --compress-debug-sections=none
|
|
|
|
@itemx --compress-debug-sections=zlib
|
|
|
|
@itemx --compress-debug-sections=zlib-gnu
|
|
|
|
@itemx --compress-debug-sections=zlib-gabi
|
|
|
|
For ELF files, these options control how DWARF debug sections are
|
|
|
|
compressed. @option{--compress-debug-sections=none} is equivalent
|
2016-02-12 22:38:57 +01:00
|
|
|
to @option{--decompress-debug-sections}.
|
2015-04-08 16:53:54 +02:00
|
|
|
@option{--compress-debug-sections=zlib} and
|
2015-07-14 19:25:52 +02:00
|
|
|
@option{--compress-debug-sections=zlib-gabi} are equivalent to
|
2015-04-08 16:53:54 +02:00
|
|
|
@option{--compress-debug-sections}.
|
2015-07-14 19:25:52 +02:00
|
|
|
@option{--compress-debug-sections=zlib-gnu} compresses DWARF debug
|
|
|
|
sections using zlib. The debug sections are renamed to begin with
|
|
|
|
@samp{.zdebug} instead of @samp{.debug}. Note - if compression would
|
|
|
|
actually make a section @emph{larger}, then it is not compressed nor
|
|
|
|
renamed.
|
2015-04-08 16:53:54 +02:00
|
|
|
|
2010-10-29 14:10:39 +02:00
|
|
|
@item --decompress-debug-sections
|
2015-03-18 16:47:13 +01:00
|
|
|
Decompress DWARF debug sections using zlib. The original section
|
|
|
|
names of the compressed sections are restored.
|
2010-10-29 14:10:39 +02:00
|
|
|
|
Properly implement STT_COMMON
The BFD configure option, --enable-elf-stt-common, can't be to used to
verify STT_COMMON implementation with the normal binutils build. Instead,
this patch removes it from BFD. It adds --elf-stt-common=[no|yes] to ELF
assembler/objcopy and adds -z common/-z nocommon to ld.
A configure option, --enable-elf-stt-common, is added to gas to specify
whether ELF assembler should generate common symbols with the STT_COMMON
type by default.
Since BSF_KEEP_G is never used, it is renamed to BSF_ELF_COMMON for ELF
common symbols.
bfd/
PR ld/19645
* bfd.c (bfd): Change flags to 20 bits.
(BFD_CONVERT_ELF_COMMON): New.
(BFD_USE_ELF_STT_COMMON): Likewise.
(BFD_FLAGS_SAVED): Add BFD_CONVERT_ELF_COMMON and
BFD_USE_ELF_STT_COMMON.
(BFD_FLAGS_FOR_BFD_USE_MASK): Likewise.
* configure.ac: Remove --enable-elf-stt-common.
* elf.c (swap_out_syms): Choose STT_COMMON or STT_OBJECT for
common symbol depending on BFD_CONVERT_ELF_COMMON and
BFD_USE_ELF_STT_COMMON.
* elfcode.h (elf_slurp_symbol_table): Set BSF_ELF_COMMON for
STT_COMMON.
* elflink.c (bfd_elf_link_mark_dynamic_symbol): Also check
STT_COMMON.
(elf_link_convert_common_type): New function.
(elf_link_output_extsym): Choose STT_COMMON or STT_OBJECT for
common symbol depending on BFD_CONVERT_ELF_COMMON and
BFD_USE_ELF_STT_COMMON. Set sym.st_info after sym.st_shndx.
* elfxx-target.h (TARGET_BIG_SYM): Add BFD_CONVERT_ELF_COMMON
and BFD_USE_ELF_STT_COMMON to object_flags.
(TARGET_LITTLE_SYM): Likewise.
* syms.c (BSF_KEEP_G): Renamed to ...
(BSF_ELF_COMMON): This.
* bfd-in2.h: Regenerated.
* config.in: Likewise.
* configure: Likewise.
binutils/
PR ld/19645
* NEWS: Mention --elf-stt-common= for objcopy.
* doc/binutils.texi: Document --elf-stt-common= for objcopy.
* objcopy.c (do_elf_stt_common): New.
(command_line_switch): Add OPTION_ELF_STT_COMMON.
(copy_options): Add --elf-stt-common=.
(copy_usage): Add --elf-stt-common=.
(copy_object): Also check do_elf_stt_common for ELF targets.
(copy_file): Handle do_elf_stt_common.
(copy_main): Handle OPTION_ELF_STT_COMMON.
* readelf.c (apply_relocations): Support STT_COMMON.
* testsuite/binutils-all/common-1.s: New file.
* testsuite/binutils-all/common-1a.d: Likewise.
* testsuite/binutils-all/common-1b.d: Likewise.
* testsuite/binutils-all/common-1c.d: Likewise.
* testsuite/binutils-all/common-1d.d: Likewise.
* testsuite/binutils-all/common-1e.d: Likewise.
* testsuite/binutils-all/common-1f.d: Likewise.
* testsuite/binutils-all/common-2.s: Likewise.
* testsuite/binutils-all/common-2a.d: Likewise.
* testsuite/binutils-all/common-2b.d: Likewise.
* testsuite/binutils-all/common-2c.d: Likewise.
* testsuite/binutils-all/common-2d.d: Likewise.
* testsuite/binutils-all/common-2e.d: Likewise.
* testsuite/binutils-all/common-2f.d: Likewise.
* testsuite/binutils-all/objcopy.exp
(objcopy_test_elf_common_symbols): New proc.
Run objcopy_test_elf_common_symbols for ELF targets
gas/
PR ld/19645
* NEWS: Mention --enable-elf-stt-common and --elf-stt-common=
for ELF assemblers.
* as.c (flag_use_elf_stt_common): New.
(show_usage): Add --elf-stt-common=.
(option_values): Add OPTION_ELF_STT_COMMON.
(std_longopts): Add --elf-stt-common=.
(parse_args): Handle --elf-stt-common=.
* as.h (flag_use_elf_stt_common): New.
* config.in: Regenerated.
* configure: Likewise.
* configure.ac: Add --enable-elf-stt-common and define
DEFAULT_GENERATE_ELF_STT_COMMON.
* gas/write.c (write_object_file): Set BFD_CONVERT_ELF_COMMON
and BFD_USE_ELF_STT_COMMON if flag_use_elf_stt_common is set.
* doc/as.texinfo: Document --elf-stt-common=.
* testsuite/gas/elf/common3.s: New file.
* testsuite/gas/elf/common3a.d: Likewise.
* testsuite/gas/elf/common3b.d: Likewise.
* testsuite/gas/elf/common4.s: Likewise.
* testsuite/gas/elf/common4a.d: Likewise.
* testsuite/gas/elf/common4b.d: Likewise.
* testsuite/gas/i386/dw2-compress-3b.d: Likewise.
* testsuite/gas/i386/dw2-compressed-3b.d: Likewise.
* testsuite/gas/elf/elf.exp: Run common3a, common3b, common4a
and common4b.
* testsuite/gas/i386/dw2-compress-3.d: Renamed to ...
* testsuite/gas/i386/dw2-compress-3a.d: This. Pass
--elf-stt-common=no to as.
* testsuite/gas/i386/dw2-compressed-3.d: Renamed to ...
* testsuite/gas/i386/dw2-compressed-3a.d: This. Pass
--elf-stt-common=no to as.
* testsuite/gas/i386/i386.exp: Run dw2-compress-3a,
dw2-compress-3b, dw2-compressed-3a and dw2-compressed-3b instead
of dw2-compress-3 and dw2-compressed-3.
include/
PR ld/19645
* bfdlink.h (bfd_link_elf_stt_common): New enum.
(bfd_link_info): Add elf_stt_common.
ld/
PR ld/19645
* NEWS: Mention -z common/-z nocommon for ELF targets.
* emultempl/elf32.em (gld${EMULATION_NAME}_handle_option): Handle
-z common and -z nocommon.
* ld.texinfo: Document -z common/-z nocommon.
* lexsup.c (elf_shlib_list_options): Add -z common/-z nocommon.
* testsuite/ld-elf/tls_common.exp: Test --elf-stt-common=no and
--elf-stt-common=yes with assembler.
* testsuite/ld-elfcomm/common-1.s: New file.
* testsuite/ld-elfcomm/common-1a.d: Likewise.
* testsuite/ld-elfcomm/common-1b.d: Likewise.
* testsuite/ld-elfcomm/common-1c.d: Likewise.
* testsuite/ld-elfcomm/common-1d.d: Likewise.
* testsuite/ld-elfcomm/common-1e.d: Likewise.
* testsuite/ld-elfcomm/common-1f.d: Likewise.
* testsuite/ld-elfcomm/common-2.s: Likewise.
* testsuite/ld-elfcomm/common-2a.d: Likewise.
* testsuite/ld-elfcomm/common-2b.d: Likewise.
* testsuite/ld-elfcomm/common-2c.d: Likewise.
* testsuite/ld-elfcomm/common-2d.d: Likewise.
* testsuite/ld-elfcomm/common-2e.d: Likewise.
* testsuite/ld-elfcomm/common-2f.d: Likewise.
* testsuite/ld-elfcomm/common-3a.rd: Likewise.
* testsuite/ld-elfcomm/common-3b.rd: Likewise.
* testsuite/ld-i386/pr19645.d: Likewise.
* testsuite/ld-i386/pr19645.s: Likewise.
* testsuite/ld-x86-64/largecomm-1.s: Likewise.
* testsuite/ld-x86-64/largecomm-1a.d: Likewise.
* testsuite/ld-x86-64/largecomm-1b.d: Likewise.
* testsuite/ld-x86-64/largecomm-1c.d: Likewise.
* testsuite/ld-x86-64/largecomm-1d.d: Likewise.
* testsuite/ld-x86-64/largecomm-1e.d: Likewise.
* testsuite/ld-x86-64/largecomm-1f.d: Likewise.
* testsuite/ld-x86-64/pr19645.d: Likewise.
* testsuite/ld-x86-64/pr19645.s: Likewise.
* testsuite/ld-elfcomm/elfcomm.exp: Test --elf-stt-common=yes
with assembler.
(assembler_generates_commons): Removed.
Run -z common/-z nocommon tests. Run *.d tests.
* testsuite/ld-i386/i386.exp: Run pr19645.
* testsuite/ld-x86-64/x86-64.exp: Likewise.
* testsuite/ld-x86-64/dwarfreloc.exp: Test --elf-stt-common with
assembler. Test STT_COMMON with readelf.
2016-02-22 18:18:52 +01:00
|
|
|
@item --elf-stt-common=yes
|
|
|
|
@itemx --elf-stt-common=no
|
|
|
|
For ELF files, these options control whether common symbols should be
|
|
|
|
converted to the @code{STT_COMMON} or @code{STT_OBJECT} type.
|
|
|
|
@option{--elf-stt-common=yes} converts common symbol type to
|
|
|
|
@code{STT_COMMON}. @option{--elf-stt-common=no} converts common symbol
|
|
|
|
type to @code{STT_OBJECT}.
|
|
|
|
|
2017-03-01 12:09:46 +01:00
|
|
|
@item --merge-notes
|
2017-04-13 15:50:56 +02:00
|
|
|
@itemx --no-merge-notes
|
|
|
|
For ELF files, attempt (or do not attempt) to reduce the size of any
|
|
|
|
SHT_NOTE type sections by removing duplicate notes.
|
2017-03-01 12:09:46 +01:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -V
|
|
|
|
@itemx --version
|
2001-08-01 17:54:41 +02:00
|
|
|
Show the version number of @command{objcopy}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2019-05-14 11:40:04 +02:00
|
|
|
@item --verilog-data-width=@var{bytes}
|
|
|
|
For Verilog output, this options controls the number of bytes
|
|
|
|
converted for each output data element. The input target controls the
|
|
|
|
endianness of the conversion.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -v
|
|
|
|
@itemx --verbose
|
|
|
|
Verbose output: list all object files modified. In the case of
|
|
|
|
archives, @samp{objcopy -V} lists all members of the archive.
|
|
|
|
|
|
|
|
@item --help
|
2001-08-01 17:54:41 +02:00
|
|
|
Show a summary of the options to @command{objcopy}.
|
2003-03-24 17:11:46 +01:00
|
|
|
|
|
|
|
@item --info
|
|
|
|
Display a list showing all architectures and object formats available.
|
1999-05-03 09:29:11 +02:00
|
|
|
@end table
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO objcopy
|
|
|
|
ld(1), objdump(1), and the Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@node objdump
|
|
|
|
@chapter objdump
|
|
|
|
|
|
|
|
@cindex object file information
|
|
|
|
@kindex objdump
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@c man title objdump display information from object files
|
2001-03-25 22:32:31 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS objdump
|
2001-08-01 17:54:41 +02:00
|
|
|
objdump [@option{-a}|@option{--archive-headers}]
|
|
|
|
[@option{-b} @var{bfdname}|@option{--target=@var{bfdname}}]
|
|
|
|
[@option{-C}|@option{--demangle}[=@var{style}] ]
|
2018-11-07 19:07:36 +01:00
|
|
|
[@option{-d}|@option{--disassemble}[=@var{symbol}]]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-D}|@option{--disassemble-all}]
|
|
|
|
[@option{-z}|@option{--disassemble-zeroes}]
|
|
|
|
[@option{-EB}|@option{-EL}|@option{--endian=}@{big | little @}]
|
|
|
|
[@option{-f}|@option{--file-headers}]
|
2008-02-22 10:42:58 +01:00
|
|
|
[@option{-F}|@option{--file-offsets}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{--file-start-context}]
|
|
|
|
[@option{-g}|@option{--debugging}]
|
2003-07-22 15:33:32 +02:00
|
|
|
[@option{-e}|@option{--debugging-tags}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-h}|@option{--section-headers}|@option{--headers}]
|
|
|
|
[@option{-i}|@option{--info}]
|
|
|
|
[@option{-j} @var{section}|@option{--section=}@var{section}]
|
|
|
|
[@option{-l}|@option{--line-numbers}]
|
|
|
|
[@option{-S}|@option{--source}]
|
2019-08-28 12:39:19 +02:00
|
|
|
[@option{--source-comment}[=@var{text}]]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-m} @var{machine}|@option{--architecture=}@var{machine}]
|
|
|
|
[@option{-M} @var{options}|@option{--disassembler-options=}@var{options}]
|
|
|
|
[@option{-p}|@option{--private-headers}]
|
2011-05-16 14:22:13 +02:00
|
|
|
[@option{-P} @var{options}|@option{--private=}@var{options}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-r}|@option{--reloc}]
|
|
|
|
[@option{-R}|@option{--dynamic-reloc}]
|
|
|
|
[@option{-s}|@option{--full-contents}]
|
Add support to readelf and objdump for following links to separate debug information files.
Hi Guys,
I am applying the rather large patch attached to this email to enhance
the readelf and objdump programs so that they now have the ability to
follow links to separate debug info files. (As requested by PR
15152). So for example whereas before we had this output:
$ readelf -wi main.exe
Contents of the .debug_info section:
[...]
<15> DW_AT_comp_dir : (alt indirect string, offset: 0x30c)
[...]
With the new option enabled we get:
$ readelf -wiK main.exe
main.exe: Found separate debug info file: dwz.debug
Contents of the .debug_info section (loaded from main.exe):
[...]
<15> DW_AT_comp_dir : (alt indirect string, offset: 0x30c) /home/nickc/Downloads/dwzm
[...]
The link following feature also means that we can get two lots of
output if the same section exists in both the main file and the
separate debug info file:
$ readelf -wiK main.exe
main.exe: Found separate debug info file: dwz.debug
Contents of the .debug_info section (loaded from main.exe):
[...]
Contents of the .debug_info section (loaded from dwz.debug):
[...]
The patch also adds the ability to display the contents of debuglink
sections:
$ readelf -wk main.exe
Contents of the .gnu_debugaltlink section:
Separate debug info file: dwz.debug
Build-ID (0x14 bytes):
c4 a8 89 8d 64 cf 70 8a 35 68 21 f2 ed 24 45 3e 18 7a 7a 93
Naturally there are long versions of these options (=follow-links and
=links). The documentation has been updated as well, and since both
readelf and objdump use the same set of debug display options, I have
moved the text into a separate file. There are also a couple of new
binutils tests to exercise the new behaviour.
There are a couple of missing features in the current patch however,
although I do intend to address them in follow up submissions:
Firstly the code does not check the build-id inside separate debug
info files when it is searching for a file specified by a
.gnu_debugaltlink section. It just assumes that if the file is there,
then it contains the information being sought.
Secondly I have not checked the DWARF-5 version of these link
features, so there will probably be code to add there.
Thirdly I have only implemented link following for the
DW_FORM_GNU_strp_alt format. Other alternate formats (eg
DW_FORM_GNU_ref_alt) have yet to be implemented.
Lastly, whilst implementing this feature I found it necessary to move
some of the global variables used by readelf (eg section_headers) into
a structure that can be passed around. I have moved all of the global
variables that were necessary to get the patch working, but I need to
complete the operation and move the remaining, file-specific variables
(eg dynamic_strings).
Cheers
Nick
binutils PR 15152
* dwarf.h (enum dwarf_section_display_enum): Add gnu_debuglink,
gnu_debugaltlink and separate_debug_str.
(struct dwarf_section): Add filename field.
Add prototypes for load_separate_debug_file, close_debug_file and
open_debug_file.
* dwarf.c (do_debug_links): New.
(do_follow_links): New.
(separate_debug_file, separate_debug_filename): New.
(fetch_alt_indirect_string): New function. Retrieves a string
from the debug string table in the separate debug info file.
(read_and_display_attr_value): Use it with DW_FORM_GNU_strp_alt.
(load_debug_section_with_follow): New function. Like
load_debug_section, but if the first attempt fails, then tries
again in the separate debug info file.
(introduce): New function.
(process_debug_info): Use load_debug_section_with_follow and
introduce.
(load_debug_info): Likewise.
(display_debug_lines_raw): Likewise.
(display_debug_lines_decoded): Likewise.
(display_debug_macinfo): Likewise.
(display_debug_macro): Likewise.
(display_debug_abbrev): Likewise.
(display_debug_loc): Likewise.
(display_debug_str): Likewise.
(display_debug_aranges): Likewise.
(display_debug_addr); Likewise.
(display_debug_frames): Likewise.
(display_gdb_index): Likewise.
(process_cu_tu_index): Likewise.
(load_cu_tu_indexes): Likewise.
(display_debug_links): New function. Displays the contents of a
.gnu_debuglink or .gnu_debugaltlink section.
(calc_gnu_debuglink_ctc32):New function. Calculates a CRC32
value.
(check_gnu_debuglink): New function. Checks the CRC of a
potential separate debug info file.
(parse_gnu_debuglink): New function. Reads a CRC value out of a
.gnu_debuglink section.
(check_gnu_debugaltlink): New function.
(parse_gnu_debugaltlink): New function. Reads the build-id value
out of a .gnu_debugaltlink section.
(load_separate_debug_info): New function. Finds and loads a
separate debug info file.
(load_separate_debug_file): New function. Attempts to find and
follow a link to a separate debug info file.
(free_debug_memory): Free the separate debug info file
information.
(opts_table): Add "follow-links" and "links".
(dwarf_select_sections_by_letters): Add "k" and "K".
(debug_displays): Reformat. Add .gnu-debuglink and
.gnu_debugaltlink.
Add an extra entry for .debug_str in a separate debug info file.
* doc/binutils.texi: Move description of debug dump features
common to both readelf and objdump into...
* objdump.c (usage): Add -Wk and -WK.
(load_specific_debug_section): Initialise the filename field in
the dwarf_section structure.
(close_debug_file): New function.
(open_debug_file): New function.
(dump_dwarf): Load and dump the separate debug info sections.
* readelf.c (struct filedata): New structure. Contains various
variables that used to be global:
(current_file_size, string_table, string_table_length, elf_header)
(section_headers, program_headers, dump_sects, num_dump_sects):
Move into filedata structure.
(cmdline): New global variable. Contains list of sections to dump
by number, as specified on the command line.
Add filedata parameter to most functions.
(load_debug_section): Load the string table if it has not already
been retrieved.
(close_file): New function.
(close_debug_file): New function.
(open_file): New function.
(open_debug_file): New function.
(process_object): Process sections in any separate debug info files.
* doc/debug.options.texi: New file. Add description of =links and
=follow-links options.
* NEWS: Mention the new feature.
* elfcomm.c: Have the byte gte functions take a const pointer.
* elfcomm.h: Update prototypes.
* testsuite/binutils-all/dw5.W: Update expected output.
* testsuite/binutils-all/objdump.WL: Update expected output.
* testsuite/binutils-all/objdump.exp: Add test of -WK and -Wk.
* testsuite/binutils-all/readelf.exp: Add test of -wK and -wk.
* testsuite/binutils-all/readelf.k: New file.
* testsuite/binutils-all/objdump.Wk: New file.
* testsuite/binutils-all/objdump.WK2: New file.
* testsuite/binutils-all/linkdebug.s: New file.
* testsuite/binutils-all/debuglink.s: New file.
gas * testsuite/gas/avr/large-debug-line-table.d: Update expected
output.
* testsuite/gas/elf/dwarf2-11.d: Likewise.
* testsuite/gas/elf/dwarf2-12.d: Likewise.
* testsuite/gas/elf/dwarf2-13.d: Likewise.
* testsuite/gas/elf/dwarf2-14.d: Likewise.
* testsuite/gas/elf/dwarf2-15.d: Likewise.
* testsuite/gas/elf/dwarf2-16.d: Likewise.
* testsuite/gas/elf/dwarf2-17.d: Likewise.
* testsuite/gas/elf/dwarf2-18.d: Likewise.
* testsuite/gas/elf/dwarf2-5.d: Likewise.
* testsuite/gas/elf/dwarf2-6.d: Likewise.
* testsuite/gas/elf/dwarf2-7.d: Likewise.
ld * testsuite/ld-avr/gc-section-debugline.d: Update expected
output.
2017-11-15 12:34:03 +01:00
|
|
|
[@option{-W[lLiaprmfFsoRtUuTgAckK]}|
|
2018-06-13 12:51:15 +02:00
|
|
|
@option{--dwarf}[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links]]
|
binutils: CTF support for objdump and readelf
This introduces CTF support for objdump and readelf. objdump has the
following new arguments:
--ctf=SECTION: display CTF in the given SECTION
--ctf-parent=SECTION: name of CTF section that is the parent of this section
readelf has the above, and these two as well:
--ctf-symbols=SECTION: name of symbol table section (optional)
--ctf-strings=SECTION: name of string table section (optional)
(objdump can always use BFD machinery to determine the applicable string
and symbol tables automatically, so these arguments are unnecessary.)
Nearly all the work is done by the ctf_dump machinery in libctf: most of
the remaining work is option-processing and section-reading, and thus is
different for objdump and readelf: the minimal amount of similar code
remaining is, in my view, too small to share, particularly given that
objdump uses ctf_bfdopen() and readelf uses ctf_simple_open() since it
doesn't have a bfd.
I am not particularly satisfied with the way resources are freed in
either of these (I was forced to do it at the top level, for lack of
anywhere else to free resources allocated during option processing), but
I can't see any better way to do it without introducing new
infrastructure for no other purpose.
There are essentially arbitrary ordering changes to the Makefile.in's
order of libtool-related stuff that I can't get rid of, but they have no
semantic effect. (It is possible that some hunks of these changes could
be dropped, but that seems a bit risky to me.)
binutils/
* objdump.c (ctf-api.h): New include.
(dump_ctf_section_info): New variable.
(dump_ctf_section_name): Likewise.
(usage): Describe new options.
(enum option_values): Add OPTION_CTF and OPTION_CTF_PARENT.
(main): Use them to add --ctf and --ctf-parent.
(read_section_stabs): Add new parameter, entsize_ptr.
(find_stabs_section): Adjust accordingly.
(make_ctfsect): New.
(dump_ctf_indent_lines): New.
(dump_ctf_archive_member): New.
(dump_ctf): New.
(dump_bfd): Call it. Free resources afterwards.
* readelf.c (ctf-api.h): New include.
(CTF_DUMP): New.
(static bfd_boolean do_ctf): Likewise.
(dump_ctf_parent_name): Likewise.
(dump_ctf_symtab_name): Likewise.
(dump_ctf_strtab_name): Likewise.
(OPTION_CTF_DUMP): Likewise.
(OPTION_CTF_PARENT): Likewise.
(OPTION_CTF_SYMBOLS): Likewise.
(OPTION_CTF_STRINGS): Likewise.
(options): Add them.
(usage): Likewise.
(parse_args): Handle the new options, requesting CTF_DUMP.
(process_section_contents): Handle CTF_DUMP.
(shdr_to_ctf_sect): New.
(dump_ctf_indent_lines): New.
(dump_section_as_ctf): New.
(main): Free resources.
* Makefile.am (LIBCTF): New variable.
(objdump_DEPENDENCIES): Use it.
(readelf_DEPENDENCIES): Likewise.
(objdump_LDADD): Likewise.
(readelf_LDADD): Likewise.
* aclocal.m4: Regenerated.
* Makefile.in: Likewise.
* doc/binutils.texi (objdump): Document the new options.
(readelf): Likewise.
* doc/ctf.options.texi: New.
* doc/Makefile.in: Regenerated.
* NEWS: Mention the new feature.
2019-04-24 13:04:33 +02:00
|
|
|
[@option{--ctf=}@var{section}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-G}|@option{--stabs}]
|
|
|
|
[@option{-t}|@option{--syms}]
|
|
|
|
[@option{-T}|@option{--dynamic-syms}]
|
|
|
|
[@option{-x}|@option{--all-headers}]
|
|
|
|
[@option{-w}|@option{--wide}]
|
|
|
|
[@option{--start-address=}@var{address}]
|
|
|
|
[@option{--stop-address=}@var{address}]
|
|
|
|
[@option{--prefix-addresses}]
|
|
|
|
[@option{--[no-]show-raw-insn}]
|
|
|
|
[@option{--adjust-vma=}@var{offset}]
|
2016-06-29 12:09:06 +02:00
|
|
|
[@option{--dwarf-depth=@var{n}}]
|
|
|
|
[@option{--dwarf-start=@var{n}}]
|
binutils: CTF support for objdump and readelf
This introduces CTF support for objdump and readelf. objdump has the
following new arguments:
--ctf=SECTION: display CTF in the given SECTION
--ctf-parent=SECTION: name of CTF section that is the parent of this section
readelf has the above, and these two as well:
--ctf-symbols=SECTION: name of symbol table section (optional)
--ctf-strings=SECTION: name of string table section (optional)
(objdump can always use BFD machinery to determine the applicable string
and symbol tables automatically, so these arguments are unnecessary.)
Nearly all the work is done by the ctf_dump machinery in libctf: most of
the remaining work is option-processing and section-reading, and thus is
different for objdump and readelf: the minimal amount of similar code
remaining is, in my view, too small to share, particularly given that
objdump uses ctf_bfdopen() and readelf uses ctf_simple_open() since it
doesn't have a bfd.
I am not particularly satisfied with the way resources are freed in
either of these (I was forced to do it at the top level, for lack of
anywhere else to free resources allocated during option processing), but
I can't see any better way to do it without introducing new
infrastructure for no other purpose.
There are essentially arbitrary ordering changes to the Makefile.in's
order of libtool-related stuff that I can't get rid of, but they have no
semantic effect. (It is possible that some hunks of these changes could
be dropped, but that seems a bit risky to me.)
binutils/
* objdump.c (ctf-api.h): New include.
(dump_ctf_section_info): New variable.
(dump_ctf_section_name): Likewise.
(usage): Describe new options.
(enum option_values): Add OPTION_CTF and OPTION_CTF_PARENT.
(main): Use them to add --ctf and --ctf-parent.
(read_section_stabs): Add new parameter, entsize_ptr.
(find_stabs_section): Adjust accordingly.
(make_ctfsect): New.
(dump_ctf_indent_lines): New.
(dump_ctf_archive_member): New.
(dump_ctf): New.
(dump_bfd): Call it. Free resources afterwards.
* readelf.c (ctf-api.h): New include.
(CTF_DUMP): New.
(static bfd_boolean do_ctf): Likewise.
(dump_ctf_parent_name): Likewise.
(dump_ctf_symtab_name): Likewise.
(dump_ctf_strtab_name): Likewise.
(OPTION_CTF_DUMP): Likewise.
(OPTION_CTF_PARENT): Likewise.
(OPTION_CTF_SYMBOLS): Likewise.
(OPTION_CTF_STRINGS): Likewise.
(options): Add them.
(usage): Likewise.
(parse_args): Handle the new options, requesting CTF_DUMP.
(process_section_contents): Handle CTF_DUMP.
(shdr_to_ctf_sect): New.
(dump_ctf_indent_lines): New.
(dump_section_as_ctf): New.
(main): Free resources.
* Makefile.am (LIBCTF): New variable.
(objdump_DEPENDENCIES): Use it.
(readelf_DEPENDENCIES): Likewise.
(objdump_LDADD): Likewise.
(readelf_LDADD): Likewise.
* aclocal.m4: Regenerated.
* Makefile.in: Likewise.
* doc/binutils.texi (objdump): Document the new options.
(readelf): Likewise.
* doc/ctf.options.texi: New.
* doc/Makefile.in: Regenerated.
* NEWS: Mention the new feature.
2019-04-24 13:04:33 +02:00
|
|
|
[@option{--ctf-parent=}@var{section}]
|
|
|
|
[@option{--ctf-symbols=}@var{section}]
|
|
|
|
[@option{--ctf-strings=}@var{section}]
|
2018-12-07 12:32:55 +01:00
|
|
|
[@option{--no-recurse-limit}|@option{--recurse-limit}]
|
2004-10-08 16:54:04 +02:00
|
|
|
[@option{--special-syms}]
|
2009-02-03 16:48:50 +01:00
|
|
|
[@option{--prefix=}@var{prefix}]
|
|
|
|
[@option{--prefix-strip=}@var{level}]
|
2009-07-20 15:40:48 +02:00
|
|
|
[@option{--insn-width=}@var{width}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-V}|@option{--version}]
|
|
|
|
[@option{-H}|@option{--help}]
|
1999-05-03 09:29:11 +02:00
|
|
|
@var{objfile}@dots{}
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION objdump
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{objdump} displays information about one or more object files.
|
1999-05-03 09:29:11 +02:00
|
|
|
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.
|
|
|
|
|
|
|
|
@var{objfile}@dots{} are the object files to be examined. When you
|
2001-08-01 17:54:41 +02:00
|
|
|
specify archives, @command{objdump} shows information on each of the member
|
1999-05-03 09:29:11 +02:00
|
|
|
object files.
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS objdump
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
The long and short forms of options, shown here as alternatives, are
|
1999-11-21 12:37:21 +01:00
|
|
|
equivalent. At least one option from the list
|
2011-05-16 14:22:13 +02:00
|
|
|
@option{-a,-d,-D,-e,-f,-g,-G,-h,-H,-p,-P,-r,-R,-s,-S,-t,-T,-V,-x} must be given.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @env
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -a
|
|
|
|
@itemx --archive-header
|
|
|
|
@cindex archive headers
|
|
|
|
If any of the @var{objfile} files are archives, display the archive
|
|
|
|
header information (in a format similar to @samp{ls -l}). Besides the
|
|
|
|
information you could list with @samp{ar tv}, @samp{objdump -a} shows
|
|
|
|
the object file format of each archive member.
|
|
|
|
|
|
|
|
@item --adjust-vma=@var{offset}
|
|
|
|
@cindex section addresses in objdump
|
|
|
|
@cindex VMA in objdump
|
|
|
|
When dumping information, first add @var{offset} to all the section
|
|
|
|
addresses. This is useful if the section addresses do not correspond to
|
|
|
|
the symbol table, which can happen when putting sections at particular
|
|
|
|
addresses when using a format which can not represent section addresses,
|
|
|
|
such as a.out.
|
|
|
|
|
|
|
|
@item -b @var{bfdname}
|
|
|
|
@itemx --target=@var{bfdname}
|
|
|
|
@cindex object code format
|
|
|
|
Specify that the object-code format for the object files is
|
|
|
|
@var{bfdname}. This option may not be necessary; @var{objdump} can
|
|
|
|
automatically recognize many formats.
|
|
|
|
|
|
|
|
For example,
|
|
|
|
@example
|
|
|
|
objdump -b oasys -m vax -h fu.o
|
|
|
|
@end example
|
|
|
|
@noindent
|
2001-08-01 17:54:41 +02:00
|
|
|
displays summary information from the section headers (@option{-h}) of
|
|
|
|
@file{fu.o}, which is explicitly identified (@option{-m}) as a VAX object
|
1999-05-03 09:29:11 +02:00
|
|
|
file in the format produced by Oasys compilers. You can list the
|
2001-08-01 17:54:41 +02:00
|
|
|
formats available with the @option{-i} option.
|
1999-05-03 09:29:11 +02:00
|
|
|
@xref{Target Selection}, for more information.
|
|
|
|
|
|
|
|
@item -C
|
2000-07-20 20:02:56 +02:00
|
|
|
@itemx --demangle[=@var{style}]
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex demangling in objdump
|
|
|
|
Decode (@dfn{demangle}) low-level symbol names into user-level names.
|
|
|
|
Besides removing any initial underscore prepended by the system, this
|
2000-07-20 20:02:56 +02:00
|
|
|
makes C++ function names readable. Different compilers have different
|
2007-06-29 02:34:14 +02:00
|
|
|
mangling styles. The optional demangling style argument can be used to
|
|
|
|
choose an appropriate demangling style for your compiler. @xref{c++filt},
|
2000-07-20 20:02:56 +02:00
|
|
|
for more information on demangling.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2018-12-07 12:32:55 +01:00
|
|
|
@item --recurse-limit
|
|
|
|
@itemx --no-recurse-limit
|
|
|
|
@itemx --recursion-limit
|
|
|
|
@itemx --no-recursion-limit
|
|
|
|
Enables or disables a limit on the amount of recursion performed
|
|
|
|
whilst demangling strings. Since the name mangling formats allow for
|
|
|
|
an inifinite level of recursion it is possible to create strings whose
|
|
|
|
decoding will exhaust the amount of stack space available on the host
|
|
|
|
machine, triggering a memory fault. The limit tries to prevent this
|
2018-12-11 13:01:15 +01:00
|
|
|
from happening by restricting recursion to 2048 levels of nesting.
|
2018-12-07 12:32:55 +01:00
|
|
|
|
|
|
|
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.
|
|
|
|
|
2003-02-21 11:30:35 +01:00
|
|
|
@item -g
|
|
|
|
@itemx --debugging
|
2018-04-16 07:46:00 +02:00
|
|
|
Display debugging information. This attempts to parse STABS
|
2008-06-12 13:57:40 +02:00
|
|
|
debugging format information stored in the file and print it out using
|
2018-04-16 07:46:00 +02:00
|
|
|
a C like syntax. If no STABS debuging was found this option
|
2008-06-12 13:57:40 +02:00
|
|
|
falls back on the @option{-W} option to print any DWARF information in
|
|
|
|
the file.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2003-07-22 15:33:32 +02:00
|
|
|
@item -e
|
|
|
|
@itemx --debugging-tags
|
|
|
|
Like @option{-g}, but the information is generated in a format compatible
|
|
|
|
with ctags tool.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -d
|
|
|
|
@itemx --disassemble
|
2018-11-07 19:07:36 +01:00
|
|
|
@itemx --disassemble=@var{symbol}
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex disassembling object code
|
|
|
|
@cindex machine instructions
|
2018-11-07 19:07:36 +01:00
|
|
|
Display the assembler mnemonics for the machine instructions from the
|
|
|
|
input file. This option only disassembles those sections which are
|
|
|
|
expected to contain instructions. If the optional @var{symbol}
|
2019-01-17 16:29:43 +01:00
|
|
|
argument is given, then display the assembler mnemonics starting at
|
|
|
|
@var{symbol}. If @var{symbol} is a function name then disassembly
|
|
|
|
will stop at the end of the function, otherwise it will stop when the
|
|
|
|
next symbol is encountered. If there are no matches for @var{symbol}
|
|
|
|
then nothing will be displayed.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2019-02-25 13:15:41 +01:00
|
|
|
Note if the @option{--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.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -D
|
|
|
|
@itemx --disassemble-all
|
2001-08-01 17:54:41 +02:00
|
|
|
Like @option{-d}, but disassemble the contents of all sections, not just
|
1999-05-03 09:29:11 +02:00
|
|
|
those expected to contain instructions.
|
|
|
|
|
2015-06-22 17:53:27 +02:00
|
|
|
This option also has a subtle effect on the disassembly of
|
|
|
|
instructions in code sections. When option @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 @option{-D} is in effect however
|
|
|
|
this assumption is supressed. This means that it is possible for the
|
|
|
|
output of @option{-d} and @option{-D} to differ if, for example, data
|
|
|
|
is stored in code sections.
|
|
|
|
|
2009-06-18 12:31:21 +02:00
|
|
|
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.
|
|
|
|
|
2019-02-25 13:15:41 +01:00
|
|
|
Note if the @option{--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.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --prefix-addresses
|
|
|
|
When disassembling, print the complete address on each line. This is
|
|
|
|
the older disassembly format.
|
|
|
|
|
|
|
|
@item -EB
|
|
|
|
@itemx -EL
|
|
|
|
@itemx --endian=@{big|little@}
|
|
|
|
@cindex endianness
|
|
|
|
@cindex disassembly endianness
|
|
|
|
Specify the endianness of the object files. This only affects
|
|
|
|
disassembly. This can be useful when disassembling a file format which
|
|
|
|
does not describe endianness information, such as S-records.
|
|
|
|
|
|
|
|
@item -f
|
2003-02-21 11:30:35 +01:00
|
|
|
@itemx --file-headers
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex object file header
|
|
|
|
Display summary information from the overall header of
|
|
|
|
each of the @var{objfile} files.
|
|
|
|
|
2008-02-22 10:42:58 +01:00
|
|
|
@item -F
|
|
|
|
@itemx --file-offsets
|
|
|
|
@cindex object file offsets
|
|
|
|
When disassembling sections, whenever a symbol is displayed, also
|
|
|
|
display the file offset of the region of data that is about to be
|
|
|
|
dumped. If zeroes are being skipped, then when disassembly resumes,
|
|
|
|
tell the user how many zeroes were skipped and the file offset of the
|
2008-02-26 09:44:10 +01:00
|
|
|
location from where the disassembly resumes. When dumping sections,
|
|
|
|
display the file offset of the location from where the dump starts.
|
2008-02-22 10:42:58 +01:00
|
|
|
|
2000-02-08 19:38:13 +01:00
|
|
|
@item --file-start-context
|
|
|
|
@cindex source code context
|
|
|
|
Specify that when displaying interlisted source code/disassembly
|
2001-08-01 17:54:41 +02:00
|
|
|
(assumes @option{-S}) from a file that has not yet been displayed, extend the
|
2000-02-08 19:38:13 +01:00
|
|
|
context to the start of the file.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -h
|
2003-02-21 11:30:35 +01:00
|
|
|
@itemx --section-headers
|
|
|
|
@itemx --headers
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex section headers
|
|
|
|
Display summary information from the section headers of the
|
|
|
|
object file.
|
|
|
|
|
|
|
|
File segments may be relocated to nonstandard addresses, for example by
|
2001-08-01 17:54:41 +02:00
|
|
|
using the @option{-Ttext}, @option{-Tdata}, or @option{-Tbss} options to
|
|
|
|
@command{ld}. However, some object file formats, such as a.out, do not
|
1999-05-03 09:29:11 +02:00
|
|
|
store the starting address of the file segments. In those situations,
|
2001-08-01 17:54:41 +02:00
|
|
|
although @command{ld} relocates the sections correctly, using @samp{objdump
|
1999-05-03 09:29:11 +02:00
|
|
|
-h} to list the file section headers cannot show the correct addresses.
|
|
|
|
Instead, it shows the usual addresses, which are implicit for the
|
|
|
|
target.
|
|
|
|
|
2016-01-20 13:53:50 +01:00
|
|
|
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 @command{objdump} will report both
|
|
|
|
since the exact setting of the flag bits might be important.
|
|
|
|
|
2003-02-21 11:30:35 +01:00
|
|
|
@item -H
|
|
|
|
@itemx --help
|
2001-08-01 17:54:41 +02:00
|
|
|
Print a summary of the options to @command{objdump} and exit.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -i
|
|
|
|
@itemx --info
|
|
|
|
@cindex architectures available
|
|
|
|
@cindex object formats available
|
|
|
|
Display a list showing all architectures and object formats available
|
2001-08-01 17:54:41 +02:00
|
|
|
for specification with @option{-b} or @option{-m}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -j @var{name}
|
|
|
|
@itemx --section=@var{name}
|
|
|
|
@cindex section information
|
|
|
|
Display information only for section @var{name}.
|
|
|
|
|
|
|
|
@item -l
|
|
|
|
@itemx --line-numbers
|
|
|
|
@cindex source filenames for object files
|
|
|
|
Label the display (using debugging information) with the filename and
|
|
|
|
source line numbers corresponding to the object code or relocs shown.
|
2001-08-01 17:54:41 +02:00
|
|
|
Only useful with @option{-d}, @option{-D}, or @option{-r}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -m @var{machine}
|
|
|
|
@itemx --architecture=@var{machine}
|
|
|
|
@cindex architecture
|
|
|
|
@cindex disassembly architecture
|
|
|
|
Specify the architecture to use when disassembling object files. This
|
|
|
|
can be useful when disassembling object files which do not describe
|
|
|
|
architecture information, such as S-records. You can list the available
|
2001-08-01 17:54:41 +02:00
|
|
|
architectures with the @option{-i} option.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2009-06-18 12:31:21 +02:00
|
|
|
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 @var{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 @option{-marm}.
|
|
|
|
|
1999-06-16 04:24:36 +02:00
|
|
|
@item -M @var{options}
|
|
|
|
@itemx --disassembler-options=@var{options}
|
|
|
|
Pass target specific information to the disassembler. Only supported on
|
2003-07-18 13:34:41 +02:00
|
|
|
some targets. If it is necessary to specify more than one
|
|
|
|
disassembler option then multiple @option{-M} options can be used or
|
|
|
|
can be placed together into a comma separated list.
|
1999-06-16 04:24:36 +02:00
|
|
|
|
2016-07-21 10:20:10 +02:00
|
|
|
For ARC, @option{dsp} controls the printing of DSP instructions,
|
|
|
|
@option{spfp} selects the printing of FPX single precision FP
|
|
|
|
instructions, @option{dpfp} selects the printing of FPX double
|
|
|
|
precision FP instructions, @option{quarkse_em} selects the printing of
|
|
|
|
special QuarkSE-EM instructions, @option{fpuda} selects the printing
|
|
|
|
of double precision assist instructions, @option{fpus} selects the
|
|
|
|
printing of FPU single precision FP instructions, while @option{fpud}
|
2018-06-26 13:56:23 +02:00
|
|
|
selects the printing of FPU double precision FP instructions.
|
2017-11-03 15:36:42 +01:00
|
|
|
Additionally, one can choose to have all the immediates printed in
|
|
|
|
hexadecimal using @option{hex}. By default, the short immediates are
|
|
|
|
printed using the decimal representation, while the long immediate
|
|
|
|
values are printed as hexadecimal.
|
2016-07-20 18:08:07 +02:00
|
|
|
|
[ARC] Allow CPU to be enforced via disassemble_info options
Currently print_insn_arc relies on BFD mach and ELF private headers to
distinguish between various ARC architectures. Sometimes those values are not
correct or available, mainly in the case of debugging targets without and ELF
file available. Changing a BFD mach is not a problem for the debugger, because
this is a generic BFD field, and GDB, for example, already sets it according to
information provided in XML target description or specified via GDB 'set arch'
command. However, things are more complicated for ELF private headers, since
it requires existing of an actual ELF file. To workaround this problem this
patch allows CPU model to be specified via disassemble info options. If CPU is
specified in options, then it will take a higher precedence than whatever might
be specified in ELF file.
This is mostly needed for ARC EM and ARC HS, because they have the same
"architecture" (mach) ARCv2 and differ in their private ELF headers. Other ARC
architectures can be distinguished between each other purely via "mach" field.
Proposed disassemble option format is "cpu=<CPU>", where CPU can be any valid
ARC CPU name as supported by GAS. Note that this creates a seeming redundancy
with objdump -m/--architecture option, however -mEM and -mHS still result in
"ARCv2" architecture internally, while -Mcpu={HS,EM} would have an actual
effect on disassembler.
opcodes/ChangeLog:
yyyy-mm-dd Anton Kolesov <anton.kolesov@synopsys.com>
* arc-dis.c (enforced_isa_mask): Declare.
(cpu_types): Likewise.
(parse_cpu_option): New function.
(parse_disassembler_options): Use it.
(print_insn_arc): Use enforced_isa_mask.
(print_arc_disassembler_options): Document new options.
binutils/ChangeLog:
yyyy-mm-dd Anton Kolesov <anton.kolesov@synopsys.com>
* doc/binutils.texi: Document new cpu=... disassembler options for ARC.
2017-03-16 13:21:31 +01:00
|
|
|
@option{cpu=...} allows to enforce a particular ISA when disassembling
|
|
|
|
instructions, overriding the @option{-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
|
|
|
|
@option{-mcpu=...} option.
|
|
|
|
|
1999-06-16 04:24:36 +02:00
|
|
|
If the target is an ARM architecture then this switch can be used to
|
|
|
|
select which register name set is used during disassembler. Specifying
|
2005-10-10 10:41:25 +02:00
|
|
|
@option{-M reg-names-std} (the default) will select the register names as
|
2000-01-27 23:17:12 +01:00
|
|
|
used in ARM's instruction set documentation, but with register 13 called
|
|
|
|
'sp', register 14 called 'lr' and register 15 called 'pc'. Specifying
|
2001-08-01 17:54:41 +02:00
|
|
|
@option{-M reg-names-apcs} will select the name set used by the ARM
|
|
|
|
Procedure Call Standard, whilst specifying @option{-M reg-names-raw} will
|
2000-01-27 23:17:12 +01:00
|
|
|
just use @samp{r} followed by the register number.
|
|
|
|
|
|
|
|
There are also two variants on the APCS register naming scheme enabled
|
2001-08-01 17:54:41 +02:00
|
|
|
by @option{-M reg-names-atpcs} and @option{-M reg-names-special-atpcs} which
|
|
|
|
use the ARM/Thumb Procedure Call Standard naming conventions. (Either
|
2003-02-21 11:30:35 +01:00
|
|
|
with the normal register names or the special register names).
|
1999-06-16 04:24:36 +02:00
|
|
|
|
2000-01-03 21:49:47 +01:00
|
|
|
This option can also be used for ARM architectures to force the
|
2001-08-05 23:01:26 +02:00
|
|
|
disassembler to interpret all instructions as Thumb instructions by
|
2001-08-01 17:54:41 +02:00
|
|
|
using the switch @option{--disassembler-options=force-thumb}. This can be
|
2000-01-03 21:49:47 +01:00
|
|
|
useful when attempting to disassemble thumb code produced by other
|
|
|
|
compilers.
|
|
|
|
|
2018-05-15 17:34:54 +02:00
|
|
|
For AArch64 targets this switch can be used to set whether instructions are
|
|
|
|
disassembled as the most general instruction using the @option{-M no-aliases}
|
|
|
|
option or whether instruction notes should be generated as comments in the
|
|
|
|
disasssembly using @option{-M notes}.
|
|
|
|
|
2001-11-14 04:15:28 +01:00
|
|
|
For the x86, some of the options duplicate functions of the @option{-m}
|
|
|
|
switch, but allow finer grained control. Multiple selections from the
|
|
|
|
following may be specified as a comma separated string.
|
2014-12-23 14:11:10 +01:00
|
|
|
@table @code
|
|
|
|
@item x86-64
|
|
|
|
@itemx i386
|
|
|
|
@itemx i8086
|
|
|
|
Select disassembly for the given architecture.
|
|
|
|
|
|
|
|
@item intel
|
|
|
|
@itemx att
|
|
|
|
Select between intel syntax mode and AT&T syntax mode.
|
|
|
|
|
2015-05-15 18:47:39 +02:00
|
|
|
@item amd64
|
|
|
|
@itemx intel64
|
|
|
|
Select between AMD64 ISA and Intel64 ISA.
|
|
|
|
|
2014-12-23 14:11:10 +01:00
|
|
|
@item intel-mnemonic
|
|
|
|
@itemx att-mnemonic
|
|
|
|
Select between intel mnemonic mode and AT&T mnemonic mode.
|
|
|
|
Note: @code{intel-mnemonic} implies @code{intel} and
|
|
|
|
@code{att-mnemonic} implies @code{att}.
|
|
|
|
|
|
|
|
@item addr64
|
|
|
|
@itemx addr32
|
|
|
|
@itemx addr16
|
|
|
|
@itemx data32
|
|
|
|
@itemx data16
|
2019-08-15 15:38:31 +02:00
|
|
|
Specify the default address size and operand size. These five options
|
2014-12-23 14:11:10 +01:00
|
|
|
will be overridden if @code{x86-64}, @code{i386} or @code{i8086}
|
|
|
|
appear later in the option string.
|
|
|
|
|
|
|
|
@item suffix
|
|
|
|
When in AT&T mode, instructs the disassembler to print a mnemonic
|
|
|
|
suffix even when the suffix could be inferred by the operands.
|
|
|
|
@end table
|
2001-11-14 04:15:28 +01:00
|
|
|
|
2017-03-29 05:13:06 +02:00
|
|
|
For PowerPC, the @option{-M} argument @option{raw} selects
|
|
|
|
disasssembly of hardware insns rather than aliases. For example, you
|
|
|
|
will see @code{rlwinm} rather than @code{clrlwi}, and @code{addi}
|
|
|
|
rather than @code{li}. All of the @option{-m} arguments for
|
|
|
|
@command{gas} that select a CPU are supported. These are:
|
|
|
|
@option{403}, @option{405}, @option{440}, @option{464}, @option{476},
|
|
|
|
@option{601}, @option{603}, @option{604}, @option{620}, @option{7400},
|
|
|
|
@option{7410}, @option{7450}, @option{7455}, @option{750cl},
|
|
|
|
@option{821}, @option{850}, @option{860}, @option{a2}, @option{booke},
|
|
|
|
@option{booke32}, @option{cell}, @option{com}, @option{e200z4},
|
|
|
|
@option{e300}, @option{e500}, @option{e500mc}, @option{e500mc64},
|
|
|
|
@option{e500x2}, @option{e5500}, @option{e6500}, @option{efs},
|
|
|
|
@option{power4}, @option{power5}, @option{power6}, @option{power7},
|
|
|
|
@option{power8}, @option{power9}, @option{ppc}, @option{ppc32},
|
|
|
|
@option{ppc64}, @option{ppc64bridge}, @option{ppcps}, @option{pwr},
|
|
|
|
@option{pwr2}, @option{pwr4}, @option{pwr5}, @option{pwr5x},
|
|
|
|
@option{pwr6}, @option{pwr7}, @option{pwr8}, @option{pwr9},
|
|
|
|
@option{pwrx}, @option{titan}, and @option{vle}.
|
|
|
|
@option{32} and @option{64} modify the default or a prior CPU
|
|
|
|
selection, disabling and enabling 64-bit insns respectively. In
|
|
|
|
addition, @option{altivec}, @option{any}, @option{htm}, @option{vsx},
|
|
|
|
and @option{spe} add capabilities to a previous @emph{or later} CPU
|
|
|
|
selection. @option{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.
|
binutils/ChangeLog
* doc/binutils.texi (objdump): Document ppc -M options.
gas/ChangeLog
* config/tc-ppc.c (ppc_insert_operand): Pass (ppc_cpu | ppc_size)
to operand->insert.
(md_assemble): Likewise.
gas/testsuite/ChangeLog
* gas/ppc/booke.d: Modify reloc and target matches for powerpc64.
include/opcode/ChangeLog
* ppc.h (struct powerpc_operand <insert, extract>): Add dialect param.
opcodes/ChangeLog
* ppc-opc.c (PPC64): Revert 2001-10-12. Do include PPC_OPCODE_PPC.
(insert_bat, extract_bat, insert_bba, extract_bba,
insert_bd, extract_bd, insert_bdm, extract_bdm,
insert_bdp, extract_bdp, valid_bo,
insert_bo, extract_bo, insert_boe, extract_boe,
insert_ds, extract_ds, insert_de, extract_de,
insert_des, extract_des, insert_li, extract_li,
insert_mbe, extract_mbe, insert_mb6, extract_mb6,
insert_nb, extract_nb, insert_nsi, extract_nsi,
insert_ral, insert_ram, insert_ras,
insert_rbs, extract_rbs, insert_sh6, extract_sh6,
insert_spr, extract_spr, insert_tbr, extract_tbr): Add dialect param.
(extract_bd, extract_bdm, extract_bdp,
extract_ds, extract_des,
extract_li, extract_nsi): Implement sign extension without conditional.
(insert_bdm, extract_bdm,
insert_bdp, extract_bdp, valid_bo): Handle 64 bit branch hints.
(extract_bdm, extract_bdp): Correct 32 bit validation.
(AT1_MASK, AT2_MASK): Define.
(BBOAT_MASK): Define.
(BBOATCB_MASK, BBOAT2CB_MASK, BBOATBI_MASK): Define.
(BOFM64, BOFP64, BOTM64, BOTP64): Define.
(BODNZM64, BODNZP64, BODZM64, BODZP64): Define.
(PPCCOM32, PPCCOM64): Define.
(powerpc_opcodes): Modify existing 32 bit insns with branch hints
and add new patterns to implement 64 bit branches with hints. Move
booke instructions so they match before ppc64.
* ppc-dis.c (powerpc_dialect): Set PPC_OPCODE_64 in dialect for
64 bit default targets, and parse "32" and "64" in options.
Formatting fixes.
(print_insn_powerpc): Pass dialect to operand->extract.
2001-11-15 02:08:53 +01:00
|
|
|
|
2006-07-24 15:49:50 +02:00
|
|
|
For MIPS, this option controls the printing of instruction mnemonic
|
2005-01-20 00:35:26 +01:00
|
|
|
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:
|
[ binutils/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* doc/binutils.texi (objdump): Document MIPS -M options.
[ gas/testsuite/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* gas/mips/cp0-names-mips32.d: New file.
* gas/mips/cp0-names-mips64.d: New file.
* gas/mips/cp0-names-numeric.d: New file.
* gas/mips/cp0-names-sb1.d: New file.
* gas/mips/cp0-names.s: New file.
* gas/mips/fpr-names-32.d: New file.
* gas/mips/fpr-names-64.d: New file.
* gas/mips/fpr-names-n32.d: New file.
* gas/mips/fpr-names-numeric.d: New file.
* gas/mips/fpr-names.s: New file.
* gas/mips/gpr-names-32.d: New file.
* gas/mips/gpr-names-64.d: New file.
* gas/mips/gpr-names-n32.d: New file.
* gas/mips/gpr-names-numeric.d: New file.
* gas/mips/gpr-names.s: New file.
* gas/mips/mips.exp: Run new tests.
[ include/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* dis-asm.h (print_mips_disassembler_options): Prototype.
[ include/opcode/ChangeLog ]
2002-12-19 Chris Demetriou <cgd@broadcom.com>
* mips.h (OP_OP_COP0, OP_OP_COP1, OP_OP_COP2, OP_OP_COP3)
(OP_OP_LWC1, OP_OP_LWC2, OP_OP_LWC3, OP_OP_LDC1, OP_OP_LDC2)
(OP_OP_LDC3, OP_OP_SWC1, OP_OP_SWC2, OP_OP_SWC3, OP_OP_SDC1)
(OP_OP_SDC2, OP_OP_SDC3): Define.
[ opcodes/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* disassemble.c (disassembler_usage): Add invocation of
print_mips_disassembler_options.
* mips-dis.c (print_mips_disassembler_options)
(set_default_mips_dis_options, parse_mips_dis_option)
(parse_mips_dis_options, choose_abi_by_name, choose_arch_by_name)
(choose_arch_by_number): New functions.
(mips_abi_choice, mips_arch_choice): New structures.
(mips32_reg_names, mips64_reg_names, reg_names): Remove.
(mips_gpr_names_numeric, mips_gpr_names_oldabi)
(mips_gpr_names_newabi, mips_fpr_names_numeric)
(mips_fpr_names_32, mips_fpr_names_n32, mips_fpr_names_64)
(mips_cp0_names_numeric, mips_cp0_names_mips3264)
(mips_cp0_names_sb1, mips_abi_choices, mips_arch_choices)
(mips_processor, mips_isa, mips_gpr_names, mips_fpr_names)
(mips_cp0_names): New variables.
(print_insn_args): Use new variables to print GPR, FPR, and CP0
register names.
(mips_isa_type): Remove.
(print_insn_mips): Remove ISA and CPU setup since it is now done...
(_print_insn_mips): Here. Remove register setup code, and
call set_default_mips_dis_options and parse_mips_dis_options
instead.
(print_mips16_insn_arg): Use mips_gpr_names instead of mips32_names.
2002-12-27 09:00:31 +01:00
|
|
|
|
|
|
|
@table @code
|
2005-01-20 00:35:26 +01:00
|
|
|
@item no-aliases
|
2006-07-24 15:49:50 +02:00
|
|
|
Print the 'raw' instruction mnemonic instead of some pseudo
|
|
|
|
instruction mnemonic. I.e., print 'daddu' or 'or' instead of 'move',
|
2005-01-20 00:35:26 +01:00
|
|
|
'sll' instead of 'nop', etc.
|
|
|
|
|
2013-10-14 20:45:46 +02:00
|
|
|
@item msa
|
|
|
|
Disassemble MSA instructions.
|
|
|
|
|
binutils/ChangeLog:
* doc/binutils.texi: Document -Mvirt disassembler option.
gas/ChangeLog:
* config/tc-mips.c (struct mips_set_options): New ase_virt field.
(mips_opts): Update for the new field.
(file_ase_virt): New variable.
(ISA_SUPPORTS_VIRT_ASE): New macro.
(ISA_SUPPORTS_VIRT64_ASE): New macro.
(MIPS_CPU_ASE_VIRT): New define.
(is_opcode_valid): Handle ase_virt.
(macro_build): Handle "+J".
(validate_mips_insn): Likewise.
(mips_ip): Likewise.
(enum options): Add OPTION_VIRT and OPTION_NO_VIRT.
(md_longopts): Add mvirt and mnovirt
(md_parse_option): Handle OPTION_VIRT and OPTION_NO_VIRT.
(mips_after_parse_args): Handle ase_virt field.
(s_mipsset): Handle "virt" and "novirt".
(mips_elf_final_processing): Add a comment about virt ASE might need a new flag.
(md_show_usage): Print out the usage of -mvirt and mno-virt options.
* doc/c-mips.texi: Document -mvirt and -mno-virt.
Document ".set virt" and ".set novirt".
gas/testsuite/ChangeLog:
* gas/mips/mips.exp: Run virt and virt64 testcases.
* gas/mips/virt.d: New file.
* gas/mips/virt.s: New file.
* gas/mips/virt64.d: New file.
* gas/mips/virt64.s: New file.
include/opcode/ChangeLog:
* mips.h (OP_MASK_CODE10): Correct definition.
(OP_SH_CODE10): Likewise.
Add a comment that "+J" is used now for OP_*CODE10.
(INSN_ASE_MASK): Update.
(INSN_VIRT): New macro.
(INSN_VIRT64): New macro
opcodes/ChangeLog:
* mips-dis.c (mips_arch_choices): Add INSN_VIRT to mips32r2 .
Add INSN_VIRT and INSN_VIRT64 to mips64r2.
(parse_mips_dis_option): Handle the virt option.
(print_insn_args): Handle "+J".
(print_mips_disassembler_options): Print out message about virt64.
* mips-opc.c (IVIRT): New define.
(IVIRT64): New define.
(mips_builtin_opcodes): Add dmfgc0, dmtgc0, hypcall, mfgc0, mtgc0,
tlbgr, tlbgwi, tlbginv, tlbginvf, tlbgwr, tlbgp VIRT instructions.
Move rfe to the bottom as it conflicts with tlbgp.
2013-05-10 03:08:48 +02:00
|
|
|
@item virt
|
|
|
|
Disassemble the virtualization ASE instructions.
|
|
|
|
|
2014-04-23 12:24:30 +02:00
|
|
|
@item xpa
|
|
|
|
Disassemble the eXtended Physical Address (XPA) ASE instructions.
|
|
|
|
|
[ binutils/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* doc/binutils.texi (objdump): Document MIPS -M options.
[ gas/testsuite/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* gas/mips/cp0-names-mips32.d: New file.
* gas/mips/cp0-names-mips64.d: New file.
* gas/mips/cp0-names-numeric.d: New file.
* gas/mips/cp0-names-sb1.d: New file.
* gas/mips/cp0-names.s: New file.
* gas/mips/fpr-names-32.d: New file.
* gas/mips/fpr-names-64.d: New file.
* gas/mips/fpr-names-n32.d: New file.
* gas/mips/fpr-names-numeric.d: New file.
* gas/mips/fpr-names.s: New file.
* gas/mips/gpr-names-32.d: New file.
* gas/mips/gpr-names-64.d: New file.
* gas/mips/gpr-names-n32.d: New file.
* gas/mips/gpr-names-numeric.d: New file.
* gas/mips/gpr-names.s: New file.
* gas/mips/mips.exp: Run new tests.
[ include/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* dis-asm.h (print_mips_disassembler_options): Prototype.
[ include/opcode/ChangeLog ]
2002-12-19 Chris Demetriou <cgd@broadcom.com>
* mips.h (OP_OP_COP0, OP_OP_COP1, OP_OP_COP2, OP_OP_COP3)
(OP_OP_LWC1, OP_OP_LWC2, OP_OP_LWC3, OP_OP_LDC1, OP_OP_LDC2)
(OP_OP_LDC3, OP_OP_SWC1, OP_OP_SWC2, OP_OP_SWC3, OP_OP_SDC1)
(OP_OP_SDC2, OP_OP_SDC3): Define.
[ opcodes/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* disassemble.c (disassembler_usage): Add invocation of
print_mips_disassembler_options.
* mips-dis.c (print_mips_disassembler_options)
(set_default_mips_dis_options, parse_mips_dis_option)
(parse_mips_dis_options, choose_abi_by_name, choose_arch_by_name)
(choose_arch_by_number): New functions.
(mips_abi_choice, mips_arch_choice): New structures.
(mips32_reg_names, mips64_reg_names, reg_names): Remove.
(mips_gpr_names_numeric, mips_gpr_names_oldabi)
(mips_gpr_names_newabi, mips_fpr_names_numeric)
(mips_fpr_names_32, mips_fpr_names_n32, mips_fpr_names_64)
(mips_cp0_names_numeric, mips_cp0_names_mips3264)
(mips_cp0_names_sb1, mips_abi_choices, mips_arch_choices)
(mips_processor, mips_isa, mips_gpr_names, mips_fpr_names)
(mips_cp0_names): New variables.
(print_insn_args): Use new variables to print GPR, FPR, and CP0
register names.
(mips_isa_type): Remove.
(print_insn_mips): Remove ISA and CPU setup since it is now done...
(_print_insn_mips): Here. Remove register setup code, and
call set_default_mips_dis_options and parse_mips_dis_options
instead.
(print_mips16_insn_arg): Use mips_gpr_names instead of mips32_names.
2002-12-27 09:00:31 +01:00
|
|
|
@item gpr-names=@var{ABI}
|
|
|
|
Print GPR (general-purpose register) names as appropriate
|
|
|
|
for the specified ABI. By default, GPR names are selected according to
|
|
|
|
the ABI of the binary being disassembled.
|
|
|
|
|
|
|
|
@item fpr-names=@var{ABI}
|
|
|
|
Print FPR (floating-point register) names as
|
|
|
|
appropriate for the specified ABI. By default, FPR numbers are printed
|
|
|
|
rather than names.
|
|
|
|
|
|
|
|
@item cp0-names=@var{ARCH}
|
|
|
|
Print CP0 (system control coprocessor; coprocessor 0) register names
|
|
|
|
as appropriate for the CPU or architecture specified by
|
|
|
|
@var{ARCH}. By default, CP0 register names are selected according to
|
|
|
|
the architecture and CPU of the binary being disassembled.
|
|
|
|
|
[ bfd/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* aoutx.h (NAME(aout,machine_type)): Add bfd_mach_mipsisa32r2 case.
* archures.c (bfd_mach_mipsisa32r2): New define.
* bfd-in2.h: Regenerate.
* cpu-mips.c (I_mipsisa32r2): New enum value.
(arch_info_struct): Add entry for I_mipsisa32r2.
* elfxx-mips.c (elf_mips_isa, _bfd_elf_mips_mach)
(_bfd_mips_elf_print_private_bfd_data): Handle E_MIPS_ARCH_32R2.
(_bfd_mips_elf_final_write_processing): Add
bfd_mach_mipsisa32r2 case.
(_bfd_mips_elf_merge_private_bfd_data): Handle merging of
binaries marked as using MIPS32 Release 2.
[ binutils/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* doc/binutils.texi (objdump): Note MIPS HWR (Hardware Register)
changes in MIPS -M options.
[ gas/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* configure.in: Recognize mipsisa32r2, mipsisa32r2el, and
CPU variants.
* configure: Regenerate.
* config/tc-mips.c (ISA_HAS_DROR, ISA_HAS_ROR): New defines.
(macro_build): Handle "K" operand.
(macro2): Use ISA_HAS_DROR and ISA_HAS_ROR in the places where
CPU_HAS_DROR and CPU_HAS_ROR are currently used.
(mips_ip): New variable "lastpos", and implement "+A", "+B",
and "+C" operands for MIPS32 Release 2 ins/ext instructions.
Implement "K" operand for MIPS32 Release 2 rdhwr instruction.
(validate_mips_insn): Implement "+" as a way to extend the
allowed operands, and implement "K", "+A", "+B", and "+C"
operands.
(OPTION_MIPS32R2): New define.
(md_longopts): Add entry for OPTION_MIPS32R2.
(OPTION_ELF_BASE): Adjust to accomodate OPTIONS_MIPS32R2.
(md_parse_option): Handle OPTION_MIPS32R2.
(s_mipsset): Reimplement handling of ".set mipsN" options
and add support for ".set mips32r2".
(mips_cpu_info_table): Add entry for "mips32r2" (MIPS32 Release 2).
(md_show_usage): Document "-mips32r2" option.
* doc/as.texinfo: Document "-mips32r2" option.
* doc/c-mips.texi: Likewise.
[ gas/testsuite/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* gas/mips/cp0-names-mips32r2.d: New test.
* gas/mips/hwr-names-mips32r2.d: New test.
* gas/mips/hwr-names-numeric.d: New test.
* gas/mips/hwr-names.s: New test source file.
* gas/mips/mips32r2.d: New test.
* gas/mips/mips32r2.s: New test source file.
* gas/mips/mips32r2-ill.l: New test.
* gas/mips/mips32r2-ill.s: New test source file.
* gas/mips/mips.exp: Add mips32r2 architecture data array
entry. Run new tests mentioned above.
[ include/elf/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* mips.h (E_MIPS_ARCH_32R2): New define.
[ include/opcode/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* mips.h: Document "+" as the start of two-character operand
type names, and add new "K", "+A", "+B", and "+C" operand types.
(OP_MASK_INSMSB, OP_SH_INSMSB, OP_MASK_EXTMSB)
(OP_SH_EXTMSB, INSN_ISA32R2, ISA_MIPS32R2, CPU_MIPS32R2): New
defines.
[ opcodes/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* mips-dis.c (mips_cp0_names_mips3264r2, mips_hwr_names_numeric)
(mips_hwr_names_mips3264r2): New arrays.
(mips_arch_choice): New "hwr_names" member.
(mips_arch_choices): Adjust for structure change, and add a new
entry for "mips32r2" ISA.
(mips_hwr_names): New variable.
(set_default_mips_dis_options): Set mips_hwr_names.
(parse_mips_dis_option): New "hwr-names" option which sets
mips_hwr_names, and adjust "reg-names=ARCH" to set mips_hwr_names.
(print_insn_arg): Change return type to "int"
and use that to indicate number of characters consumed.
Add support for "+" operand extension character, "+A", "+B",
"+C", and "K" operands.
(print_insn_mips): Adjust for changes to print_insn_arg.
(print_mips_disassembler_options): Adjust for "hwr-names"
addition and "reg-names" change.
* mips-opc (I33): New define (shorthand for INSN_ISA32R2).
(mips_builtin_opcodes): Note that "nop" and "ssnop" are special
forms of "sll". Add new MIPS32 Release 2 instructions: ehb,
di, ei, ext, ins, jr.hb, jalr.hb, mfhc1, mfhc2, mthc1, mthc2,
rdhwr, rdpgpr, seb, seh, synci, wrpgpr, wsbh.
Note that hardware rotate instructions (ror, rorv) can be
used on MIPS32 Release 2, and add the official mnemonics
for them (rotr, rotrv) and the similar "rotl" mnemonic for
left-rotate.
2002-12-31 08:29:29 +01:00
|
|
|
@item hwr-names=@var{ARCH}
|
|
|
|
Print HWR (hardware register, used by the @code{rdhwr} instruction) names
|
|
|
|
as appropriate for the CPU or architecture specified by
|
|
|
|
@var{ARCH}. By default, HWR names are selected according to
|
|
|
|
the architecture and CPU of the binary being disassembled.
|
|
|
|
|
[ binutils/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* doc/binutils.texi (objdump): Document MIPS -M options.
[ gas/testsuite/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* gas/mips/cp0-names-mips32.d: New file.
* gas/mips/cp0-names-mips64.d: New file.
* gas/mips/cp0-names-numeric.d: New file.
* gas/mips/cp0-names-sb1.d: New file.
* gas/mips/cp0-names.s: New file.
* gas/mips/fpr-names-32.d: New file.
* gas/mips/fpr-names-64.d: New file.
* gas/mips/fpr-names-n32.d: New file.
* gas/mips/fpr-names-numeric.d: New file.
* gas/mips/fpr-names.s: New file.
* gas/mips/gpr-names-32.d: New file.
* gas/mips/gpr-names-64.d: New file.
* gas/mips/gpr-names-n32.d: New file.
* gas/mips/gpr-names-numeric.d: New file.
* gas/mips/gpr-names.s: New file.
* gas/mips/mips.exp: Run new tests.
[ include/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* dis-asm.h (print_mips_disassembler_options): Prototype.
[ include/opcode/ChangeLog ]
2002-12-19 Chris Demetriou <cgd@broadcom.com>
* mips.h (OP_OP_COP0, OP_OP_COP1, OP_OP_COP2, OP_OP_COP3)
(OP_OP_LWC1, OP_OP_LWC2, OP_OP_LWC3, OP_OP_LDC1, OP_OP_LDC2)
(OP_OP_LDC3, OP_OP_SWC1, OP_OP_SWC2, OP_OP_SWC3, OP_OP_SDC1)
(OP_OP_SDC2, OP_OP_SDC3): Define.
[ opcodes/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* disassemble.c (disassembler_usage): Add invocation of
print_mips_disassembler_options.
* mips-dis.c (print_mips_disassembler_options)
(set_default_mips_dis_options, parse_mips_dis_option)
(parse_mips_dis_options, choose_abi_by_name, choose_arch_by_name)
(choose_arch_by_number): New functions.
(mips_abi_choice, mips_arch_choice): New structures.
(mips32_reg_names, mips64_reg_names, reg_names): Remove.
(mips_gpr_names_numeric, mips_gpr_names_oldabi)
(mips_gpr_names_newabi, mips_fpr_names_numeric)
(mips_fpr_names_32, mips_fpr_names_n32, mips_fpr_names_64)
(mips_cp0_names_numeric, mips_cp0_names_mips3264)
(mips_cp0_names_sb1, mips_abi_choices, mips_arch_choices)
(mips_processor, mips_isa, mips_gpr_names, mips_fpr_names)
(mips_cp0_names): New variables.
(print_insn_args): Use new variables to print GPR, FPR, and CP0
register names.
(mips_isa_type): Remove.
(print_insn_mips): Remove ISA and CPU setup since it is now done...
(_print_insn_mips): Here. Remove register setup code, and
call set_default_mips_dis_options and parse_mips_dis_options
instead.
(print_mips16_insn_arg): Use mips_gpr_names instead of mips32_names.
2002-12-27 09:00:31 +01:00
|
|
|
@item reg-names=@var{ABI}
|
|
|
|
Print GPR and FPR names as appropriate for the selected ABI.
|
|
|
|
|
|
|
|
@item reg-names=@var{ARCH}
|
[ bfd/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* aoutx.h (NAME(aout,machine_type)): Add bfd_mach_mipsisa32r2 case.
* archures.c (bfd_mach_mipsisa32r2): New define.
* bfd-in2.h: Regenerate.
* cpu-mips.c (I_mipsisa32r2): New enum value.
(arch_info_struct): Add entry for I_mipsisa32r2.
* elfxx-mips.c (elf_mips_isa, _bfd_elf_mips_mach)
(_bfd_mips_elf_print_private_bfd_data): Handle E_MIPS_ARCH_32R2.
(_bfd_mips_elf_final_write_processing): Add
bfd_mach_mipsisa32r2 case.
(_bfd_mips_elf_merge_private_bfd_data): Handle merging of
binaries marked as using MIPS32 Release 2.
[ binutils/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* doc/binutils.texi (objdump): Note MIPS HWR (Hardware Register)
changes in MIPS -M options.
[ gas/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* configure.in: Recognize mipsisa32r2, mipsisa32r2el, and
CPU variants.
* configure: Regenerate.
* config/tc-mips.c (ISA_HAS_DROR, ISA_HAS_ROR): New defines.
(macro_build): Handle "K" operand.
(macro2): Use ISA_HAS_DROR and ISA_HAS_ROR in the places where
CPU_HAS_DROR and CPU_HAS_ROR are currently used.
(mips_ip): New variable "lastpos", and implement "+A", "+B",
and "+C" operands for MIPS32 Release 2 ins/ext instructions.
Implement "K" operand for MIPS32 Release 2 rdhwr instruction.
(validate_mips_insn): Implement "+" as a way to extend the
allowed operands, and implement "K", "+A", "+B", and "+C"
operands.
(OPTION_MIPS32R2): New define.
(md_longopts): Add entry for OPTION_MIPS32R2.
(OPTION_ELF_BASE): Adjust to accomodate OPTIONS_MIPS32R2.
(md_parse_option): Handle OPTION_MIPS32R2.
(s_mipsset): Reimplement handling of ".set mipsN" options
and add support for ".set mips32r2".
(mips_cpu_info_table): Add entry for "mips32r2" (MIPS32 Release 2).
(md_show_usage): Document "-mips32r2" option.
* doc/as.texinfo: Document "-mips32r2" option.
* doc/c-mips.texi: Likewise.
[ gas/testsuite/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* gas/mips/cp0-names-mips32r2.d: New test.
* gas/mips/hwr-names-mips32r2.d: New test.
* gas/mips/hwr-names-numeric.d: New test.
* gas/mips/hwr-names.s: New test source file.
* gas/mips/mips32r2.d: New test.
* gas/mips/mips32r2.s: New test source file.
* gas/mips/mips32r2-ill.l: New test.
* gas/mips/mips32r2-ill.s: New test source file.
* gas/mips/mips.exp: Add mips32r2 architecture data array
entry. Run new tests mentioned above.
[ include/elf/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* mips.h (E_MIPS_ARCH_32R2): New define.
[ include/opcode/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* mips.h: Document "+" as the start of two-character operand
type names, and add new "K", "+A", "+B", and "+C" operand types.
(OP_MASK_INSMSB, OP_SH_INSMSB, OP_MASK_EXTMSB)
(OP_SH_EXTMSB, INSN_ISA32R2, ISA_MIPS32R2, CPU_MIPS32R2): New
defines.
[ opcodes/ChangeLog ]
2002-12-30 Chris Demetriou <cgd@broadcom.com>
* mips-dis.c (mips_cp0_names_mips3264r2, mips_hwr_names_numeric)
(mips_hwr_names_mips3264r2): New arrays.
(mips_arch_choice): New "hwr_names" member.
(mips_arch_choices): Adjust for structure change, and add a new
entry for "mips32r2" ISA.
(mips_hwr_names): New variable.
(set_default_mips_dis_options): Set mips_hwr_names.
(parse_mips_dis_option): New "hwr-names" option which sets
mips_hwr_names, and adjust "reg-names=ARCH" to set mips_hwr_names.
(print_insn_arg): Change return type to "int"
and use that to indicate number of characters consumed.
Add support for "+" operand extension character, "+A", "+B",
"+C", and "K" operands.
(print_insn_mips): Adjust for changes to print_insn_arg.
(print_mips_disassembler_options): Adjust for "hwr-names"
addition and "reg-names" change.
* mips-opc (I33): New define (shorthand for INSN_ISA32R2).
(mips_builtin_opcodes): Note that "nop" and "ssnop" are special
forms of "sll". Add new MIPS32 Release 2 instructions: ehb,
di, ei, ext, ins, jr.hb, jalr.hb, mfhc1, mfhc2, mthc1, mthc2,
rdhwr, rdpgpr, seb, seh, synci, wrpgpr, wsbh.
Note that hardware rotate instructions (ror, rorv) can be
used on MIPS32 Release 2, and add the official mnemonics
for them (rotr, rotrv) and the similar "rotl" mnemonic for
left-rotate.
2002-12-31 08:29:29 +01:00
|
|
|
Print CPU-specific register names (CP0 register and HWR names)
|
|
|
|
as appropriate for the selected CPU or architecture.
|
[ binutils/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* doc/binutils.texi (objdump): Document MIPS -M options.
[ gas/testsuite/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* gas/mips/cp0-names-mips32.d: New file.
* gas/mips/cp0-names-mips64.d: New file.
* gas/mips/cp0-names-numeric.d: New file.
* gas/mips/cp0-names-sb1.d: New file.
* gas/mips/cp0-names.s: New file.
* gas/mips/fpr-names-32.d: New file.
* gas/mips/fpr-names-64.d: New file.
* gas/mips/fpr-names-n32.d: New file.
* gas/mips/fpr-names-numeric.d: New file.
* gas/mips/fpr-names.s: New file.
* gas/mips/gpr-names-32.d: New file.
* gas/mips/gpr-names-64.d: New file.
* gas/mips/gpr-names-n32.d: New file.
* gas/mips/gpr-names-numeric.d: New file.
* gas/mips/gpr-names.s: New file.
* gas/mips/mips.exp: Run new tests.
[ include/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* dis-asm.h (print_mips_disassembler_options): Prototype.
[ include/opcode/ChangeLog ]
2002-12-19 Chris Demetriou <cgd@broadcom.com>
* mips.h (OP_OP_COP0, OP_OP_COP1, OP_OP_COP2, OP_OP_COP3)
(OP_OP_LWC1, OP_OP_LWC2, OP_OP_LWC3, OP_OP_LDC1, OP_OP_LDC2)
(OP_OP_LDC3, OP_OP_SWC1, OP_OP_SWC2, OP_OP_SWC3, OP_OP_SDC1)
(OP_OP_SDC2, OP_OP_SDC3): Define.
[ opcodes/ChangeLog ]
2002-12-27 Chris Demetriou <cgd@broadcom.com>
* disassemble.c (disassembler_usage): Add invocation of
print_mips_disassembler_options.
* mips-dis.c (print_mips_disassembler_options)
(set_default_mips_dis_options, parse_mips_dis_option)
(parse_mips_dis_options, choose_abi_by_name, choose_arch_by_name)
(choose_arch_by_number): New functions.
(mips_abi_choice, mips_arch_choice): New structures.
(mips32_reg_names, mips64_reg_names, reg_names): Remove.
(mips_gpr_names_numeric, mips_gpr_names_oldabi)
(mips_gpr_names_newabi, mips_fpr_names_numeric)
(mips_fpr_names_32, mips_fpr_names_n32, mips_fpr_names_64)
(mips_cp0_names_numeric, mips_cp0_names_mips3264)
(mips_cp0_names_sb1, mips_abi_choices, mips_arch_choices)
(mips_processor, mips_isa, mips_gpr_names, mips_fpr_names)
(mips_cp0_names): New variables.
(print_insn_args): Use new variables to print GPR, FPR, and CP0
register names.
(mips_isa_type): Remove.
(print_insn_mips): Remove ISA and CPU setup since it is now done...
(_print_insn_mips): Here. Remove register setup code, and
call set_default_mips_dis_options and parse_mips_dis_options
instead.
(print_mips16_insn_arg): Use mips_gpr_names instead of mips32_names.
2002-12-27 09:00:31 +01:00
|
|
|
@end table
|
|
|
|
|
|
|
|
For any of the options listed above, @var{ABI} or
|
|
|
|
@var{ARCH} may be specified as @samp{numeric} to have numbers printed
|
|
|
|
rather than names, for the selected types of registers.
|
|
|
|
You can list the available values of @var{ABI} and @var{ARCH} using
|
|
|
|
the @option{--help} option.
|
|
|
|
|
2005-03-29 18:13:48 +02:00
|
|
|
For VAX, you can specify function entry addresses with @option{-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
|
2006-07-24 15:49:50 +02:00
|
|
|
be decoded as VAX instructions, which would probably lead the rest
|
2005-03-29 18:13:48 +02:00
|
|
|
of the function being wrongly disassembled.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -p
|
|
|
|
@itemx --private-headers
|
|
|
|
Print information that is specific to the object file format. The exact
|
|
|
|
information printed depends upon the object file format. For some
|
|
|
|
object file formats, no additional information is printed.
|
|
|
|
|
2011-05-16 14:22:13 +02:00
|
|
|
@item -P @var{options}
|
|
|
|
@itemx --private=@var{options}
|
|
|
|
Print information that is specific to the object file format. The
|
|
|
|
argument @var{options} is a comma separated list that depends on the
|
|
|
|
format (the lists of options is displayed with the help).
|
|
|
|
|
2014-12-23 14:11:10 +01:00
|
|
|
For XCOFF, the available options are:
|
|
|
|
@table @code
|
|
|
|
@item header
|
|
|
|
@item aout
|
|
|
|
@item sections
|
|
|
|
@item syms
|
|
|
|
@item relocs
|
|
|
|
@item lineno,
|
|
|
|
@item loader
|
|
|
|
@item except
|
|
|
|
@item typchk
|
|
|
|
@item traceback
|
|
|
|
@item toc
|
|
|
|
@item ldinfo
|
|
|
|
@end table
|
|
|
|
|
|
|
|
Not all object formats support this option. In particular the ELF
|
|
|
|
format does not use it.
|
2011-05-16 14:22:13 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -r
|
|
|
|
@itemx --reloc
|
|
|
|
@cindex relocation entries, in object file
|
2001-08-01 17:54:41 +02:00
|
|
|
Print the relocation entries of the file. If used with @option{-d} or
|
|
|
|
@option{-D}, the relocations are printed interspersed with the
|
1999-05-03 09:29:11 +02:00
|
|
|
disassembly.
|
|
|
|
|
|
|
|
@item -R
|
|
|
|
@itemx --dynamic-reloc
|
|
|
|
@cindex dynamic relocation entries, in object file
|
|
|
|
Print the dynamic relocation entries of the file. This is only
|
|
|
|
meaningful for dynamic objects, such as certain types of shared
|
2009-01-13 07:41:53 +01:00
|
|
|
libraries. As for @option{-r}, if used with @option{-d} or
|
|
|
|
@option{-D}, the relocations are printed interspersed with the
|
|
|
|
disassembly.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -s
|
|
|
|
@itemx --full-contents
|
|
|
|
@cindex sections, full contents
|
|
|
|
@cindex object file sections
|
2003-09-03 10:26:52 +02:00
|
|
|
Display the full contents of any sections requested. By default all
|
|
|
|
non-empty sections are displayed.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -S
|
|
|
|
@itemx --source
|
|
|
|
@cindex source disassembly
|
|
|
|
@cindex disassembly, with source
|
|
|
|
Display source code intermixed with disassembly, if possible. Implies
|
2001-08-01 17:54:41 +02:00
|
|
|
@option{-d}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2019-08-28 12:39:19 +02:00
|
|
|
@item --source-comment[=@var{txt}]
|
|
|
|
@cindex source disassembly
|
|
|
|
@cindex disassembly, with source
|
|
|
|
Like the @option{-S} option, but all source code lines are displayed
|
|
|
|
with a prefix of @var{txt}. Typically @var{txt} will be a comment
|
|
|
|
string which can be used to distinguish the assembler code from the
|
|
|
|
source code. If @var{txt} is not provided then a default string of
|
|
|
|
@var{``# ``} (hash followed by a space), will be used.
|
|
|
|
|
2009-02-03 16:48:50 +01:00
|
|
|
@item --prefix=@var{prefix}
|
|
|
|
@cindex Add prefix to absolute paths
|
|
|
|
Specify @var{prefix} to add to the absolute paths when used with
|
2011-11-29 19:07:41 +01:00
|
|
|
@option{-S}.
|
2009-02-03 16:48:50 +01:00
|
|
|
|
|
|
|
@item --prefix-strip=@var{level}
|
|
|
|
@cindex Strip absolute paths
|
|
|
|
Indicate how many initial directory names to strip off the hardwired
|
|
|
|
absolute paths. It has no effect without @option{--prefix=}@var{prefix}.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --show-raw-insn
|
|
|
|
When disassembling instructions, print the instruction in hex as well as
|
|
|
|
in symbolic form. This is the default except when
|
2001-08-01 17:54:41 +02:00
|
|
|
@option{--prefix-addresses} is used.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --no-show-raw-insn
|
|
|
|
When disassembling instructions, do not print the instruction bytes.
|
2001-08-01 17:54:41 +02:00
|
|
|
This is the default when @option{--prefix-addresses} is used.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2009-07-20 15:40:48 +02:00
|
|
|
@item --insn-width=@var{width}
|
2011-11-29 19:07:41 +01:00
|
|
|
@cindex Instruction width
|
2009-07-20 15:40:48 +02:00
|
|
|
Display @var{width} bytes on a single line when disassembling
|
|
|
|
instructions.
|
|
|
|
|
Add support to readelf and objdump for following links to separate debug information files.
Hi Guys,
I am applying the rather large patch attached to this email to enhance
the readelf and objdump programs so that they now have the ability to
follow links to separate debug info files. (As requested by PR
15152). So for example whereas before we had this output:
$ readelf -wi main.exe
Contents of the .debug_info section:
[...]
<15> DW_AT_comp_dir : (alt indirect string, offset: 0x30c)
[...]
With the new option enabled we get:
$ readelf -wiK main.exe
main.exe: Found separate debug info file: dwz.debug
Contents of the .debug_info section (loaded from main.exe):
[...]
<15> DW_AT_comp_dir : (alt indirect string, offset: 0x30c) /home/nickc/Downloads/dwzm
[...]
The link following feature also means that we can get two lots of
output if the same section exists in both the main file and the
separate debug info file:
$ readelf -wiK main.exe
main.exe: Found separate debug info file: dwz.debug
Contents of the .debug_info section (loaded from main.exe):
[...]
Contents of the .debug_info section (loaded from dwz.debug):
[...]
The patch also adds the ability to display the contents of debuglink
sections:
$ readelf -wk main.exe
Contents of the .gnu_debugaltlink section:
Separate debug info file: dwz.debug
Build-ID (0x14 bytes):
c4 a8 89 8d 64 cf 70 8a 35 68 21 f2 ed 24 45 3e 18 7a 7a 93
Naturally there are long versions of these options (=follow-links and
=links). The documentation has been updated as well, and since both
readelf and objdump use the same set of debug display options, I have
moved the text into a separate file. There are also a couple of new
binutils tests to exercise the new behaviour.
There are a couple of missing features in the current patch however,
although I do intend to address them in follow up submissions:
Firstly the code does not check the build-id inside separate debug
info files when it is searching for a file specified by a
.gnu_debugaltlink section. It just assumes that if the file is there,
then it contains the information being sought.
Secondly I have not checked the DWARF-5 version of these link
features, so there will probably be code to add there.
Thirdly I have only implemented link following for the
DW_FORM_GNU_strp_alt format. Other alternate formats (eg
DW_FORM_GNU_ref_alt) have yet to be implemented.
Lastly, whilst implementing this feature I found it necessary to move
some of the global variables used by readelf (eg section_headers) into
a structure that can be passed around. I have moved all of the global
variables that were necessary to get the patch working, but I need to
complete the operation and move the remaining, file-specific variables
(eg dynamic_strings).
Cheers
Nick
binutils PR 15152
* dwarf.h (enum dwarf_section_display_enum): Add gnu_debuglink,
gnu_debugaltlink and separate_debug_str.
(struct dwarf_section): Add filename field.
Add prototypes for load_separate_debug_file, close_debug_file and
open_debug_file.
* dwarf.c (do_debug_links): New.
(do_follow_links): New.
(separate_debug_file, separate_debug_filename): New.
(fetch_alt_indirect_string): New function. Retrieves a string
from the debug string table in the separate debug info file.
(read_and_display_attr_value): Use it with DW_FORM_GNU_strp_alt.
(load_debug_section_with_follow): New function. Like
load_debug_section, but if the first attempt fails, then tries
again in the separate debug info file.
(introduce): New function.
(process_debug_info): Use load_debug_section_with_follow and
introduce.
(load_debug_info): Likewise.
(display_debug_lines_raw): Likewise.
(display_debug_lines_decoded): Likewise.
(display_debug_macinfo): Likewise.
(display_debug_macro): Likewise.
(display_debug_abbrev): Likewise.
(display_debug_loc): Likewise.
(display_debug_str): Likewise.
(display_debug_aranges): Likewise.
(display_debug_addr); Likewise.
(display_debug_frames): Likewise.
(display_gdb_index): Likewise.
(process_cu_tu_index): Likewise.
(load_cu_tu_indexes): Likewise.
(display_debug_links): New function. Displays the contents of a
.gnu_debuglink or .gnu_debugaltlink section.
(calc_gnu_debuglink_ctc32):New function. Calculates a CRC32
value.
(check_gnu_debuglink): New function. Checks the CRC of a
potential separate debug info file.
(parse_gnu_debuglink): New function. Reads a CRC value out of a
.gnu_debuglink section.
(check_gnu_debugaltlink): New function.
(parse_gnu_debugaltlink): New function. Reads the build-id value
out of a .gnu_debugaltlink section.
(load_separate_debug_info): New function. Finds and loads a
separate debug info file.
(load_separate_debug_file): New function. Attempts to find and
follow a link to a separate debug info file.
(free_debug_memory): Free the separate debug info file
information.
(opts_table): Add "follow-links" and "links".
(dwarf_select_sections_by_letters): Add "k" and "K".
(debug_displays): Reformat. Add .gnu-debuglink and
.gnu_debugaltlink.
Add an extra entry for .debug_str in a separate debug info file.
* doc/binutils.texi: Move description of debug dump features
common to both readelf and objdump into...
* objdump.c (usage): Add -Wk and -WK.
(load_specific_debug_section): Initialise the filename field in
the dwarf_section structure.
(close_debug_file): New function.
(open_debug_file): New function.
(dump_dwarf): Load and dump the separate debug info sections.
* readelf.c (struct filedata): New structure. Contains various
variables that used to be global:
(current_file_size, string_table, string_table_length, elf_header)
(section_headers, program_headers, dump_sects, num_dump_sects):
Move into filedata structure.
(cmdline): New global variable. Contains list of sections to dump
by number, as specified on the command line.
Add filedata parameter to most functions.
(load_debug_section): Load the string table if it has not already
been retrieved.
(close_file): New function.
(close_debug_file): New function.
(open_file): New function.
(open_debug_file): New function.
(process_object): Process sections in any separate debug info files.
* doc/debug.options.texi: New file. Add description of =links and
=follow-links options.
* NEWS: Mention the new feature.
* elfcomm.c: Have the byte gte functions take a const pointer.
* elfcomm.h: Update prototypes.
* testsuite/binutils-all/dw5.W: Update expected output.
* testsuite/binutils-all/objdump.WL: Update expected output.
* testsuite/binutils-all/objdump.exp: Add test of -WK and -Wk.
* testsuite/binutils-all/readelf.exp: Add test of -wK and -wk.
* testsuite/binutils-all/readelf.k: New file.
* testsuite/binutils-all/objdump.Wk: New file.
* testsuite/binutils-all/objdump.WK2: New file.
* testsuite/binutils-all/linkdebug.s: New file.
* testsuite/binutils-all/debuglink.s: New file.
gas * testsuite/gas/avr/large-debug-line-table.d: Update expected
output.
* testsuite/gas/elf/dwarf2-11.d: Likewise.
* testsuite/gas/elf/dwarf2-12.d: Likewise.
* testsuite/gas/elf/dwarf2-13.d: Likewise.
* testsuite/gas/elf/dwarf2-14.d: Likewise.
* testsuite/gas/elf/dwarf2-15.d: Likewise.
* testsuite/gas/elf/dwarf2-16.d: Likewise.
* testsuite/gas/elf/dwarf2-17.d: Likewise.
* testsuite/gas/elf/dwarf2-18.d: Likewise.
* testsuite/gas/elf/dwarf2-5.d: Likewise.
* testsuite/gas/elf/dwarf2-6.d: Likewise.
* testsuite/gas/elf/dwarf2-7.d: Likewise.
ld * testsuite/ld-avr/gc-section-debugline.d: Update expected
output.
2017-11-15 12:34:03 +01:00
|
|
|
@item -W[lLiaprmfFsoRtUuTgAckK]
|
|
|
|
@itemx --dwarf[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links]
|
|
|
|
@include debug.options.texi
|
2011-04-28 19:23:17 +02:00
|
|
|
|
2012-05-11 20:18:34 +02:00
|
|
|
@item --dwarf-check
|
|
|
|
Enable additional checks for consistency of Dwarf information.
|
|
|
|
|
binutils: CTF support for objdump and readelf
This introduces CTF support for objdump and readelf. objdump has the
following new arguments:
--ctf=SECTION: display CTF in the given SECTION
--ctf-parent=SECTION: name of CTF section that is the parent of this section
readelf has the above, and these two as well:
--ctf-symbols=SECTION: name of symbol table section (optional)
--ctf-strings=SECTION: name of string table section (optional)
(objdump can always use BFD machinery to determine the applicable string
and symbol tables automatically, so these arguments are unnecessary.)
Nearly all the work is done by the ctf_dump machinery in libctf: most of
the remaining work is option-processing and section-reading, and thus is
different for objdump and readelf: the minimal amount of similar code
remaining is, in my view, too small to share, particularly given that
objdump uses ctf_bfdopen() and readelf uses ctf_simple_open() since it
doesn't have a bfd.
I am not particularly satisfied with the way resources are freed in
either of these (I was forced to do it at the top level, for lack of
anywhere else to free resources allocated during option processing), but
I can't see any better way to do it without introducing new
infrastructure for no other purpose.
There are essentially arbitrary ordering changes to the Makefile.in's
order of libtool-related stuff that I can't get rid of, but they have no
semantic effect. (It is possible that some hunks of these changes could
be dropped, but that seems a bit risky to me.)
binutils/
* objdump.c (ctf-api.h): New include.
(dump_ctf_section_info): New variable.
(dump_ctf_section_name): Likewise.
(usage): Describe new options.
(enum option_values): Add OPTION_CTF and OPTION_CTF_PARENT.
(main): Use them to add --ctf and --ctf-parent.
(read_section_stabs): Add new parameter, entsize_ptr.
(find_stabs_section): Adjust accordingly.
(make_ctfsect): New.
(dump_ctf_indent_lines): New.
(dump_ctf_archive_member): New.
(dump_ctf): New.
(dump_bfd): Call it. Free resources afterwards.
* readelf.c (ctf-api.h): New include.
(CTF_DUMP): New.
(static bfd_boolean do_ctf): Likewise.
(dump_ctf_parent_name): Likewise.
(dump_ctf_symtab_name): Likewise.
(dump_ctf_strtab_name): Likewise.
(OPTION_CTF_DUMP): Likewise.
(OPTION_CTF_PARENT): Likewise.
(OPTION_CTF_SYMBOLS): Likewise.
(OPTION_CTF_STRINGS): Likewise.
(options): Add them.
(usage): Likewise.
(parse_args): Handle the new options, requesting CTF_DUMP.
(process_section_contents): Handle CTF_DUMP.
(shdr_to_ctf_sect): New.
(dump_ctf_indent_lines): New.
(dump_section_as_ctf): New.
(main): Free resources.
* Makefile.am (LIBCTF): New variable.
(objdump_DEPENDENCIES): Use it.
(readelf_DEPENDENCIES): Likewise.
(objdump_LDADD): Likewise.
(readelf_LDADD): Likewise.
* aclocal.m4: Regenerated.
* Makefile.in: Likewise.
* doc/binutils.texi (objdump): Document the new options.
(readelf): Likewise.
* doc/ctf.options.texi: New.
* doc/Makefile.in: Regenerated.
* NEWS: Mention the new feature.
2019-04-24 13:04:33 +02:00
|
|
|
@include ctf.options.texi
|
|
|
|
|
1999-11-21 12:37:21 +01:00
|
|
|
@item -G
|
2003-02-21 11:30:35 +01:00
|
|
|
@itemx --stabs
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex stab
|
|
|
|
@cindex .stab
|
|
|
|
@cindex debug symbols
|
|
|
|
@cindex ELF object file format
|
|
|
|
Display the full contents of any sections requested. Display the
|
|
|
|
contents of the .stab and .stab.index and .stab.excl sections from an
|
|
|
|
ELF file. This is only useful on systems (such as Solaris 2.0) in which
|
|
|
|
@code{.stab} debugging symbol-table entries are carried in an ELF
|
|
|
|
section. In most other file formats, debugging symbol-table entries are
|
2001-08-01 17:54:41 +02:00
|
|
|
interleaved with linkage symbols, and are visible in the @option{--syms}
|
2001-03-25 22:32:31 +02:00
|
|
|
output.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --start-address=@var{address}
|
|
|
|
@cindex start-address
|
|
|
|
Start displaying data at the specified address. This affects the output
|
2001-08-01 17:54:41 +02:00
|
|
|
of the @option{-d}, @option{-r} and @option{-s} options.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --stop-address=@var{address}
|
|
|
|
@cindex stop-address
|
|
|
|
Stop displaying data at the specified address. This affects the output
|
2001-08-01 17:54:41 +02:00
|
|
|
of the @option{-d}, @option{-r} and @option{-s} options.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -t
|
|
|
|
@itemx --syms
|
|
|
|
@cindex symbol table entries, printing
|
|
|
|
Print the symbol table entries of the file.
|
2007-09-17 11:58:27 +02:00
|
|
|
This is similar to the information provided by the @samp{nm} program,
|
|
|
|
although the display format is different. The format of the output
|
|
|
|
depends upon the format of the file being dumped, but there are two main
|
|
|
|
types. One looks like this:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
[ 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
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
where the number inside the square brackets is the number of the entry
|
|
|
|
in the symbol table, the @var{sec} number is the section number, the
|
|
|
|
@var{fl} value are the symbol's flag bits, the @var{ty} number is the
|
|
|
|
symbol's type, the @var{scl} number is the symbol's storage class and
|
|
|
|
the @var{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:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
00000000 l d .bss 00000000 .bss
|
|
|
|
00000000 g .text 00000000 fred
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
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
|
2007-09-17 13:14:22 +02:00
|
|
|
characters are described below. Next is the section with which the
|
|
|
|
symbol is associated or @emph{*ABS*} if the section is absolute (ie
|
|
|
|
not connected with any section), or @emph{*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.
|
2007-09-17 11:58:27 +02:00
|
|
|
|
|
|
|
The flag characters are divided into 7 groups as follows:
|
|
|
|
@table @code
|
|
|
|
@item l
|
|
|
|
@itemx g
|
2009-07-23 15:00:30 +02:00
|
|
|
@itemx u
|
2007-09-17 11:58:27 +02:00
|
|
|
@itemx !
|
2009-07-23 15:00:30 +02:00
|
|
|
The symbol is a local (l), global (g), unique global (u), neither
|
|
|
|
global nor local (a space) or both global and local (!). A
|
2007-10-16 21:01:47 +02:00
|
|
|
symbol can be neither local or global for a variety of reasons, e.g.,
|
2007-09-17 11:58:27 +02:00
|
|
|
because it is used for debugging, but it is probably an indication of
|
2009-07-23 15:00:30 +02:00
|
|
|
a bug if it is ever both local and global. Unique global symbols are
|
|
|
|
a GNU extension to the standard set of ELF symbol bindings. For such
|
|
|
|
a symbol the dynamic linker will make sure that in the entire process
|
|
|
|
there is just one symbol with this name and type in use.
|
2007-09-17 11:58:27 +02:00
|
|
|
|
|
|
|
@item w
|
|
|
|
The symbol is weak (w) or strong (a space).
|
|
|
|
|
|
|
|
@item C
|
|
|
|
The symbol denotes a constructor (C) or an ordinary symbol (a space).
|
|
|
|
|
|
|
|
@item W
|
|
|
|
The symbol is a warning (W) or a normal symbol (a space). A warning
|
|
|
|
symbol's name is a message to be displayed if the symbol following the
|
|
|
|
warning symbol is ever referenced.
|
|
|
|
|
|
|
|
@item I
|
2008-12-04 09:04:47 +01:00
|
|
|
@item i
|
|
|
|
The symbol is an indirect reference to another symbol (I), a function
|
|
|
|
to be evaluated during reloc processing (i) or a normal symbol (a
|
|
|
|
space).
|
2007-09-17 11:58:27 +02:00
|
|
|
|
|
|
|
@item d
|
|
|
|
@itemx D
|
|
|
|
The symbol is a debugging symbol (d) or a dynamic symbol (D) or a
|
|
|
|
normal symbol (a space).
|
|
|
|
|
|
|
|
@item F
|
|
|
|
@item f
|
|
|
|
@item O
|
2007-09-17 13:14:22 +02:00
|
|
|
The symbol is the name of a function (F) or a file (f) or an object
|
2007-09-17 11:58:27 +02:00
|
|
|
(O) or just a normal symbol (a space).
|
|
|
|
@end table
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -T
|
|
|
|
@itemx --dynamic-syms
|
|
|
|
@cindex dynamic symbol table entries, printing
|
|
|
|
Print the dynamic symbol table entries of the file. This is only
|
|
|
|
meaningful for dynamic objects, such as certain types of shared
|
|
|
|
libraries. This is similar to the information provided by the @samp{nm}
|
2001-08-01 17:54:41 +02:00
|
|
|
program when given the @option{-D} (@option{--dynamic}) option.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2016-11-11 12:49:45 +01:00
|
|
|
The output format is similar to that produced by the @option{--syms}
|
|
|
|
option, except that an extra field is inserted before the symbol's
|
|
|
|
name, giving the version information associated with the symbol.
|
2016-11-11 15:13:02 +01:00
|
|
|
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.
|
2016-11-11 12:49:45 +01:00
|
|
|
|
2004-10-08 16:54:04 +02:00
|
|
|
@item --special-syms
|
|
|
|
When displaying symbols include those which the target considers to be
|
|
|
|
special in some way and which would not normally be of interest to the
|
|
|
|
user.
|
|
|
|
|
2003-02-21 11:30:35 +01:00
|
|
|
@item -V
|
|
|
|
@itemx --version
|
2001-08-01 17:54:41 +02:00
|
|
|
Print the version number of @command{objdump} and exit.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -x
|
2003-02-21 11:30:35 +01:00
|
|
|
@itemx --all-headers
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex all header information, object file
|
|
|
|
@cindex header information, all
|
|
|
|
Display all available header information, including the symbol table and
|
2001-08-01 17:54:41 +02:00
|
|
|
relocation entries. Using @option{-x} is equivalent to specifying all of
|
2004-09-06 10:07:42 +02:00
|
|
|
@option{-a -f -h -p -r -t}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -w
|
|
|
|
@itemx --wide
|
|
|
|
@cindex wide output, printing
|
|
|
|
Format some lines for output devices that have more than 80 columns.
|
2001-12-20 12:20:17 +01:00
|
|
|
Also do not truncate symbol names when they are displayed.
|
2002-10-23 00:40:47 +02:00
|
|
|
|
|
|
|
@item -z
|
2002-10-23 00:59:02 +02:00
|
|
|
@itemx --disassemble-zeroes
|
2002-10-23 00:40:47 +02:00
|
|
|
Normally the disassembly output will skip blocks of zeroes. This
|
|
|
|
option directs the disassembler to disassemble those blocks, just like
|
|
|
|
any other data.
|
1999-05-03 09:29:11 +02:00
|
|
|
@end table
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO objdump
|
|
|
|
nm(1), readelf(1), and the Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@node ranlib
|
|
|
|
@chapter ranlib
|
|
|
|
|
|
|
|
@kindex ranlib
|
|
|
|
@cindex archive contents
|
|
|
|
@cindex symbol index
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@c man title ranlib generate an index to an archive
|
2001-03-25 22:32:31 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS ranlib
|
2012-02-01 17:49:26 +01:00
|
|
|
ranlib [@option{--plugin} @var{name}] [@option{-DhHvVt}] @var{archive}
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION ranlib
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{ranlib} generates an index to the contents of an archive and
|
1999-05-03 09:29:11 +02:00
|
|
|
stores it in the archive. The index lists each symbol defined by a
|
2007-06-29 02:34:14 +02:00
|
|
|
member of an archive that is a relocatable object file.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
You may use @samp{nm -s} or @samp{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.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
The @sc{gnu} @command{ranlib} program is another form of @sc{gnu} @command{ar}; running
|
|
|
|
@command{ranlib} is completely equivalent to executing @samp{ar -s}.
|
1999-05-03 09:29:11 +02:00
|
|
|
@xref{ar}.
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS ranlib
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @env
|
2011-11-29 19:07:41 +01:00
|
|
|
@item -h
|
|
|
|
@itemx -H
|
|
|
|
@itemx --help
|
|
|
|
Show usage information for @command{ranlib}.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -v
|
|
|
|
@itemx -V
|
1999-10-08 15:56:33 +02:00
|
|
|
@itemx --version
|
2001-08-01 17:54:41 +02:00
|
|
|
Show the version number of @command{ranlib}.
|
2008-02-27 12:11:06 +01:00
|
|
|
|
2011-11-29 19:07:41 +01:00
|
|
|
@item -D
|
|
|
|
@cindex deterministic archives
|
2011-12-21 20:39:11 +01:00
|
|
|
@kindex --enable-deterministic-archives
|
2011-11-29 19:07:41 +01:00
|
|
|
Operate in @emph{deterministic} mode. The symbol map archive member's
|
|
|
|
header will show zero for the UID, GID, and timestamp. When this
|
|
|
|
option is used, multiple runs will produce identical output files.
|
|
|
|
|
2013-08-23 16:20:34 +02:00
|
|
|
If @file{binutils} was configured with
|
|
|
|
@option{--enable-deterministic-archives}, then this mode is on by
|
|
|
|
default. It can be disabled with the @samp{-U} option, described
|
|
|
|
below.
|
2011-12-21 20:39:11 +01:00
|
|
|
|
2008-02-27 12:11:06 +01:00
|
|
|
@item -t
|
|
|
|
Update the timestamp of the symbol map of an archive.
|
2011-12-21 20:39:11 +01:00
|
|
|
|
|
|
|
@item -U
|
|
|
|
@cindex deterministic archives
|
|
|
|
@kindex --enable-deterministic-archives
|
|
|
|
Do @emph{not} operate in @emph{deterministic} mode. This is the
|
|
|
|
inverse of the @samp{-D} option, above: the archive index will get
|
|
|
|
actual UID, GID, timestamp, and file mode values.
|
|
|
|
|
2013-08-23 16:20:34 +02:00
|
|
|
If @file{binutils} was configured @emph{without}
|
|
|
|
@option{--enable-deterministic-archives}, then this mode is on by
|
|
|
|
default.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@end table
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO ranlib
|
|
|
|
ar(1), nm(1), and the Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@node size
|
|
|
|
@chapter size
|
|
|
|
|
|
|
|
@kindex size
|
|
|
|
@cindex section sizes
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@c man title size list section sizes and total size of binary files
|
2001-03-25 22:32:31 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS size
|
binutils: Add new GNU format mode to `size` utility
The size tool currently defaults to berkeley format output. However,
this output format has a weird quirk, read-only data is counted
against the text sections, not the data sections.
The code offers no real explanation for why this is, but I'm reluctant
to change it for two reasons, first, I'm assuming it probably makes
sense in some case that I'm not thinking of (maybe a target where
sections are not marked executable, and so there's no distinction
between read-only data and code), and second, the code has been this
way for at least 20 years, I worry that changing things now might
cause more confusion than it solves.
This commit then introduces a new output format for the size tool,
this new format displays the results in a similar manor to the
berkeley format, but counts read-only data in the data column, and
only executable sections are counted in the text column.
Given that this is a brand new output format I've gone ahead and
simplified things a little, while the berkeley format displays the
total twice, once in decimal and once in hex, the new display format
just displays the total in decimal. Of course, there's still the
'--radix' option which can be used to display all the results in
hexadecimal or octal.
I've called the new format 'gnu', so '--format=gnu' or '-G' are used
to access it.
binutils/ChangeLog:
* size.c (berkeley_format): Delete.
(enum output_format): New enum.
(selected_output_format): New variable.
(usage): Update to mention GNU format.
(main): Update to extract options, and select format as needed.
Handle GNU format where needed.
(berkeley_sum): Renamed to...
(berkeley_or_gnu_sum): ...this, and updated to handle both formats.
(berkeley_format): Renamed to...
(berkeley_or_gnu_format): ...this, and updated to handle both
formats.
(print_sizes): Handle GNU format.
* doc/binutils.texi (size): Document new GNU format.
* testsuite/binutils-all/size.exp: Add test of extended
functionality.
* NEWS: Mention new functionality.
2019-01-24 15:27:27 +01:00
|
|
|
size [@option{-A}|@option{-B}|@option{-G}|@option{--format=}@var{compatibility}]
|
2002-01-25 16:37:04 +01:00
|
|
|
[@option{--help}]
|
|
|
|
[@option{-d}|@option{-o}|@option{-x}|@option{--radix=}@var{number}]
|
2007-07-05 11:01:28 +02:00
|
|
|
[@option{--common}]
|
2002-01-25 16:37:04 +01:00
|
|
|
[@option{-t}|@option{--totals}]
|
2007-06-29 02:34:14 +02:00
|
|
|
[@option{--target=}@var{bfdname}] [@option{-V}|@option{--version}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@var{objfile}@dots{}]
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION size
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
The @sc{gnu} @command{size} utility lists the section sizes and the total
|
|
|
|
size for each of the binary files @var{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.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@var{objfile}@dots{} are the files to be examined. If none are
|
|
|
|
specified, the file @code{a.out} will be used instead.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS size
|
|
|
|
|
2018-07-02 12:18:24 +02:00
|
|
|
The command-line options have the following meanings:
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @env
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -A
|
|
|
|
@itemx -B
|
binutils: Add new GNU format mode to `size` utility
The size tool currently defaults to berkeley format output. However,
this output format has a weird quirk, read-only data is counted
against the text sections, not the data sections.
The code offers no real explanation for why this is, but I'm reluctant
to change it for two reasons, first, I'm assuming it probably makes
sense in some case that I'm not thinking of (maybe a target where
sections are not marked executable, and so there's no distinction
between read-only data and code), and second, the code has been this
way for at least 20 years, I worry that changing things now might
cause more confusion than it solves.
This commit then introduces a new output format for the size tool,
this new format displays the results in a similar manor to the
berkeley format, but counts read-only data in the data column, and
only executable sections are counted in the text column.
Given that this is a brand new output format I've gone ahead and
simplified things a little, while the berkeley format displays the
total twice, once in decimal and once in hex, the new display format
just displays the total in decimal. Of course, there's still the
'--radix' option which can be used to display all the results in
hexadecimal or octal.
I've called the new format 'gnu', so '--format=gnu' or '-G' are used
to access it.
binutils/ChangeLog:
* size.c (berkeley_format): Delete.
(enum output_format): New enum.
(selected_output_format): New variable.
(usage): Update to mention GNU format.
(main): Update to extract options, and select format as needed.
Handle GNU format where needed.
(berkeley_sum): Renamed to...
(berkeley_or_gnu_sum): ...this, and updated to handle both formats.
(berkeley_format): Renamed to...
(berkeley_or_gnu_format): ...this, and updated to handle both
formats.
(print_sizes): Handle GNU format.
* doc/binutils.texi (size): Document new GNU format.
* testsuite/binutils-all/size.exp: Add test of extended
functionality.
* NEWS: Mention new functionality.
2019-01-24 15:27:27 +01:00
|
|
|
@itemx -G
|
1999-05-03 09:29:11 +02:00
|
|
|
@itemx --format=@var{compatibility}
|
2001-08-01 17:54:41 +02:00
|
|
|
@cindex @command{size} display format
|
1999-05-03 09:29:11 +02:00
|
|
|
Using one of these options, you can choose whether the output from @sc{gnu}
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{size} resembles output from System V @command{size} (using @option{-A},
|
|
|
|
or @option{--format=sysv}), or Berkeley @command{size} (using @option{-B}, or
|
|
|
|
@option{--format=berkeley}). The default is the one-line format similar to
|
binutils: Add new GNU format mode to `size` utility
The size tool currently defaults to berkeley format output. However,
this output format has a weird quirk, read-only data is counted
against the text sections, not the data sections.
The code offers no real explanation for why this is, but I'm reluctant
to change it for two reasons, first, I'm assuming it probably makes
sense in some case that I'm not thinking of (maybe a target where
sections are not marked executable, and so there's no distinction
between read-only data and code), and second, the code has been this
way for at least 20 years, I worry that changing things now might
cause more confusion than it solves.
This commit then introduces a new output format for the size tool,
this new format displays the results in a similar manor to the
berkeley format, but counts read-only data in the data column, and
only executable sections are counted in the text column.
Given that this is a brand new output format I've gone ahead and
simplified things a little, while the berkeley format displays the
total twice, once in decimal and once in hex, the new display format
just displays the total in decimal. Of course, there's still the
'--radix' option which can be used to display all the results in
hexadecimal or octal.
I've called the new format 'gnu', so '--format=gnu' or '-G' are used
to access it.
binutils/ChangeLog:
* size.c (berkeley_format): Delete.
(enum output_format): New enum.
(selected_output_format): New variable.
(usage): Update to mention GNU format.
(main): Update to extract options, and select format as needed.
Handle GNU format where needed.
(berkeley_sum): Renamed to...
(berkeley_or_gnu_sum): ...this, and updated to handle both formats.
(berkeley_format): Renamed to...
(berkeley_or_gnu_format): ...this, and updated to handle both
formats.
(print_sizes): Handle GNU format.
* doc/binutils.texi (size): Document new GNU format.
* testsuite/binutils-all/size.exp: Add test of extended
functionality.
* NEWS: Mention new functionality.
2019-01-24 15:27:27 +01:00
|
|
|
Berkeley's. Alternatively, you can choose the GNU format output
|
|
|
|
(using @option{-G}, or @option{--format=gnu}), this is similar to
|
|
|
|
Berkeley's output format, but sizes are counted differently.
|
1999-05-03 09:29:11 +02:00
|
|
|
@c Bonus for doc-source readers: you can also say --format=strange (or
|
|
|
|
@c anything else that starts with 's') for sysv, and --format=boring (or
|
|
|
|
@c anything else that starts with 'b') for Berkeley.
|
|
|
|
|
|
|
|
Here is an example of the Berkeley (default) format of output from
|
2007-06-29 02:34:14 +02:00
|
|
|
@command{size}:
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
1999-10-08 15:56:33 +02:00
|
|
|
$ size --format=Berkeley ranlib size
|
2019-01-31 11:14:09 +01:00
|
|
|
text data bss dec hex filename
|
|
|
|
294880 81920 11592 388392 5ed28 ranlib
|
|
|
|
294880 81920 11888 388688 5ee50 size
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
binutils: Add new GNU format mode to `size` utility
The size tool currently defaults to berkeley format output. However,
this output format has a weird quirk, read-only data is counted
against the text sections, not the data sections.
The code offers no real explanation for why this is, but I'm reluctant
to change it for two reasons, first, I'm assuming it probably makes
sense in some case that I'm not thinking of (maybe a target where
sections are not marked executable, and so there's no distinction
between read-only data and code), and second, the code has been this
way for at least 20 years, I worry that changing things now might
cause more confusion than it solves.
This commit then introduces a new output format for the size tool,
this new format displays the results in a similar manor to the
berkeley format, but counts read-only data in the data column, and
only executable sections are counted in the text column.
Given that this is a brand new output format I've gone ahead and
simplified things a little, while the berkeley format displays the
total twice, once in decimal and once in hex, the new display format
just displays the total in decimal. Of course, there's still the
'--radix' option which can be used to display all the results in
hexadecimal or octal.
I've called the new format 'gnu', so '--format=gnu' or '-G' are used
to access it.
binutils/ChangeLog:
* size.c (berkeley_format): Delete.
(enum output_format): New enum.
(selected_output_format): New variable.
(usage): Update to mention GNU format.
(main): Update to extract options, and select format as needed.
Handle GNU format where needed.
(berkeley_sum): Renamed to...
(berkeley_or_gnu_sum): ...this, and updated to handle both formats.
(berkeley_format): Renamed to...
(berkeley_or_gnu_format): ...this, and updated to handle both
formats.
(print_sizes): Handle GNU format.
* doc/binutils.texi (size): Document new GNU format.
* testsuite/binutils-all/size.exp: Add test of extended
functionality.
* NEWS: Mention new functionality.
2019-01-24 15:27:27 +01:00
|
|
|
The Berkeley style output counts read only data in the @code{text}
|
|
|
|
column, not in the @code{data} column, the @code{dec} and @code{hex}
|
|
|
|
columns both display the sum of the @code{text}, @code{data}, and
|
|
|
|
@code{bss} columns in decimal and hexadecimal respectively.
|
|
|
|
|
|
|
|
The GNU format counts read only data in the @code{data} column, not
|
|
|
|
the @code{text} column, and only displays the sum of the @code{text},
|
|
|
|
@code{data}, and @code{bss} columns once, in the @code{total} column.
|
|
|
|
The @option{--radix} option can be used to change the number base for
|
|
|
|
all columns. Here is the same data displayed with GNU conventions:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
$ size --format=GNU ranlib size
|
|
|
|
text data bss total filename
|
|
|
|
279880 96920 11592 388392 ranlib
|
|
|
|
279880 96920 11888 388688 size
|
|
|
|
@end smallexample
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@noindent
|
|
|
|
This is the same data, but displayed closer to System V conventions:
|
|
|
|
|
|
|
|
@smallexample
|
1999-10-08 15:56:33 +02:00
|
|
|
$ size --format=SysV ranlib size
|
1999-05-03 09:29:11 +02:00
|
|
|
ranlib :
|
|
|
|
section size addr
|
2007-06-29 02:34:14 +02:00
|
|
|
.text 294880 8192
|
|
|
|
.data 81920 303104
|
|
|
|
.bss 11592 385024
|
|
|
|
Total 388392
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
|
|
|
|
size :
|
|
|
|
section size addr
|
2007-06-29 02:34:14 +02:00
|
|
|
.text 294880 8192
|
|
|
|
.data 81920 303104
|
|
|
|
.bss 11888 385024
|
|
|
|
Total 388688
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
@item --help
|
|
|
|
Show a summary of acceptable arguments and options.
|
|
|
|
|
|
|
|
@item -d
|
|
|
|
@itemx -o
|
|
|
|
@itemx -x
|
|
|
|
@itemx --radix=@var{number}
|
2001-08-01 17:54:41 +02:00
|
|
|
@cindex @command{size} number format
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex radix for section sizes
|
|
|
|
Using one of these options, you can control whether the size of each
|
2001-08-01 17:54:41 +02:00
|
|
|
section is given in decimal (@option{-d}, or @option{--radix=10}); octal
|
|
|
|
(@option{-o}, or @option{--radix=8}); or hexadecimal (@option{-x}, or
|
|
|
|
@option{--radix=16}). In @option{--radix=@var{number}}, only the three
|
1999-05-03 09:29:11 +02:00
|
|
|
values (8, 10, 16) are supported. The total size is always given in two
|
2001-08-01 17:54:41 +02:00
|
|
|
radices; decimal and hexadecimal for @option{-d} or @option{-x} output, or
|
|
|
|
octal and hexadecimal if you're using @option{-o}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2007-07-05 11:01:28 +02:00
|
|
|
@item --common
|
|
|
|
Print total size of common symbols in each file. When using Berkeley
|
binutils: Add new GNU format mode to `size` utility
The size tool currently defaults to berkeley format output. However,
this output format has a weird quirk, read-only data is counted
against the text sections, not the data sections.
The code offers no real explanation for why this is, but I'm reluctant
to change it for two reasons, first, I'm assuming it probably makes
sense in some case that I'm not thinking of (maybe a target where
sections are not marked executable, and so there's no distinction
between read-only data and code), and second, the code has been this
way for at least 20 years, I worry that changing things now might
cause more confusion than it solves.
This commit then introduces a new output format for the size tool,
this new format displays the results in a similar manor to the
berkeley format, but counts read-only data in the data column, and
only executable sections are counted in the text column.
Given that this is a brand new output format I've gone ahead and
simplified things a little, while the berkeley format displays the
total twice, once in decimal and once in hex, the new display format
just displays the total in decimal. Of course, there's still the
'--radix' option which can be used to display all the results in
hexadecimal or octal.
I've called the new format 'gnu', so '--format=gnu' or '-G' are used
to access it.
binutils/ChangeLog:
* size.c (berkeley_format): Delete.
(enum output_format): New enum.
(selected_output_format): New variable.
(usage): Update to mention GNU format.
(main): Update to extract options, and select format as needed.
Handle GNU format where needed.
(berkeley_sum): Renamed to...
(berkeley_or_gnu_sum): ...this, and updated to handle both formats.
(berkeley_format): Renamed to...
(berkeley_or_gnu_format): ...this, and updated to handle both
formats.
(print_sizes): Handle GNU format.
* doc/binutils.texi (size): Document new GNU format.
* testsuite/binutils-all/size.exp: Add test of extended
functionality.
* NEWS: Mention new functionality.
2019-01-24 15:27:27 +01:00
|
|
|
or GNU format these are included in the bss size.
|
2007-07-05 11:01:28 +02:00
|
|
|
|
2002-01-25 16:37:04 +01:00
|
|
|
@item -t
|
|
|
|
@itemx --totals
|
binutils: Add new GNU format mode to `size` utility
The size tool currently defaults to berkeley format output. However,
this output format has a weird quirk, read-only data is counted
against the text sections, not the data sections.
The code offers no real explanation for why this is, but I'm reluctant
to change it for two reasons, first, I'm assuming it probably makes
sense in some case that I'm not thinking of (maybe a target where
sections are not marked executable, and so there's no distinction
between read-only data and code), and second, the code has been this
way for at least 20 years, I worry that changing things now might
cause more confusion than it solves.
This commit then introduces a new output format for the size tool,
this new format displays the results in a similar manor to the
berkeley format, but counts read-only data in the data column, and
only executable sections are counted in the text column.
Given that this is a brand new output format I've gone ahead and
simplified things a little, while the berkeley format displays the
total twice, once in decimal and once in hex, the new display format
just displays the total in decimal. Of course, there's still the
'--radix' option which can be used to display all the results in
hexadecimal or octal.
I've called the new format 'gnu', so '--format=gnu' or '-G' are used
to access it.
binutils/ChangeLog:
* size.c (berkeley_format): Delete.
(enum output_format): New enum.
(selected_output_format): New variable.
(usage): Update to mention GNU format.
(main): Update to extract options, and select format as needed.
Handle GNU format where needed.
(berkeley_sum): Renamed to...
(berkeley_or_gnu_sum): ...this, and updated to handle both formats.
(berkeley_format): Renamed to...
(berkeley_or_gnu_format): ...this, and updated to handle both
formats.
(print_sizes): Handle GNU format.
* doc/binutils.texi (size): Document new GNU format.
* testsuite/binutils-all/size.exp: Add test of extended
functionality.
* NEWS: Mention new functionality.
2019-01-24 15:27:27 +01:00
|
|
|
Show totals of all objects listed (Berkeley or GNU format mode only).
|
2002-01-25 16:37:04 +01:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --target=@var{bfdname}
|
|
|
|
@cindex object code format
|
|
|
|
Specify that the object-code format for @var{objfile} is
|
2001-08-01 17:54:41 +02:00
|
|
|
@var{bfdname}. This option may not be necessary; @command{size} can
|
1999-05-03 09:29:11 +02:00
|
|
|
automatically recognize many formats.
|
|
|
|
@xref{Target Selection}, for more information.
|
|
|
|
|
|
|
|
@item -V
|
|
|
|
@itemx --version
|
2001-08-01 17:54:41 +02:00
|
|
|
Display the version number of @command{size}.
|
1999-05-03 09:29:11 +02:00
|
|
|
@end table
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO size
|
|
|
|
ar(1), objdump(1), readelf(1), and the Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@node strings
|
|
|
|
@chapter strings
|
|
|
|
@kindex strings
|
|
|
|
@cindex listings strings
|
|
|
|
@cindex printing strings
|
|
|
|
@cindex strings, printing
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@c man title strings print the sequences of printable characters in files
|
2001-03-25 22:32:31 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS strings
|
2009-04-01 16:57:11 +02:00
|
|
|
strings [@option{-afovV}] [@option{-}@var{min-len}]
|
2001-09-14 13:32:25 +02:00
|
|
|
[@option{-n} @var{min-len}] [@option{--bytes=}@var{min-len}]
|
|
|
|
[@option{-t} @var{radix}] [@option{--radix=}@var{radix}]
|
|
|
|
[@option{-e} @var{encoding}] [@option{--encoding=}@var{encoding}]
|
|
|
|
[@option{-}] [@option{--all}] [@option{--print-file-name}]
|
2006-07-06 11:49:56 +02:00
|
|
|
[@option{-T} @var{bfdname}] [@option{--target=}@var{bfdname}]
|
2014-06-26 15:10:48 +02:00
|
|
|
[@option{-w}] [@option{--include-all-whitespace}]
|
2015-09-10 10:29:13 +02:00
|
|
|
[@option{-s}] [@option{--output-separator}@var{sep_string}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{--help}] [@option{--version}] @var{file}@dots{}
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION strings
|
|
|
|
|
2014-10-31 11:10:37 +01:00
|
|
|
For each @var{file} given, @sc{gnu} @command{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.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2014-10-31 11:10:37 +01:00
|
|
|
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.
|
|
|
|
|
2018-07-02 12:18:24 +02:00
|
|
|
For backwards compatibility any file that occurs after a command-line
|
2014-10-31 11:10:37 +01:00
|
|
|
option of just @option{-} will also be scanned in full, regardless of
|
2019-05-14 11:40:04 +02:00
|
|
|
the presence of any @option{-d} option.
|
2014-10-31 11:10:37 +01:00
|
|
|
|
|
|
|
@command{strings} is mainly useful for determining the contents of
|
|
|
|
non-text files.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS strings
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @env
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -a
|
|
|
|
@itemx --all
|
|
|
|
@itemx -
|
2014-10-31 11:10:37 +01:00
|
|
|
Scan the whole file, regardless of what sections it contains or
|
|
|
|
whether those sections are loaded or initialized. Normally this is
|
|
|
|
the default behaviour, but strings can be configured so that the
|
|
|
|
@option{-d} is the default instead.
|
|
|
|
|
|
|
|
The @option{-} option is position dependent and forces strings to
|
|
|
|
perform full scans of any file that is mentioned after the @option{-}
|
|
|
|
on the command line, even if the @option{-d} option has been
|
|
|
|
specified.
|
|
|
|
|
|
|
|
@item -d
|
|
|
|
@itemx --data
|
|
|
|
Only print strings from initialized, loaded data sections in the
|
|
|
|
file. This may reduce the amount of garbage in the output, but it
|
|
|
|
also exposes the strings program to any security flaws that may be
|
|
|
|
present in the BFD library used to scan and load sections. Strings
|
|
|
|
can be configured so that this option is the default behaviour. In
|
|
|
|
such cases the @option{-a} option can be used to avoid using the BFD
|
|
|
|
library and instead just print all of the strings found in the file.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -f
|
|
|
|
@itemx --print-file-name
|
|
|
|
Print the name of the file before each string.
|
|
|
|
|
|
|
|
@item --help
|
|
|
|
Print a summary of the program usage on the standard output and exit.
|
|
|
|
|
|
|
|
@item -@var{min-len}
|
|
|
|
@itemx -n @var{min-len}
|
|
|
|
@itemx --bytes=@var{min-len}
|
|
|
|
Print sequences of characters that are at least @var{min-len} characters
|
|
|
|
long, instead of the default 4.
|
|
|
|
|
|
|
|
@item -o
|
2001-08-01 17:54:41 +02:00
|
|
|
Like @samp{-t o}. Some other versions of @command{strings} have @option{-o}
|
1999-05-03 09:29:11 +02:00
|
|
|
act like @samp{-t d} instead. Since we can not be compatible with both
|
|
|
|
ways, we simply chose one.
|
|
|
|
|
|
|
|
@item -t @var{radix}
|
|
|
|
@itemx --radix=@var{radix}
|
|
|
|
Print the offset within the file before each string. The single
|
|
|
|
character argument specifies the radix of the offset---@samp{o} for
|
|
|
|
octal, @samp{x} for hexadecimal, or @samp{d} for decimal.
|
|
|
|
|
2001-09-14 13:32:25 +02:00
|
|
|
@item -e @var{encoding}
|
|
|
|
@itemx --encoding=@var{encoding}
|
|
|
|
Select the character encoding of the strings that are to be found.
|
2002-12-23 11:37:38 +01:00
|
|
|
Possible values for @var{encoding} are: @samp{s} = single-7-bit-byte
|
|
|
|
characters (ASCII, ISO 8859, etc., default), @samp{S} =
|
|
|
|
single-8-bit-byte characters, @samp{b} = 16-bit bigendian, @samp{l} =
|
|
|
|
16-bit littleendian, @samp{B} = 32-bit bigendian, @samp{L} = 32-bit
|
2008-04-30 09:27:17 +02:00
|
|
|
littleendian. Useful for finding wide character strings. (@samp{l}
|
|
|
|
and @samp{b} apply to, for example, Unicode UTF-16/UCS-2 encodings).
|
2001-09-14 13:32:25 +02:00
|
|
|
|
2006-07-06 11:49:56 +02:00
|
|
|
@item -T @var{bfdname}
|
|
|
|
@itemx --target=@var{bfdname}
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex object code format
|
|
|
|
Specify an object code format other than your system's default format.
|
|
|
|
@xref{Target Selection}, for more information.
|
|
|
|
|
|
|
|
@item -v
|
2009-04-01 16:57:11 +02:00
|
|
|
@itemx -V
|
1999-05-03 09:29:11 +02:00
|
|
|
@itemx --version
|
|
|
|
Print the program version number on the standard output and exit.
|
2014-06-26 15:10:48 +02:00
|
|
|
|
|
|
|
@item -w
|
|
|
|
@itemx --include-all-whitespace
|
|
|
|
By default tab and space characters are included in the strings that
|
|
|
|
are displayed, but other whitespace characters, such a newlines and
|
|
|
|
carriage returns, are not. The @option{-w} option changes this so
|
|
|
|
that all whitespace characters are considered to be part of a string.
|
2015-09-10 10:29:13 +02:00
|
|
|
|
|
|
|
@item -s
|
|
|
|
@itemx --output-separator
|
|
|
|
By default, output strings are delimited by a new-line. This option
|
|
|
|
allows you to supply any string to be used as the output record
|
|
|
|
separator. Useful with --include-all-whitespace where strings
|
|
|
|
may contain new-lines internally.
|
1999-05-03 09:29:11 +02:00
|
|
|
@end table
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO strings
|
|
|
|
ar(1), nm(1), objdump(1), ranlib(1), readelf(1)
|
|
|
|
and the Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@node strip
|
|
|
|
@chapter strip
|
|
|
|
|
|
|
|
@kindex strip
|
|
|
|
@cindex removing symbols
|
|
|
|
@cindex discarding symbols
|
|
|
|
@cindex symbols, discarding
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@c man title strip discard symbols and other data from object files
|
2001-03-25 22:32:31 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS strip
|
2003-06-12 09:23:31 +02:00
|
|
|
strip [@option{-F} @var{bfdname} |@option{--target=}@var{bfdname}]
|
|
|
|
[@option{-I} @var{bfdname} |@option{--input-target=}@var{bfdname}]
|
|
|
|
[@option{-O} @var{bfdname} |@option{--output-target=}@var{bfdname}]
|
|
|
|
[@option{-s}|@option{--strip-all}]
|
|
|
|
[@option{-S}|@option{-g}|@option{-d}|@option{--strip-debug}]
|
2012-05-08 19:49:36 +02:00
|
|
|
[@option{--strip-dwo}]
|
2017-04-13 15:50:56 +02:00
|
|
|
[@option{-K} @var{symbolname}|@option{--keep-symbol=}@var{symbolname}]
|
|
|
|
[@option{-M}|@option{--merge-notes}][@option{--no-merge-notes}]
|
2003-06-12 09:23:31 +02:00
|
|
|
[@option{-N} @var{symbolname} |@option{--strip-symbol=}@var{symbolname}]
|
2003-11-11 18:50:26 +01:00
|
|
|
[@option{-w}|@option{--wildcard}]
|
2003-06-12 09:23:31 +02:00
|
|
|
[@option{-x}|@option{--discard-all}] [@option{-X} |@option{--discard-locals}]
|
|
|
|
[@option{-R} @var{sectionname} |@option{--remove-section=}@var{sectionname}]
|
objcopy/strip: Add option --remove-relocations=SECTIONPATTERN
The objcopy and strip tools make use of the bfd library to manipulate
the state of the input file (to produce an output file). Within the
input file (for ELF at least), relocations are held within a section,
and so, if the user wanted to remove the relocations, but keep the
section to which the relocations would have been applied, it is tempting
to think that specifying the name of a relocation section to objcopy's
--remove-section option might do what you want, for example:
objcopy --remove-section=.rela.text input.elf output.elf
However, this does not work. The reason is that when the input file is
loaded, relocations are not managed as sections, but are, instead,
loaded as data associated with the section to which the relocations
would be applied. In our example above the relocations in '.rela.text'
are held as data on the section '.text' once 'input.elf' is loaded.
One task that objcopy and strip do is copy the relocations from the
input file to the output file if the section is also being copied from
the input file to the output file.
This commit adds a new command line option for objcopy and strip,
--remove-relocations, which can be used to remove the relocations, while
keeping the section that the relocations would have been applied to, for
example:
objcopy --remove-relocations=.text input.elf output.elf
in this case the section '.text' will appear in both 'input.elf' and
'output.elf', but any relocations in 'input.elf' that apply to '.text'
will not be present in 'output.elf'.
I have also added a special case to the handling of --remove-section
that spots if a user tries to remove a relocation section (currently
this is done by spotting the '.rela.' or '.rel.' prefix) and forwards
the request to --remove-relocations.
As with --remove-section and --only-section the --remove-relocations
option supports the '!' prefix on the section-patterns it takes to allow
for sections to be specifically not matched.
There are tests for all the new functionality.
binutils/ChangeLog:
* doc/binutils.texi (objcopy): Document 'remove-relocations'.
(strip): Likewise.
* objcopy.c (SECTION_CONTEXT_REMOVE_RELOCS): Define.
(enum command_line_switch): Add 'OPTION_REMOVE_RELOCS'.
(struct option strip_options): Add 'remove-relocations'.
(struct option copy_options): Likewise.
(copy_usage): Likewise.
(strip_usage): Likewise.
(handle_remove_relocations_option): New function.
(discard_relocations): New function.
(handle_remove_section_option): New function.
(copy_relocations_in_section): Use discard_relocations.
(strip_main): Use handle_remove_section_option for
'remove-section', and handle 'remove-relocations' option.
(copy_main): Likewise.
* testsuite/binutils-all/objcopy.exp: Run new tests.
* testsuite/binutils-all/remove-relocs-01.d: New file.
* testsuite/binutils-all/remove-relocs-01.s: New file.
* testsuite/binutils-all/remove-relocs-02.d: New file.
* testsuite/binutils-all/remove-relocs-03.d: New file.
* testsuite/binutils-all/remove-relocs-04.d: New file.
* testsuite/binutils-all/remove-relocs-05.d: New file.
* testsuite/binutils-all/remove-relocs-06.d: New file.
2015-08-21 21:08:26 +02:00
|
|
|
[@option{--remove-relocations=}@var{sectionpattern}]
|
2003-06-12 09:23:31 +02:00
|
|
|
[@option{-o} @var{file}] [@option{-p}|@option{--preserve-dates}]
|
2012-04-25 19:50:14 +02:00
|
|
|
[@option{-D}|@option{--enable-deterministic-archives}]
|
2013-01-07 18:40:59 +01:00
|
|
|
[@option{-U}|@option{--disable-deterministic-archives}]
|
2005-11-15 09:33:38 +01:00
|
|
|
[@option{--keep-file-symbols}]
|
2003-06-26 10:14:10 +02:00
|
|
|
[@option{--only-keep-debug}]
|
2003-03-24 17:11:46 +01:00
|
|
|
[@option{-v} |@option{--verbose}] [@option{-V}|@option{--version}]
|
|
|
|
[@option{--help}] [@option{--info}]
|
1999-05-03 09:29:11 +02:00
|
|
|
@var{objfile}@dots{}
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION strip
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@sc{gnu} @command{strip} discards all symbols from object files
|
1999-05-03 09:29:11 +02:00
|
|
|
@var{objfile}. The list of object files may include archives.
|
|
|
|
At least one object file must be given.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{strip} modifies the files named in its argument,
|
1999-05-03 09:29:11 +02:00
|
|
|
rather than writing modified copies under different names.
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS strip
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @env
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -F @var{bfdname}
|
|
|
|
@itemx --target=@var{bfdname}
|
|
|
|
Treat the original @var{objfile} as a file with the object
|
|
|
|
code format @var{bfdname}, and rewrite it in the same format.
|
|
|
|
@xref{Target Selection}, for more information.
|
|
|
|
|
|
|
|
@item --help
|
2001-08-01 17:54:41 +02:00
|
|
|
Show a summary of the options to @command{strip} and exit.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2003-03-24 17:11:46 +01:00
|
|
|
@item --info
|
|
|
|
Display a list showing all architectures and object formats available.
|
|
|
|
|
2003-02-21 11:30:35 +01:00
|
|
|
@item -I @var{bfdname}
|
1999-05-03 09:29:11 +02:00
|
|
|
@itemx --input-target=@var{bfdname}
|
|
|
|
Treat the original @var{objfile} as a file with the object
|
|
|
|
code format @var{bfdname}.
|
|
|
|
@xref{Target Selection}, for more information.
|
|
|
|
|
|
|
|
@item -O @var{bfdname}
|
|
|
|
@itemx --output-target=@var{bfdname}
|
|
|
|
Replace @var{objfile} with a file in the output format @var{bfdname}.
|
|
|
|
@xref{Target Selection}, for more information.
|
|
|
|
|
|
|
|
@item -R @var{sectionname}
|
|
|
|
@itemx --remove-section=@var{sectionname}
|
2014-12-23 21:28:16 +01:00
|
|
|
Remove any section named @var{sectionname} from the output file, in
|
|
|
|
addition to whatever sections would otherwise be removed. This
|
1999-05-03 09:29:11 +02:00
|
|
|
option may be given more than once. Note that using this option
|
2013-02-15 10:32:31 +01:00
|
|
|
inappropriately may make the output file unusable. The wildcard
|
|
|
|
character @samp{*} may be given at the end of @var{sectionname}. If
|
|
|
|
so, then any section starting with @var{sectionname} will be removed.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2015-08-24 14:02:39 +02:00
|
|
|
If the first character of @var{sectionpattern} is the exclamation
|
|
|
|
point (!) then matching sections will not be removed even if an
|
|
|
|
earlier use of @option{--remove-section} on the same command line
|
|
|
|
would otherwise remove it. For example:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
--remove-section=.text.* --remove-section=!.text.foo
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
will remove all sections matching the pattern '.text.*', but will not
|
|
|
|
remove the section '.text.foo'.
|
|
|
|
|
objcopy/strip: Add option --remove-relocations=SECTIONPATTERN
The objcopy and strip tools make use of the bfd library to manipulate
the state of the input file (to produce an output file). Within the
input file (for ELF at least), relocations are held within a section,
and so, if the user wanted to remove the relocations, but keep the
section to which the relocations would have been applied, it is tempting
to think that specifying the name of a relocation section to objcopy's
--remove-section option might do what you want, for example:
objcopy --remove-section=.rela.text input.elf output.elf
However, this does not work. The reason is that when the input file is
loaded, relocations are not managed as sections, but are, instead,
loaded as data associated with the section to which the relocations
would be applied. In our example above the relocations in '.rela.text'
are held as data on the section '.text' once 'input.elf' is loaded.
One task that objcopy and strip do is copy the relocations from the
input file to the output file if the section is also being copied from
the input file to the output file.
This commit adds a new command line option for objcopy and strip,
--remove-relocations, which can be used to remove the relocations, while
keeping the section that the relocations would have been applied to, for
example:
objcopy --remove-relocations=.text input.elf output.elf
in this case the section '.text' will appear in both 'input.elf' and
'output.elf', but any relocations in 'input.elf' that apply to '.text'
will not be present in 'output.elf'.
I have also added a special case to the handling of --remove-section
that spots if a user tries to remove a relocation section (currently
this is done by spotting the '.rela.' or '.rel.' prefix) and forwards
the request to --remove-relocations.
As with --remove-section and --only-section the --remove-relocations
option supports the '!' prefix on the section-patterns it takes to allow
for sections to be specifically not matched.
There are tests for all the new functionality.
binutils/ChangeLog:
* doc/binutils.texi (objcopy): Document 'remove-relocations'.
(strip): Likewise.
* objcopy.c (SECTION_CONTEXT_REMOVE_RELOCS): Define.
(enum command_line_switch): Add 'OPTION_REMOVE_RELOCS'.
(struct option strip_options): Add 'remove-relocations'.
(struct option copy_options): Likewise.
(copy_usage): Likewise.
(strip_usage): Likewise.
(handle_remove_relocations_option): New function.
(discard_relocations): New function.
(handle_remove_section_option): New function.
(copy_relocations_in_section): Use discard_relocations.
(strip_main): Use handle_remove_section_option for
'remove-section', and handle 'remove-relocations' option.
(copy_main): Likewise.
* testsuite/binutils-all/objcopy.exp: Run new tests.
* testsuite/binutils-all/remove-relocs-01.d: New file.
* testsuite/binutils-all/remove-relocs-01.s: New file.
* testsuite/binutils-all/remove-relocs-02.d: New file.
* testsuite/binutils-all/remove-relocs-03.d: New file.
* testsuite/binutils-all/remove-relocs-04.d: New file.
* testsuite/binutils-all/remove-relocs-05.d: New file.
* testsuite/binutils-all/remove-relocs-06.d: New file.
2015-08-21 21:08:26 +02:00
|
|
|
@item --remove-relocations=@var{sectionpattern}
|
|
|
|
Remove relocations from the output file for any section matching
|
|
|
|
@var{sectionpattern}. This option may be given more than once. Note
|
|
|
|
that using this option inappropriately may make the output file
|
|
|
|
unusable. Wildcard characters are accepted in @var{sectionpattern}.
|
|
|
|
For example:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
--remove-relocations=.text.*
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
will remove the relocations for all sections matching the patter
|
|
|
|
'.text.*'.
|
|
|
|
|
|
|
|
If the first character of @var{sectionpattern} is the exclamation
|
|
|
|
point (!) then matching sections will not have their relocation
|
|
|
|
removed even if an earlier use of @option{--remove-relocations} on the
|
|
|
|
same command line would otherwise cause the relocations to be removed.
|
|
|
|
For example:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
--remove-relocations=.text.* --remove-relocations=!.text.foo
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
will remove all relocations for sections matching the pattern
|
|
|
|
'.text.*', but will not remove relocations for the section
|
|
|
|
'.text.foo'.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -s
|
|
|
|
@itemx --strip-all
|
|
|
|
Remove all symbols.
|
|
|
|
|
|
|
|
@item -g
|
|
|
|
@itemx -S
|
2002-01-25 16:37:04 +01:00
|
|
|
@itemx -d
|
1999-05-03 09:29:11 +02:00
|
|
|
@itemx --strip-debug
|
|
|
|
Remove debugging symbols only.
|
2012-05-08 19:49:36 +02:00
|
|
|
|
|
|
|
@item --strip-dwo
|
|
|
|
Remove the contents of all DWARF .dwo sections, leaving the
|
|
|
|
remaining debugging sections and all symbols intact.
|
|
|
|
See the description of this option in the @command{objcopy} section
|
|
|
|
for more information.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --strip-unneeded
|
|
|
|
Remove all symbols that are not needed for relocation processing.
|
|
|
|
|
|
|
|
@item -K @var{symbolname}
|
|
|
|
@itemx --keep-symbol=@var{symbolname}
|
2005-04-25 11:23:24 +02:00
|
|
|
When stripping symbols, keep symbol @var{symbolname} even if it would
|
|
|
|
normally be stripped. This option may be given more than once.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2017-04-13 15:50:56 +02:00
|
|
|
@item -M
|
|
|
|
@itemx --merge-notes
|
|
|
|
@itemx --no-merge-notes
|
|
|
|
For ELF files, attempt (or do not attempt) to reduce the size of any
|
|
|
|
SHT_NOTE type sections by removing duplicate notes. The default is to
|
2019-04-24 18:44:31 +02:00
|
|
|
attempt this reduction unless stripping debug or DWO information.
|
2017-04-13 15:50:56 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -N @var{symbolname}
|
|
|
|
@itemx --strip-symbol=@var{symbolname}
|
|
|
|
Remove symbol @var{symbolname} from the source file. This option may be
|
|
|
|
given more than once, and may be combined with strip options other than
|
2001-08-01 17:54:41 +02:00
|
|
|
@option{-K}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -o @var{file}
|
|
|
|
Put the stripped output in @var{file}, rather than replacing the
|
|
|
|
existing file. When this argument is used, only one @var{objfile}
|
|
|
|
argument may be specified.
|
|
|
|
|
|
|
|
@item -p
|
|
|
|
@itemx --preserve-dates
|
|
|
|
Preserve the access and modification dates of the file.
|
|
|
|
|
2012-04-25 19:50:14 +02:00
|
|
|
@item -D
|
|
|
|
@itemx --enable-deterministic-archives
|
2013-01-07 18:40:59 +01:00
|
|
|
@cindex deterministic archives
|
|
|
|
@kindex --enable-deterministic-archives
|
2012-04-25 19:50:14 +02:00
|
|
|
Operate in @emph{deterministic} mode. When copying archive members
|
|
|
|
and writing the archive index, use zero for UIDs, GIDs, timestamps,
|
|
|
|
and use consistent file modes for all files.
|
|
|
|
|
2013-01-07 18:40:59 +01:00
|
|
|
If @file{binutils} was configured with
|
|
|
|
@option{--enable-deterministic-archives}, then this mode is on by default.
|
|
|
|
It can be disabled with the @samp{-U} option, below.
|
|
|
|
|
|
|
|
@item -U
|
|
|
|
@itemx --disable-deterministic-archives
|
|
|
|
@cindex deterministic archives
|
|
|
|
@kindex --enable-deterministic-archives
|
|
|
|
Do @emph{not} operate in @emph{deterministic} mode. This is the
|
|
|
|
inverse of the @option{-D} option, above: when copying archive members
|
|
|
|
and writing the archive index, use their actual UID, GID, timestamp,
|
|
|
|
and file mode values.
|
|
|
|
|
|
|
|
This is the default unless @file{binutils} was configured with
|
|
|
|
@option{--enable-deterministic-archives}.
|
|
|
|
|
2003-11-11 18:50:26 +01:00
|
|
|
@item -w
|
|
|
|
@itemx --wildcard
|
|
|
|
Permit regular expressions in @var{symbolname}s used in other command
|
|
|
|
line options. The question mark (?), asterisk (*), backslash (\) and
|
|
|
|
square brackets ([]) operators can be used anywhere in the symbol
|
|
|
|
name. If the first character of the symbol name is the exclamation
|
|
|
|
point (!) then the sense of the switch is reversed for that symbol.
|
|
|
|
For example:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
-w -K !foo -K fo*
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
would cause strip to only keep symbols that start with the letters
|
|
|
|
``fo'', but to discard the symbol ``foo''.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -x
|
|
|
|
@itemx --discard-all
|
|
|
|
Remove non-global symbols.
|
|
|
|
|
|
|
|
@item -X
|
|
|
|
@itemx --discard-locals
|
|
|
|
Remove compiler-generated local symbols.
|
|
|
|
(These usually start with @samp{L} or @samp{.}.)
|
|
|
|
|
2005-11-15 09:33:38 +01:00
|
|
|
@item --keep-file-symbols
|
|
|
|
When stripping a file, perhaps with @option{--strip-debug} or
|
|
|
|
@option{--strip-unneeded}, retain any symbols specifying source file names,
|
|
|
|
which would otherwise get stripped.
|
|
|
|
|
2003-06-26 10:14:10 +02:00
|
|
|
@item --only-keep-debug
|
2015-08-05 17:16:39 +02:00
|
|
|
Strip a file, emptying the contents of any sections that would not be
|
2007-06-29 02:34:14 +02:00
|
|
|
stripped by @option{--strip-debug} and leaving the debugging sections
|
2015-08-05 17:16:39 +02:00
|
|
|
intact. In ELF files, this preserves all the note sections in the
|
|
|
|
output as well.
|
|
|
|
|
|
|
|
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.
|
2003-06-26 10:14:10 +02:00
|
|
|
|
|
|
|
The intention is that this option will be used in conjunction with
|
|
|
|
@option{--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:
|
|
|
|
|
|
|
|
@enumerate
|
2018-06-26 13:56:23 +02:00
|
|
|
@item Link the executable as normal. Assuming that it is called
|
2003-06-26 10:14:10 +02:00
|
|
|
@code{foo} then...
|
|
|
|
@item Run @code{objcopy --only-keep-debug foo foo.dbg} to
|
|
|
|
create a file containing the debugging info.
|
|
|
|
@item Run @code{objcopy --strip-debug foo} to create a
|
|
|
|
stripped executable.
|
|
|
|
@item Run @code{objcopy --add-gnu-debuglink=foo.dbg foo}
|
|
|
|
to add a link to the debugging info into the stripped executable.
|
|
|
|
@end enumerate
|
|
|
|
|
2007-10-16 21:01:47 +02:00
|
|
|
Note---the choice of @code{.dbg} as an extension for the debug info
|
2003-06-26 10:14:10 +02:00
|
|
|
file is arbitrary. Also the @code{--only-keep-debug} step is
|
|
|
|
optional. You could instead do this:
|
|
|
|
|
|
|
|
@enumerate
|
|
|
|
@item Link the executable as normal.
|
2007-10-16 21:01:47 +02:00
|
|
|
@item Copy @code{foo} to @code{foo.full}
|
2003-06-26 10:14:10 +02:00
|
|
|
@item Run @code{strip --strip-debug foo}
|
|
|
|
@item Run @code{objcopy --add-gnu-debuglink=foo.full foo}
|
|
|
|
@end enumerate
|
|
|
|
|
2007-10-16 21:01:47 +02:00
|
|
|
i.e., the file pointed to by the @option{--add-gnu-debuglink} can be the
|
2003-06-26 10:14:10 +02:00
|
|
|
full executable. It does not have to be a file created by the
|
|
|
|
@option{--only-keep-debug} switch.
|
|
|
|
|
2007-10-16 21:01:47 +02:00
|
|
|
Note---this switch is only intended for use on fully linked files. It
|
2006-09-05 10:22:27 +02:00
|
|
|
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.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -V
|
|
|
|
@itemx --version
|
2001-08-01 17:54:41 +02:00
|
|
|
Show the version number for @command{strip}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -v
|
|
|
|
@itemx --verbose
|
|
|
|
Verbose output: list all object files modified. In the case of
|
|
|
|
archives, @samp{strip -v} lists all members of the archive.
|
|
|
|
@end table
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO strip
|
|
|
|
the Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
2013-01-07 13:11:13 +01:00
|
|
|
@node c++filt, addr2line, strip, Top
|
1999-05-03 09:29:11 +02:00
|
|
|
@chapter c++filt
|
|
|
|
|
|
|
|
@kindex c++filt
|
|
|
|
@cindex demangling C++ symbols
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@c man title cxxfilt demangle C++ and Java symbols
|
2001-03-25 22:32:31 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS cxxfilt
|
2012-02-29 11:44:10 +01:00
|
|
|
c++filt [@option{-_}|@option{--strip-underscore}]
|
|
|
|
[@option{-n}|@option{--no-strip-underscore}]
|
2003-11-23 02:10:45 +01:00
|
|
|
[@option{-p}|@option{--no-params}]
|
2005-10-11 18:33:16 +02:00
|
|
|
[@option{-t}|@option{--types}]
|
2005-10-04 13:03:38 +02:00
|
|
|
[@option{-i}|@option{--no-verbose}]
|
2018-12-07 12:32:55 +01:00
|
|
|
[@option{-r}|@option{--no-recurse-limit}]
|
|
|
|
[@option{-R}|@option{--recurse-limit}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-s} @var{format}|@option{--format=}@var{format}]
|
|
|
|
[@option{--help}] [@option{--version}] [@var{symbol}@dots{}]
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION cxxfilt
|
|
|
|
|
1999-08-08 20:18:11 +02:00
|
|
|
@kindex cxxfilt
|
2005-10-11 18:33:16 +02:00
|
|
|
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 @dfn{mangling}. The
|
|
|
|
@command{c++filt}
|
2007-06-29 02:34:14 +02:00
|
|
|
@footnote{MS-DOS does not allow @kbd{+} characters in file names, so on
|
2005-01-11 12:58:49 +01:00
|
|
|
MS-DOS this program is named @command{CXXFILT}.}
|
1999-08-08 20:18:11 +02:00
|
|
|
program does the inverse mapping: it decodes (@dfn{demangles}) low-level
|
2005-10-11 18:33:16 +02:00
|
|
|
names into user-level names so that they can be read.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
Every alphanumeric word (consisting of letters, digits, underscores,
|
2005-10-04 13:03:38 +02:00
|
|
|
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
|
2005-10-11 18:33:16 +02:00
|
|
|
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 @command{c++filt} and see the same source file
|
|
|
|
containing demangled names.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2005-10-11 18:33:16 +02:00
|
|
|
You can also use @command{c++filt} to decipher individual symbols by
|
|
|
|
passing them on the command line:
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@example
|
|
|
|
c++filt @var{symbol}
|
|
|
|
@end example
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
If no @var{symbol} arguments are given, @command{c++filt} reads symbol
|
2005-10-11 18:33:16 +02:00
|
|
|
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
|
2018-07-02 12:18:24 +02:00
|
|
|
command-line arguments are expected to be just mangled names and no
|
2006-07-24 15:49:50 +02:00
|
|
|
checking is performed to separate them from surrounding text. Thus
|
2005-10-11 18:33:16 +02:00
|
|
|
for example:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
c++filt -n _Z1fv
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
will work and demangle the name to ``f()'' whereas:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
c++filt -n _Z1fv,
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
will not work. (Note the extra comma at the end of the mangled
|
|
|
|
name which makes it invalid). This command however will work:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
echo _Z1fv, | c++filt -n
|
|
|
|
@end smallexample
|
|
|
|
|
2007-10-16 21:01:47 +02:00
|
|
|
and will display ``f(),'', i.e., the demangled name followed by a
|
2005-10-11 18:33:16 +02:00
|
|
|
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
|
2007-10-16 21:01:47 +02:00
|
|
|
characters trailing after a mangled name. For example:
|
2005-10-11 18:33:16 +02:00
|
|
|
|
|
|
|
@smallexample
|
|
|
|
.type _Z1fv, @@function
|
|
|
|
@end smallexample
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS cxxfilt
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @env
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -_
|
2012-02-29 11:44:10 +01:00
|
|
|
@itemx --strip-underscore
|
1999-05-03 09:29:11 +02:00
|
|
|
On some systems, both the C and C++ compilers put an underscore in front
|
|
|
|
of every name. For example, the C name @code{foo} gets the low-level
|
|
|
|
name @code{_foo}. This option removes the initial underscore. Whether
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{c++filt} removes the underscore by default is target dependent.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -n
|
2012-02-29 11:44:10 +01:00
|
|
|
@itemx --no-strip-underscore
|
1999-05-03 09:29:11 +02:00
|
|
|
Do not remove the initial underscore.
|
|
|
|
|
2003-11-23 02:10:45 +01:00
|
|
|
@item -p
|
|
|
|
@itemx --no-params
|
|
|
|
When demangling the name of a function, do not display the types of
|
|
|
|
the function's parameters.
|
|
|
|
|
2005-10-04 13:03:38 +02:00
|
|
|
@item -t
|
2005-10-11 18:33:16 +02:00
|
|
|
@itemx --types
|
|
|
|
Attempt to demangle types as well as function names. This is disabled
|
|
|
|
by default since mangled types are normally only used internally in
|
2007-10-16 21:01:47 +02:00
|
|
|
the compiler, and they can be confused with non-mangled names. For example,
|
2005-10-11 18:33:16 +02:00
|
|
|
a function called ``a'' treated as a mangled type name would be
|
|
|
|
demangled to ``signed char''.
|
2005-10-04 13:03:38 +02:00
|
|
|
|
|
|
|
@item -i
|
|
|
|
@itemx --no-verbose
|
|
|
|
Do not include implementation details (if any) in the demangled
|
|
|
|
output.
|
|
|
|
|
2018-12-07 12:32:55 +01:00
|
|
|
@item -r
|
|
|
|
@itemx -R
|
|
|
|
@itemx --recurse-limit
|
|
|
|
@itemx --no-recurse-limit
|
|
|
|
@itemx --recursion-limit
|
|
|
|
@itemx --no-recursion-limit
|
|
|
|
Enables or disables a limit on the amount of recursion performed
|
|
|
|
whilst demangling strings. Since the name mangling formats allow for
|
|
|
|
an inifinite level of recursion it is possible to create strings whose
|
|
|
|
decoding will exhaust the amount of stack space available on the host
|
|
|
|
machine, triggering a memory fault. The limit tries to prevent this
|
2018-12-11 13:01:15 +01:00
|
|
|
from happening by restricting recursion to 2048 levels of nesting.
|
2018-12-07 12:32:55 +01:00
|
|
|
|
|
|
|
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 @option{-r} option is a synonym for the
|
|
|
|
@option{--no-recurse-limit} option. The @option{-R} option is a
|
|
|
|
synonym for the @option{--recurse-limit} option.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -s @var{format}
|
|
|
|
@itemx --format=@var{format}
|
2003-02-21 11:30:35 +01:00
|
|
|
@command{c++filt} can decode various methods of mangling, used by
|
|
|
|
different compilers. The argument to this option selects which
|
1999-05-03 09:29:11 +02:00
|
|
|
method it uses:
|
|
|
|
|
|
|
|
@table @code
|
2003-02-21 11:30:35 +01:00
|
|
|
@item auto
|
|
|
|
Automatic selection based on executable (the default method)
|
1999-05-03 09:29:11 +02:00
|
|
|
@item gnu
|
2003-02-21 11:30:35 +01:00
|
|
|
the one used by the @sc{gnu} C++ compiler (g++)
|
1999-05-03 09:29:11 +02:00
|
|
|
@item lucid
|
2003-02-21 11:30:35 +01:00
|
|
|
the one used by the Lucid compiler (lcc)
|
1999-05-03 09:29:11 +02:00
|
|
|
@item arm
|
|
|
|
the one specified by the C++ Annotated Reference Manual
|
|
|
|
@item hp
|
2003-02-21 11:30:35 +01:00
|
|
|
the one used by the HP compiler (aCC)
|
1999-05-03 09:29:11 +02:00
|
|
|
@item edg
|
|
|
|
the one used by the EDG compiler
|
2002-08-14 17:12:07 +02:00
|
|
|
@item gnu-v3
|
2003-02-21 11:30:35 +01:00
|
|
|
the one used by the @sc{gnu} C++ compiler (g++) with the V3 ABI.
|
|
|
|
@item java
|
|
|
|
the one used by the @sc{gnu} Java compiler (gcj)
|
|
|
|
@item gnat
|
|
|
|
the one used by the @sc{gnu} Ada compiler (GNAT).
|
1999-05-03 09:29:11 +02:00
|
|
|
@end table
|
|
|
|
|
|
|
|
@item --help
|
2001-08-01 17:54:41 +02:00
|
|
|
Print a summary of the options to @command{c++filt} and exit.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --version
|
2001-08-01 17:54:41 +02:00
|
|
|
Print the version number of @command{c++filt} and exit.
|
1999-05-03 09:29:11 +02:00
|
|
|
@end table
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO cxxfilt
|
|
|
|
the Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@quotation
|
2001-08-01 17:54:41 +02:00
|
|
|
@emph{Warning:} @command{c++filt} is a new utility, and the details of its
|
1999-05-03 09:29:11 +02:00
|
|
|
user interface are subject to change in future releases. In particular,
|
2006-07-24 15:49:50 +02:00
|
|
|
a command-line option may be required in the future to decode a name
|
2007-06-29 02:34:14 +02:00
|
|
|
passed as an argument on the command line; in other words,
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@example
|
|
|
|
c++filt @var{symbol}
|
|
|
|
@end example
|
|
|
|
|
|
|
|
@noindent
|
|
|
|
may in a future release become
|
|
|
|
|
|
|
|
@example
|
|
|
|
c++filt @var{option} @var{symbol}
|
|
|
|
@end example
|
|
|
|
@end quotation
|
|
|
|
|
|
|
|
@node addr2line
|
|
|
|
@chapter addr2line
|
|
|
|
|
|
|
|
@kindex addr2line
|
|
|
|
@cindex address to file name and line number
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@c man title addr2line convert addresses into file names and line numbers
|
2001-03-25 22:32:31 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS addr2line
|
2009-12-09 13:58:23 +01:00
|
|
|
addr2line [@option{-a}|@option{--addresses}]
|
|
|
|
[@option{-b} @var{bfdname}|@option{--target=}@var{bfdname}]
|
2002-07-23 07:12:57 +02:00
|
|
|
[@option{-C}|@option{--demangle}[=@var{style}]]
|
2018-12-07 12:32:55 +01:00
|
|
|
[@option{-r}|@option{--no-recurse-limit}]
|
|
|
|
[@option{-R}|@option{--recurse-limit}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-e} @var{filename}|@option{--exe=}@var{filename}]
|
|
|
|
[@option{-f}|@option{--functions}] [@option{-s}|@option{--basename}]
|
2005-05-23 19:45:42 +02:00
|
|
|
[@option{-i}|@option{--inlines}]
|
2009-12-10 17:12:33 +01:00
|
|
|
[@option{-p}|@option{--pretty-print}]
|
2006-04-05 18:12:01 +02:00
|
|
|
[@option{-j}|@option{--section=}@var{name}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-H}|@option{--help}] [@option{-V}|@option{--version}]
|
|
|
|
[addr addr @dots{}]
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION addr2line
|
|
|
|
|
2006-04-05 18:12:01 +02:00
|
|
|
@command{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.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2006-04-05 18:12:01 +02:00
|
|
|
The executable or relocatable object to use is specified with the @option{-e}
|
|
|
|
option. The default is the file @file{a.out}. The section in the relocatable
|
|
|
|
object to use is specified with the @option{-j} option.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{addr2line} has two modes of operation.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
In the first, hexadecimal addresses are specified on the command line,
|
2001-08-01 17:54:41 +02:00
|
|
|
and @command{addr2line} displays the file name and line number for each
|
1999-05-03 09:29:11 +02:00
|
|
|
address.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
In the second, @command{addr2line} reads hexadecimal addresses from
|
1999-05-03 09:29:11 +02:00
|
|
|
standard input, and prints the file name and line number for each
|
2001-08-01 17:54:41 +02:00
|
|
|
address on standard output. In this mode, @command{addr2line} may be used
|
1999-05-03 09:29:11 +02:00
|
|
|
in a pipe to convert dynamically chosen addresses.
|
|
|
|
|
2014-07-03 17:30:49 +02:00
|
|
|
The format of the output is @samp{FILENAME:LINENO}. By default
|
|
|
|
each input address generates one line of output.
|
2011-10-13 17:33:34 +02:00
|
|
|
|
2014-07-03 17:30:49 +02:00
|
|
|
Two options can generate additional lines before each
|
|
|
|
@samp{FILENAME:LINENO} line (in that order).
|
|
|
|
|
|
|
|
If the @option{-a} option is used then a line with the input address
|
|
|
|
is displayed.
|
|
|
|
|
|
|
|
If the @option{-f} option is used, then a line with the
|
|
|
|
@samp{FUNCTIONNAME} is displayed. This is the name of the function
|
|
|
|
containing the address.
|
|
|
|
|
|
|
|
One option can generate additional lines after the
|
|
|
|
@samp{FILENAME:LINENO} line.
|
2011-10-13 17:33:34 +02:00
|
|
|
|
|
|
|
If the @option{-i} option is used and the code at the given address is
|
2014-07-03 17:30:49 +02:00
|
|
|
present there because of inlining by the compiler then additional
|
|
|
|
lines are displayed afterwards. One or two extra lines (if the
|
|
|
|
@option{-f} option is used) are displayed for each inlined function.
|
|
|
|
|
|
|
|
Alternatively if the @option{-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
|
|
|
|
@option{-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 @samp{(inlined by)}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
If the file name or function name can not be determined,
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{addr2line} will print two question marks in their place. If the
|
|
|
|
line number can not be determined, @command{addr2line} will print 0.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS addr2line
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
The long and short forms of options, shown here as alternatives, are
|
|
|
|
equivalent.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @env
|
2009-12-09 13:58:23 +01:00
|
|
|
@item -a
|
|
|
|
@itemx --addresses
|
2011-10-13 17:33:34 +02:00
|
|
|
Display the address before the function name, file and line number
|
2009-12-09 13:58:23 +01:00
|
|
|
information. The address is printed with a @samp{0x} prefix to easily
|
|
|
|
identify it.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -b @var{bfdname}
|
|
|
|
@itemx --target=@var{bfdname}
|
|
|
|
@cindex object code format
|
|
|
|
Specify that the object-code format for the object files is
|
|
|
|
@var{bfdname}.
|
|
|
|
|
|
|
|
@item -C
|
2000-07-20 20:02:56 +02:00
|
|
|
@itemx --demangle[=@var{style}]
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex demangling in objdump
|
|
|
|
Decode (@dfn{demangle}) low-level symbol names into user-level names.
|
|
|
|
Besides removing any initial underscore prepended by the system, this
|
2000-07-20 20:02:56 +02:00
|
|
|
makes C++ function names readable. Different compilers have different
|
2007-06-29 02:34:14 +02:00
|
|
|
mangling styles. The optional demangling style argument can be used to
|
|
|
|
choose an appropriate demangling style for your compiler. @xref{c++filt},
|
2000-07-20 20:02:56 +02:00
|
|
|
for more information on demangling.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -e @var{filename}
|
|
|
|
@itemx --exe=@var{filename}
|
|
|
|
Specify the name of the executable for which addresses should be
|
|
|
|
translated. The default file is @file{a.out}.
|
|
|
|
|
|
|
|
@item -f
|
|
|
|
@itemx --functions
|
|
|
|
Display function names as well as file and line number information.
|
|
|
|
|
|
|
|
@item -s
|
|
|
|
@itemx --basenames
|
|
|
|
Display only the base of each file name.
|
2005-05-23 19:45:42 +02:00
|
|
|
|
|
|
|
@item -i
|
|
|
|
@itemx --inlines
|
|
|
|
If the address belongs to a function that was inlined, the source
|
|
|
|
information for all enclosing scopes back to the first non-inlined
|
|
|
|
function will also be printed. For example, if @code{main} inlines
|
|
|
|
@code{callee1} which inlines @code{callee2}, and address is from
|
|
|
|
@code{callee2}, the source information for @code{callee1} and @code{main}
|
|
|
|
will also be printed.
|
2006-04-05 18:12:01 +02:00
|
|
|
|
|
|
|
@item -j
|
|
|
|
@itemx --section
|
|
|
|
Read offsets relative to the specified section instead of absolute addresses.
|
2009-12-10 17:12:33 +01:00
|
|
|
|
|
|
|
@item -p
|
|
|
|
@itemx --pretty-print
|
|
|
|
Make the output more human friendly: each location are printed on one line.
|
|
|
|
If option @option{-i} is specified, lines for all enclosing scopes are
|
|
|
|
prefixed with @samp{(inlined by)}.
|
2018-12-07 12:32:55 +01:00
|
|
|
|
|
|
|
@item -r
|
|
|
|
@itemx -R
|
|
|
|
@itemx --recurse-limit
|
|
|
|
@itemx --no-recurse-limit
|
|
|
|
@itemx --recursion-limit
|
|
|
|
@itemx --no-recursion-limit
|
|
|
|
Enables or disables a limit on the amount of recursion performed
|
|
|
|
whilst demangling strings. Since the name mangling formats allow for
|
|
|
|
an inifinite level of recursion it is possible to create strings whose
|
|
|
|
decoding will exhaust the amount of stack space available on the host
|
|
|
|
machine, triggering a memory fault. The limit tries to prevent this
|
2018-12-11 13:01:15 +01:00
|
|
|
from happening by restricting recursion to 2048 levels of nesting.
|
2018-12-07 12:32:55 +01:00
|
|
|
|
|
|
|
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 @option{-r} option is a synonym for the
|
|
|
|
@option{--no-recurse-limit} option. The @option{-R} option is a
|
|
|
|
synonym for the @option{--recurse-limit} option.
|
|
|
|
|
|
|
|
Note this option is only effective if the @option{-C} or
|
|
|
|
@option{--demangle} option has been enabled.
|
|
|
|
|
2000-07-21 02:09:48 +02:00
|
|
|
@end table
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO addr2line
|
|
|
|
Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
2007-06-19 15:24:33 +02:00
|
|
|
@node windmc
|
|
|
|
@chapter windmc
|
|
|
|
|
|
|
|
@command{windmc} may be used to generator Windows message resources.
|
|
|
|
|
|
|
|
@quotation
|
|
|
|
@emph{Warning:} @command{windmc} is not always built as part of the binary
|
|
|
|
utilities, since it is only useful for Windows targets.
|
|
|
|
@end quotation
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@c man title windmc generates Windows message resources
|
2007-06-19 15:24:33 +02:00
|
|
|
|
|
|
|
@smallexample
|
2010-02-23 14:01:48 +01:00
|
|
|
@c man begin SYNOPSIS windmc
|
2007-06-19 15:24:33 +02:00
|
|
|
windmc [options] input-file
|
|
|
|
@c man end
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
@c man begin DESCRIPTION windmc
|
|
|
|
|
|
|
|
@command{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:
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item h
|
|
|
|
A C header file containing the message definitions.
|
|
|
|
|
|
|
|
@item rc
|
|
|
|
A resource file compilable by the @command{windres} tool.
|
|
|
|
|
|
|
|
@item bin
|
|
|
|
One or more binary files containing the resource data for a specific
|
|
|
|
message language.
|
|
|
|
|
|
|
|
@item dbg
|
|
|
|
A C include file that maps message id's to their symbolic name.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
The exact description of these different formats is available in
|
|
|
|
documentation from Microsoft.
|
|
|
|
|
|
|
|
When @command{windmc} converts from the @code{mc} format to the @code{bin}
|
|
|
|
format, @code{rc}, @code{h}, and optional @code{dbg} it is acting like the
|
|
|
|
Windows Message Compiler.
|
|
|
|
|
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS windmc
|
|
|
|
|
|
|
|
@table @env
|
|
|
|
@item -a
|
|
|
|
@itemx --ascii_in
|
2010-02-23 14:01:48 +01:00
|
|
|
Specifies that the input file specified is ASCII. This is the default
|
2007-06-19 15:24:33 +02:00
|
|
|
behaviour.
|
|
|
|
|
|
|
|
@item -A
|
|
|
|
@itemx --ascii_out
|
2010-02-23 14:01:48 +01:00
|
|
|
Specifies that messages in the output @code{bin} files should be in ASCII
|
2007-06-19 15:24:33 +02:00
|
|
|
format.
|
|
|
|
|
|
|
|
@item -b
|
|
|
|
@itemx --binprefix
|
|
|
|
Specifies that @code{bin} filenames should have to be prefixed by the
|
|
|
|
basename of the source file.
|
|
|
|
|
|
|
|
@item -c
|
|
|
|
@itemx --customflag
|
|
|
|
Sets the customer bit in all message id's.
|
|
|
|
|
|
|
|
@item -C @var{codepage}
|
|
|
|
@itemx --codepage_in @var{codepage}
|
|
|
|
Sets the default codepage to be used to convert input file to UTF16. The
|
|
|
|
default is ocdepage 1252.
|
|
|
|
|
|
|
|
@item -d
|
|
|
|
@itemx --decimal_values
|
|
|
|
Outputs the constants in the header file in decimal. Default is using
|
|
|
|
hexadecimal output.
|
|
|
|
|
|
|
|
@item -e @var{ext}
|
|
|
|
@itemx --extension @var{ext}
|
|
|
|
The extension for the header file. The default is .h extension.
|
|
|
|
|
|
|
|
@item -F @var{target}
|
|
|
|
@itemx --target @var{target}
|
|
|
|
Specify the BFD format to use for a bin file as output. This
|
|
|
|
is a BFD target name; you can use the @option{--help} option to see a list
|
|
|
|
of supported targets. Normally @command{windmc} will use the default
|
|
|
|
format, which is the first one listed by the @option{--help} option.
|
|
|
|
@ifclear man
|
|
|
|
@ref{Target Selection}.
|
|
|
|
@end ifclear
|
|
|
|
|
|
|
|
@item -h @var{path}
|
|
|
|
@itemx --headerdir @var{path}
|
|
|
|
The target directory of the generated header file. The default is the
|
|
|
|
current directory.
|
|
|
|
|
|
|
|
@item -H
|
|
|
|
@itemx --help
|
2018-07-02 12:18:24 +02:00
|
|
|
Displays a list of command-line options and then exits.
|
2007-06-19 15:24:33 +02:00
|
|
|
|
|
|
|
@item -m @var{characters}
|
|
|
|
@itemx --maxlength @var{characters}
|
|
|
|
Instructs @command{windmc} to generate a warning if the length
|
|
|
|
of any message exceeds the number specified.
|
|
|
|
|
|
|
|
@item -n
|
|
|
|
@itemx --nullterminate
|
|
|
|
Terminate message text in @code{bin} files by zero. By default they are
|
|
|
|
terminated by CR/LF.
|
|
|
|
|
|
|
|
@item -o
|
|
|
|
@itemx --hresult_use
|
|
|
|
Not yet implemented. Instructs @code{windmc} to generate an OLE2 header
|
|
|
|
file, using HRESULT definitions. Status codes are used if the flag is not
|
|
|
|
specified.
|
|
|
|
|
|
|
|
@item -O @var{codepage}
|
|
|
|
@itemx --codepage_out @var{codepage}
|
|
|
|
Sets the default codepage to be used to output text files. The default
|
|
|
|
is ocdepage 1252.
|
|
|
|
|
|
|
|
@item -r @var{path}
|
|
|
|
@itemx --rcdir @var{path}
|
|
|
|
The target directory for the generated @code{rc} script and the generated
|
|
|
|
@code{bin} files that the resource compiler script includes. The default
|
|
|
|
is the current directory.
|
|
|
|
|
|
|
|
@item -u
|
|
|
|
@itemx --unicode_in
|
|
|
|
Specifies that the input file is UTF16.
|
|
|
|
|
|
|
|
@item -U
|
|
|
|
@itemx --unicode_out
|
|
|
|
Specifies that messages in the output @code{bin} file should be in UTF16
|
|
|
|
format. This is the default behaviour.
|
|
|
|
|
|
|
|
@item -v
|
|
|
|
@item --verbose
|
2007-08-10 09:12:37 +02:00
|
|
|
Enable verbose mode.
|
2007-06-19 15:24:33 +02:00
|
|
|
|
|
|
|
@item -V
|
|
|
|
@item --version
|
2007-08-10 09:12:37 +02:00
|
|
|
Prints the version number for @command{windmc}.
|
2007-06-19 15:24:33 +02:00
|
|
|
|
|
|
|
@item -x @var{path}
|
|
|
|
@itemx --xdgb @var{path}
|
|
|
|
The path of the @code{dbg} C include file that maps message id's to the
|
|
|
|
symbolic name. No such file is generated without specifying the switch.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO windmc
|
|
|
|
the Info entries for @file{binutils}.
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@node windres
|
|
|
|
@chapter windres
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{windres} may be used to manipulate Windows resources.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@quotation
|
2001-08-01 17:54:41 +02:00
|
|
|
@emph{Warning:} @command{windres} is not always built as part of the binary
|
1999-05-03 09:29:11 +02:00
|
|
|
utilities, since it is only useful for Windows targets.
|
|
|
|
@end quotation
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@c man title windres manipulate Windows resources
|
2001-03-25 22:32:31 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS windres
|
1999-05-03 09:29:11 +02:00
|
|
|
windres [options] [input-file] [output-file]
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION windres
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{windres} reads resources from an input file and copies them into
|
1999-05-03 09:29:11 +02:00
|
|
|
an output file. Either file may be in one of three formats:
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item rc
|
|
|
|
A text format read by the Resource Compiler.
|
|
|
|
|
|
|
|
@item res
|
|
|
|
A binary format generated by the Resource Compiler.
|
|
|
|
|
|
|
|
@item coff
|
|
|
|
A COFF object or executable.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
The exact description of these different formats is available in
|
|
|
|
documentation from Microsoft.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
When @command{windres} converts from the @code{rc} format to the @code{res}
|
1999-05-03 09:29:11 +02:00
|
|
|
format, it is acting like the Windows Resource Compiler. When
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{windres} converts from the @code{res} format to the @code{coff}
|
1999-05-03 09:29:11 +02:00
|
|
|
format, it is acting like the Windows @code{CVTRES} program.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
When @command{windres} generates an @code{rc} file, the output is similar
|
1999-05-03 09:29:11 +02:00
|
|
|
but not identical to the format expected for the input. When an input
|
|
|
|
@code{rc} file refers to an external filename, an output @code{rc} file
|
|
|
|
will instead include the file contents.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
If the input or output format is not specified, @command{windres} will
|
1999-05-03 09:29:11 +02:00
|
|
|
guess based on the file name, or, for the input file, the file contents.
|
|
|
|
A file with an extension of @file{.rc} will be treated as an @code{rc}
|
|
|
|
file, a file with an extension of @file{.res} will be treated as a
|
|
|
|
@code{res} file, and a file with an extension of @file{.o} or
|
|
|
|
@file{.exe} will be treated as a @code{coff} file.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
If no output file is specified, @command{windres} will print the resources
|
1999-05-03 09:29:11 +02:00
|
|
|
in @code{rc} format to standard output.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
The normal use is for you to write an @code{rc} file, use @command{windres}
|
1999-05-03 09:29:11 +02:00
|
|
|
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
|
|
|
|
@code{rc} file available to Windows.
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS windres
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @env
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -i @var{filename}
|
|
|
|
@itemx --input @var{filename}
|
|
|
|
The name of the input file. If this option is not used, then
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{windres} will use the first non-option argument as the input file
|
|
|
|
name. If there are no non-option arguments, then @command{windres} will
|
|
|
|
read from standard input. @command{windres} can not read a COFF file from
|
2003-04-24 09:58:49 +02:00
|
|
|
standard input.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -o @var{filename}
|
|
|
|
@itemx --output @var{filename}
|
|
|
|
The name of the output file. If this option is not used, then
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{windres} will use the first non-option argument, after any used
|
1999-05-03 09:29:11 +02:00
|
|
|
for the input file name, as the output file name. If there is no
|
2001-08-01 17:54:41 +02:00
|
|
|
non-option argument, then @command{windres} will write to standard output.
|
2003-04-24 09:58:49 +02:00
|
|
|
@command{windres} can not write a COFF file to standard output. Note,
|
2006-07-24 15:49:50 +02:00
|
|
|
for compatibility with @command{rc} the option @option{-fo} is also
|
2003-04-24 09:58:49 +02:00
|
|
|
accepted, but its use is not recommended.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2003-04-22 19:31:08 +02:00
|
|
|
@item -J @var{format}
|
1999-05-03 09:29:11 +02:00
|
|
|
@itemx --input-format @var{format}
|
|
|
|
The input format to read. @var{format} may be @samp{res}, @samp{rc}, or
|
2001-08-01 17:54:41 +02:00
|
|
|
@samp{coff}. If no input format is specified, @command{windres} will
|
1999-05-03 09:29:11 +02:00
|
|
|
guess, as described above.
|
|
|
|
|
|
|
|
@item -O @var{format}
|
|
|
|
@itemx --output-format @var{format}
|
|
|
|
The output format to generate. @var{format} may be @samp{res},
|
|
|
|
@samp{rc}, or @samp{coff}. If no output format is specified,
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{windres} will guess, as described above.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -F @var{target}
|
|
|
|
@itemx --target @var{target}
|
|
|
|
Specify the BFD format to use for a COFF file as input or output. This
|
2001-08-01 17:54:41 +02:00
|
|
|
is a BFD target name; you can use the @option{--help} option to see a list
|
|
|
|
of supported targets. Normally @command{windres} will use the default
|
|
|
|
format, which is the first one listed by the @option{--help} option.
|
|
|
|
@ifclear man
|
1999-05-03 09:29:11 +02:00
|
|
|
@ref{Target Selection}.
|
2001-08-01 17:54:41 +02:00
|
|
|
@end ifclear
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --preprocessor @var{program}
|
2001-08-01 17:54:41 +02:00
|
|
|
When @command{windres} reads an @code{rc} file, it runs it through the C
|
1999-05-03 09:29:11 +02:00
|
|
|
preprocessor first. This option may be used to specify the preprocessor
|
|
|
|
to use, including any leading arguments. The default preprocessor
|
|
|
|
argument is @code{gcc -E -xc-header -DRC_INVOKED}.
|
|
|
|
|
2011-04-13 09:50:15 +02:00
|
|
|
@item --preprocessor-arg @var{option}
|
|
|
|
When @command{windres} reads an @code{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.
|
|
|
|
|
2003-04-22 19:31:08 +02:00
|
|
|
@item -I @var{directory}
|
|
|
|
@itemx --include-dir @var{directory}
|
1999-05-03 09:29:11 +02:00
|
|
|
Specify an include directory to use when reading an @code{rc} file.
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{windres} will pass this to the preprocessor as an @option{-I}
|
|
|
|
option. @command{windres} will also search this directory when looking for
|
2003-04-22 19:31:08 +02:00
|
|
|
files named in the @code{rc} file. If the argument passed to this command
|
2007-06-29 02:34:14 +02:00
|
|
|
matches any of the supported @var{formats} (as described in the @option{-J}
|
2003-04-22 19:31:08 +02:00
|
|
|
option), it will issue a deprecation warning, and behave just like the
|
|
|
|
@option{-J} option. New programs should not use this behaviour. If a
|
|
|
|
directory happens to match a @var{format}, simple prefix it with @samp{./}
|
|
|
|
to disable the backward compatibility.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
1999-05-25 14:10:27 +02:00
|
|
|
@item -D @var{target}
|
1999-09-09 18:01:34 +02:00
|
|
|
@itemx --define @var{sym}[=@var{val}]
|
2001-08-01 17:54:41 +02:00
|
|
|
Specify a @option{-D} option to pass to the preprocessor when reading an
|
1999-05-03 09:29:11 +02:00
|
|
|
@code{rc} file.
|
|
|
|
|
2003-04-03 15:40:51 +02:00
|
|
|
@item -U @var{target}
|
|
|
|
@itemx --undefine @var{sym}
|
|
|
|
Specify a @option{-U} option to pass to the preprocessor when reading an
|
|
|
|
@code{rc} file.
|
|
|
|
|
2003-04-02 01:09:29 +02:00
|
|
|
@item -r
|
|
|
|
Ignored for compatibility with rc.
|
|
|
|
|
1999-05-25 14:10:27 +02:00
|
|
|
@item -v
|
|
|
|
Enable verbose mode. This tells you what the preprocessor is if you
|
|
|
|
didn't specify one.
|
|
|
|
|
2007-06-19 13:29:05 +02:00
|
|
|
@item -c @var{val}
|
|
|
|
@item --codepage @var{val}
|
|
|
|
Specify the default codepage to use when reading an @code{rc} file.
|
|
|
|
@var{val} should be a hexadecimal prefixed by @samp{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.
|
|
|
|
|
2003-04-05 10:21:47 +02:00
|
|
|
@item -l @var{val}
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --language @var{val}
|
|
|
|
Specify the default language to use when reading an @code{rc} file.
|
|
|
|
@var{val} should be a hexadecimal language code. The low eight bits are
|
|
|
|
the language, and the high eight bits are the sublanguage.
|
|
|
|
|
2000-01-07 23:33:48 +01:00
|
|
|
@item --use-temp-file
|
|
|
|
Use a temporary file to instead of using popen to read the output of
|
2007-06-29 02:34:14 +02:00
|
|
|
the preprocessor. Use this option if the popen implementation is buggy
|
|
|
|
on the host (eg., certain non-English language versions of Windows 95 and
|
2000-01-07 23:33:48 +01:00
|
|
|
Windows 98 are known to have buggy popen where the output will instead
|
|
|
|
go the console).
|
|
|
|
|
|
|
|
@item --no-use-temp-file
|
|
|
|
Use popen, not a temporary file, to read the output of the preprocessor.
|
|
|
|
This is the default behaviour.
|
|
|
|
|
2003-04-05 10:21:47 +02:00
|
|
|
@item -h
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --help
|
|
|
|
Prints a usage summary.
|
|
|
|
|
2003-04-05 10:21:47 +02:00
|
|
|
@item -V
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --version
|
2001-08-01 17:54:41 +02:00
|
|
|
Prints the version number for @command{windres}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --yydebug
|
2001-08-01 17:54:41 +02:00
|
|
|
If @command{windres} is compiled with @code{YYDEBUG} defined as @code{1},
|
1999-05-03 09:29:11 +02:00
|
|
|
this will turn on parser debugging.
|
|
|
|
@end table
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO windres
|
|
|
|
the Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@node dlltool
|
2004-12-06 22:20:50 +01:00
|
|
|
@chapter dlltool
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex DLL
|
|
|
|
@kindex dlltool
|
|
|
|
|
2004-12-06 22:20:50 +01:00
|
|
|
@command{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
|
|
|
|
@file{.def} file or scanning the @file{.a} and @file{.o} files which
|
|
|
|
will be in the DLL. A @file{.o} file can contain information in
|
|
|
|
special @samp{.drectve} sections with export information.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@quotation
|
2004-12-06 22:20:50 +01:00
|
|
|
@emph{Note:} @command{dlltool} is not always built as part of the
|
|
|
|
binary utilities, since it is only useful for those targets which
|
|
|
|
support DLLs.
|
1999-05-03 09:29:11 +02:00
|
|
|
@end quotation
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@c man title dlltool create files needed to build and use DLLs
|
2001-03-25 22:32:31 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS dlltool
|
2001-08-01 17:54:41 +02:00
|
|
|
dlltool [@option{-d}|@option{--input-def} @var{def-file-name}]
|
|
|
|
[@option{-b}|@option{--base-file} @var{base-file-name}]
|
|
|
|
[@option{-e}|@option{--output-exp} @var{exports-file-name}]
|
|
|
|
[@option{-z}|@option{--output-def} @var{def-file-name}]
|
2007-06-29 02:34:14 +02:00
|
|
|
[@option{-l}|@option{--output-lib} @var{library-file-name}]
|
2009-09-04 03:22:19 +02:00
|
|
|
[@option{-y}|@option{--output-delaylib} @var{library-file-name}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{--export-all-symbols}] [@option{--no-export-all-symbols}]
|
|
|
|
[@option{--exclude-symbols} @var{list}]
|
|
|
|
[@option{--no-default-excludes}]
|
|
|
|
[@option{-S}|@option{--as} @var{path-to-assembler}] [@option{-f}|@option{--as-flags} @var{options}]
|
|
|
|
[@option{-D}|@option{--dllname} @var{name}] [@option{-m}|@option{--machine} @var{machine}]
|
2006-03-09 21:28:49 +01:00
|
|
|
[@option{-a}|@option{--add-indirect}]
|
|
|
|
[@option{-U}|@option{--add-underscore}] [@option{--add-stdcall-underscore}]
|
|
|
|
[@option{-k}|@option{--kill-at}] [@option{-A}|@option{--add-stdcall-alias}]
|
2004-07-12 19:07:55 +02:00
|
|
|
[@option{-p}|@option{--ext-prefix-alias} @var{prefix}]
|
2008-11-15 19:15:18 +01:00
|
|
|
[@option{-x}|@option{--no-idata4}] [@option{-c}|@option{--no-idata5}]
|
2009-01-08 14:29:14 +01:00
|
|
|
[@option{--use-nul-prefixed-import-tables}]
|
2009-01-13 10:23:51 +01:00
|
|
|
[@option{-I}|@option{--identify} @var{library-file-name}] [@option{--identify-strict}]
|
|
|
|
[@option{-i}|@option{--interwork}]
|
2003-11-25 20:50:04 +01:00
|
|
|
[@option{-n}|@option{--nodelete}] [@option{-t}|@option{--temp-prefix} @var{prefix}]
|
2007-06-29 02:34:14 +02:00
|
|
|
[@option{-v}|@option{--verbose}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-h}|@option{--help}] [@option{-V}|@option{--version}]
|
2009-10-28 18:21:36 +01:00
|
|
|
[@option{--no-leading-underscore}] [@option{--leading-underscore}]
|
1999-05-03 09:29:11 +02:00
|
|
|
[object-file @dots{}]
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION dlltool
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{dlltool} reads its inputs, which can come from the @option{-d} and
|
|
|
|
@option{-b} options as well as object files specified on the command
|
|
|
|
line. It then processes these inputs and if the @option{-e} option has
|
|
|
|
been specified it creates a exports file. If the @option{-l} option
|
|
|
|
has been specified it creates a library file and if the @option{-z} option
|
2007-06-29 02:34:14 +02:00
|
|
|
has been specified it creates a def file. Any or all of the @option{-e},
|
|
|
|
@option{-l} and @option{-z} options can be present in one invocation of
|
2001-08-01 17:54:41 +02:00
|
|
|
dlltool.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
When creating a DLL, along with the source for the DLL, it is necessary
|
2001-08-01 17:54:41 +02:00
|
|
|
to have three other files. @command{dlltool} can help with the creation of
|
1999-05-03 09:29:11 +02:00
|
|
|
these files.
|
|
|
|
|
2004-12-06 22:20:50 +01:00
|
|
|
The first file is a @file{.def} file which specifies which functions are
|
1999-05-03 09:29:11 +02:00
|
|
|
exported from the DLL, which functions the DLL imports, and so on. This
|
2001-08-01 17:54:41 +02:00
|
|
|
is a text file and can be created by hand, or @command{dlltool} can be used
|
|
|
|
to create it using the @option{-z} option. In this case @command{dlltool}
|
1999-05-03 09:29:11 +02:00
|
|
|
will scan the object files specified on its command line looking for
|
|
|
|
those functions which have been specially marked as being exported and
|
2004-12-06 22:20:50 +01:00
|
|
|
put entries for them in the @file{.def} file it creates.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
In order to mark a function as being exported from a DLL, it needs to
|
2001-08-01 17:54:41 +02:00
|
|
|
have an @option{-export:<name_of_function>} entry in the @samp{.drectve}
|
1999-05-03 09:29:11 +02:00
|
|
|
section of the object file. This can be done in C by using the
|
|
|
|
asm() operator:
|
|
|
|
|
|
|
|
@smallexample
|
2007-06-29 02:34:14 +02:00
|
|
|
asm (".section .drectve");
|
1999-05-03 09:29:11 +02:00
|
|
|
asm (".ascii \"-export:my_func\"");
|
|
|
|
|
|
|
|
int my_func (void) @{ @dots{} @}
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
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
|
2001-08-01 17:54:41 +02:00
|
|
|
binary file and it can be created by giving the @option{-e} option to
|
2007-06-29 02:34:14 +02:00
|
|
|
@command{dlltool} when it is creating or reading in a @file{.def} file.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
The third file needed for DLL creation is the library file that programs
|
2008-11-15 19:15:18 +01:00
|
|
|
will link with in order to access the functions in the DLL (an `import
|
|
|
|
library'). This file can be created by giving the @option{-l} option to
|
|
|
|
dlltool when it is creating or reading in a @file{.def} file.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2009-09-04 03:22:19 +02:00
|
|
|
If the @option{-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.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{dlltool} builds the library file by hand, but it builds the
|
1999-05-03 09:29:11 +02:00
|
|
|
exports file by creating temporary files containing assembler statements
|
2018-07-02 12:18:24 +02:00
|
|
|
and then assembling these. The @option{-S} command-line option can be
|
1999-05-03 09:29:11 +02:00
|
|
|
used to specify the path to the assembler that dlltool will use,
|
2001-08-01 17:54:41 +02:00
|
|
|
and the @option{-f} option can be used to pass specific flags to that
|
|
|
|
assembler. The @option{-n} can be used to prevent dlltool from deleting
|
|
|
|
these temporary assembler files when it is done, and if @option{-n} is
|
1999-05-03 09:29:11 +02:00
|
|
|
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 @samp{dll.c} and
|
|
|
|
also creating a program (from an object file called @samp{program.o})
|
|
|
|
that uses that DLL:
|
|
|
|
|
|
|
|
@smallexample
|
|
|
|
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
|
|
|
|
@end smallexample
|
|
|
|
|
2008-11-15 19:15:18 +01:00
|
|
|
|
|
|
|
@command{dlltool} may also be used to query an existing import library
|
2011-11-29 19:07:41 +01:00
|
|
|
to determine the name of the DLL to which it is associated. See the
|
2008-11-15 19:15:18 +01:00
|
|
|
description of the @option{-I} or @option{--identify} option.
|
2011-11-29 19:07:41 +01:00
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS dlltool
|
|
|
|
|
2018-07-02 12:18:24 +02:00
|
|
|
The command-line options have the following meanings:
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @env
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -d @var{filename}
|
|
|
|
@itemx --input-def @var{filename}
|
|
|
|
@cindex input .def file
|
2004-12-06 22:20:50 +01:00
|
|
|
Specifies the name of a @file{.def} file to be read in and processed.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -b @var{filename}
|
|
|
|
@itemx --base-file @var{filename}
|
|
|
|
@cindex base files
|
|
|
|
Specifies the name of a base file to be read in and processed. The
|
|
|
|
contents of this file will be added to the relocation section in the
|
|
|
|
exports file generated by dlltool.
|
|
|
|
|
|
|
|
@item -e @var{filename}
|
|
|
|
@itemx --output-exp @var{filename}
|
|
|
|
Specifies the name of the export file to be created by dlltool.
|
|
|
|
|
|
|
|
@item -z @var{filename}
|
|
|
|
@itemx --output-def @var{filename}
|
2004-12-06 22:20:50 +01:00
|
|
|
Specifies the name of the @file{.def} file to be created by dlltool.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -l @var{filename}
|
|
|
|
@itemx --output-lib @var{filename}
|
|
|
|
Specifies the name of the library file to be created by dlltool.
|
|
|
|
|
2009-09-04 03:22:19 +02:00
|
|
|
@item -y @var{filename}
|
|
|
|
@itemx --output-delaylib @var{filename}
|
|
|
|
Specifies the name of the delay-import library file to be created by dlltool.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item --export-all-symbols
|
|
|
|
Treat all global and weak defined symbols found in the input object
|
|
|
|
files as symbols to be exported. There is a small list of symbols which
|
2001-08-01 17:54:41 +02:00
|
|
|
are not exported by default; see the @option{--no-default-excludes}
|
1999-05-03 09:29:11 +02:00
|
|
|
option. You may add to the list of symbols to not export by using the
|
2001-08-01 17:54:41 +02:00
|
|
|
@option{--exclude-symbols} option.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --no-export-all-symbols
|
2004-12-06 22:20:50 +01:00
|
|
|
Only export symbols explicitly listed in an input @file{.def} file or in
|
1999-05-03 09:29:11 +02:00
|
|
|
@samp{.drectve} sections in the input object files. This is the default
|
|
|
|
behaviour. The @samp{.drectve} sections are created by @samp{dllexport}
|
|
|
|
attributes in the source code.
|
|
|
|
|
|
|
|
@item --exclude-symbols @var{list}
|
|
|
|
Do not export the symbols in @var{list}. This is a list of symbol names
|
|
|
|
separated by comma or colon characters. The symbol names should not
|
|
|
|
contain a leading underscore. This is only meaningful when
|
2001-08-01 17:54:41 +02:00
|
|
|
@option{--export-all-symbols} is used.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item --no-default-excludes
|
2001-08-01 17:54:41 +02:00
|
|
|
When @option{--export-all-symbols} is used, it will by default avoid
|
1999-05-03 09:29:11 +02:00
|
|
|
exporting certain special symbols. The current list of symbols to avoid
|
|
|
|
exporting is @samp{DllMain@@12}, @samp{DllEntryPoint@@0},
|
2001-08-01 17:54:41 +02:00
|
|
|
@samp{impure_ptr}. You may use the @option{--no-default-excludes} option
|
1999-05-03 09:29:11 +02:00
|
|
|
to go ahead and export these special symbols. This is only meaningful
|
2001-08-01 17:54:41 +02:00
|
|
|
when @option{--export-all-symbols} is used.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -S @var{path}
|
|
|
|
@itemx --as @var{path}
|
|
|
|
Specifies the path, including the filename, of the assembler to be used
|
|
|
|
to create the exports file.
|
|
|
|
|
2002-01-15 18:18:53 +01:00
|
|
|
@item -f @var{options}
|
|
|
|
@itemx --as-flags @var{options}
|
2018-07-02 12:18:24 +02:00
|
|
|
Specifies any specific command-line options to be passed to the
|
1999-05-03 09:29:11 +02:00
|
|
|
assembler when building the exports file. This option will work even if
|
2001-08-01 17:54:41 +02:00
|
|
|
the @option{-S} option is not used. This option only takes one argument,
|
1999-05-03 09:29:11 +02:00
|
|
|
and if it occurs more than once on the command line, then later
|
|
|
|
occurrences will override earlier occurrences. So if it is necessary to
|
2002-01-15 18:18:53 +01:00
|
|
|
pass multiple options to the assembler they should be enclosed in
|
1999-05-03 09:29:11 +02:00
|
|
|
double quotes.
|
|
|
|
|
|
|
|
@item -D @var{name}
|
|
|
|
@itemx --dll-name @var{name}
|
2004-12-06 22:20:50 +01:00
|
|
|
Specifies the name to be stored in the @file{.def} file as the name of
|
|
|
|
the DLL when the @option{-e} option is used. If this option is not
|
|
|
|
present, then the filename given to the @option{-e} option will be
|
|
|
|
used as the name of the DLL.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -m @var{machine}
|
|
|
|
@itemx -machine @var{machine}
|
|
|
|
Specifies the type of machine for which the library file should be
|
2001-08-01 17:54:41 +02:00
|
|
|
built. @command{dlltool} has a built in default type, depending upon how
|
1999-05-03 09:29:11 +02:00
|
|
|
it was created, but this option can be used to override that. This is
|
|
|
|
normally only useful when creating DLLs for an ARM processor, when the
|
2001-08-05 23:01:26 +02:00
|
|
|
contents of the DLL are actually encode using Thumb instructions.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -a
|
|
|
|
@itemx --add-indirect
|
2001-08-01 17:54:41 +02:00
|
|
|
Specifies that when @command{dlltool} is creating the exports file it
|
1999-05-03 09:29:11 +02:00
|
|
|
should add a section which allows the exported functions to be
|
|
|
|
referenced without using the import library. Whatever the hell that
|
2007-06-29 02:34:14 +02:00
|
|
|
means!
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -U
|
|
|
|
@itemx --add-underscore
|
2001-08-01 17:54:41 +02:00
|
|
|
Specifies that when @command{dlltool} is creating the exports file it
|
2007-06-29 02:34:14 +02:00
|
|
|
should prepend an underscore to the names of @emph{all} exported symbols.
|
2006-03-09 21:28:49 +01:00
|
|
|
|
2009-10-28 18:21:36 +01:00
|
|
|
@item --no-leading-underscore
|
|
|
|
@item --leading-underscore
|
|
|
|
Specifies whether standard symbol should be forced to be prefixed, or
|
|
|
|
not.
|
|
|
|
|
2006-03-09 21:28:49 +01:00
|
|
|
@item --add-stdcall-underscore
|
|
|
|
Specifies that when @command{dlltool} is creating the exports file it
|
|
|
|
should prepend an underscore to the names of exported @emph{stdcall}
|
|
|
|
functions. Variable names and non-stdcall function names are not modified.
|
|
|
|
This option is useful when creating GNU-compatible import libs for third
|
|
|
|
party DLLs that were built with MS-Windows tools.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -k
|
|
|
|
@itemx --kill-at
|
2015-01-05 10:41:48 +01:00
|
|
|
Specifies that @samp{@@<number>} suffixes should be omitted from the names
|
|
|
|
of stdcall functions that will be imported from the DLL. This is
|
|
|
|
useful when creating an import library for a DLL which exports stdcall
|
|
|
|
functions but without the usual @samp{@@<number>} symbol name suffix.
|
|
|
|
|
|
|
|
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).
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -A
|
|
|
|
@itemx --add-stdcall-alias
|
2001-08-01 17:54:41 +02:00
|
|
|
Specifies that when @command{dlltool} is creating the exports file it
|
1999-05-03 09:29:11 +02:00
|
|
|
should add aliases for stdcall symbols without @samp{@@ <number>}
|
|
|
|
in addition to the symbols with @samp{@@ <number>}.
|
|
|
|
|
2004-07-12 19:07:55 +02:00
|
|
|
@item -p
|
|
|
|
@itemx --ext-prefix-alias @var{prefix}
|
|
|
|
Causes @command{dlltool} to create external aliases for all DLL
|
|
|
|
imports with the specified prefix. The aliases are created for both
|
|
|
|
external and import symbols with no leading underscore.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -x
|
|
|
|
@itemx --no-idata4
|
2001-08-01 17:54:41 +02:00
|
|
|
Specifies that when @command{dlltool} is creating the exports and library
|
|
|
|
files it should omit the @code{.idata4} section. This is for compatibility
|
1999-05-03 09:29:11 +02:00
|
|
|
with certain operating systems.
|
|
|
|
|
2009-01-08 14:29:14 +01:00
|
|
|
@item --use-nul-prefixed-import-tables
|
|
|
|
Specifies that when @command{dlltool} is creating the exports and library
|
|
|
|
files it should prefix the @code{.idata4} and @code{.idata5} by zero an
|
|
|
|
element. This emulates old gnu import library generation of
|
|
|
|
@code{dlltool}. By default this option is turned off.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -c
|
|
|
|
@itemx --no-idata5
|
2001-08-01 17:54:41 +02:00
|
|
|
Specifies that when @command{dlltool} is creating the exports and library
|
|
|
|
files it should omit the @code{.idata5} section. This is for compatibility
|
1999-05-03 09:29:11 +02:00
|
|
|
with certain operating systems.
|
|
|
|
|
2008-11-15 19:15:18 +01:00
|
|
|
@item -I @var{filename}
|
|
|
|
@itemx --identify @var{filename}
|
|
|
|
Specifies that @command{dlltool} should inspect the import library
|
2009-01-13 10:23:51 +01:00
|
|
|
indicated by @var{filename} and report, on @code{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.
|
|
|
|
@command{dlltool} fails if the import library does not exist or is not
|
|
|
|
actually an import library. See also @option{--identify-strict}.
|
|
|
|
|
|
|
|
@item --identify-strict
|
|
|
|
Modifies the behavior of the @option{--identify} option, such
|
|
|
|
that an error is reported if @var{filename} is associated with
|
|
|
|
more than one DLL.
|
2008-11-15 19:15:18 +01:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -i
|
|
|
|
@itemx --interwork
|
2001-08-01 17:54:41 +02:00
|
|
|
Specifies that @command{dlltool} should mark the objects in the library
|
1999-05-03 09:29:11 +02:00
|
|
|
file and exports file that it produces as supporting interworking
|
2001-08-05 23:01:26 +02:00
|
|
|
between ARM and Thumb code.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -n
|
|
|
|
@itemx --nodelete
|
2001-08-01 17:54:41 +02:00
|
|
|
Makes @command{dlltool} preserve the temporary assembler files it used to
|
1999-05-03 09:29:11 +02:00
|
|
|
create the exports file. If this option is repeated then dlltool will
|
|
|
|
also preserve the temporary object files it uses to create the library
|
2003-11-25 20:50:04 +01:00
|
|
|
file.
|
|
|
|
|
|
|
|
@item -t @var{prefix}
|
|
|
|
@itemx --temp-prefix @var{prefix}
|
|
|
|
Makes @command{dlltool} use @var{prefix} when constructing the names of
|
|
|
|
temporary assembler and object files. By default, the temp file prefix
|
2007-06-29 02:34:14 +02:00
|
|
|
is generated from the pid.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -v
|
|
|
|
@itemx --verbose
|
|
|
|
Make dlltool describe what it is doing.
|
|
|
|
|
|
|
|
@item -h
|
|
|
|
@itemx --help
|
2018-07-02 12:18:24 +02:00
|
|
|
Displays a list of command-line options and then exits.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -V
|
|
|
|
@itemx --version
|
|
|
|
Displays dlltool's version number and then exits.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
2004-12-06 22:20:50 +01:00
|
|
|
@menu
|
|
|
|
* def file format:: The format of the dlltool @file{.def} file
|
|
|
|
@end menu
|
|
|
|
|
|
|
|
@node def file format
|
|
|
|
@section The format of the @command{dlltool} @file{.def} file
|
|
|
|
|
|
|
|
A @file{.def} file contains any number of the following commands:
|
|
|
|
|
|
|
|
@table @asis
|
|
|
|
|
|
|
|
@item @code{NAME} @var{name} @code{[ ,} @var{base} @code{]}
|
|
|
|
The result is going to be named @var{name}@code{.exe}.
|
|
|
|
|
|
|
|
@item @code{LIBRARY} @var{name} @code{[ ,} @var{base} @code{]}
|
|
|
|
The result is going to be named @var{name}@code{.dll}.
|
2012-02-24 15:20:19 +01:00
|
|
|
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).
|
2004-12-06 22:20:50 +01:00
|
|
|
|
2009-10-23 16:53:57 +02:00
|
|
|
@item @code{EXPORTS ( ( (} @var{name1} @code{[ = } @var{name2} @code{] ) | ( } @var{name1} @code{=} @var{module-name} @code{.} @var{external-name} @code{) ) [ == } @var{its_name} @code{]}
|
2004-12-06 22:20:50 +01:00
|
|
|
@item @code{[} @var{integer} @code{] [ NONAME ] [ CONSTANT ] [ DATA ] [ PRIVATE ] ) *}
|
|
|
|
Declares @var{name1} as an exported symbol from the DLL, with optional
|
|
|
|
ordinal number @var{integer}, or declares @var{name1} as an alias
|
2009-10-23 16:53:57 +02:00
|
|
|
(forward) of the function @var{external-name} in the DLL.
|
|
|
|
If @var{its_name} is specified, this name is used as string in export table.
|
2004-12-06 22:20:50 +01:00
|
|
|
@var{module-name}.
|
2012-02-24 15:20:19 +01:00
|
|
|
Note: The @code{EXPORTS} has to be the last command in .def file, as keywords
|
|
|
|
are treated - beside @code{LIBRARY} - as simple name-identifiers.
|
|
|
|
If you want to use LIBRARY as name then you need to quote it.
|
2004-12-06 22:20:50 +01:00
|
|
|
|
2009-10-23 16:53:57 +02:00
|
|
|
@item @code{IMPORTS ( (} @var{internal-name} @code{=} @var{module-name} @code{.} @var{integer} @code{) | [} @var{internal-name} @code{= ]} @var{module-name} @code{.} @var{external-name} @code{) [ == ) @var{its_name} @code{]} *}
|
2004-12-06 22:20:50 +01:00
|
|
|
Declares that @var{external-name} or the exported function whose
|
|
|
|
ordinal number is @var{integer} is to be imported from the file
|
|
|
|
@var{module-name}. If @var{internal-name} is specified then this is
|
|
|
|
the name that the imported function will be referred to in the body of
|
|
|
|
the DLL.
|
2009-10-23 16:53:57 +02:00
|
|
|
If @var{its_name} is specified, this name is used as string in import table.
|
2012-02-24 15:20:19 +01:00
|
|
|
Note: The @code{IMPORTS} has to be the last command in .def file, as keywords
|
|
|
|
are treated - beside @code{LIBRARY} - as simple name-identifiers.
|
|
|
|
If you want to use LIBRARY as name then you need to quote it.
|
2004-12-06 22:20:50 +01:00
|
|
|
|
|
|
|
@item @code{DESCRIPTION} @var{string}
|
|
|
|
Puts @var{string} into the output @file{.exp} file in the
|
|
|
|
@code{.rdata} section.
|
|
|
|
|
|
|
|
@item @code{STACKSIZE} @var{number-reserve} @code{[, } @var{number-commit} @code{]}
|
|
|
|
@item @code{HEAPSIZE} @var{number-reserve} @code{[, } @var{number-commit} @code{]}
|
|
|
|
Generates @code{--stack} or @code{--heap}
|
|
|
|
@var{number-reserve},@var{number-commit} in the output @code{.drectve}
|
|
|
|
section. The linker will see this and act upon it.
|
|
|
|
|
|
|
|
@item @code{CODE} @var{attr} @code{+}
|
|
|
|
@item @code{DATA} @var{attr} @code{+}
|
|
|
|
@item @code{SECTIONS (} @var{section-name} @var{attr}@code{ + ) *}
|
|
|
|
Generates @code{--attr} @var{section-name} @var{attr} in the output
|
|
|
|
@code{.drectve} section, where @var{attr} is one of @code{READ},
|
|
|
|
@code{WRITE}, @code{EXECUTE} or @code{SHARED}. The linker will see
|
|
|
|
this and act upon it.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO dlltool
|
2004-12-06 22:20:50 +01:00
|
|
|
The Info pages for @file{binutils}.
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@node readelf
|
|
|
|
@chapter readelf
|
|
|
|
|
|
|
|
@cindex ELF file information
|
|
|
|
@kindex readelf
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@c man title readelf display information about ELF files
|
2001-03-25 22:32:31 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@smallexample
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin SYNOPSIS readelf
|
2007-06-29 02:34:14 +02:00
|
|
|
readelf [@option{-a}|@option{--all}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-h}|@option{--file-header}]
|
|
|
|
[@option{-l}|@option{--program-headers}|@option{--segments}]
|
|
|
|
[@option{-S}|@option{--section-headers}|@option{--sections}]
|
2005-04-01 17:09:43 +02:00
|
|
|
[@option{-g}|@option{--section-groups}]
|
2005-08-11 15:14:29 +02:00
|
|
|
[@option{-t}|@option{--section-details}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-e}|@option{--headers}]
|
|
|
|
[@option{-s}|@option{--syms}|@option{--symbols}]
|
2010-01-11 15:45:42 +01:00
|
|
|
[@option{--dyn-syms}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-n}|@option{--notes}]
|
|
|
|
[@option{-r}|@option{--relocs}]
|
|
|
|
[@option{-u}|@option{--unwind}]
|
|
|
|
[@option{-d}|@option{--dynamic}]
|
|
|
|
[@option{-V}|@option{--version-info}]
|
2003-02-21 11:30:35 +01:00
|
|
|
[@option{-A}|@option{--arch-specific}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-D}|@option{--use-dynamic}]
|
2005-11-14 16:00:30 +01:00
|
|
|
[@option{-x} <number or name>|@option{--hex-dump=}<number or name>]
|
2007-08-30 15:47:35 +02:00
|
|
|
[@option{-p} <number or name>|@option{--string-dump=}<number or name>]
|
2009-06-24 12:37:35 +02:00
|
|
|
[@option{-R} <number or name>|@option{--relocated-dump=}<number or name>]
|
2015-05-15 18:16:31 +02:00
|
|
|
[@option{-z}|@option{--decompress}]
|
2007-09-17 18:09:24 +02:00
|
|
|
[@option{-c}|@option{--archive-index}]
|
Add support to readelf and objdump for following links to separate debug information files.
Hi Guys,
I am applying the rather large patch attached to this email to enhance
the readelf and objdump programs so that they now have the ability to
follow links to separate debug info files. (As requested by PR
15152). So for example whereas before we had this output:
$ readelf -wi main.exe
Contents of the .debug_info section:
[...]
<15> DW_AT_comp_dir : (alt indirect string, offset: 0x30c)
[...]
With the new option enabled we get:
$ readelf -wiK main.exe
main.exe: Found separate debug info file: dwz.debug
Contents of the .debug_info section (loaded from main.exe):
[...]
<15> DW_AT_comp_dir : (alt indirect string, offset: 0x30c) /home/nickc/Downloads/dwzm
[...]
The link following feature also means that we can get two lots of
output if the same section exists in both the main file and the
separate debug info file:
$ readelf -wiK main.exe
main.exe: Found separate debug info file: dwz.debug
Contents of the .debug_info section (loaded from main.exe):
[...]
Contents of the .debug_info section (loaded from dwz.debug):
[...]
The patch also adds the ability to display the contents of debuglink
sections:
$ readelf -wk main.exe
Contents of the .gnu_debugaltlink section:
Separate debug info file: dwz.debug
Build-ID (0x14 bytes):
c4 a8 89 8d 64 cf 70 8a 35 68 21 f2 ed 24 45 3e 18 7a 7a 93
Naturally there are long versions of these options (=follow-links and
=links). The documentation has been updated as well, and since both
readelf and objdump use the same set of debug display options, I have
moved the text into a separate file. There are also a couple of new
binutils tests to exercise the new behaviour.
There are a couple of missing features in the current patch however,
although I do intend to address them in follow up submissions:
Firstly the code does not check the build-id inside separate debug
info files when it is searching for a file specified by a
.gnu_debugaltlink section. It just assumes that if the file is there,
then it contains the information being sought.
Secondly I have not checked the DWARF-5 version of these link
features, so there will probably be code to add there.
Thirdly I have only implemented link following for the
DW_FORM_GNU_strp_alt format. Other alternate formats (eg
DW_FORM_GNU_ref_alt) have yet to be implemented.
Lastly, whilst implementing this feature I found it necessary to move
some of the global variables used by readelf (eg section_headers) into
a structure that can be passed around. I have moved all of the global
variables that were necessary to get the patch working, but I need to
complete the operation and move the remaining, file-specific variables
(eg dynamic_strings).
Cheers
Nick
binutils PR 15152
* dwarf.h (enum dwarf_section_display_enum): Add gnu_debuglink,
gnu_debugaltlink and separate_debug_str.
(struct dwarf_section): Add filename field.
Add prototypes for load_separate_debug_file, close_debug_file and
open_debug_file.
* dwarf.c (do_debug_links): New.
(do_follow_links): New.
(separate_debug_file, separate_debug_filename): New.
(fetch_alt_indirect_string): New function. Retrieves a string
from the debug string table in the separate debug info file.
(read_and_display_attr_value): Use it with DW_FORM_GNU_strp_alt.
(load_debug_section_with_follow): New function. Like
load_debug_section, but if the first attempt fails, then tries
again in the separate debug info file.
(introduce): New function.
(process_debug_info): Use load_debug_section_with_follow and
introduce.
(load_debug_info): Likewise.
(display_debug_lines_raw): Likewise.
(display_debug_lines_decoded): Likewise.
(display_debug_macinfo): Likewise.
(display_debug_macro): Likewise.
(display_debug_abbrev): Likewise.
(display_debug_loc): Likewise.
(display_debug_str): Likewise.
(display_debug_aranges): Likewise.
(display_debug_addr); Likewise.
(display_debug_frames): Likewise.
(display_gdb_index): Likewise.
(process_cu_tu_index): Likewise.
(load_cu_tu_indexes): Likewise.
(display_debug_links): New function. Displays the contents of a
.gnu_debuglink or .gnu_debugaltlink section.
(calc_gnu_debuglink_ctc32):New function. Calculates a CRC32
value.
(check_gnu_debuglink): New function. Checks the CRC of a
potential separate debug info file.
(parse_gnu_debuglink): New function. Reads a CRC value out of a
.gnu_debuglink section.
(check_gnu_debugaltlink): New function.
(parse_gnu_debugaltlink): New function. Reads the build-id value
out of a .gnu_debugaltlink section.
(load_separate_debug_info): New function. Finds and loads a
separate debug info file.
(load_separate_debug_file): New function. Attempts to find and
follow a link to a separate debug info file.
(free_debug_memory): Free the separate debug info file
information.
(opts_table): Add "follow-links" and "links".
(dwarf_select_sections_by_letters): Add "k" and "K".
(debug_displays): Reformat. Add .gnu-debuglink and
.gnu_debugaltlink.
Add an extra entry for .debug_str in a separate debug info file.
* doc/binutils.texi: Move description of debug dump features
common to both readelf and objdump into...
* objdump.c (usage): Add -Wk and -WK.
(load_specific_debug_section): Initialise the filename field in
the dwarf_section structure.
(close_debug_file): New function.
(open_debug_file): New function.
(dump_dwarf): Load and dump the separate debug info sections.
* readelf.c (struct filedata): New structure. Contains various
variables that used to be global:
(current_file_size, string_table, string_table_length, elf_header)
(section_headers, program_headers, dump_sects, num_dump_sects):
Move into filedata structure.
(cmdline): New global variable. Contains list of sections to dump
by number, as specified on the command line.
Add filedata parameter to most functions.
(load_debug_section): Load the string table if it has not already
been retrieved.
(close_file): New function.
(close_debug_file): New function.
(open_file): New function.
(open_debug_file): New function.
(process_object): Process sections in any separate debug info files.
* doc/debug.options.texi: New file. Add description of =links and
=follow-links options.
* NEWS: Mention the new feature.
* elfcomm.c: Have the byte gte functions take a const pointer.
* elfcomm.h: Update prototypes.
* testsuite/binutils-all/dw5.W: Update expected output.
* testsuite/binutils-all/objdump.WL: Update expected output.
* testsuite/binutils-all/objdump.exp: Add test of -WK and -Wk.
* testsuite/binutils-all/readelf.exp: Add test of -wK and -wk.
* testsuite/binutils-all/readelf.k: New file.
* testsuite/binutils-all/objdump.Wk: New file.
* testsuite/binutils-all/objdump.WK2: New file.
* testsuite/binutils-all/linkdebug.s: New file.
* testsuite/binutils-all/debuglink.s: New file.
gas * testsuite/gas/avr/large-debug-line-table.d: Update expected
output.
* testsuite/gas/elf/dwarf2-11.d: Likewise.
* testsuite/gas/elf/dwarf2-12.d: Likewise.
* testsuite/gas/elf/dwarf2-13.d: Likewise.
* testsuite/gas/elf/dwarf2-14.d: Likewise.
* testsuite/gas/elf/dwarf2-15.d: Likewise.
* testsuite/gas/elf/dwarf2-16.d: Likewise.
* testsuite/gas/elf/dwarf2-17.d: Likewise.
* testsuite/gas/elf/dwarf2-18.d: Likewise.
* testsuite/gas/elf/dwarf2-5.d: Likewise.
* testsuite/gas/elf/dwarf2-6.d: Likewise.
* testsuite/gas/elf/dwarf2-7.d: Likewise.
ld * testsuite/ld-avr/gc-section-debugline.d: Update expected
output.
2017-11-15 12:34:03 +01:00
|
|
|
[@option{-w[lLiaprmfFsoRtUuTgAckK]}|
|
|
|
|
@option{--debug-dump}[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links]]
|
2011-04-28 19:23:17 +02:00
|
|
|
[@option{--dwarf-depth=@var{n}}]
|
|
|
|
[@option{--dwarf-start=@var{n}}]
|
binutils: CTF support for objdump and readelf
This introduces CTF support for objdump and readelf. objdump has the
following new arguments:
--ctf=SECTION: display CTF in the given SECTION
--ctf-parent=SECTION: name of CTF section that is the parent of this section
readelf has the above, and these two as well:
--ctf-symbols=SECTION: name of symbol table section (optional)
--ctf-strings=SECTION: name of string table section (optional)
(objdump can always use BFD machinery to determine the applicable string
and symbol tables automatically, so these arguments are unnecessary.)
Nearly all the work is done by the ctf_dump machinery in libctf: most of
the remaining work is option-processing and section-reading, and thus is
different for objdump and readelf: the minimal amount of similar code
remaining is, in my view, too small to share, particularly given that
objdump uses ctf_bfdopen() and readelf uses ctf_simple_open() since it
doesn't have a bfd.
I am not particularly satisfied with the way resources are freed in
either of these (I was forced to do it at the top level, for lack of
anywhere else to free resources allocated during option processing), but
I can't see any better way to do it without introducing new
infrastructure for no other purpose.
There are essentially arbitrary ordering changes to the Makefile.in's
order of libtool-related stuff that I can't get rid of, but they have no
semantic effect. (It is possible that some hunks of these changes could
be dropped, but that seems a bit risky to me.)
binutils/
* objdump.c (ctf-api.h): New include.
(dump_ctf_section_info): New variable.
(dump_ctf_section_name): Likewise.
(usage): Describe new options.
(enum option_values): Add OPTION_CTF and OPTION_CTF_PARENT.
(main): Use them to add --ctf and --ctf-parent.
(read_section_stabs): Add new parameter, entsize_ptr.
(find_stabs_section): Adjust accordingly.
(make_ctfsect): New.
(dump_ctf_indent_lines): New.
(dump_ctf_archive_member): New.
(dump_ctf): New.
(dump_bfd): Call it. Free resources afterwards.
* readelf.c (ctf-api.h): New include.
(CTF_DUMP): New.
(static bfd_boolean do_ctf): Likewise.
(dump_ctf_parent_name): Likewise.
(dump_ctf_symtab_name): Likewise.
(dump_ctf_strtab_name): Likewise.
(OPTION_CTF_DUMP): Likewise.
(OPTION_CTF_PARENT): Likewise.
(OPTION_CTF_SYMBOLS): Likewise.
(OPTION_CTF_STRINGS): Likewise.
(options): Add them.
(usage): Likewise.
(parse_args): Handle the new options, requesting CTF_DUMP.
(process_section_contents): Handle CTF_DUMP.
(shdr_to_ctf_sect): New.
(dump_ctf_indent_lines): New.
(dump_section_as_ctf): New.
(main): Free resources.
* Makefile.am (LIBCTF): New variable.
(objdump_DEPENDENCIES): Use it.
(readelf_DEPENDENCIES): Likewise.
(objdump_LDADD): Likewise.
(readelf_LDADD): Likewise.
* aclocal.m4: Regenerated.
* Makefile.in: Likewise.
* doc/binutils.texi (objdump): Document the new options.
(readelf): Likewise.
* doc/ctf.options.texi: New.
* doc/Makefile.in: Regenerated.
* NEWS: Mention the new feature.
2019-04-24 13:04:33 +02:00
|
|
|
[@option{--ctf=}@var{section}]
|
|
|
|
[@option{--ctf-parent=}@var{section}]
|
|
|
|
[@option{--ctf-symbols=}@var{section}]
|
|
|
|
[@option{--ctf-strings=}@var{section}]
|
2010-01-07 19:36:38 +01:00
|
|
|
[@option{-I}|@option{--histogram}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-v}|@option{--version}]
|
2001-09-25 18:44:19 +02:00
|
|
|
[@option{-W}|@option{--wide}]
|
2001-08-01 17:54:41 +02:00
|
|
|
[@option{-H}|@option{--help}]
|
1999-05-03 09:29:11 +02:00
|
|
|
@var{elffile}@dots{}
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
1999-05-03 09:29:11 +02:00
|
|
|
@end smallexample
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man begin DESCRIPTION readelf
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{readelf} displays information about one or more ELF format object
|
1999-05-03 09:29:11 +02:00
|
|
|
files. The options control what particular information to display.
|
|
|
|
|
2003-08-11 11:15:55 +02:00
|
|
|
@var{elffile}@dots{} are the object files to be examined. 32-bit and
|
|
|
|
64-bit ELF files are supported, as are archives containing ELF files.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2003-11-26 12:49:10 +01:00
|
|
|
This program performs a similar function to @command{objdump} but it
|
|
|
|
goes into more detail and it exists independently of the @sc{bfd}
|
|
|
|
library, so if there is a bug in @sc{bfd} then readelf will not be
|
|
|
|
affected.
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS readelf
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
The long and short forms of options, shown here as alternatives, are
|
|
|
|
equivalent. At least one option besides @samp{-v} or @samp{-H} must be
|
2007-06-29 02:34:14 +02:00
|
|
|
given.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@table @env
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -a
|
|
|
|
@itemx --all
|
2006-07-06 12:04:09 +02:00
|
|
|
Equivalent to specifying @option{--file-header},
|
2001-08-01 17:54:41 +02:00
|
|
|
@option{--program-headers}, @option{--sections}, @option{--symbols},
|
2017-11-01 12:35:42 +01:00
|
|
|
@option{--relocs}, @option{--dynamic}, @option{--notes},
|
|
|
|
@option{--version-info}, @option{--arch-specific}, @option{--unwind},
|
|
|
|
@option{--section-groups} and @option{--histogram}.
|
|
|
|
|
|
|
|
Note - this option does not enable @option{--use-dynamic} itself, so
|
|
|
|
if that option is not present on the command line then dynamic symbols
|
|
|
|
and dynamic relocs will not be displayed.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -h
|
|
|
|
@itemx --file-header
|
|
|
|
@cindex ELF file header information
|
|
|
|
Displays the information contained in the ELF header at the start of the
|
|
|
|
file.
|
|
|
|
|
|
|
|
@item -l
|
|
|
|
@itemx --program-headers
|
|
|
|
@itemx --segments
|
|
|
|
@cindex ELF program header information
|
|
|
|
@cindex ELF segment information
|
|
|
|
Displays the information contained in the file's segment headers, if it
|
|
|
|
has any.
|
|
|
|
|
|
|
|
@item -S
|
|
|
|
@itemx --sections
|
|
|
|
@itemx --section-headers
|
|
|
|
@cindex ELF section information
|
|
|
|
Displays the information contained in the file's section headers, if it
|
|
|
|
has any.
|
|
|
|
|
2005-04-01 17:09:43 +02:00
|
|
|
@item -g
|
|
|
|
@itemx --section-groups
|
|
|
|
@cindex ELF section group information
|
|
|
|
Displays the information contained in the file's section groups, if it
|
|
|
|
has any.
|
|
|
|
|
2005-08-11 15:14:29 +02:00
|
|
|
@item -t
|
|
|
|
@itemx --section-details
|
|
|
|
@cindex ELF section information
|
|
|
|
Displays the detailed section information. Implies @option{-S}.
|
2005-04-01 17:09:43 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -s
|
|
|
|
@itemx --symbols
|
|
|
|
@itemx --syms
|
|
|
|
@cindex ELF symbol table information
|
|
|
|
Displays the entries in symbol table section of the file, if it has one.
|
2016-11-11 12:49:45 +01:00
|
|
|
If a symbol has version information associated with it then this is
|
|
|
|
displayed as well. The version string is displayed as a suffix to the
|
|
|
|
symbol name, preceeded by an @@ character. For example
|
|
|
|
@samp{foo@@VER_1}. If the version is the default version to be used
|
|
|
|
when resolving unversioned references to the symbol then it is
|
|
|
|
displayed as a suffix preceeded by two @@ characters. For example
|
|
|
|
@samp{foo@@@@VER_2}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2010-01-11 15:45:42 +01:00
|
|
|
@item --dyn-syms
|
|
|
|
@cindex ELF dynamic symbol table information
|
|
|
|
Displays the entries in dynamic symbol table section of the file, if it
|
2016-11-11 12:49:45 +01:00
|
|
|
has one. The output format is the same as the format used by the
|
|
|
|
@option{--syms} option.
|
2010-01-11 15:45:42 +01:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -e
|
|
|
|
@itemx --headers
|
2001-08-01 17:54:41 +02:00
|
|
|
Display all the headers in the file. Equivalent to @option{-h -l -S}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
1999-08-31 18:54:56 +02:00
|
|
|
@item -n
|
|
|
|
@itemx --notes
|
2004-10-26 18:05:42 +02:00
|
|
|
@cindex ELF notes
|
|
|
|
Displays the contents of the NOTE segments and/or sections, if any.
|
1999-08-31 18:54:56 +02:00
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -r
|
|
|
|
@itemx --relocs
|
|
|
|
@cindex ELF reloc information
|
2001-02-10 23:20:55 +01:00
|
|
|
Displays the contents of the file's relocation section, if it has one.
|
|
|
|
|
|
|
|
@item -u
|
|
|
|
@itemx --unwind
|
|
|
|
@cindex unwind information
|
|
|
|
Displays the contents of the file's unwind section, if it has one. Only
|
2010-03-25 09:03:56 +01:00
|
|
|
the unwind sections for IA64 ELF files, as well as ARM unwind tables
|
2018-10-18 17:58:16 +02:00
|
|
|
(@code{.ARM.exidx} / @code{.ARM.extab}) are currently supported. If
|
|
|
|
support is not yet implemented for your architecture you could try
|
|
|
|
dumping the contents of the @var{.eh_frames} section using the
|
|
|
|
@option{--debug-dump=frames} or @option{--debug-dump=frames-interp}
|
|
|
|
options.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item -d
|
|
|
|
@itemx --dynamic
|
|
|
|
@cindex ELF dynamic section information
|
|
|
|
Displays the contents of the file's dynamic section, if it has one.
|
|
|
|
|
|
|
|
@item -V
|
|
|
|
@itemx --version-info
|
2012-08-17 04:43:21 +02:00
|
|
|
@cindex ELF version sections information
|
1999-05-03 09:29:11 +02:00
|
|
|
Displays the contents of the version sections in the file, it they
|
|
|
|
exist.
|
|
|
|
|
2003-02-21 11:30:35 +01:00
|
|
|
@item -A
|
|
|
|
@itemx --arch-specific
|
|
|
|
Displays architecture-specific information in the file, if there
|
|
|
|
is any.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -D
|
|
|
|
@itemx --use-dynamic
|
2001-08-01 17:54:41 +02:00
|
|
|
When displaying symbols, this option makes @command{readelf} use the
|
2010-01-11 15:45:42 +01:00
|
|
|
symbol hash tables in the file's dynamic section, rather than the
|
|
|
|
symbol table sections.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2017-11-01 12:35:42 +01:00
|
|
|
When displaying relocations, this option makes @command{readelf}
|
|
|
|
display the dynamic relocations rather than the static relocations.
|
|
|
|
|
2005-11-14 16:00:30 +01:00
|
|
|
@item -x <number or name>
|
|
|
|
@itemx --hex-dump=<number or name>
|
2009-06-24 12:37:35 +02:00
|
|
|
Displays the contents of the indicated section as a hexadecimal bytes.
|
2005-11-14 16:00:30 +01:00
|
|
|
A number identifies a particular section by index in the section table;
|
|
|
|
any other string identifies all sections with that name in the object file.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2009-06-24 12:37:35 +02:00
|
|
|
@item -R <number or name>
|
|
|
|
@itemx --relocated-dump=<number or name>
|
|
|
|
Displays the contents of the indicated section as a hexadecimal
|
|
|
|
bytes. A number identifies a particular section by index in the
|
|
|
|
section table; any other string identifies all sections with that name
|
|
|
|
in the object file. The contents of the section will be relocated
|
|
|
|
before they are displayed.
|
|
|
|
|
2007-08-30 15:47:35 +02:00
|
|
|
@item -p <number or name>
|
|
|
|
@itemx --string-dump=<number or name>
|
|
|
|
Displays the contents of the indicated section as printable strings.
|
|
|
|
A number identifies a particular section by index in the section table;
|
|
|
|
any other string identifies all sections with that name in the object file.
|
|
|
|
|
2015-05-15 18:16:31 +02:00
|
|
|
@item -z
|
|
|
|
@itemx --decompress
|
|
|
|
Requests that the section(s) being dumped by @option{x}, @option{R} or
|
|
|
|
@option{p} options are decompressed before being displayed. If the
|
|
|
|
section(s) are not compressed then they are displayed as is.
|
|
|
|
|
2007-09-17 18:09:24 +02:00
|
|
|
@item -c
|
|
|
|
@itemx --archive-index
|
|
|
|
@cindex Archive file symbol index information
|
2012-08-17 04:43:21 +02:00
|
|
|
Displays the file symbol index information contained in the header part
|
2007-09-17 18:09:24 +02:00
|
|
|
of binary archives. Performs the same function as the @option{t}
|
|
|
|
command to @command{ar}, but without using the BFD library. @xref{ar}.
|
|
|
|
|
Add support to readelf and objdump for following links to separate debug information files.
Hi Guys,
I am applying the rather large patch attached to this email to enhance
the readelf and objdump programs so that they now have the ability to
follow links to separate debug info files. (As requested by PR
15152). So for example whereas before we had this output:
$ readelf -wi main.exe
Contents of the .debug_info section:
[...]
<15> DW_AT_comp_dir : (alt indirect string, offset: 0x30c)
[...]
With the new option enabled we get:
$ readelf -wiK main.exe
main.exe: Found separate debug info file: dwz.debug
Contents of the .debug_info section (loaded from main.exe):
[...]
<15> DW_AT_comp_dir : (alt indirect string, offset: 0x30c) /home/nickc/Downloads/dwzm
[...]
The link following feature also means that we can get two lots of
output if the same section exists in both the main file and the
separate debug info file:
$ readelf -wiK main.exe
main.exe: Found separate debug info file: dwz.debug
Contents of the .debug_info section (loaded from main.exe):
[...]
Contents of the .debug_info section (loaded from dwz.debug):
[...]
The patch also adds the ability to display the contents of debuglink
sections:
$ readelf -wk main.exe
Contents of the .gnu_debugaltlink section:
Separate debug info file: dwz.debug
Build-ID (0x14 bytes):
c4 a8 89 8d 64 cf 70 8a 35 68 21 f2 ed 24 45 3e 18 7a 7a 93
Naturally there are long versions of these options (=follow-links and
=links). The documentation has been updated as well, and since both
readelf and objdump use the same set of debug display options, I have
moved the text into a separate file. There are also a couple of new
binutils tests to exercise the new behaviour.
There are a couple of missing features in the current patch however,
although I do intend to address them in follow up submissions:
Firstly the code does not check the build-id inside separate debug
info files when it is searching for a file specified by a
.gnu_debugaltlink section. It just assumes that if the file is there,
then it contains the information being sought.
Secondly I have not checked the DWARF-5 version of these link
features, so there will probably be code to add there.
Thirdly I have only implemented link following for the
DW_FORM_GNU_strp_alt format. Other alternate formats (eg
DW_FORM_GNU_ref_alt) have yet to be implemented.
Lastly, whilst implementing this feature I found it necessary to move
some of the global variables used by readelf (eg section_headers) into
a structure that can be passed around. I have moved all of the global
variables that were necessary to get the patch working, but I need to
complete the operation and move the remaining, file-specific variables
(eg dynamic_strings).
Cheers
Nick
binutils PR 15152
* dwarf.h (enum dwarf_section_display_enum): Add gnu_debuglink,
gnu_debugaltlink and separate_debug_str.
(struct dwarf_section): Add filename field.
Add prototypes for load_separate_debug_file, close_debug_file and
open_debug_file.
* dwarf.c (do_debug_links): New.
(do_follow_links): New.
(separate_debug_file, separate_debug_filename): New.
(fetch_alt_indirect_string): New function. Retrieves a string
from the debug string table in the separate debug info file.
(read_and_display_attr_value): Use it with DW_FORM_GNU_strp_alt.
(load_debug_section_with_follow): New function. Like
load_debug_section, but if the first attempt fails, then tries
again in the separate debug info file.
(introduce): New function.
(process_debug_info): Use load_debug_section_with_follow and
introduce.
(load_debug_info): Likewise.
(display_debug_lines_raw): Likewise.
(display_debug_lines_decoded): Likewise.
(display_debug_macinfo): Likewise.
(display_debug_macro): Likewise.
(display_debug_abbrev): Likewise.
(display_debug_loc): Likewise.
(display_debug_str): Likewise.
(display_debug_aranges): Likewise.
(display_debug_addr); Likewise.
(display_debug_frames): Likewise.
(display_gdb_index): Likewise.
(process_cu_tu_index): Likewise.
(load_cu_tu_indexes): Likewise.
(display_debug_links): New function. Displays the contents of a
.gnu_debuglink or .gnu_debugaltlink section.
(calc_gnu_debuglink_ctc32):New function. Calculates a CRC32
value.
(check_gnu_debuglink): New function. Checks the CRC of a
potential separate debug info file.
(parse_gnu_debuglink): New function. Reads a CRC value out of a
.gnu_debuglink section.
(check_gnu_debugaltlink): New function.
(parse_gnu_debugaltlink): New function. Reads the build-id value
out of a .gnu_debugaltlink section.
(load_separate_debug_info): New function. Finds and loads a
separate debug info file.
(load_separate_debug_file): New function. Attempts to find and
follow a link to a separate debug info file.
(free_debug_memory): Free the separate debug info file
information.
(opts_table): Add "follow-links" and "links".
(dwarf_select_sections_by_letters): Add "k" and "K".
(debug_displays): Reformat. Add .gnu-debuglink and
.gnu_debugaltlink.
Add an extra entry for .debug_str in a separate debug info file.
* doc/binutils.texi: Move description of debug dump features
common to both readelf and objdump into...
* objdump.c (usage): Add -Wk and -WK.
(load_specific_debug_section): Initialise the filename field in
the dwarf_section structure.
(close_debug_file): New function.
(open_debug_file): New function.
(dump_dwarf): Load and dump the separate debug info sections.
* readelf.c (struct filedata): New structure. Contains various
variables that used to be global:
(current_file_size, string_table, string_table_length, elf_header)
(section_headers, program_headers, dump_sects, num_dump_sects):
Move into filedata structure.
(cmdline): New global variable. Contains list of sections to dump
by number, as specified on the command line.
Add filedata parameter to most functions.
(load_debug_section): Load the string table if it has not already
been retrieved.
(close_file): New function.
(close_debug_file): New function.
(open_file): New function.
(open_debug_file): New function.
(process_object): Process sections in any separate debug info files.
* doc/debug.options.texi: New file. Add description of =links and
=follow-links options.
* NEWS: Mention the new feature.
* elfcomm.c: Have the byte gte functions take a const pointer.
* elfcomm.h: Update prototypes.
* testsuite/binutils-all/dw5.W: Update expected output.
* testsuite/binutils-all/objdump.WL: Update expected output.
* testsuite/binutils-all/objdump.exp: Add test of -WK and -Wk.
* testsuite/binutils-all/readelf.exp: Add test of -wK and -wk.
* testsuite/binutils-all/readelf.k: New file.
* testsuite/binutils-all/objdump.Wk: New file.
* testsuite/binutils-all/objdump.WK2: New file.
* testsuite/binutils-all/linkdebug.s: New file.
* testsuite/binutils-all/debuglink.s: New file.
gas * testsuite/gas/avr/large-debug-line-table.d: Update expected
output.
* testsuite/gas/elf/dwarf2-11.d: Likewise.
* testsuite/gas/elf/dwarf2-12.d: Likewise.
* testsuite/gas/elf/dwarf2-13.d: Likewise.
* testsuite/gas/elf/dwarf2-14.d: Likewise.
* testsuite/gas/elf/dwarf2-15.d: Likewise.
* testsuite/gas/elf/dwarf2-16.d: Likewise.
* testsuite/gas/elf/dwarf2-17.d: Likewise.
* testsuite/gas/elf/dwarf2-18.d: Likewise.
* testsuite/gas/elf/dwarf2-5.d: Likewise.
* testsuite/gas/elf/dwarf2-6.d: Likewise.
* testsuite/gas/elf/dwarf2-7.d: Likewise.
ld * testsuite/ld-avr/gc-section-debugline.d: Update expected
output.
2017-11-15 12:34:03 +01:00
|
|
|
@item -w[lLiaprmfFsoRtUuTgAckK]
|
|
|
|
@itemx --debug-dump[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index,=addr,=cu_index,=links,=follow-links]
|
|
|
|
@include debug.options.texi
|
2011-04-28 19:23:17 +02:00
|
|
|
|
binutils: CTF support for objdump and readelf
This introduces CTF support for objdump and readelf. objdump has the
following new arguments:
--ctf=SECTION: display CTF in the given SECTION
--ctf-parent=SECTION: name of CTF section that is the parent of this section
readelf has the above, and these two as well:
--ctf-symbols=SECTION: name of symbol table section (optional)
--ctf-strings=SECTION: name of string table section (optional)
(objdump can always use BFD machinery to determine the applicable string
and symbol tables automatically, so these arguments are unnecessary.)
Nearly all the work is done by the ctf_dump machinery in libctf: most of
the remaining work is option-processing and section-reading, and thus is
different for objdump and readelf: the minimal amount of similar code
remaining is, in my view, too small to share, particularly given that
objdump uses ctf_bfdopen() and readelf uses ctf_simple_open() since it
doesn't have a bfd.
I am not particularly satisfied with the way resources are freed in
either of these (I was forced to do it at the top level, for lack of
anywhere else to free resources allocated during option processing), but
I can't see any better way to do it without introducing new
infrastructure for no other purpose.
There are essentially arbitrary ordering changes to the Makefile.in's
order of libtool-related stuff that I can't get rid of, but they have no
semantic effect. (It is possible that some hunks of these changes could
be dropped, but that seems a bit risky to me.)
binutils/
* objdump.c (ctf-api.h): New include.
(dump_ctf_section_info): New variable.
(dump_ctf_section_name): Likewise.
(usage): Describe new options.
(enum option_values): Add OPTION_CTF and OPTION_CTF_PARENT.
(main): Use them to add --ctf and --ctf-parent.
(read_section_stabs): Add new parameter, entsize_ptr.
(find_stabs_section): Adjust accordingly.
(make_ctfsect): New.
(dump_ctf_indent_lines): New.
(dump_ctf_archive_member): New.
(dump_ctf): New.
(dump_bfd): Call it. Free resources afterwards.
* readelf.c (ctf-api.h): New include.
(CTF_DUMP): New.
(static bfd_boolean do_ctf): Likewise.
(dump_ctf_parent_name): Likewise.
(dump_ctf_symtab_name): Likewise.
(dump_ctf_strtab_name): Likewise.
(OPTION_CTF_DUMP): Likewise.
(OPTION_CTF_PARENT): Likewise.
(OPTION_CTF_SYMBOLS): Likewise.
(OPTION_CTF_STRINGS): Likewise.
(options): Add them.
(usage): Likewise.
(parse_args): Handle the new options, requesting CTF_DUMP.
(process_section_contents): Handle CTF_DUMP.
(shdr_to_ctf_sect): New.
(dump_ctf_indent_lines): New.
(dump_section_as_ctf): New.
(main): Free resources.
* Makefile.am (LIBCTF): New variable.
(objdump_DEPENDENCIES): Use it.
(readelf_DEPENDENCIES): Likewise.
(objdump_LDADD): Likewise.
(readelf_LDADD): Likewise.
* aclocal.m4: Regenerated.
* Makefile.in: Likewise.
* doc/binutils.texi (objdump): Document the new options.
(readelf): Likewise.
* doc/ctf.options.texi: New.
* doc/Makefile.in: Regenerated.
* NEWS: Mention the new feature.
2019-04-24 13:04:33 +02:00
|
|
|
@include ctf.options.texi
|
|
|
|
@item --ctf-symbols=@var{section}
|
|
|
|
@item --ctf-strings=@var{section}
|
|
|
|
Specify the name of another section from which the CTF file can inherit
|
|
|
|
strings and symbols.
|
|
|
|
|
|
|
|
If either of @option{--ctf-symbols} or @option{--ctf-strings} is specified, the
|
|
|
|
other must be specified as well.
|
|
|
|
|
2003-02-21 11:30:35 +01:00
|
|
|
@item -I
|
|
|
|
@itemx --histogram
|
1999-05-03 09:29:11 +02:00
|
|
|
Display a histogram of bucket list lengths when displaying the contents
|
|
|
|
of the symbol tables.
|
|
|
|
|
|
|
|
@item -v
|
|
|
|
@itemx --version
|
|
|
|
Display the version number of readelf.
|
|
|
|
|
2001-09-25 18:44:19 +02:00
|
|
|
@item -W
|
|
|
|
@itemx --wide
|
|
|
|
Don't break output lines to fit into 80 columns. By default
|
|
|
|
@command{readelf} breaks section header and segment listing lines for
|
|
|
|
64-bit ELF files, so that they fit into 80 columns. This option causes
|
|
|
|
@command{readelf} to print each section header resp. each segment one a
|
|
|
|
single line, which is far more readable on terminals wider than 80 columns.
|
|
|
|
|
1999-05-03 09:29:11 +02:00
|
|
|
@item -H
|
|
|
|
@itemx --help
|
2018-07-02 12:18:24 +02:00
|
|
|
Display the command-line options understood by @command{readelf}.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@end table
|
|
|
|
|
2001-03-25 22:32:31 +02:00
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO readelf
|
|
|
|
objdump(1), and the Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2010-01-06 17:52:15 +01:00
|
|
|
@node elfedit
|
|
|
|
@chapter elfedit
|
|
|
|
|
|
|
|
@cindex Update ELF header
|
|
|
|
@kindex elfedit
|
|
|
|
|
2019-08-07 16:15:59 +02:00
|
|
|
@c man title elfedit update ELF header and program property of ELF files
|
2010-01-06 17:52:15 +01:00
|
|
|
|
|
|
|
@smallexample
|
|
|
|
@c man begin SYNOPSIS elfedit
|
|
|
|
elfedit [@option{--input-mach=}@var{machine}]
|
2010-01-08 19:50:39 +01:00
|
|
|
[@option{--input-type=}@var{type}]
|
2010-12-12 16:29:31 +01:00
|
|
|
[@option{--input-osabi=}@var{osabi}]
|
2010-01-08 18:23:05 +01:00
|
|
|
@option{--output-mach=}@var{machine}
|
2010-01-08 19:50:39 +01:00
|
|
|
@option{--output-type=}@var{type}
|
2010-12-12 16:29:31 +01:00
|
|
|
@option{--output-osabi=}@var{osabi}
|
2018-11-06 18:38:33 +01:00
|
|
|
@option{--enable-x86-feature=}@var{feature}
|
|
|
|
@option{--disable-x86-feature=}@var{feature}
|
2010-01-06 17:52:15 +01:00
|
|
|
[@option{-v}|@option{--version}]
|
|
|
|
[@option{-h}|@option{--help}]
|
|
|
|
@var{elffile}@dots{}
|
|
|
|
@c man end
|
|
|
|
@end smallexample
|
|
|
|
|
|
|
|
@c man begin DESCRIPTION elfedit
|
|
|
|
|
2018-11-06 18:38:33 +01:00
|
|
|
@command{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.
|
2010-01-06 17:52:15 +01:00
|
|
|
|
|
|
|
@var{elffile}@dots{} are the ELF files to be updated. 32-bit and
|
|
|
|
64-bit ELF files are supported, as are archives containing ELF files.
|
|
|
|
@c man end
|
|
|
|
|
|
|
|
@c man begin OPTIONS elfedit
|
|
|
|
|
|
|
|
The long and short forms of options, shown here as alternatives, are
|
2010-08-23 18:25:53 +02:00
|
|
|
equivalent. At least one of the @option{--output-mach},
|
2018-11-06 18:38:33 +01:00
|
|
|
@option{--output-type}, @option{--output-osabi},
|
|
|
|
@option{--enable-x86-feature} and @option{--disable-x86-feature}
|
|
|
|
options must be given.
|
2010-01-06 17:52:15 +01:00
|
|
|
|
|
|
|
@table @env
|
|
|
|
|
2013-01-04 23:27:58 +01:00
|
|
|
@item --input-mach=@var{machine}
|
2010-01-08 19:50:39 +01:00
|
|
|
Set the matching input ELF machine type to @var{machine}. If
|
|
|
|
@option{--input-mach} isn't specified, it will match any ELF
|
|
|
|
machine types.
|
2010-01-06 17:52:15 +01:00
|
|
|
|
2015-05-11 18:57:20 +02:00
|
|
|
The supported ELF machine types are, @var{i386}, @var{IAMCU}, @var{L1OM},
|
|
|
|
@var{K1OM} and @var{x86-64}.
|
2010-01-06 17:52:15 +01:00
|
|
|
|
2013-01-04 23:27:58 +01:00
|
|
|
@item --output-mach=@var{machine}
|
2010-01-06 17:52:15 +01:00
|
|
|
Change the ELF machine type in the ELF header to @var{machine}. The
|
|
|
|
supported ELF machine types are the same as @option{--input-mach}.
|
|
|
|
|
2013-01-04 23:27:58 +01:00
|
|
|
@item --input-type=@var{type}
|
2010-01-08 19:50:39 +01:00
|
|
|
Set the matching input ELF file type to @var{type}. If
|
|
|
|
@option{--input-type} isn't specified, it will match any ELF file types.
|
|
|
|
|
|
|
|
The supported ELF file types are, @var{rel}, @var{exec} and @var{dyn}.
|
|
|
|
|
2013-01-04 23:27:58 +01:00
|
|
|
@item --output-type=@var{type}
|
2010-01-08 19:50:39 +01:00
|
|
|
Change the ELF file type in the ELF header to @var{type}. The
|
|
|
|
supported ELF types are the same as @option{--input-type}.
|
|
|
|
|
2013-01-04 23:27:58 +01:00
|
|
|
@item --input-osabi=@var{osabi}
|
2010-12-12 16:29:31 +01:00
|
|
|
Set the matching input ELF file OSABI to @var{osabi}. If
|
2010-08-23 18:25:53 +02:00
|
|
|
@option{--input-osabi} isn't specified, it will match any ELF OSABIs.
|
|
|
|
|
|
|
|
The supported ELF OSABIs are, @var{none}, @var{HPUX}, @var{NetBSD},
|
2011-07-03 15:37:09 +02:00
|
|
|
@var{GNU}, @var{Linux} (alias for @var{GNU}),
|
|
|
|
@var{Solaris}, @var{AIX}, @var{Irix},
|
2010-08-23 18:25:53 +02:00
|
|
|
@var{FreeBSD}, @var{TRU64}, @var{Modesto}, @var{OpenBSD}, @var{OpenVMS},
|
|
|
|
@var{NSK}, @var{AROS} and @var{FenixOS}.
|
|
|
|
|
2013-01-04 23:27:58 +01:00
|
|
|
@item --output-osabi=@var{osabi}
|
2010-12-12 16:29:31 +01:00
|
|
|
Change the ELF OSABI in the ELF header to @var{osabi}. The
|
2010-08-23 18:25:53 +02:00
|
|
|
supported ELF OSABI are the same as @option{--input-osabi}.
|
|
|
|
|
2018-11-06 18:38:33 +01:00
|
|
|
@item --enable-x86-feature=@var{feature}
|
|
|
|
Set the @var{feature} bit in program property in @var{exec} or @var{dyn}
|
|
|
|
ELF files with machine types of @var{i386} or @var{x86-64}. The
|
|
|
|
supported features are, @var{ibt} and @var{shstk}.
|
|
|
|
|
|
|
|
@item --disable-x86-feature=@var{feature}
|
|
|
|
Clear the @var{feature} bit in program property in @var{exec} or
|
|
|
|
@var{dyn} ELF files with machine types of @var{i386} or @var{x86-64}.
|
|
|
|
The supported features are the same as @option{--enable-x86-feature}.
|
|
|
|
|
|
|
|
Note: @option{--enable-x86-feature} and @option{--disable-x86-feature}
|
|
|
|
are available only on hosts with @samp{mmap} support.
|
|
|
|
|
2010-01-06 17:52:15 +01:00
|
|
|
@item -v
|
|
|
|
@itemx --version
|
|
|
|
Display the version number of @command{elfedit}.
|
|
|
|
|
|
|
|
@item -h
|
|
|
|
@itemx --help
|
2018-07-02 12:18:24 +02:00
|
|
|
Display the command-line options understood by @command{elfedit}.
|
2010-01-06 17:52:15 +01:00
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@c man end
|
|
|
|
|
|
|
|
@ignore
|
|
|
|
@c man begin SEEALSO elfedit
|
|
|
|
readelf(1), and the Info entries for @file{binutils}.
|
|
|
|
@c man end
|
|
|
|
@end ignore
|
|
|
|
|
2005-10-03 21:37:44 +02:00
|
|
|
@node Common Options
|
|
|
|
@chapter Common Options
|
|
|
|
|
|
|
|
The following command-line options are supported by all of the
|
|
|
|
programs described in this manual.
|
|
|
|
|
2005-11-17 02:01:05 +01:00
|
|
|
@c man begin OPTIONS
|
2005-10-03 21:37:44 +02:00
|
|
|
@table @env
|
2006-05-02 16:20:46 +02:00
|
|
|
@include at-file.texi
|
2005-11-17 02:01:05 +01:00
|
|
|
@c man end
|
2005-10-03 21:37:44 +02:00
|
|
|
|
|
|
|
@item --help
|
|
|
|
Display the command-line options supported by the program.
|
|
|
|
|
|
|
|
@item --version
|
|
|
|
Display the version number of the program.
|
|
|
|
|
2005-11-17 02:01:05 +01:00
|
|
|
@c man begin OPTIONS
|
2005-10-03 21:37:44 +02:00
|
|
|
@end table
|
2005-11-17 02:01:05 +01:00
|
|
|
@c man end
|
2005-10-03 21:37:44 +02:00
|
|
|
|
2007-11-07 12:36:42 +01:00
|
|
|
@node Selecting the Target System
|
2003-02-21 11:30:35 +01:00
|
|
|
@chapter Selecting the Target System
|
1999-05-03 09:29:11 +02:00
|
|
|
|
2003-02-21 11:30:35 +01:00
|
|
|
You can specify two aspects of the target system to the @sc{gnu}
|
1999-05-03 09:29:11 +02:00
|
|
|
binary file utilities, each in several ways:
|
|
|
|
|
|
|
|
@itemize @bullet
|
|
|
|
@item
|
|
|
|
the target
|
|
|
|
|
|
|
|
@item
|
|
|
|
the architecture
|
|
|
|
@end itemize
|
|
|
|
|
|
|
|
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
|
2001-08-01 17:54:41 +02:00
|
|
|
@option{--enable-targets=all}, the commands list most of the available
|
1999-05-03 09:29:11 +02:00
|
|
|
values, but a few are left out; not all targets can be configured in at
|
|
|
|
once because some of them can only be configured @dfn{native} (on hosts
|
|
|
|
with the same type as the target system).
|
|
|
|
|
|
|
|
@menu
|
2007-06-29 02:34:14 +02:00
|
|
|
* Target Selection::
|
|
|
|
* Architecture Selection::
|
1999-05-03 09:29:11 +02:00
|
|
|
@end menu
|
|
|
|
|
|
|
|
@node Target Selection
|
|
|
|
@section Target Selection
|
|
|
|
|
|
|
|
A @dfn{target} is an object file format. A given target may be
|
|
|
|
supported for multiple architectures (@pxref{Architecture Selection}).
|
|
|
|
A target selection may also have variations for different operating
|
|
|
|
systems or architectures.
|
|
|
|
|
|
|
|
The command to list valid target values is @samp{objdump -i}
|
|
|
|
(the first column of output contains the relevant information).
|
|
|
|
|
|
|
|
Some sample values are: @samp{a.out-hp300bsd}, @samp{ecoff-littlemips},
|
|
|
|
@samp{a.out-sunos-big}.
|
|
|
|
|
|
|
|
You can also specify a target using a configuration triplet. This is
|
1999-10-08 15:56:33 +02:00
|
|
|
the same sort of name that is passed to @file{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
|
1999-05-03 09:29:11 +02:00
|
|
|
running the shell script @file{config.sub} which is included with the
|
|
|
|
sources.
|
|
|
|
|
|
|
|
Some sample configuration triplets are: @samp{m68k-hp-bsd},
|
|
|
|
@samp{mips-dec-ultrix}, @samp{sparc-sun-sunos}.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@subheading @command{objdump} Target
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
Ways to specify:
|
|
|
|
|
|
|
|
@enumerate
|
|
|
|
@item
|
2018-07-02 12:18:24 +02:00
|
|
|
command-line option: @option{-b} or @option{--target}
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item
|
|
|
|
environment variable @code{GNUTARGET}
|
|
|
|
|
|
|
|
@item
|
|
|
|
deduced from the input file
|
|
|
|
@end enumerate
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@subheading @command{objcopy} and @command{strip} Input Target
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
Ways to specify:
|
|
|
|
|
|
|
|
@enumerate
|
|
|
|
@item
|
2018-07-02 12:18:24 +02:00
|
|
|
command-line options: @option{-I} or @option{--input-target}, or @option{-F} or @option{--target}
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item
|
|
|
|
environment variable @code{GNUTARGET}
|
|
|
|
|
|
|
|
@item
|
|
|
|
deduced from the input file
|
|
|
|
@end enumerate
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@subheading @command{objcopy} and @command{strip} Output Target
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
Ways to specify:
|
|
|
|
|
|
|
|
@enumerate
|
|
|
|
@item
|
2018-07-02 12:18:24 +02:00
|
|
|
command-line options: @option{-O} or @option{--output-target}, or @option{-F} or @option{--target}
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item
|
2001-08-01 17:54:41 +02:00
|
|
|
the input target (see ``@command{objcopy} and @command{strip} Input Target'' above)
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item
|
|
|
|
environment variable @code{GNUTARGET}
|
|
|
|
|
|
|
|
@item
|
|
|
|
deduced from the input file
|
|
|
|
@end enumerate
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@subheading @command{nm}, @command{size}, and @command{strings} Target
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
Ways to specify:
|
|
|
|
|
|
|
|
@enumerate
|
|
|
|
@item
|
2018-07-02 12:18:24 +02:00
|
|
|
command-line option: @option{--target}
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item
|
|
|
|
environment variable @code{GNUTARGET}
|
|
|
|
|
|
|
|
@item
|
|
|
|
deduced from the input file
|
|
|
|
@end enumerate
|
|
|
|
|
|
|
|
@node Architecture Selection
|
2003-02-21 11:30:35 +01:00
|
|
|
@section Architecture Selection
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
An @dfn{architecture} is a type of @sc{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 @sc{cpu}.
|
|
|
|
|
|
|
|
The command to list valid architecture values is @samp{objdump -i} (the
|
|
|
|
second column contains the relevant information).
|
|
|
|
|
|
|
|
Sample values: @samp{m68k:68020}, @samp{mips:3000}, @samp{sparc}.
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@subheading @command{objdump} Architecture
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
Ways to specify:
|
|
|
|
|
|
|
|
@enumerate
|
|
|
|
@item
|
2018-07-02 12:18:24 +02:00
|
|
|
command-line option: @option{-m} or @option{--architecture}
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item
|
|
|
|
deduced from the input file
|
|
|
|
@end enumerate
|
|
|
|
|
2001-08-01 17:54:41 +02:00
|
|
|
@subheading @command{objcopy}, @command{nm}, @command{size}, @command{strings} Architecture
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
Ways to specify:
|
|
|
|
|
|
|
|
@enumerate
|
|
|
|
@item
|
|
|
|
deduced from the input file
|
|
|
|
@end enumerate
|
|
|
|
|
|
|
|
@node Reporting Bugs
|
|
|
|
@chapter Reporting Bugs
|
|
|
|
@cindex bugs
|
|
|
|
@cindex reporting bugs
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
@menu
|
|
|
|
* Bug Criteria:: Have you found a bug?
|
|
|
|
* Bug Reporting:: How to report bugs
|
|
|
|
@end menu
|
|
|
|
|
|
|
|
@node Bug Criteria
|
2003-02-21 11:30:35 +01:00
|
|
|
@section Have You Found a Bug?
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex bug criteria
|
|
|
|
|
|
|
|
If you are not sure whether you have found a bug, here are some guidelines:
|
|
|
|
|
|
|
|
@itemize @bullet
|
|
|
|
@cindex fatal signal
|
|
|
|
@cindex crash
|
|
|
|
@item
|
|
|
|
If a binary utility gets a fatal signal, for any input whatever, that is
|
|
|
|
a bug. Reliable utilities never crash.
|
|
|
|
|
|
|
|
@cindex error on valid input
|
|
|
|
@item
|
|
|
|
If a binary utility produces an error message for valid input, that is a
|
|
|
|
bug.
|
|
|
|
|
|
|
|
@item
|
|
|
|
If you are an experienced user of binary utilities, your suggestions for
|
|
|
|
improvement are welcome in any case.
|
|
|
|
@end itemize
|
|
|
|
|
|
|
|
@node Bug Reporting
|
2003-02-21 11:30:35 +01:00
|
|
|
@section How to Report Bugs
|
1999-05-03 09:29:11 +02:00
|
|
|
@cindex bug reports
|
|
|
|
@cindex bugs, reporting
|
|
|
|
|
|
|
|
A number of companies and individuals offer support for @sc{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 @file{etc/SERVICE} in the @sc{gnu} Emacs
|
|
|
|
distribution.
|
|
|
|
|
2007-03-07 23:50:01 +01:00
|
|
|
@ifset BUGURL
|
1999-05-03 09:29:11 +02:00
|
|
|
In any event, we also recommend that you send bug reports for the binary
|
2007-03-07 23:50:01 +01:00
|
|
|
utilities to @value{BUGURL}.
|
|
|
|
@end ifset
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
The fundamental principle of reporting bugs usefully is this:
|
|
|
|
@strong{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
|
2003-02-21 11:30:35 +01:00
|
|
|
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.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
To enable us to fix the bug, you should include all these things:
|
|
|
|
|
|
|
|
@itemize @bullet
|
|
|
|
@item
|
|
|
|
The version of the utility. Each utility announces it if you start it
|
2001-08-01 17:54:41 +02:00
|
|
|
with the @option{--version} argument.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
Without this, we will not know whether there is any point in looking for
|
|
|
|
the bug in the current version of the binary utilities.
|
|
|
|
|
|
|
|
@item
|
|
|
|
Any patches you may have applied to the source, including any patches
|
|
|
|
made to the @code{BFD} library.
|
|
|
|
|
|
|
|
@item
|
|
|
|
The type of machine you are using, and the operating system name and
|
|
|
|
version number.
|
|
|
|
|
|
|
|
@item
|
|
|
|
What compiler (and its version) was used to compile the utilities---e.g.
|
|
|
|
``@code{gcc-2.7}''.
|
|
|
|
|
|
|
|
@item
|
|
|
|
The command arguments you gave the utility to observe the bug. To
|
|
|
|
guarantee you will not omit something important, list them all. A copy
|
|
|
|
of the Makefile (or the output from make) is sufficient.
|
|
|
|
|
|
|
|
If we were to try to guess the arguments, we would probably guess wrong
|
|
|
|
and then we might not encounter the bug.
|
|
|
|
|
|
|
|
@item
|
|
|
|
A complete input file, or set of input files, that will reproduce the
|
|
|
|
bug. If the utility is reading an object file or files, then it is
|
2007-03-07 23:50:01 +01:00
|
|
|
generally most helpful to send the actual object files.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
If the source files were produced exclusively using @sc{gnu} programs
|
2001-08-01 17:54:41 +02:00
|
|
|
(e.g., @command{gcc}, @command{gas}, and/or the @sc{gnu} @command{ld}), then it
|
1999-05-03 09:29:11 +02:00
|
|
|
may be OK to send the source files rather than the object files. In
|
2001-08-01 17:54:41 +02:00
|
|
|
this case, be sure to say exactly what version of @command{gcc}, or
|
1999-05-03 09:29:11 +02:00
|
|
|
whatever, was used to produce the object files. Also say how
|
2001-08-01 17:54:41 +02:00
|
|
|
@command{gcc}, or whatever, was configured.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@item
|
|
|
|
A description of what behavior you observe that you believe is
|
|
|
|
incorrect. For example, ``It gets a fatal signal.''
|
|
|
|
|
|
|
|
Of course, if the bug is that the utility gets a fatal signal, then we
|
|
|
|
will certainly notice it. But if the bug is incorrect 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
|
1999-10-08 15:56:33 +02:00
|
|
|
say so explicitly. Suppose something strange is going on, such as your
|
2006-07-24 15:49:50 +02:00
|
|
|
copy of the utility is out of sync, or you have encountered a bug in
|
1999-05-03 09:29:11 +02:00
|
|
|
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.
|
|
|
|
|
|
|
|
@item
|
|
|
|
If you wish to suggest changes to the source, send us context diffs, as
|
2001-08-01 17:54:41 +02:00
|
|
|
generated by @command{diff} with the @option{-u}, @option{-c}, or @option{-p}
|
1999-05-03 09:29:11 +02:00
|
|
|
option. Always send diffs from the old file to the new file. If you
|
2001-08-01 17:54:41 +02:00
|
|
|
wish to discuss something in the @command{ld} source, refer to it by
|
1999-10-08 15:56:33 +02:00
|
|
|
context, not by line number.
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
The line numbers in our development sources will not match those in your
|
|
|
|
sources. Your line numbers would convey no useful information to us.
|
|
|
|
@end itemize
|
|
|
|
|
|
|
|
Here are some things that are not necessary:
|
|
|
|
|
|
|
|
@itemize @bullet
|
|
|
|
@item
|
|
|
|
A description of the envelope of the bug.
|
|
|
|
|
|
|
|
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 @emph{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.
|
|
|
|
|
|
|
|
@item
|
|
|
|
A patch for the bug.
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
@item
|
|
|
|
A guess about what the bug is or what it depends on.
|
|
|
|
|
|
|
|
Such guesses are usually wrong. Even we cannot guess right about such
|
|
|
|
things without first using the debugger to find the facts.
|
|
|
|
@end itemize
|
|
|
|
|
2007-11-07 12:36:42 +01:00
|
|
|
@node GNU Free Documentation License
|
|
|
|
@appendix GNU Free Documentation License
|
2011-11-29 19:07:41 +01:00
|
|
|
|
2003-02-21 11:30:35 +01:00
|
|
|
@include fdl.texi
|
2000-11-06 21:27:26 +01:00
|
|
|
|
2008-02-26 09:25:46 +01:00
|
|
|
@node Binutils Index
|
|
|
|
@unnumbered Binutils Index
|
1999-05-03 09:29:11 +02:00
|
|
|
|
|
|
|
@printindex cp
|
|
|
|
|
|
|
|
@bye
|