1
0
Fork 0

arduino-0018-windows

This commit is contained in:
orange 2010-03-30 21:53:44 +02:00
parent 157fd6f1a1
commit f39fc49523
5182 changed files with 950586 additions and 0 deletions

View file

@ -0,0 +1,73 @@
<html lang="en">
<head>
<title>Architecture Selection - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Selecting-the-Target-System.html#Selecting-the-Target-System" title="Selecting the Target System">
<link rel="prev" href="Target-Selection.html#Target-Selection" title="Target Selection">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="Architecture-Selection"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="Target-Selection.html#Target-Selection">Target Selection</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="Selecting-the-Target-System.html#Selecting-the-Target-System">Selecting the Target System</a>
<hr><br>
</div>
<h3 class="section">17.2 Architecture Selection</h3>
<p>An <dfn>architecture</dfn> is a type of <span class="sc">cpu</span> 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 <span class="sc">cpu</span>.
<p>The command to list valid architecture values is <span class="samp">objdump -i</span> (the
second column contains the relevant information).
<p>Sample values: <span class="samp">m68k:68020</span>, <span class="samp">mips:3000</span>, <span class="samp">sparc</span>.
<h4 class="subheading"><span class="command">objdump</span> Architecture</h4>
<p>Ways to specify:
<ol type=1 start=1>
<li>command line option: <span class="option">-m</span> or <span class="option">--architecture</span>
<li>deduced from the input file
</ol>
<h4 class="subheading"><span class="command">objcopy</span>, <span class="command">nm</span>, <span class="command">size</span>, <span class="command">strings</span> Architecture</h4>
<p>Ways to specify:
<ol type=1 start=1>
<li>deduced from the input file
</ol>
</body></html>

View file

@ -0,0 +1,187 @@
<html lang="en">
<head>
<title>Binutils Index - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License" title="GNU Free Documentation License">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="Binutils-Index"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License">GNU Free Documentation License</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="unnumbered">Binutils Index</h2>
<ul class="index-cp" compact>
<li><a href="objdump.html#index-_002estab-87">.stab</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="addr2line.html#index-addr2line-118"><code>addr2line</code></a>: <a href="addr2line.html#addr2line">addr2line</a></li>
<li><a href="addr2line.html#index-address-to-file-name-and-line-number-119">address to file name and line number</a>: <a href="addr2line.html#addr2line">addr2line</a></li>
<li><a href="objdump.html#index-all-header-information_002c-object-file-94">all header information, object file</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="ar.html#index-ar-2"><code>ar</code></a>: <a href="ar.html#ar">ar</a></li>
<li><a href="ar.html#index-_0040command_007bar_007d-compatibility-10"><span class="command">ar</span> compatibility</a>: <a href="ar.html#ar">ar</a></li>
<li><a href="objdump.html#index-architecture-76">architecture</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-architectures-available-72">architectures available</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="ranlib.html#index-archive-contents-98">archive contents</a>: <a href="ranlib.html#ranlib">ranlib</a></li>
<li><a href="readelf.html#index-Archive-file-symbol-index-information-140">Archive file symbol index information</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="objdump.html#index-archive-headers-59">archive headers</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="ar.html#index-archives-3">archives</a>: <a href="ar.html#ar">ar</a></li>
<li><a href="dlltool.html#index-base-files-125">base files</a>: <a href="dlltool.html#dlltool">dlltool</a></li>
<li><a href="Bug-Criteria.html#index-bug-criteria-143">bug criteria</a>: <a href="Bug-Criteria.html#Bug-Criteria">Bug Criteria</a></li>
<li><a href="Bug-Reporting.html#index-bug-reports-147">bug reports</a>: <a href="Bug-Reporting.html#Bug-Reporting">Bug Reporting</a></li>
<li><a href="Reporting-Bugs.html#index-bugs-141">bugs</a>: <a href="Reporting-Bugs.html#Reporting-Bugs">Reporting Bugs</a></li>
<li><a href="Bug-Reporting.html#index-bugs_002c-reporting-148">bugs, reporting</a>: <a href="Bug-Reporting.html#Bug-Reporting">Bug Reporting</a></li>
<li><a href="c_002b_002bfilt.html#index-c_002b_002bfilt-115"><code>c++filt</code></a>: <a href="c_002b_002bfilt.html#c_002b_002bfilt">c++filt</a></li>
<li><a href="objcopy.html#index-changing-object-addresses-53">changing object addresses</a>: <a href="objcopy.html#objcopy">objcopy</a></li>
<li><a href="objcopy.html#index-changing-section-address-54">changing section address</a>: <a href="objcopy.html#objcopy">objcopy</a></li>
<li><a href="objcopy.html#index-changing-section-LMA-55">changing section LMA</a>: <a href="objcopy.html#objcopy">objcopy</a></li>
<li><a href="objcopy.html#index-changing-section-VMA-56">changing section VMA</a>: <a href="objcopy.html#objcopy">objcopy</a></li>
<li><a href="objcopy.html#index-changing-start-address-52">changing start address</a>: <a href="objcopy.html#objcopy">objcopy</a></li>
<li><a href="ar.html#index-collections-of-files-4">collections of files</a>: <a href="ar.html#ar">ar</a></li>
<li><a href="ar.html#index-compatibility_002c-_0040command_007bar_007d-9">compatibility, <span class="command">ar</span></a>: <a href="ar.html#ar">ar</a></li>
<li><a href="ar-cmdline.html#index-contents-of-archive-18">contents of archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="Bug-Criteria.html#index-crash-145">crash</a>: <a href="Bug-Criteria.html#Bug-Criteria">Bug Criteria</a></li>
<li><a href="ar-cmdline.html#index-creating-archives-23">creating archives</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="ar-cmdline.html#index-creating-thin-archive-27">creating thin archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="c_002b_002bfilt.html#index-cxxfilt-117"><code>cxxfilt</code></a>: <a href="c_002b_002bfilt.html#c_002b_002bfilt">c++filt</a></li>
<li><a href="ar-cmdline.html#index-dates-in-archive-24">dates in archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="objdump.html#index-debug-symbols-88">debug symbols</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="nm.html#index-debugging-symbols-36">debugging symbols</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="ar-cmdline.html#index-deleting-from-archive-13">deleting from archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="c_002b_002bfilt.html#index-demangling-C_002b_002b-symbols-116">demangling C++ symbols</a>: <a href="c_002b_002bfilt.html#c_002b_002bfilt">c++filt</a></li>
<li><a href="nm.html#index-demangling-in-nm-39">demangling in nm</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="addr2line.html#index-demangling-in-objdump-121">demangling in objdump</a>: <a href="addr2line.html#addr2line">addr2line</a></li>
<li><a href="objdump.html#index-demangling-in-objdump-63">demangling in objdump</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-disassembling-object-code-64">disassembling object code</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-disassembly-architecture-77">disassembly architecture</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-disassembly-endianness-67">disassembly endianness</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-disassembly_002c-with-source-83">disassembly, with source</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="strip.html#index-discarding-symbols-113">discarding symbols</a>: <a href="strip.html#strip">strip</a></li>
<li><a href="dlltool.html#index-DLL-122">DLL</a>: <a href="dlltool.html#dlltool">dlltool</a></li>
<li><a href="dlltool.html#index-dlltool-123"><code>dlltool</code></a>: <a href="dlltool.html#dlltool">dlltool</a></li>
<li><a href="objdump.html#index-DWARF-84">DWARF</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-dynamic-relocation-entries_002c-in-object-file-79">dynamic relocation entries, in object file</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-dynamic-symbol-table-entries_002c-printing-93">dynamic symbol table entries, printing</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="nm.html#index-dynamic-symbols-40">dynamic symbols</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="readelf.html#index-ELF-dynamic-section-information-138">ELF dynamic section information</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="readelf.html#index-ELF-file-header-information-128">ELF file header information</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="readelf.html#index-ELF-file-information-126">ELF file information</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="readelf.html#index-ELF-notes-135">ELF notes</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="objdump.html#index-ELF-object-file-format-89">ELF object file format</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="readelf.html#index-ELF-program-header-information-129">ELF program header information</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="readelf.html#index-ELF-reloc-information-136">ELF reloc information</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="readelf.html#index-ELF-section-group-information-132">ELF section group information</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="readelf.html#index-ELF-section-information-133">ELF section information</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="readelf.html#index-ELF-segment-information-130">ELF segment information</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="readelf.html#index-ELF-symbol-table-information-134">ELF symbol table information</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="readelf.html#index-ELF-version-sections-informations-139">ELF version sections informations</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="objdump.html#index-endianness-66">endianness</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="Bug-Criteria.html#index-error-on-valid-input-146">error on valid input</a>: <a href="Bug-Criteria.html#Bug-Criteria">Bug Criteria</a></li>
<li><a href="nm.html#index-external-symbols-48">external symbols</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="ar-cmdline.html#index-extract-from-archive-21">extract from archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="Bug-Criteria.html#index-fatal-signal-144">fatal signal</a>: <a href="Bug-Criteria.html#Bug-Criteria">Bug Criteria</a></li>
<li><a href="nm.html#index-file-name-34">file name</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="objdump.html#index-header-information_002c-all-95">header information, all</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="dlltool.html#index-input-_002edef-file-124">input .def file</a>: <a href="dlltool.html#dlltool">dlltool</a></li>
<li><a href="nm.html#index-input-file-name-33">input file name</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="ar.html#index-libraries-6">libraries</a>: <a href="ar.html#ar">ar</a></li>
<li><a href="strings.html#index-listings-strings-107">listings strings</a>: <a href="strings.html#strings">strings</a></li>
<li><a href="objdump.html#index-machine-instructions-65">machine instructions</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="ar-cmdline.html#index-moving-in-archive-14">moving in archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="ar-scripts.html#index-MRI-compatibility_002c-_0040command_007bar_007d-29">MRI compatibility, <span class="command">ar</span></a>: <a href="ar-scripts.html#ar-scripts">ar scripts</a></li>
<li><a href="ar-cmdline.html#index-name-duplication-in-archive-20">name duplication in archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="ar.html#index-name-length-5">name length</a>: <a href="ar.html#ar">ar</a></li>
<li><a href="nm.html#index-nm-32"><code>nm</code></a>: <a href="nm.html#nm">nm</a></li>
<li><a href="nm.html#index-_0040command_007bnm_007d-compatibility-38"><span class="command">nm</span> compatibility</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="nm.html#index-_0040command_007bnm_007d-format-37"><span class="command">nm</span> format</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="ar-cmdline.html#index-not-writing-archive-index-26">not writing archive index</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="objdump.html#index-objdump-58"><code>objdump</code></a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="size.html#index-object-code-format-105">object code format</a>: <a href="size.html#size">size</a></li>
<li><a href="addr2line.html#index-object-code-format-120">object code format</a>: <a href="addr2line.html#addr2line">addr2line</a></li>
<li><a href="nm.html#index-object-code-format-47">object code format</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="strings.html#index-object-code-format-110">object code format</a>: <a href="strings.html#strings">strings</a></li>
<li><a href="objdump.html#index-object-code-format-62">object code format</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-object-file-header-68">object file header</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-object-file-information-57">object file information</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-object-file-offsets-69">object file offsets</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-object-file-sections-81">object file sections</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-object-formats-available-73">object formats available</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="ar-cmdline.html#index-operations-on-archive-12">operations on archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="ar-cmdline.html#index-printing-from-archive-15">printing from archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="strings.html#index-printing-strings-108">printing strings</a>: <a href="strings.html#strings">strings</a></li>
<li><a href="ar-cmdline.html#index-quick-append-to-archive-16">quick append to archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="size.html#index-radix-for-section-sizes-104">radix for section sizes</a>: <a href="size.html#size">size</a></li>
<li><a href="ranlib.html#index-ranlib-97"><code>ranlib</code></a>: <a href="ranlib.html#ranlib">ranlib</a></li>
<li><a href="readelf.html#index-readelf-127"><code>readelf</code></a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="ar-cmdline.html#index-relative-placement-in-archive-22">relative placement in archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="objdump.html#index-relocation-entries_002c-in-object-file-78">relocation entries, in object file</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="strip.html#index-removing-symbols-112">removing symbols</a>: <a href="strip.html#strip">strip</a></li>
<li><a href="ar-cmdline.html#index-repeated-names-in-archive-19">repeated names in archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="ar-cmdline.html#index-replacement-in-archive-17">replacement in archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="Reporting-Bugs.html#index-reporting-bugs-142">reporting bugs</a>: <a href="Reporting-Bugs.html#Reporting-Bugs">Reporting Bugs</a></li>
<li><a href="ar-scripts.html#index-scripts_002c-_0040command_007bar_007d-30">scripts, <span class="command">ar</span></a>: <a href="ar-scripts.html#ar-scripts">ar scripts</a></li>
<li><a href="objdump.html#index-section-addresses-in-objdump-60">section addresses in objdump</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-section-headers-71">section headers</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-section-information-74">section information</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="size.html#index-section-sizes-101">section sizes</a>: <a href="size.html#size">size</a></li>
<li><a href="objdump.html#index-sections_002c-full-contents-80">sections, full contents</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="size.html#index-size-100"><code>size</code></a>: <a href="size.html#size">size</a></li>
<li><a href="size.html#index-_0040command_007bsize_007d-display-format-102"><span class="command">size</span> display format</a>: <a href="size.html#size">size</a></li>
<li><a href="size.html#index-_0040command_007bsize_007d-number-format-103"><span class="command">size</span> number format</a>: <a href="size.html#size">size</a></li>
<li><a href="nm.html#index-sorting-symbols-45">sorting symbols</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="objdump.html#index-source-code-context-70">source code context</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-source-disassembly-82">source disassembly</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="nm.html#index-source-file-name-35">source file name</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="objdump.html#index-source-filenames-for-object-files-75">source filenames for object files</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-stab-86">stab</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-start_002daddress-90">start-address</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-stop_002daddress-91">stop-address</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="strings.html#index-strings-106"><code>strings</code></a>: <a href="strings.html#strings">strings</a></li>
<li><a href="strings.html#index-strings_002c-printing-109">strings, printing</a>: <a href="strings.html#strings">strings</a></li>
<li><a href="strip.html#index-strip-111"><code>strip</code></a>: <a href="strip.html#strip">strip</a></li>
<li><a href="ranlib.html#index-symbol-index-99">symbol index</a>: <a href="ranlib.html#ranlib">ranlib</a></li>
<li><a href="ar.html#index-symbol-index-7">symbol index</a>: <a href="ar.html#ar">ar</a></li>
<li><a href="nm.html#index-symbol-index_002c-listing-46">symbol index, listing</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="nm.html#index-symbol-line-numbers-44">symbol line numbers</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="objdump.html#index-symbol-table-entries_002c-printing-92">symbol table entries, printing</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="nm.html#index-symbols-31">symbols</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="strip.html#index-symbols_002c-discarding-114">symbols, discarding</a>: <a href="strip.html#strip">strip</a></li>
<li><a href="ar.html#index-thin-archives-8">thin archives</a>: <a href="ar.html#ar">ar</a></li>
<li><a href="nm.html#index-undefined-symbols-49">undefined symbols</a>: <a href="nm.html#nm">nm</a></li>
<li><a href="ar-cmdline.html#index-Unix-compatibility_002c-_0040command_007bar_007d-11">Unix compatibility, <span class="command">ar</span></a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="readelf.html#index-unwind-information-137">unwind information</a>: <a href="readelf.html#readelf">readelf</a></li>
<li><a href="ar-cmdline.html#index-updating-an-archive-28">updating an archive</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
<li><a href="index.html#index-version-1">version</a>: <a href="index.html#Top">Top</a></li>
<li><a href="objdump.html#index-VMA-in-objdump-61">VMA in objdump</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="objdump.html#index-wide-output_002c-printing-96">wide output, printing</a>: <a href="objdump.html#objdump">objdump</a></li>
<li><a href="ar-cmdline.html#index-writing-archive-index-25">writing archive index</a>: <a href="ar-cmdline.html#ar-cmdline">ar cmdline</a></li>
</ul></body></html>

View file

@ -0,0 +1,62 @@
<html lang="en">
<head>
<title>Bug Criteria - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Reporting-Bugs.html#Reporting-Bugs" title="Reporting Bugs">
<link rel="next" href="Bug-Reporting.html#Bug-Reporting" title="Bug Reporting">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="Bug-Criteria"></a>Next:&nbsp;<a rel="next" accesskey="n" href="Bug-Reporting.html#Bug-Reporting">Bug Reporting</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="Reporting-Bugs.html#Reporting-Bugs">Reporting Bugs</a>
<hr><br>
</div>
<h3 class="section">18.1 Have You Found a Bug?</h3>
<p><a name="index-bug-criteria-143"></a>
If you are not sure whether you have found a bug, here are some guidelines:
<a name="index-fatal-signal-144"></a>
<a name="index-crash-145"></a>
<ul><li>If a binary utility gets a fatal signal, for any input whatever, that is
a bug. Reliable utilities never crash.
<p><a name="index-error-on-valid-input-146"></a><li>If a binary utility produces an error message for valid input, that is a
bug.
<li>If you are an experienced user of binary utilities, your suggestions for
improvement are welcome in any case.
</ul>
</body></html>

View file

@ -0,0 +1,190 @@
<html lang="en">
<head>
<title>Bug Reporting - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Reporting-Bugs.html#Reporting-Bugs" title="Reporting Bugs">
<link rel="prev" href="Bug-Criteria.html#Bug-Criteria" title="Bug Criteria">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="Bug-Reporting"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="Bug-Criteria.html#Bug-Criteria">Bug Criteria</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="Reporting-Bugs.html#Reporting-Bugs">Reporting Bugs</a>
<hr><br>
</div>
<h3 class="section">18.2 How to Report Bugs</h3>
<p><a name="index-bug-reports-147"></a><a name="index-bugs_002c-reporting-148"></a>
A number of companies and individuals offer support for <span class="sc">gnu</span>
products. If you obtained the binary utilities from a support
organization, we recommend you contact that organization first.
<p>You can find contact information for many support companies and
individuals in the file <span class="file">etc/SERVICE</span> in the <span class="sc">gnu</span> Emacs
distribution.
<p>In any event, we also recommend that you send bug reports for the binary
utilities to <a href="http://www.sourceware.org/bugzilla/">http://www.sourceware.org/bugzilla/</a>.
<p>The fundamental principle of reporting bugs usefully is this:
<strong>report all the facts</strong>. If you are not sure whether to state a
fact or leave it out, state it!
<p>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.
<p>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.
<p>Sometimes people give a few sketchy facts and ask, &ldquo;Does this ring a
bell?&rdquo; 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.
<p>To enable us to fix the bug, you should include all these things:
<ul>
<li>The version of the utility. Each utility announces it if you start it
with the <span class="option">--version</span> argument.
<p>Without this, we will not know whether there is any point in looking for
the bug in the current version of the binary utilities.
<li>Any patches you may have applied to the source, including any patches
made to the <code>BFD</code> library.
<li>The type of machine you are using, and the operating system name and
version number.
<li>What compiler (and its version) was used to compile the utilities&mdash;e.g.
&ldquo;<code>gcc-2.7</code>&rdquo;.
<li>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.
<p>If we were to try to guess the arguments, we would probably guess wrong
and then we might not encounter the bug.
<li>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
generally most helpful to send the actual object files.
<p>If the source files were produced exclusively using <span class="sc">gnu</span> programs
(e.g., <span class="command">gcc</span>, <span class="command">gas</span>, and/or the <span class="sc">gnu</span> <span class="command">ld</span>), then it
may be OK to send the source files rather than the object files. In
this case, be sure to say exactly what version of <span class="command">gcc</span>, or
whatever, was used to produce the object files. Also say how
<span class="command">gcc</span>, or whatever, was configured.
<li>A description of what behavior you observe that you believe is
incorrect. For example, &ldquo;It gets a fatal signal.&rdquo;
<p>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.
<p>Even if the problem you experience is a fatal signal, you should still
say so explicitly. Suppose something strange is going on, such as your
copy of the utility is out of sync, or you have encountered a bug in
the C library on your system. (This has happened!) Your copy might
crash and ours would not. If you told us to expect a crash, then when
ours fails to crash, we would know that the bug was not happening for
us. If you had not told us to expect a crash, then we would not be able
to draw any conclusion from our observations.
<li>If you wish to suggest changes to the source, send us context diffs, as
generated by <span class="command">diff</span> with the <span class="option">-u</span>, <span class="option">-c</span>, or <span class="option">-p</span>
option. Always send diffs from the old file to the new file. If you
wish to discuss something in the <span class="command">ld</span> source, refer to it by
context, not by line number.
<p>The line numbers in our development sources will not match those in your
sources. Your line numbers would convey no useful information to us.
</ul>
<p>Here are some things that are not necessary:
<ul>
<li>A description of the envelope of the bug.
<p>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.
<p>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.
<p>Of course, if you can find a simpler example to report <em>instead</em>
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.
<p>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.
<li>A patch for the bug.
<p>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.
<p>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.
<p>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.
<li>A guess about what the bug is or what it depends on.
<p>Such guesses are usually wrong. Even we cannot guess right about such
things without first using the debugger to find the facts.
</ul>
</body></html>

View file

@ -0,0 +1,76 @@
<html lang="en">
<head>
<title>Common Options - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="dlltool.html#dlltool" title="dlltool">
<link rel="next" href="Selecting-the-Target-System.html#Selecting-the-Target-System" title="Selecting the Target System">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="Common-Options"></a>Next:&nbsp;<a rel="next" accesskey="n" href="Selecting-the-Target-System.html#Selecting-the-Target-System">Selecting the Target System</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="dlltool.html#dlltool">dlltool</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">16 Common Options</h2>
<p>The following command-line options are supported by all of the
programs described in this manual.
<!-- man begin OPTIONS -->
<dl>
<!-- This file is designed to be included in manuals that use -->
<!-- expandargv. -->
<dt><span class="env">@</span><var>file</var><dd>Read command-line options from <var>file</var>. The options read are
inserted in place of the original @<var>file</var> option. If <var>file</var>
does not exist, or cannot be read, then the option will be treated
literally, and not removed.
<p>Options in <var>file</var> are separated by whitespace. A whitespace
character may be included in an option by surrounding the entire
option in either single or double quotes. Any character (including a
backslash) may be included by prefixing the character to be included
with a backslash. The <var>file</var> may itself contain additional
@<var>file</var> options; any such options will be processed recursively.
<!-- man end -->
<br><dt><span class="env">--help</span><dd>Display the command-line options supported by the program.
<br><dt><span class="env">--version</span><dd>Display the version number of the program.
<!-- man begin OPTIONS -->
</dl>
<!-- man end -->
</body></html>

View file

@ -0,0 +1,459 @@
<html lang="en">
<head>
<title>GNU Free Documentation License - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="Reporting-Bugs.html#Reporting-Bugs" title="Reporting Bugs">
<link rel="next" href="Binutils-Index.html#Binutils-Index" title="Binutils Index">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="GNU-Free-Documentation-License"></a>Next:&nbsp;<a rel="next" accesskey="n" href="Binutils-Index.html#Binutils-Index">Binutils Index</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="Reporting-Bugs.html#Reporting-Bugs">Reporting Bugs</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="appendix">Appendix A GNU Free Documentation License</h2>
<!-- The GNU Free Documentation License. -->
<div align="center">Version 1.2, November 2002</div>
<!-- This file is intended to be included within another document, -->
<!-- hence no sectioning command or @node. -->
<pre class="display"> Copyright &copy; 2000,2001,2002 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
</pre>
<ol type=1 start=0>
<li>PREAMBLE
<p>The purpose of this License is to make a manual, textbook, or other
functional and useful document <dfn>free</dfn> in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.
<p>This License is a kind of &ldquo;copyleft&rdquo;, which means that derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.
<p>We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
<li>APPLICABILITY AND DEFINITIONS
<p>This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
work under the conditions stated herein. The &ldquo;Document&rdquo;, below,
refers to any such manual or work. Any member of the public is a
licensee, and is addressed as &ldquo;you&rdquo;. You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
<p>A &ldquo;Modified Version&rdquo; of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
<p>A &ldquo;Secondary Section&rdquo; is a named appendix or a front-matter section
of the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document's overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not explain
any mathematics.) The relationship could be a matter of historical
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
<p>The &ldquo;Invariant Sections&rdquo; are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
<p>The &ldquo;Cover Texts&rdquo; are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
<p>A &ldquo;Transparent&rdquo; copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
pixels) generic paint programs or (for drawings) some widely available
drawing editor, and that is suitable for input to text formatters or
for automatic translation to a variety of formats suitable for input
to text formatters. A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not &ldquo;Transparent&rdquo; is called &ldquo;Opaque&rdquo;.
<p>Examples of suitable formats for Transparent copies include plain
<span class="sc">ascii</span> without markup, Texinfo input format, LaTeX input
format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly available
<acronym>DTD</acronym>, and standard-conforming simple <acronym>HTML</acronym>,
PostScript or <acronym>PDF</acronym> designed for human modification. Examples
of transparent image formats include <acronym>PNG</acronym>, <acronym>XCF</acronym> and
<acronym>JPG</acronym>. Opaque formats include proprietary formats that can be
read and edited only by proprietary word processors, <acronym>SGML</acronym> or
<acronym>XML</acronym> for which the <acronym>DTD</acronym> and/or processing tools are
not generally available, and the machine-generated <acronym>HTML</acronym>,
PostScript or <acronym>PDF</acronym> produced by some word processors for
output purposes only.
<p>The &ldquo;Title Page&rdquo; means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, &ldquo;Title Page&rdquo; means
the text near the most prominent appearance of the work's title,
preceding the beginning of the body of the text.
<p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as &ldquo;Acknowledgements&rdquo;,
&ldquo;Dedications&rdquo;, &ldquo;Endorsements&rdquo;, or &ldquo;History&rdquo;.) To &ldquo;Preserve the Title&rdquo;
of such a section when you modify the Document means that it remains a
section &ldquo;Entitled XYZ&rdquo; according to this definition.
<p>The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
<li>VERBATIM COPYING
<p>You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
conditions whatsoever to those of this License. You may not use
technical measures to obstruct or control the reading or further
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
<p>You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
<li>COPYING IN QUANTITY
<p>If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
Document's license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
you as the publisher of these copies. The front cover must present
the full title with all words of the title equally prominent and
visible. You may add other material on the covers in addition.
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.
<p>If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
<p>If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
public has access to download using public-standard network protocols
a complete Transparent copy of the Document, free of added material.
If you use the latter option, you must take reasonably prudent steps,
when you begin distribution of Opaque copies in quantity, to ensure
that this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.
<p>It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
<li>MODIFICATIONS
<p>You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:
<ol type=A start=1>
<li>Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
<li>List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
<li>State on the Title page the name of the publisher of the
Modified Version, as the publisher.
<li>Preserve all the copyright notices of the Document.
<li>Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
<li>Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
<li>Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document's license notice.
<li>Include an unaltered copy of this License.
<li>Preserve the section Entitled &ldquo;History&rdquo;, Preserve its Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled &ldquo;History&rdquo; in the Document, create one
stating the title, year, authors, and publisher of the Document as
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
<li>Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the &ldquo;History&rdquo; section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
<li>For any section Entitled &ldquo;Acknowledgements&rdquo; or &ldquo;Dedications&rdquo;, Preserve
the Title of the section, and preserve in the section all the
substance and tone of each of the contributor acknowledgements and/or
dedications given therein.
<li>Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
<li>Delete any section Entitled &ldquo;Endorsements&rdquo;. Such a section
may not be included in the Modified Version.
<li>Do not retitle any existing section to be Entitled &ldquo;Endorsements&rdquo; or
to conflict in title with any Invariant Section.
<li>Preserve any Warranty Disclaimers.
</ol>
<p>If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
list of Invariant Sections in the Modified Version's license notice.
These titles must be distinct from any other section titles.
<p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it contains
nothing but endorsements of your Modified Version by various
parties&mdash;for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
<p>You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
through arrangements made by) any one entity. If the Document already
includes a cover text for the same cover, previously added by you or
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
<p>The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
<li>COMBINING DOCUMENTS
<p>You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.
<p>The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
adding at the end of it, in parentheses, the name of the original
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.
<p>In the combination, you must combine any sections Entitled &ldquo;History&rdquo;
in the various original documents, forming one section Entitled
&ldquo;History&rdquo;; likewise combine any sections Entitled &ldquo;Acknowledgements&rdquo;,
and any sections Entitled &ldquo;Dedications&rdquo;. You must delete all
sections Entitled &ldquo;Endorsements.&rdquo;
<li>COLLECTIONS OF DOCUMENTS
<p>You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
<p>You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
<li>AGGREGATION WITH INDEPENDENT WORKS
<p>A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an &ldquo;aggregate&rdquo; if the copyright
resulting from the compilation is not used to limit the legal rights
of the compilation's users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.
<p>If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
the entire aggregate, the Document's Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
<li>TRANSLATION
<p>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections. You may include a
translation of this License, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also include
the original English version of this License and the original versions
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.
<p>If a section in the Document is Entitled &ldquo;Acknowledgements&rdquo;,
&ldquo;Dedications&rdquo;, or &ldquo;History&rdquo;, the requirement (section 4) to Preserve
its Title (section 1) will typically require changing the actual
title.
<li>TERMINATION
<p>You may not copy, modify, sublicense, or distribute the Document except
as expressly provided for under this License. Any other attempt to
copy, modify, sublicense or distribute the Document is void, and will
automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this
License will not have their licenses terminated so long as such
parties remain in full compliance.
<li>FUTURE REVISIONS OF THIS LICENSE
<p>The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
<a href="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</a>.
<p>Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License &ldquo;or any later version&rdquo; applies to it, you have the option of
following the terms and conditions either of that specified version or
of any later version that has been published (not as a draft) by the
Free Software Foundation. If the Document does not specify a version
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation.
</ol>
<h3 class="heading">ADDENDUM: How to use this License for your documents</h3>
<p>To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:
<pre class="smallexample"> Copyright (C) <var>year</var> <var>your name</var>.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled ``GNU
Free Documentation License''.
</pre>
<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
replace the &ldquo;with<small class="dots">...</small>Texts.&rdquo; line with this:
<pre class="smallexample"> with the Invariant Sections being <var>list their titles</var>, with
the Front-Cover Texts being <var>list</var>, and with the Back-Cover Texts
being <var>list</var>.
</pre>
<p>If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
<p>If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.
<!-- Local Variables: -->
<!-- ispell-local-pdict: "ispell-dict" -->
<!-- End: -->
</body></html>

View file

@ -0,0 +1,65 @@
<html lang="en">
<head>
<title>Reporting Bugs - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="Selecting-the-Target-System.html#Selecting-the-Target-System" title="Selecting the Target System">
<link rel="next" href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License" title="GNU Free Documentation License">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="Reporting-Bugs"></a>Next:&nbsp;<a rel="next" accesskey="n" href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License">GNU Free Documentation License</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="Selecting-the-Target-System.html#Selecting-the-Target-System">Selecting the Target System</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">18 Reporting Bugs</h2>
<p><a name="index-bugs-141"></a><a name="index-reporting-bugs-142"></a>
Your bug reports play an essential role in making the binary utilities
reliable.
<p>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.
<p>In order for a bug report to serve its purpose, you must include the
information that enables us to fix the bug.
<ul class="menu">
<li><a accesskey="1" href="Bug-Criteria.html#Bug-Criteria">Bug Criteria</a>: Have you found a bug?
<li><a accesskey="2" href="Bug-Reporting.html#Bug-Reporting">Bug Reporting</a>: How to report bugs
</ul>
</body></html>

View file

@ -0,0 +1,72 @@
<html lang="en">
<head>
<title>Selecting the Target System - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="Common-Options.html#Common-Options" title="Common Options">
<link rel="next" href="Reporting-Bugs.html#Reporting-Bugs" title="Reporting Bugs">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="Selecting-the-Target-System"></a>Next:&nbsp;<a rel="next" accesskey="n" href="Reporting-Bugs.html#Reporting-Bugs">Reporting Bugs</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="Common-Options.html#Common-Options">Common Options</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">17 Selecting the Target System</h2>
<p>You can specify two aspects of the target system to the <span class="sc">gnu</span>
binary file utilities, each in several ways:
<ul>
<li>the target
<li>the architecture
</ul>
<p>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.
<p>The commands to list valid values only list the values for which the
programs you are running were configured. If they were configured with
<span class="option">--enable-targets=all</span>, the commands list most of the available
values, but a few are left out; not all targets can be configured in at
once because some of them can only be configured <dfn>native</dfn> (on hosts
with the same type as the target system).
<ul class="menu">
<li><a accesskey="1" href="Target-Selection.html#Target-Selection">Target Selection</a>
<li><a accesskey="2" href="Architecture-Selection.html#Architecture-Selection">Architecture Selection</a>
</ul>
</body></html>

View file

@ -0,0 +1,117 @@
<html lang="en">
<head>
<title>Target Selection - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Selecting-the-Target-System.html#Selecting-the-Target-System" title="Selecting the Target System">
<link rel="next" href="Architecture-Selection.html#Architecture-Selection" title="Architecture Selection">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="Target-Selection"></a>Next:&nbsp;<a rel="next" accesskey="n" href="Architecture-Selection.html#Architecture-Selection">Architecture Selection</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="Selecting-the-Target-System.html#Selecting-the-Target-System">Selecting the Target System</a>
<hr><br>
</div>
<h3 class="section">17.1 Target Selection</h3>
<p>A <dfn>target</dfn> is an object file format. A given target may be
supported for multiple architectures (see <a href="Architecture-Selection.html#Architecture-Selection">Architecture Selection</a>).
A target selection may also have variations for different operating
systems or architectures.
<p>The command to list valid target values is <span class="samp">objdump -i</span>
(the first column of output contains the relevant information).
<p>Some sample values are: <span class="samp">a.out-hp300bsd</span>, <span class="samp">ecoff-littlemips</span>,
<span class="samp">a.out-sunos-big</span>.
<p>You can also specify a target using a configuration triplet. This is
the same sort of name that is passed to <span class="file">configure</span> to specify a
target. When you use a configuration triplet as an argument, it must be
fully canonicalized. You can see the canonical version of a triplet by
running the shell script <span class="file">config.sub</span> which is included with the
sources.
<p>Some sample configuration triplets are: <span class="samp">m68k-hp-bsd</span>,
<span class="samp">mips-dec-ultrix</span>, <span class="samp">sparc-sun-sunos</span>.
<h4 class="subheading"><span class="command">objdump</span> Target</h4>
<p>Ways to specify:
<ol type=1 start=1>
<li>command line option: <span class="option">-b</span> or <span class="option">--target</span>
<li>environment variable <code>GNUTARGET</code>
<li>deduced from the input file
</ol>
<h4 class="subheading"><span class="command">objcopy</span> and <span class="command">strip</span> Input Target</h4>
<p>Ways to specify:
<ol type=1 start=1>
<li>command line options: <span class="option">-I</span> or <span class="option">--input-target</span>, or <span class="option">-F</span> or <span class="option">--target</span>
<li>environment variable <code>GNUTARGET</code>
<li>deduced from the input file
</ol>
<h4 class="subheading"><span class="command">objcopy</span> and <span class="command">strip</span> Output Target</h4>
<p>Ways to specify:
<ol type=1 start=1>
<li>command line options: <span class="option">-O</span> or <span class="option">--output-target</span>, or <span class="option">-F</span> or <span class="option">--target</span>
<li>the input target (see &ldquo;<span class="command">objcopy</span> and <span class="command">strip</span> Input Target&rdquo; above)
<li>environment variable <code>GNUTARGET</code>
<li>deduced from the input file
</ol>
<h4 class="subheading"><span class="command">nm</span>, <span class="command">size</span>, and <span class="command">strings</span> Target</h4>
<p>Ways to specify:
<ol type=1 start=1>
<li>command line option: <span class="option">--target</span>
<li>environment variable <code>GNUTARGET</code>
<li>deduced from the input file
</ol>
</body></html>

View file

@ -0,0 +1,126 @@
<html lang="en">
<head>
<title>addr2line - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="c_002b_002bfilt.html#c_002b_002bfilt" title="c++filt">
<link rel="next" href="nlmconv.html#nlmconv" title="nlmconv">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="addr2line"></a>Next:&nbsp;<a rel="next" accesskey="n" href="nlmconv.html#nlmconv">nlmconv</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="c_002b_002bfilt.html#c_002b_002bfilt">c++filt</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">10 addr2line</h2>
<p><a name="index-addr2line-118"></a><a name="index-address-to-file-name-and-line-number-119"></a>
<!-- man title addr2line convert addresses into file names and line numbers. -->
<pre class="smallexample"> <!-- man begin SYNOPSIS addr2line -->
addr2line [<span class="option">-b</span> <var>bfdname</var>|<span class="option">--target=</span><var>bfdname</var>]
[<span class="option">-C</span>|<span class="option">--demangle</span>[=<var>style</var>]]
[<span class="option">-e</span> <var>filename</var>|<span class="option">--exe=</span><var>filename</var>]
[<span class="option">-f</span>|<span class="option">--functions</span>] [<span class="option">-s</span>|<span class="option">--basename</span>]
[<span class="option">-i</span>|<span class="option">--inlines</span>]
[<span class="option">-j</span>|<span class="option">--section=</span><var>name</var>]
[<span class="option">-H</span>|<span class="option">--help</span>] [<span class="option">-V</span>|<span class="option">--version</span>]
[addr addr ...]
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION addr2line -->
<p><span class="command">addr2line</span> 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.
<p>The executable or relocatable object to use is specified with the <span class="option">-e</span>
option. The default is the file <span class="file">a.out</span>. The section in the relocatable
object to use is specified with the <span class="option">-j</span> option.
<p><span class="command">addr2line</span> has two modes of operation.
<p>In the first, hexadecimal addresses are specified on the command line,
and <span class="command">addr2line</span> displays the file name and line number for each
address.
<p>In the second, <span class="command">addr2line</span> reads hexadecimal addresses from
standard input, and prints the file name and line number for each
address on standard output. In this mode, <span class="command">addr2line</span> may be used
in a pipe to convert dynamically chosen addresses.
<p>The format of the output is <span class="samp">FILENAME:LINENO</span>. The file name and
line number for each address is printed on a separate line. If the
<span class="command">-f</span> option is used, then each <span class="samp">FILENAME:LINENO</span> line is
preceded by a <span class="samp">FUNCTIONNAME</span> line which is the name of the function
containing the address.
<p>If the file name or function name can not be determined,
<span class="command">addr2line</span> will print two question marks in their place. If the
line number can not be determined, <span class="command">addr2line</span> will print 0.
<!-- man end -->
<!-- man begin OPTIONS addr2line -->
<p>The long and short forms of options, shown here as alternatives, are
equivalent.
<dl>
<dt><span class="env">-b </span><var>bfdname</var><dt><span class="env">--target=</span><var>bfdname</var><dd><a name="index-object-code-format-120"></a>Specify that the object-code format for the object files is
<var>bfdname</var>.
<br><dt><span class="env">-C</span><dt><span class="env">--demangle[=</span><var>style</var><span class="env">]</span><dd><a name="index-demangling-in-objdump-121"></a>Decode (<dfn>demangle</dfn>) low-level symbol names into user-level names.
Besides removing any initial underscore prepended by the system, this
makes C++ function names readable. Different compilers have different
mangling styles. The optional demangling style argument can be used to
choose an appropriate demangling style for your compiler. See <a href="c_002b_002bfilt.html#c_002b_002bfilt">c++filt</a>,
for more information on demangling.
<br><dt><span class="env">-e </span><var>filename</var><dt><span class="env">--exe=</span><var>filename</var><dd>Specify the name of the executable for which addresses should be
translated. The default file is <span class="file">a.out</span>.
<br><dt><span class="env">-f</span><dt><span class="env">--functions</span><dd>Display function names as well as file and line number information.
<br><dt><span class="env">-s</span><dt><span class="env">--basenames</span><dd>Display only the base of each file name.
<br><dt><span class="env">-i</span><dt><span class="env">--inlines</span><dd>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</code> inlines
<code>callee1</code> which inlines <code>callee2</code>, and address is from
<code>callee2</code>, the source information for <code>callee1</code> and <code>main</code>
will also be printed.
<br><dt><span class="env">-j</span><dt><span class="env">--section</span><dd>Read offsets relative to the specified section instead of absolute addresses.
</dl>
<!-- man end -->
</body></html>

View file

@ -0,0 +1,240 @@
<html lang="en">
<head>
<title>ar cmdline - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="ar.html#ar" title="ar">
<link rel="next" href="ar-scripts.html#ar-scripts" title="ar scripts">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="ar-cmdline"></a>Next:&nbsp;<a rel="next" accesskey="n" href="ar-scripts.html#ar-scripts">ar scripts</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="ar.html#ar">ar</a>
<hr><br>
</div>
<h3 class="section">1.1 Controlling <span class="command">ar</span> on the Command Line</h3>
<pre class="smallexample"> <!-- man begin SYNOPSIS ar -->
ar [<span class="option">-X32_64</span>] [<span class="option">-</span>]<var>p</var>[<var>mod</var> [<var>relpos</var>] [<var>count</var>]] <var>archive</var> [<var>member</var>...]
<!-- man end -->
</pre>
<p><a name="index-Unix-compatibility_002c-_0040command_007bar_007d-11"></a>When you use <span class="command">ar</span> in the Unix style, <span class="command">ar</span> insists on at least two
arguments to execute: one keyletter specifying the <em>operation</em>
(optionally accompanied by other keyletters specifying
<em>modifiers</em>), and the archive name to act on.
<p>Most operations can also accept further <var>member</var> arguments,
specifying particular files to operate on.
<!-- man begin OPTIONS ar -->
<p><span class="sc">gnu</span> <span class="command">ar</span> allows you to mix the operation code <var>p</var> and modifier
flags <var>mod</var> in any order, within the first command-line argument.
<p>If you wish, you may begin the first command-line argument with a
dash.
<p><a name="index-operations-on-archive-12"></a>The <var>p</var> keyletter specifies what operation to execute; it may be
any of the following, but you must specify only one of them:
<dl>
<dt><span class="samp">d</span><dd><a name="index-deleting-from-archive-13"></a><em>Delete</em> modules from the archive. Specify the names of modules to
be deleted as <var>member</var><small class="dots">...</small>; the archive is untouched if you
specify no files to delete.
<p>If you specify the <span class="samp">v</span> modifier, <span class="command">ar</span> lists each module
as it is deleted.
<br><dt><span class="samp">m</span><dd><a name="index-moving-in-archive-14"></a>Use this operation to <em>move</em> members in an archive.
<p>The ordering of members in an archive can make a difference in how
programs are linked using the library, if a symbol is defined in more
than one member.
<p>If no modifiers are used with <code>m</code>, any members you name in the
<var>member</var> arguments are moved to the <em>end</em> of the archive;
you can use the <span class="samp">a</span>, <span class="samp">b</span>, or <span class="samp">i</span> modifiers to move them to a
specified place instead.
<br><dt><span class="samp">p</span><dd><a name="index-printing-from-archive-15"></a><em>Print</em> the specified members of the archive, to the standard
output file. If the <span class="samp">v</span> modifier is specified, show the member
name before copying its contents to standard output.
<p>If you specify no <var>member</var> arguments, all the files in the archive are
printed.
<br><dt><span class="samp">q</span><dd><a name="index-quick-append-to-archive-16"></a><em>Quick append</em>; Historically, add the files <var>member</var><small class="dots">...</small> to the end of
<var>archive</var>, without checking for replacement.
<p>The modifiers <span class="samp">a</span>, <span class="samp">b</span>, and <span class="samp">i</span> do <em>not</em> affect this
operation; new members are always placed at the end of the archive.
<p>The modifier <span class="samp">v</span> makes <span class="command">ar</span> list each file as it is appended.
<p>Since the point of this operation is speed, the archive's symbol table
index is not updated, even if it already existed; you can use <span class="samp">ar s</span> or
<span class="command">ranlib</span> explicitly to update the symbol table index.
<p>However, too many different systems assume quick append rebuilds the
index, so <span class="sc">gnu</span> <span class="command">ar</span> implements <span class="samp">q</span> as a synonym for <span class="samp">r</span>.
<br><dt><span class="samp">r</span><dd><a name="index-replacement-in-archive-17"></a>Insert the files <var>member</var><small class="dots">...</small> into <var>archive</var> (with
<em>replacement</em>). This operation differs from <span class="samp">q</span> in that any
previously existing members are deleted if their names match those being
added.
<p>If one of the files named in <var>member</var><small class="dots">...</small> does not exist, <span class="command">ar</span>
displays an error message, and leaves undisturbed any existing members
of the archive matching that name.
<p>By default, new members are added at the end of the file; but you may
use one of the modifiers <span class="samp">a</span>, <span class="samp">b</span>, or <span class="samp">i</span> to request
placement relative to some existing member.
<p>The modifier <span class="samp">v</span> used with this operation elicits a line of
output for each file inserted, along with one of the letters <span class="samp">a</span> or
<span class="samp">r</span> to indicate whether the file was appended (no old member
deleted) or replaced.
<br><dt><span class="samp">t</span><dd><a name="index-contents-of-archive-18"></a>Display a <em>table</em> listing the contents of <var>archive</var>, or those
of the files listed in <var>member</var><small class="dots">...</small> that are present in the
archive. Normally only the member name is shown; if you also want to
see the modes (permissions), timestamp, owner, group, and size, you can
request that by also specifying the <span class="samp">v</span> modifier.
<p>If you do not specify a <var>member</var>, all files in the archive
are listed.
<p><a name="index-repeated-names-in-archive-19"></a><a name="index-name-duplication-in-archive-20"></a>If there is more than one file with the same name (say, <span class="samp">fie</span>) in
an archive (say <span class="samp">b.a</span>), <span class="samp">ar t b.a fie</span> lists only the
first instance; to see them all, you must ask for a complete
listing&mdash;in our example, <span class="samp">ar t b.a</span>.
<!-- WRS only; per Gumby, this is implementation-dependent, and in a more -->
<!-- recent case in fact works the other way. -->
<br><dt><span class="samp">x</span><dd><a name="index-extract-from-archive-21"></a><em>Extract</em> members (named <var>member</var>) from the archive. You can
use the <span class="samp">v</span> modifier with this operation, to request that
<span class="command">ar</span> list each name as it extracts it.
<p>If you do not specify a <var>member</var>, all files in the archive
are extracted.
<p>Files cannot be extracted from a thin archive.
</dl>
<p>A number of modifiers (<var>mod</var>) may immediately follow the <var>p</var>
keyletter, to specify variations on an operation's behavior:
<dl>
<dt><span class="samp">a</span><dd><a name="index-relative-placement-in-archive-22"></a>Add new files <em>after</em> an existing member of the
archive. If you use the modifier <span class="samp">a</span>, the name of an existing archive
member must be present as the <var>relpos</var> argument, before the
<var>archive</var> specification.
<br><dt><span class="samp">b</span><dd>Add new files <em>before</em> an existing member of the
archive. If you use the modifier <span class="samp">b</span>, the name of an existing archive
member must be present as the <var>relpos</var> argument, before the
<var>archive</var> specification. (same as <span class="samp">i</span>).
<br><dt><span class="samp">c</span><dd><a name="index-creating-archives-23"></a><em>Create</em> the archive. The specified <var>archive</var> 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.
<br><dt><span class="samp">f</span><dd>Truncate names in the archive. <span class="sc">gnu</span> <span class="command">ar</span> will normally permit file
names of any length. This will cause it to create archives which are
not compatible with the native <span class="command">ar</span> program on some systems. If
this is a concern, the <span class="samp">f</span> modifier may be used to truncate file
names when putting them in the archive.
<br><dt><span class="samp">i</span><dd>Insert new files <em>before</em> an existing member of the
archive. If you use the modifier <span class="samp">i</span>, the name of an existing archive
member must be present as the <var>relpos</var> argument, before the
<var>archive</var> specification. (same as <span class="samp">b</span>).
<br><dt><span class="samp">l</span><dd>This modifier is accepted but not used.
<!-- whaffor ar l modifier??? presumably compat; with -->
<!-- what???-doc@@cygnus.com, 25jan91 -->
<br><dt><span class="samp">N</span><dd>Uses the <var>count</var> parameter. This is used if there are multiple
entries in the archive with the same name. Extract or delete instance
<var>count</var> of the given name from the archive.
<br><dt><span class="samp">o</span><dd><a name="index-dates-in-archive-24"></a>Preserve the <em>original</em> 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.
<br><dt><span class="samp">P</span><dd>Use the full path name when matching names in the archive. <span class="sc">gnu</span>
<span class="command">ar</span> can not create an archive with a full path name (such archives
are not POSIX complaint), but other archive creators can. This option
will cause <span class="sc">gnu</span> <span class="command">ar</span> to match file names using a complete path
name, which can be convenient when extracting a single file from an
archive created by another tool.
<br><dt><span class="samp">s</span><dd><a name="index-writing-archive-index-25"></a>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 <span class="samp">ar s</span> on an
archive is equivalent to running <span class="samp">ranlib</span> on it.
<br><dt><span class="samp">S</span><dd><a name="index-not-writing-archive-index-26"></a>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
<span class="samp">S</span> modifier on the last execution of <span class="samp">ar</span>, or you must run
<span class="samp">ranlib</span> on the archive.
<br><dt><span class="samp">T</span><dd><a name="index-creating-thin-archive-27"></a>Make the specified <var>archive</var> a <em>thin</em> archive. If it already
exists and is a regular archive, the existing members must be present
in the same directory as <var>archive</var>.
<br><dt><span class="samp">u</span><dd><a name="index-updating-an-archive-28"></a>Normally, <span class="samp">ar r</span><small class="dots">...</small> inserts all files
listed into the archive. If you would like to insert <em>only</em> those
of the files you list that are newer than existing members of the same
names, use this modifier. The <span class="samp">u</span> modifier is allowed only for the
operation <span class="samp">r</span> (replace). In particular, the combination <span class="samp">qu</span> is
not allowed, since checking the timestamps would lose any speed
advantage from the operation <span class="samp">q</span>.
<br><dt><span class="samp">v</span><dd>This modifier requests the <em>verbose</em> version of an operation. Many
operations display additional information, such as filenames processed,
when the modifier <span class="samp">v</span> is appended.
<br><dt><span class="samp">V</span><dd>This modifier shows the version number of <span class="command">ar</span>.
</dl>
<p><span class="command">ar</span> ignores an initial option spelt <span class="samp">-X32_64</span>, for
compatibility with AIX. The behaviour produced by this option is the
default for <span class="sc">gnu</span> <span class="command">ar</span>. <span class="command">ar</span> does not support any of the other
<span class="samp">-X</span> options; in particular, it does not support <span class="option">-X32</span>
which is the default for AIX <span class="command">ar</span>.
<!-- man end -->
</body></html>

View file

@ -0,0 +1,174 @@
<html lang="en">
<head>
<title>ar scripts - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="ar.html#ar" title="ar">
<link rel="prev" href="ar-cmdline.html#ar-cmdline" title="ar cmdline">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="ar-scripts"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="ar-cmdline.html#ar-cmdline">ar cmdline</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="ar.html#ar">ar</a>
<hr><br>
</div>
<h3 class="section">1.2 Controlling <span class="command">ar</span> with a Script</h3>
<pre class="smallexample"> ar -M [ &lt;<var>script</var> ]
</pre>
<p><a name="index-MRI-compatibility_002c-_0040command_007bar_007d-29"></a><a name="index-scripts_002c-_0040command_007bar_007d-30"></a>If you use the single command-line option <span class="samp">-M</span> with <span class="command">ar</span>, you
can control its operation with a rudimentary command language. This
form of <span class="command">ar</span> operates interactively if standard input is coming
directly from a terminal. During interactive use, <span class="command">ar</span> prompts for
input (the prompt is <span class="samp">AR &gt;</span>), and continues executing even after
errors. If you redirect standard input to a script file, no prompts are
issued, and <span class="command">ar</span> abandons execution (with a nonzero exit code)
on any error.
<p>The <span class="command">ar</span> command language is <em>not</em> designed to be equivalent
to the command-line options; in fact, it provides somewhat less control
over archives. The only purpose of the command language is to ease the
transition to <span class="sc">gnu</span> <span class="command">ar</span> for developers who already have scripts
written for the MRI &ldquo;librarian&rdquo; program.
<p>The syntax for the <span class="command">ar</span> command language is straightforward:
<ul>
<li>commands are recognized in upper or lower case; for example, <code>LIST</code>
is the same as <code>list</code>. In the following descriptions, commands are
shown in upper case for clarity.
<li>a single command may appear on each line; it is the first word on the
line.
<li>empty lines are allowed, and have no effect.
<li>comments are allowed; text after either of the characters <span class="samp">*</span>
or <span class="samp">;</span> is ignored.
<li>Whenever you use a list of names as part of the argument to an <span class="command">ar</span>
command, you can separate the individual names with either commas or
blanks. Commas are shown in the explanations below, for clarity.
<li><span class="samp">+</span> is used as a line continuation character; if <span class="samp">+</span> appears
at the end of a line, the text on the following line is considered part
of the current command.
</ul>
<p>Here are the commands you can use in <span class="command">ar</span> scripts, or when using
<span class="command">ar</span> interactively. Three of them have special significance:
<p><code>OPEN</code> or <code>CREATE</code> specify a <dfn>current archive</dfn>, which is
a temporary file required for most of the other commands.
<p><code>SAVE</code> commits the changes so far specified by the script. Prior
to <code>SAVE</code>, commands affect only the temporary copy of the current
archive.
<dl>
<dt><code>ADDLIB </code><var>archive</var><dt><code>ADDLIB </code><var>archive</var><code> (</code><var>module</var><code>, </code><var>module</var><code>, ... </code><var>module</var><code>)</code><dd>Add all the contents of <var>archive</var> (or, if specified, each named
<var>module</var> from <var>archive</var>) to the current archive.
<p>Requires prior use of <code>OPEN</code> or <code>CREATE</code>.
<br><dt><code>ADDMOD </code><var>member</var><code>, </code><var>member</var><code>, ... </code><var>member</var><dd><!-- FIXME! w/Replacement?? If so, like "ar r @var{archive} @var{names}" -->
<!-- else like "ar q..." -->
Add each named <var>member</var> as a module in the current archive.
<p>Requires prior use of <code>OPEN</code> or <code>CREATE</code>.
<br><dt><code>CLEAR</code><dd>Discard the contents of the current archive, canceling the effect of
any operations since the last <code>SAVE</code>. May be executed (with no
effect) even if no current archive is specified.
<br><dt><code>CREATE </code><var>archive</var><dd>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</var> until you use <code>SAVE</code>.
You can overwrite existing archives; similarly, the contents of any
existing file named <var>archive</var> will not be destroyed until <code>SAVE</code>.
<br><dt><code>DELETE </code><var>module</var><code>, </code><var>module</var><code>, ... </code><var>module</var><dd>Delete each listed <var>module</var> from the current archive; equivalent to
<span class="samp">ar -d </span><var>archive</var> <var>module</var><span class="samp"> ... </span><var>module</var>.
<p>Requires prior use of <code>OPEN</code> or <code>CREATE</code>.
<br><dt><code>DIRECTORY </code><var>archive</var><code> (</code><var>module</var><code>, ... </code><var>module</var><code>)</code><dt><code>DIRECTORY </code><var>archive</var><code> (</code><var>module</var><code>, ... </code><var>module</var><code>) </code><var>outputfile</var><dd>List each named <var>module</var> present in <var>archive</var>. The separate
command <code>VERBOSE</code> specifies the form of the output: when verbose
output is off, output is like that of <span class="samp">ar -t </span><var>archive</var>
<var>module</var><span class="samp">...</span>. When verbose output is on, the listing is like
<span class="samp">ar -tv </span><var>archive</var> <var>module</var><span class="samp">...</span>.
<p>Output normally goes to the standard output stream; however, if you
specify <var>outputfile</var> as a final argument, <span class="command">ar</span> directs the
output to that file.
<br><dt><code>END</code><dd>Exit from <span class="command">ar</span>, with a <code>0</code> exit code to indicate successful
completion. This command does not save the output file; if you have
changed the current archive since the last <code>SAVE</code> command, those
changes are lost.
<br><dt><code>EXTRACT </code><var>module</var><code>, </code><var>module</var><code>, ... </code><var>module</var><dd>Extract each named <var>module</var> from the current archive, writing them
into the current directory as separate files. Equivalent to <span class="samp">ar -x
</span><var>archive</var> <var>module</var><span class="samp">...</span>.
<p>Requires prior use of <code>OPEN</code> or <code>CREATE</code>.
<br><dt><code>LIST</code><dd>Display full contents of the current archive, in &ldquo;verbose&rdquo; style
regardless of the state of <code>VERBOSE</code>. The effect is like <span class="samp">ar
tv </span><var>archive</var>. (This single command is a <span class="sc">gnu</span> <span class="command">ar</span>
enhancement, rather than present for MRI compatibility.)
<p>Requires prior use of <code>OPEN</code> or <code>CREATE</code>.
<br><dt><code>OPEN </code><var>archive</var><dd>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</var> until you next use <code>SAVE</code>.
<br><dt><code>REPLACE </code><var>module</var><code>, </code><var>module</var><code>, ... </code><var>module</var><dd>In the current archive, replace each existing <var>module</var> (named in
the <code>REPLACE</code> arguments) from files in the current working directory.
To execute this command without errors, both the file, and the module in
the current archive, must exist.
<p>Requires prior use of <code>OPEN</code> or <code>CREATE</code>.
<br><dt><code>VERBOSE</code><dd>Toggle an internal flag governing the output from <code>DIRECTORY</code>.
When the flag is on, <code>DIRECTORY</code> output matches output from
<span class="samp">ar -tv </span><small class="dots">...</small>.
<br><dt><code>SAVE</code><dd>Commit your changes to the current archive, and actually save it as a
file with the name specified in the last <code>CREATE</code> or <code>OPEN</code>
command.
<p>Requires prior use of <code>OPEN</code> or <code>CREATE</code>.
</dl>
</body></html>

View file

@ -0,0 +1,110 @@
<html lang="en">
<head>
<title>ar - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="index.html#Top" title="Top">
<link rel="next" href="nm.html#nm" title="nm">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="ar"></a>Next:&nbsp;<a rel="next" accesskey="n" href="nm.html#nm">nm</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="index.html#Top">Top</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">1 ar</h2>
<p><a name="index-ar-2"></a><a name="index-archives-3"></a><a name="index-collections-of-files-4"></a>
<!-- man title ar create, modify, and extract from archives -->
<pre class="smallexample"> ar [-]<var>p</var>[<var>mod</var> [<var>relpos</var>] [<var>count</var>]] <var>archive</var> [<var>member</var>...]
ar -M [ &lt;mri-script ]
</pre>
<!-- man begin DESCRIPTION ar -->
<p>The <span class="sc">gnu</span> <span class="command">ar</span> program creates, modifies, and extracts from
archives. An <dfn>archive</dfn> 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</dfn> of the archive).
<p>The original files' contents, mode (permissions), timestamp, owner, and
group are preserved in the archive, and can be restored on
extraction.
<p><a name="index-name-length-5"></a><span class="sc">gnu</span> <span class="command">ar</span> can maintain archives whose members have names of any
length; however, depending on how <span class="command">ar</span> is configured on your
system, a limit on member-name length may be imposed for compatibility
with archive formats maintained with other tools. If it exists, the
limit is often 15 characters (typical of formats related to a.out) or 16
characters (typical of formats related to coff).
<p><a name="index-libraries-6"></a><span class="command">ar</span> is considered a binary utility because archives of this sort
are most often used as <dfn>libraries</dfn> holding commonly needed
subroutines.
<p><a name="index-symbol-index-7"></a><span class="command">ar</span> creates an index to the symbols defined in relocatable
object modules in the archive when you specify the modifier <span class="samp">s</span>.
Once created, this index is updated in the archive whenever <span class="command">ar</span>
makes a change to its contents (save for the <span class="samp">q</span> 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.
<p>You may use <span class="samp">nm -s</span> or <span class="samp">nm --print-armap</span> to list this index
table. If an archive lacks the table, another form of <span class="command">ar</span> called
<span class="command">ranlib</span> can be used to add just the table.
<p><a name="index-thin-archives-8"></a><span class="sc">gnu</span> <span class="command">ar</span> can optionally create a <em>thin</em> archive,
which contains a symbol index and references to the original copies
of the member files of the archives. Such an archive is useful
for building libraries for use within a local build, where the
relocatable objects are expected to remain available, and copying the
contents of each object would only waste time and space. Thin archives
are also <em>flattened</em>, so that adding one or more archives to a
thin archive will add the elements of the nested archive individually.
The paths to the elements of the archive are stored relative to the
archive itself.
<p><a name="index-compatibility_002c-_0040command_007bar_007d-9"></a><a name="index-_0040command_007bar_007d-compatibility-10"></a><span class="sc">gnu</span> <span class="command">ar</span> is designed to be compatible with two different
facilities. You can control its activity using command-line options,
like the different varieties of <span class="command">ar</span> on Unix systems; or, if you
specify the single command-line option <span class="option">-M</span>, you can control it
with a script supplied via standard input, like the MRI &ldquo;librarian&rdquo;
program.
<!-- man end -->
<ul class="menu">
<li><a accesskey="1" href="ar-cmdline.html#ar-cmdline">ar cmdline</a>: Controlling <span class="command">ar</span> on the command line
<li><a accesskey="2" href="ar-scripts.html#ar-scripts">ar scripts</a>: Controlling <span class="command">ar</span> with a script
</ul>
</body></html>

View file

@ -0,0 +1,180 @@
<html lang="en">
<head>
<title>c++filt - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="strip.html#strip" title="strip">
<link rel="next" href="addr2line.html#addr2line" title="addr2line">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="c_002b_002bfilt"></a>Next:&nbsp;<a rel="next" accesskey="n" href="addr2line.html#addr2line">addr2line</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="strip.html#strip">strip</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">9 c++filt</h2>
<p><a name="index-c_002b_002bfilt-115"></a><a name="index-demangling-C_002b_002b-symbols-116"></a>
<!-- man title cxxfilt Demangle C++ and Java symbols. -->
<pre class="smallexample"> <!-- man begin SYNOPSIS cxxfilt -->
c++filt [<span class="option">-_</span>|<span class="option">--strip-underscores</span>]
[<span class="option">-n</span>|<span class="option">--no-strip-underscores</span>]
[<span class="option">-p</span>|<span class="option">--no-params</span>]
[<span class="option">-t</span>|<span class="option">--types</span>]
[<span class="option">-i</span>|<span class="option">--no-verbose</span>]
[<span class="option">-s</span> <var>format</var>|<span class="option">--format=</span><var>format</var>]
[<span class="option">--help</span>] [<span class="option">--version</span>] [<var>symbol</var>...]
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION cxxfilt -->
<p><a name="index-cxxfilt-117"></a>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</dfn>. The
<span class="command">c++filt</span>
<a rel="footnote" href="#fn-1" name="fnd-1"><sup>1</sup></a>
program does the inverse mapping: it decodes (<dfn>demangles</dfn>) low-level
names into user-level names so that they can be read.
<p>Every alphanumeric word (consisting of letters, digits, underscores,
dollars, or periods) seen in the input is a potential mangled name.
If the name decodes into a C++ name, the C++ name replaces the
low-level name in the output, otherwise the original word is output.
In this way you can pass an entire assembler source file, containing
mangled names, through <span class="command">c++filt</span> and see the same source file
containing demangled names.
<p>You can also use <span class="command">c++filt</span> to decipher individual symbols by
passing them on the command line:
<pre class="example"> c++filt <var>symbol</var>
</pre>
<p>If no <var>symbol</var> arguments are given, <span class="command">c++filt</span> reads symbol
names from the standard input instead. All the results are printed on
the standard output. The difference between reading names from the
command line versus reading names from the standard input is that
command line arguments are expected to be just mangled names and no
checking is performed to separate them from surrounding text. Thus
for example:
<pre class="smallexample"> c++filt -n _Z1fv
</pre>
<p>will work and demangle the name to &ldquo;f()&rdquo; whereas:
<pre class="smallexample"> c++filt -n _Z1fv,
</pre>
<p>will not work. (Note the extra comma at the end of the mangled
name which makes it invalid). This command however will work:
<pre class="smallexample"> echo _Z1fv, | c++filt -n
</pre>
<p>and will display &ldquo;f(),&rdquo;, i.e., the demangled name followed by a
trailing comma. This behaviour is because when the names are read
from the standard input it is expected that they might be part of an
assembler source file where there might be extra, extraneous
characters trailing after a mangled name. For example:
<pre class="smallexample"> .type _Z1fv, @function
</pre>
<!-- man end -->
<!-- man begin OPTIONS cxxfilt -->
<dl>
<dt><span class="env">-_</span><dt><span class="env">--strip-underscores</span><dd>On some systems, both the C and C++ compilers put an underscore in front
of every name. For example, the C name <code>foo</code> gets the low-level
name <code>_foo</code>. This option removes the initial underscore. Whether
<span class="command">c++filt</span> removes the underscore by default is target dependent.
<br><dt><span class="env">-j</span><dt><span class="env">--java</span><dd>Prints demangled names using Java syntax. The default is to use C++
syntax.
<br><dt><span class="env">-n</span><dt><span class="env">--no-strip-underscores</span><dd>Do not remove the initial underscore.
<br><dt><span class="env">-p</span><dt><span class="env">--no-params</span><dd>When demangling the name of a function, do not display the types of
the function's parameters.
<br><dt><span class="env">-t</span><dt><span class="env">--types</span><dd>Attempt to demangle types as well as function names. This is disabled
by default since mangled types are normally only used internally in
the compiler, and they can be confused with non-mangled names. For example,
a function called &ldquo;a&rdquo; treated as a mangled type name would be
demangled to &ldquo;signed char&rdquo;.
<br><dt><span class="env">-i</span><dt><span class="env">--no-verbose</span><dd>Do not include implementation details (if any) in the demangled
output.
<br><dt><span class="env">-s </span><var>format</var><dt><span class="env">--format=</span><var>format</var><dd><span class="command">c++filt</span> can decode various methods of mangling, used by
different compilers. The argument to this option selects which
method it uses:
<dl>
<dt><code>auto</code><dd>Automatic selection based on executable (the default method)
<br><dt><code>gnu</code><dd>the one used by the <span class="sc">gnu</span> C++ compiler (g++)
<br><dt><code>lucid</code><dd>the one used by the Lucid compiler (lcc)
<br><dt><code>arm</code><dd>the one specified by the C++ Annotated Reference Manual
<br><dt><code>hp</code><dd>the one used by the HP compiler (aCC)
<br><dt><code>edg</code><dd>the one used by the EDG compiler
<br><dt><code>gnu-v3</code><dd>the one used by the <span class="sc">gnu</span> C++ compiler (g++) with the V3 ABI.
<br><dt><code>java</code><dd>the one used by the <span class="sc">gnu</span> Java compiler (gcj)
<br><dt><code>gnat</code><dd>the one used by the <span class="sc">gnu</span> Ada compiler (GNAT).
</dl>
<br><dt><span class="env">--help</span><dd>Print a summary of the options to <span class="command">c++filt</span> and exit.
<br><dt><span class="env">--version</span><dd>Print the version number of <span class="command">c++filt</span> and exit.
</dl>
<!-- man end -->
<blockquote>
<em>Warning:</em> <span class="command">c++filt</span> is a new utility, and the details of its
user interface are subject to change in future releases. In particular,
a command-line option may be required in the future to decode a name
passed as an argument on the command line; in other words,
<pre class="example"> c++filt <var>symbol</var>
</pre>
<p class="noindent">may in a future release become
<pre class="example"> c++filt <var>option</var> <var>symbol</var>
</pre>
</blockquote>
<div class="footnote">
<hr>
<h4>Footnotes</h4><p class="footnote"><small>[<a name="fn-1" href="#fnd-1">1</a>]</small> MS-DOS does not allow <kbd>+</kbd> characters in file names, so on
MS-DOS this program is named <span class="command">CXXFILT</span>.</p>
<p><hr></div>
</body></html>

View file

@ -0,0 +1,76 @@
<html lang="en">
<head>
<title>def file format - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="dlltool.html#dlltool" title="dlltool">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="def-file-format"></a>Up:&nbsp;<a rel="up" accesskey="u" href="dlltool.html#dlltool">dlltool</a>
<hr><br>
</div>
<h3 class="section">14.1 The format of the <span class="command">dlltool</span> <span class="file">.def</span> file</h3>
<p>A <span class="file">.def</span> file contains any number of the following commands:
<dl>
<dt><code>NAME</code> <var>name</var> <code>[ ,</code> <var>base</var> <code>]</code><dd>The result is going to be named <var>name</var><code>.exe</code>.
<br><dt><code>LIBRARY</code> <var>name</var> <code>[ ,</code> <var>base</var> <code>]</code><dd>The result is going to be named <var>name</var><code>.dll</code>.
<br><dt><code>EXPORTS ( ( (</code> <var>name1</var> <code>[ = </code> <var>name2</var> <code>] ) | ( </code> <var>name1</var> <code>=</code> <var>module-name</var> <code>.</code> <var>external-name</var> <code>) )</code><br><dt><code>[</code> <var>integer</var> <code>] [ NONAME ] [ CONSTANT ] [ DATA ] [ PRIVATE ] ) *</code><dd>Declares <var>name1</var> as an exported symbol from the DLL, with optional
ordinal number <var>integer</var>, or declares <var>name1</var> as an alias
(forward) of the function <var>external-name</var> in the DLL
<var>module-name</var>.
<br><dt><code>IMPORTS ( (</code> <var>internal-name</var> <code>=</code> <var>module-name</var> <code>.</code> <var>integer</var> <code>) | [</code> <var>internal-name</var> <code>= ]</code> <var>module-name</var> <code>.</code> <var>external-name</var> <code>) ) *</code><dd>Declares that <var>external-name</var> or the exported function whose
ordinal number is <var>integer</var> is to be imported from the file
<var>module-name</var>. If <var>internal-name</var> is specified then this is
the name that the imported function will be referred to in the body of
the DLL.
<br><dt><code>DESCRIPTION</code> <var>string</var><dd>Puts <var>string</var> into the output <span class="file">.exp</span> file in the
<code>.rdata</code> section.
<br><dt><code>STACKSIZE</code> <var>number-reserve</var> <code>[, </code> <var>number-commit</var> <code>]</code><br><dt><code>HEAPSIZE</code> <var>number-reserve</var> <code>[, </code> <var>number-commit</var> <code>]</code><dd>Generates <code>--stack</code> or <code>--heap</code>
<var>number-reserve</var>,<var>number-commit</var> in the output <code>.drectve</code>
section. The linker will see this and act upon it.
<br><dt><code>CODE</code> <var>attr</var> <code>+</code><br><dt><code>DATA</code> <var>attr</var> <code>+</code><br><dt><code>SECTIONS (</code> <var>section-name</var> <var>attr</var><code> + ) *</code><dd>Generates <code>--attr</code> <var>section-name</var> <var>attr</var> in the output
<code>.drectve</code> section, where <var>attr</var> is one of <code>READ</code>,
<code>WRITE</code>, <code>EXECUTE</code> or <code>SHARED</code>. The linker will see
this and act upon it.
</dl>
</body></html>

View file

@ -0,0 +1,273 @@
<html lang="en">
<head>
<title>dlltool - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="windmc.html#windmc" title="windmc">
<link rel="next" href="Common-Options.html#Common-Options" title="Common Options">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="dlltool"></a>Next:&nbsp;<a rel="next" accesskey="n" href="Common-Options.html#Common-Options">Common Options</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="windmc.html#windmc">windmc</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">14 dlltool</h2>
<p><a name="index-DLL-122"></a><a name="index-dlltool-123"></a>
<span class="command">dlltool</span> 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.
<p>The export table is generated by this program by reading in a
<span class="file">.def</span> file or scanning the <span class="file">.a</span> and <span class="file">.o</span> files which
will be in the DLL. A <span class="file">.o</span> file can contain information in
special <span class="samp">.drectve</span> sections with export information.
<blockquote>
<em>Note:</em> <span class="command">dlltool</span> is not always built as part of the
binary utilities, since it is only useful for those targets which
support DLLs.
</blockquote>
<!-- man title dlltool Create files needed to build and use DLLs. -->
<pre class="smallexample"> <!-- man begin SYNOPSIS dlltool -->
dlltool [<span class="option">-d</span>|<span class="option">--input-def</span> <var>def-file-name</var>]
[<span class="option">-b</span>|<span class="option">--base-file</span> <var>base-file-name</var>]
[<span class="option">-e</span>|<span class="option">--output-exp</span> <var>exports-file-name</var>]
[<span class="option">-z</span>|<span class="option">--output-def</span> <var>def-file-name</var>]
[<span class="option">-l</span>|<span class="option">--output-lib</span> <var>library-file-name</var>]
[<span class="option">--export-all-symbols</span>] [<span class="option">--no-export-all-symbols</span>]
[<span class="option">--exclude-symbols</span> <var>list</var>]
[<span class="option">--no-default-excludes</span>]
[<span class="option">-S</span>|<span class="option">--as</span> <var>path-to-assembler</var>] [<span class="option">-f</span>|<span class="option">--as-flags</span> <var>options</var>]
[<span class="option">-D</span>|<span class="option">--dllname</span> <var>name</var>] [<span class="option">-m</span>|<span class="option">--machine</span> <var>machine</var>]
[<span class="option">-a</span>|<span class="option">--add-indirect</span>]
[<span class="option">-U</span>|<span class="option">--add-underscore</span>] [<span class="option">--add-stdcall-underscore</span>]
[<span class="option">-k</span>|<span class="option">--kill-at</span>] [<span class="option">-A</span>|<span class="option">--add-stdcall-alias</span>]
[<span class="option">-p</span>|<span class="option">--ext-prefix-alias</span> <var>prefix</var>]
[<span class="option">-x</span>|<span class="option">--no-idata4</span>] [<span class="option">-c</span>|<span class="option">--no-idata5</span>] [<span class="option">-i</span>|<span class="option">--interwork</span>]
[<span class="option">-n</span>|<span class="option">--nodelete</span>] [<span class="option">-t</span>|<span class="option">--temp-prefix</span> <var>prefix</var>]
[<span class="option">-v</span>|<span class="option">--verbose</span>]
[<span class="option">-h</span>|<span class="option">--help</span>] [<span class="option">-V</span>|<span class="option">--version</span>]
[object-file ...]
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION dlltool -->
<p><span class="command">dlltool</span> reads its inputs, which can come from the <span class="option">-d</span> and
<span class="option">-b</span> options as well as object files specified on the command
line. It then processes these inputs and if the <span class="option">-e</span> option has
been specified it creates a exports file. If the <span class="option">-l</span> option
has been specified it creates a library file and if the <span class="option">-z</span> option
has been specified it creates a def file. Any or all of the <span class="option">-e</span>,
<span class="option">-l</span> and <span class="option">-z</span> options can be present in one invocation of
dlltool.
<p>When creating a DLL, along with the source for the DLL, it is necessary
to have three other files. <span class="command">dlltool</span> can help with the creation of
these files.
<p>The first file is a <span class="file">.def</span> file which specifies which functions are
exported from the DLL, which functions the DLL imports, and so on. This
is a text file and can be created by hand, or <span class="command">dlltool</span> can be used
to create it using the <span class="option">-z</span> option. In this case <span class="command">dlltool</span>
will scan the object files specified on its command line looking for
those functions which have been specially marked as being exported and
put entries for them in the <span class="file">.def</span> file it creates.
<p>In order to mark a function as being exported from a DLL, it needs to
have an <span class="option">-export:&lt;name_of_function&gt;</span> entry in the <span class="samp">.drectve</span>
section of the object file. This can be done in C by using the
asm() operator:
<pre class="smallexample"> asm (".section .drectve");
asm (".ascii \"-export:my_func\"");
int my_func (void) { ... }
</pre>
<p>The second file needed for DLL creation is an exports file. This file
is linked with the object files that make up the body of the DLL and it
handles the interface between the DLL and the outside world. This is a
binary file and it can be created by giving the <span class="option">-e</span> option to
<span class="command">dlltool</span> when it is creating or reading in a <span class="file">.def</span> file.
<p>The third file needed for DLL creation is the library file that programs
will link with in order to access the functions in the DLL. This file
can be created by giving the <span class="option">-l</span> option to dlltool when it
is creating or reading in a <span class="file">.def</span> file.
<p><span class="command">dlltool</span> builds the library file by hand, but it builds the
exports file by creating temporary files containing assembler statements
and then assembling these. The <span class="option">-S</span> command line option can be
used to specify the path to the assembler that dlltool will use,
and the <span class="option">-f</span> option can be used to pass specific flags to that
assembler. The <span class="option">-n</span> can be used to prevent dlltool from deleting
these temporary assembler files when it is done, and if <span class="option">-n</span> is
specified twice then this will prevent dlltool from deleting the
temporary object files it used to build the library.
<p>Here is an example of creating a DLL from a source file <span class="samp">dll.c</span> and
also creating a program (from an object file called <span class="samp">program.o</span>)
that uses that DLL:
<pre class="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
</pre>
<!-- man end -->
<!-- man begin OPTIONS dlltool -->
<p>The command line options have the following meanings:
<dl>
<dt><span class="env">-d </span><var>filename</var><dt><span class="env">--input-def </span><var>filename</var><dd><a name="index-input-_002edef-file-124"></a>Specifies the name of a <span class="file">.def</span> file to be read in and processed.
<br><dt><span class="env">-b </span><var>filename</var><dt><span class="env">--base-file </span><var>filename</var><dd><a name="index-base-files-125"></a>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.
<br><dt><span class="env">-e </span><var>filename</var><dt><span class="env">--output-exp </span><var>filename</var><dd>Specifies the name of the export file to be created by dlltool.
<br><dt><span class="env">-z </span><var>filename</var><dt><span class="env">--output-def </span><var>filename</var><dd>Specifies the name of the <span class="file">.def</span> file to be created by dlltool.
<br><dt><span class="env">-l </span><var>filename</var><dt><span class="env">--output-lib </span><var>filename</var><dd>Specifies the name of the library file to be created by dlltool.
<br><dt><span class="env">--export-all-symbols</span><dd>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
are not exported by default; see the <span class="option">--no-default-excludes</span>
option. You may add to the list of symbols to not export by using the
<span class="option">--exclude-symbols</span> option.
<br><dt><span class="env">--no-export-all-symbols</span><dd>Only export symbols explicitly listed in an input <span class="file">.def</span> file or in
<span class="samp">.drectve</span> sections in the input object files. This is the default
behaviour. The <span class="samp">.drectve</span> sections are created by <span class="samp">dllexport</span>
attributes in the source code.
<br><dt><span class="env">--exclude-symbols </span><var>list</var><dd>Do not export the symbols in <var>list</var>. 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
<span class="option">--export-all-symbols</span> is used.
<br><dt><span class="env">--no-default-excludes</span><dd>When <span class="option">--export-all-symbols</span> is used, it will by default avoid
exporting certain special symbols. The current list of symbols to avoid
exporting is <span class="samp">DllMain@12</span>, <span class="samp">DllEntryPoint@0</span>,
<span class="samp">impure_ptr</span>. You may use the <span class="option">--no-default-excludes</span> option
to go ahead and export these special symbols. This is only meaningful
when <span class="option">--export-all-symbols</span> is used.
<br><dt><span class="env">-S </span><var>path</var><dt><span class="env">--as </span><var>path</var><dd>Specifies the path, including the filename, of the assembler to be used
to create the exports file.
<br><dt><span class="env">-f </span><var>options</var><dt><span class="env">--as-flags </span><var>options</var><dd>Specifies any specific command line options to be passed to the
assembler when building the exports file. This option will work even if
the <span class="option">-S</span> option is not used. This option only takes one argument,
and if it occurs more than once on the command line, then later
occurrences will override earlier occurrences. So if it is necessary to
pass multiple options to the assembler they should be enclosed in
double quotes.
<br><dt><span class="env">-D </span><var>name</var><dt><span class="env">--dll-name </span><var>name</var><dd>Specifies the name to be stored in the <span class="file">.def</span> file as the name of
the DLL when the <span class="option">-e</span> option is used. If this option is not
present, then the filename given to the <span class="option">-e</span> option will be
used as the name of the DLL.
<br><dt><span class="env">-m </span><var>machine</var><dt><span class="env">-machine </span><var>machine</var><dd>Specifies the type of machine for which the library file should be
built. <span class="command">dlltool</span> has a built in default type, depending upon how
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
contents of the DLL are actually encode using Thumb instructions.
<br><dt><span class="env">-a</span><dt><span class="env">--add-indirect</span><dd>Specifies that when <span class="command">dlltool</span> is creating the exports file it
should add a section which allows the exported functions to be
referenced without using the import library. Whatever the hell that
means!
<br><dt><span class="env">-U</span><dt><span class="env">--add-underscore</span><dd>Specifies that when <span class="command">dlltool</span> is creating the exports file it
should prepend an underscore to the names of <em>all</em> exported symbols.
<br><dt><span class="env">--add-stdcall-underscore</span><dd>Specifies that when <span class="command">dlltool</span> is creating the exports file it
should prepend an underscore to the names of exported <em>stdcall</em>
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.
<br><dt><span class="env">-k</span><dt><span class="env">--kill-at</span><dd>Specifies that when <span class="command">dlltool</span> is creating the exports file it
should not append the string <span class="samp">@ &lt;number&gt;</span>. These numbers are
called ordinal numbers and they represent another way of accessing the
function in a DLL, other than by name.
<br><dt><span class="env">-A</span><dt><span class="env">--add-stdcall-alias</span><dd>Specifies that when <span class="command">dlltool</span> is creating the exports file it
should add aliases for stdcall symbols without <span class="samp">@ &lt;number&gt;</span>
in addition to the symbols with <span class="samp">@ &lt;number&gt;</span>.
<br><dt><span class="env">-p</span><dt><span class="env">--ext-prefix-alias </span><var>prefix</var><dd>Causes <span class="command">dlltool</span> 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.
<br><dt><span class="env">-x</span><dt><span class="env">--no-idata4</span><dd>Specifies that when <span class="command">dlltool</span> is creating the exports and library
files it should omit the <code>.idata4</code> section. This is for compatibility
with certain operating systems.
<br><dt><span class="env">-c</span><dt><span class="env">--no-idata5</span><dd>Specifies that when <span class="command">dlltool</span> is creating the exports and library
files it should omit the <code>.idata5</code> section. This is for compatibility
with certain operating systems.
<br><dt><span class="env">-i</span><dt><span class="env">--interwork</span><dd>Specifies that <span class="command">dlltool</span> should mark the objects in the library
file and exports file that it produces as supporting interworking
between ARM and Thumb code.
<br><dt><span class="env">-n</span><dt><span class="env">--nodelete</span><dd>Makes <span class="command">dlltool</span> preserve the temporary assembler files it used to
create the exports file. If this option is repeated then dlltool will
also preserve the temporary object files it uses to create the library
file.
<br><dt><span class="env">-t </span><var>prefix</var><dt><span class="env">--temp-prefix </span><var>prefix</var><dd>Makes <span class="command">dlltool</span> use <var>prefix</var> when constructing the names of
temporary assembler and object files. By default, the temp file prefix
is generated from the pid.
<br><dt><span class="env">-v</span><dt><span class="env">--verbose</span><dd>Make dlltool describe what it is doing.
<br><dt><span class="env">-h</span><dt><span class="env">--help</span><dd>Displays a list of command line options and then exits.
<br><dt><span class="env">-V</span><dt><span class="env">--version</span><dd>Displays dlltool's version number and then exits.
</dl>
<!-- man end -->
<ul class="menu">
<li><a accesskey="1" href="def-file-format.html#def-file-format">def file format</a>: The format of the dlltool <span class="file">.def</span> file
</ul>
</body></html>

View file

@ -0,0 +1,122 @@
<html lang="en">
<head>
<title>GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="#Top">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled "GNU Free Documentation License".
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<h1 class="settitle">GNU Binary Utilities</h1>
<div class="contents">
<h2>Table of Contents</h2>
<ul>
<li><a name="toc_Top" href="index.html#Top">Introduction</a>
<li><a name="toc_ar" href="ar.html#ar">1 ar</a>
<ul>
<li><a href="ar-cmdline.html#ar-cmdline">1.1 Controlling <span class="command">ar</span> on the Command Line</a>
<li><a href="ar-scripts.html#ar-scripts">1.2 Controlling <span class="command">ar</span> with a Script</a>
</li></ul>
<li><a name="toc_nm" href="nm.html#nm">2 nm</a>
<li><a name="toc_objcopy" href="objcopy.html#objcopy">3 objcopy</a>
<li><a name="toc_objdump" href="objdump.html#objdump">4 objdump</a>
<li><a name="toc_ranlib" href="ranlib.html#ranlib">5 ranlib</a>
<li><a name="toc_size" href="size.html#size">6 size</a>
<li><a name="toc_strings" href="strings.html#strings">7 strings</a>
<li><a name="toc_strip" href="strip.html#strip">8 strip</a>
<li><a name="toc_c_002b_002bfilt" href="c_002b_002bfilt.html#c_002b_002bfilt">9 c++filt</a>
<li><a name="toc_addr2line" href="addr2line.html#addr2line">10 addr2line</a>
<li><a name="toc_nlmconv" href="nlmconv.html#nlmconv">11 nlmconv</a>
<li><a name="toc_windmc" href="windmc.html#windmc">12 windmc</a>
<li><a name="toc_windres" href="windres.html#windres">13 windres</a>
<li><a name="toc_dlltool" href="dlltool.html#dlltool">14 dlltool</a>
<ul>
<li><a href="def-file-format.html#def-file-format">14.1 The format of the <span class="command">dlltool</span> <span class="file">.def</span> file</a>
</li></ul>
<li><a name="toc_readelf" href="readelf.html#readelf">15 readelf</a>
<li><a name="toc_Common-Options" href="Common-Options.html#Common-Options">16 Common Options</a>
<li><a name="toc_Selecting-the-Target-System" href="Selecting-the-Target-System.html#Selecting-the-Target-System">17 Selecting the Target System</a>
<ul>
<li><a href="Target-Selection.html#Target-Selection">17.1 Target Selection</a>
<li><a href="Architecture-Selection.html#Architecture-Selection">17.2 Architecture Selection</a>
</li></ul>
<li><a name="toc_Reporting-Bugs" href="Reporting-Bugs.html#Reporting-Bugs">18 Reporting Bugs</a>
<ul>
<li><a href="Bug-Criteria.html#Bug-Criteria">18.1 Have You Found a Bug?</a>
<li><a href="Bug-Reporting.html#Bug-Reporting">18.2 How to Report Bugs</a>
</li></ul>
<li><a name="toc_GNU-Free-Documentation-License" href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License">Appendix A GNU Free Documentation License</a>
<li><a name="toc_Binutils-Index" href="Binutils-Index.html#Binutils-Index">Binutils Index</a>
</li></ul>
</div>
<div class="node">
<p>
<a name="Top"></a>Next:&nbsp;<a rel="next" accesskey="n" href="ar.html#ar">ar</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="../index.html#dir">(dir)</a>
<hr><br>
</div>
<h2 class="unnumbered">Introduction</h2>
<p><a name="index-version-1"></a>This brief manual contains documentation for the <span class="sc">gnu</span> binary
utilities
(GNU Binutils)
version 2.19:
<p>This document is distributed under the terms of the GNU Free
Documentation License. A copy of the license is included in the
section entitled &ldquo;GNU Free Documentation License&rdquo;.
<ul class="menu">
<li><a accesskey="1" href="ar.html#ar">ar</a>: Create, modify, and extract from archives
<li><a accesskey="2" href="nm.html#nm">nm</a>: List symbols from object files
<li><a accesskey="3" href="objcopy.html#objcopy">objcopy</a>: Copy and translate object files
<li><a accesskey="4" href="objdump.html#objdump">objdump</a>: Display information from object files
<li><a accesskey="5" href="ranlib.html#ranlib">ranlib</a>: Generate index to archive contents
<li><a accesskey="6" href="readelf.html#readelf">readelf</a>: Display the contents of ELF format files
<li><a accesskey="7" href="size.html#size">size</a>: List section sizes and total size
<li><a accesskey="8" href="strings.html#strings">strings</a>: List printable strings from files
<li><a accesskey="9" href="strip.html#strip">strip</a>: Discard symbols
<li><a href="c_002b_002bfilt.html#c_002b_002bfilt">c++filt</a>: Filter to demangle encoded C++ symbols
<li><a href="c_002b_002bfilt.html#c_002b_002bfilt">cxxfilt</a>: MS-DOS name for c++filt
<li><a href="addr2line.html#addr2line">addr2line</a>: Convert addresses to file and line
<li><a href="nlmconv.html#nlmconv">nlmconv</a>: Converts object code into an NLM
<li><a href="windres.html#windres">windres</a>: Manipulate Windows resources
<li><a href="windmc.html#windmc">windmc</a>: Generator for Windows message resources
<li><a href="dlltool.html#dlltool">dlltool</a>: Create files needed to build and use DLLs
<li><a href="Common-Options.html#Common-Options">Common Options</a>: Command-line options for all utilities
<li><a href="Selecting-the-Target-System.html#Selecting-the-Target-System">Selecting the Target System</a>: How these utilities determine the target
<li><a href="Reporting-Bugs.html#Reporting-Bugs">Reporting Bugs</a>: Reporting Bugs
<li><a href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License">GNU Free Documentation License</a>: GNU Free Documentation License
<li><a href="Binutils-Index.html#Binutils-Index">Binutils Index</a>: Binutils Index
</ul>
</body></html>

View file

@ -0,0 +1,111 @@
<html lang="en">
<head>
<title>nlmconv - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="addr2line.html#addr2line" title="addr2line">
<link rel="next" href="windres.html#windres" title="windres">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="nlmconv"></a>Next:&nbsp;<a rel="next" accesskey="n" href="windres.html#windres">windres</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="addr2line.html#addr2line">addr2line</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">11 nlmconv</h2>
<p><span class="command">nlmconv</span> converts a relocatable object file into a NetWare
Loadable Module.
<blockquote>
<em>Warning:</em> <span class="command">nlmconv</span> is not always built as part of the binary
utilities, since it is only useful for NLM targets.
</blockquote>
<!-- man title nlmconv converts object code into an NLM. -->
<pre class="smallexample"> <!-- man begin SYNOPSIS nlmconv -->
nlmconv [<span class="option">-I</span> <var>bfdname</var>|<span class="option">--input-target=</span><var>bfdname</var>]
[<span class="option">-O</span> <var>bfdname</var>|<span class="option">--output-target=</span><var>bfdname</var>]
[<span class="option">-T</span> <var>headerfile</var>|<span class="option">--header-file=</span><var>headerfile</var>]
[<span class="option">-d</span>|<span class="option">--debug</span>] [<span class="option">-l</span> <var>linker</var>|<span class="option">--linker=</span><var>linker</var>]
[<span class="option">-h</span>|<span class="option">--help</span>] [<span class="option">-V</span>|<span class="option">--version</span>]
<var>infile</var> <var>outfile</var>
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION nlmconv -->
<p><span class="command">nlmconv</span> converts the relocatable <span class="samp">i386</span> object file
<var>infile</var> into the NetWare Loadable Module <var>outfile</var>, optionally
reading <var>headerfile</var> for NLM header information. For instructions
on writing the NLM command file language used in header files, see the
<span class="samp">linkers</span> section, <span class="samp">NLMLINK</span> in particular, of the <cite>NLM
Development and Tools Overview</cite>, which is part of the NLM Software
Developer's Kit (&ldquo;NLM SDK&rdquo;), available from Novell, Inc.
<span class="command">nlmconv</span> uses the <span class="sc">gnu</span> Binary File Descriptor library to read
<var>infile</var>;
see <a href="../ld/BFD.html#BFD">BFD (Using LD)</a>, for more information.
<p><span class="command">nlmconv</span> can perform a link step. In other words, you can list
more than one object file for input if you list them in the definitions
file (rather than simply specifying one input file on the command line).
In this case, <span class="command">nlmconv</span> calls the linker for you.
<!-- man end -->
<!-- man begin OPTIONS nlmconv -->
<dl>
<dt><span class="env">-I </span><var>bfdname</var><dt><span class="env">--input-target=</span><var>bfdname</var><dd>Object format of the input file. <span class="command">nlmconv</span> can usually determine
the format of a given file (so no default is necessary).
See <a href="Target-Selection.html#Target-Selection">Target Selection</a>, for more information.
<br><dt><span class="env">-O </span><var>bfdname</var><dt><span class="env">--output-target=</span><var>bfdname</var><dd>Object format of the output file. <span class="command">nlmconv</span> infers the output
format based on the input format, e.g. for a <span class="samp">i386</span> input file the
output format is <span class="samp">nlm32-i386</span>.
See <a href="Target-Selection.html#Target-Selection">Target Selection</a>, for more information.
<br><dt><span class="env">-T </span><var>headerfile</var><dt><span class="env">--header-file=</span><var>headerfile</var><dd>Reads <var>headerfile</var> for NLM header information. For instructions on
writing the NLM command file language used in header files, see see the
<span class="samp">linkers</span> section, of the <cite>NLM Development and Tools
Overview</cite>, which is part of the NLM Software Developer's Kit, available
from Novell, Inc.
<br><dt><span class="env">-d</span><dt><span class="env">--debug</span><dd>Displays (on standard error) the linker command line used by <span class="command">nlmconv</span>.
<br><dt><span class="env">-l </span><var>linker</var><dt><span class="env">--linker=</span><var>linker</var><dd>Use <var>linker</var> for any linking. <var>linker</var> can be an absolute or a
relative pathname.
<br><dt><span class="env">-h</span><dt><span class="env">--help</span><dd>Prints a usage summary.
<br><dt><span class="env">-V</span><dt><span class="env">--version</span><dd>Prints the version number for <span class="command">nlmconv</span>.
</dl>
<!-- man end -->
</body></html>

View file

@ -0,0 +1,234 @@
<html lang="en">
<head>
<title>nm - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="ar.html#ar" title="ar">
<link rel="next" href="objcopy.html#objcopy" title="objcopy">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="nm"></a>Next:&nbsp;<a rel="next" accesskey="n" href="objcopy.html#objcopy">objcopy</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="ar.html#ar">ar</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">2 nm</h2>
<p><a name="index-symbols-31"></a><a name="index-nm-32"></a>
<!-- man title nm list symbols from object files -->
<pre class="smallexample"> <!-- man begin SYNOPSIS nm -->
nm [<span class="option">-a</span>|<span class="option">--debug-syms</span>] [<span class="option">-g</span>|<span class="option">--extern-only</span>]
[<span class="option">-B</span>] [<span class="option">-C</span>|<span class="option">--demangle</span>[=<var>style</var>]] [<span class="option">-D</span>|<span class="option">--dynamic</span>]
[<span class="option">-S</span>|<span class="option">--print-size</span>] [<span class="option">-s</span>|<span class="option">--print-armap</span>]
[<span class="option">-A</span>|<span class="option">-o</span>|<span class="option">--print-file-name</span>][<span class="option">--special-syms</span>]
[<span class="option">-n</span>|<span class="option">-v</span>|<span class="option">--numeric-sort</span>] [<span class="option">-p</span>|<span class="option">--no-sort</span>]
[<span class="option">-r</span>|<span class="option">--reverse-sort</span>] [<span class="option">--size-sort</span>] [<span class="option">-u</span>|<span class="option">--undefined-only</span>]
[<span class="option">-t</span> <var>radix</var>|<span class="option">--radix=</span><var>radix</var>] [<span class="option">-P</span>|<span class="option">--portability</span>]
[<span class="option">--target=</span><var>bfdname</var>] [<span class="option">-f</span><var>format</var>|<span class="option">--format=</span><var>format</var>]
[<span class="option">--defined-only</span>] [<span class="option">-l</span>|<span class="option">--line-numbers</span>] [<span class="option">--no-demangle</span>]
[<span class="option">-V</span>|<span class="option">--version</span>] [<span class="option">-X 32_64</span>] [<span class="option">--help</span>] [<var>objfile</var>...]
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION nm -->
<p><span class="sc">gnu</span> <span class="command">nm</span> lists the symbols from object files <var>objfile</var><small class="dots">...</small>.
If no object files are listed as arguments, <span class="command">nm</span> assumes the file
<span class="file">a.out</span>.
<p>For each symbol, <span class="command">nm</span> shows:
<ul>
<li>The symbol value, in the radix selected by options (see below), or
hexadecimal by default.
<li>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
local; if uppercase, the symbol is global (external).
<!-- Some more detail on exactly what these symbol types are used for -->
<!-- would be nice. -->
<dl>
<dt><code>A</code><dd>The symbol's value is absolute, and will not be changed by further
linking.
<br><dt><code>B</code><dt><code>b</code><dd>The symbol is in the uninitialized data section (known as BSS).
<br><dt><code>C</code><dd>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
references.
For more details on common symbols, see the discussion of
&ndash;warn-common in <a href="../ld/Options.html#Options">Linker options (The GNU linker)</a>.
<br><dt><code>D</code><dt><code>d</code><dd>The symbol is in the initialized data section.
<br><dt><code>G</code><dt><code>g</code><dd>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.
<br><dt><code>I</code><dd>The symbol is an indirect reference to another symbol. This is a <span class="sc">gnu</span>
extension to the a.out object file format which is rarely used.
<br><dt><code>i</code><dd>The symbol is in a section specific to the implementation of DLLs.
<br><dt><code>N</code><dd>The symbol is a debugging symbol.
<br><dt><code>p</code><dd>The symbols is in a stack unwind section.
<br><dt><code>R</code><dt><code>r</code><dd>The symbol is in a read only data section.
<br><dt><code>S</code><dt><code>s</code><dd>The symbol is in an uninitialized data section for small objects.
<br><dt><code>T</code><dt><code>t</code><dd>The symbol is in the text (code) section.
<br><dt><code>U</code><dd>The symbol is undefined.
<br><dt><code>V</code><dt><code>v</code><dd>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,
the value of the weak symbol becomes zero with no error. On some
systems, uppercase indicates that a default value has been specified.
<br><dt><code>W</code><dt><code>w</code><dd>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,
the value of the symbol is determined in a system-specific manner without
error. On some systems, uppercase indicates that a default value has been
specified.
<br><dt><code>-</code><dd>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
the stab type. Stabs symbols are used to hold debugging information.
For more information, see <a href="../stabs/index.html#Top">Stabs (The &ldquo;stabs&rdquo; debug format)</a>.
<br><dt><code>?</code><dd>The symbol type is unknown, or object file format specific.
</dl>
<li>The symbol name.
</ul>
<!-- man end -->
<!-- man begin OPTIONS nm -->
<p>The long and short forms of options, shown here as alternatives, are
equivalent.
<dl>
<dt><span class="env">-A</span><dt><span class="env">-o</span><dt><span class="env">--print-file-name</span><dd><a name="index-input-file-name-33"></a><a name="index-file-name-34"></a><a name="index-source-file-name-35"></a>Precede each symbol by the name of the input file (or archive member)
in which it was found, rather than identifying the input file once only,
before all of its symbols.
<br><dt><span class="env">-a</span><dt><span class="env">--debug-syms</span><dd><a name="index-debugging-symbols-36"></a>Display all symbols, even debugger-only symbols; normally these are not
listed.
<br><dt><span class="env">-B</span><dd><a name="index-_0040command_007bnm_007d-format-37"></a><a name="index-_0040command_007bnm_007d-compatibility-38"></a>The same as <span class="option">--format=bsd</span> (for compatibility with the MIPS <span class="command">nm</span>).
<br><dt><span class="env">-C</span><dt><span class="env">--demangle[=</span><var>style</var><span class="env">]</span><dd><a name="index-demangling-in-nm-39"></a>Decode (<dfn>demangle</dfn>) low-level symbol names into user-level names.
Besides removing any initial underscore prepended by the system, this
makes C++ function names readable. Different compilers have different
mangling styles. The optional demangling style argument can be used to
choose an appropriate demangling style for your compiler. See <a href="c_002b_002bfilt.html#c_002b_002bfilt">c++filt</a>,
for more information on demangling.
<br><dt><span class="env">--no-demangle</span><dd>Do not demangle low-level symbol names. This is the default.
<br><dt><span class="env">-D</span><dt><span class="env">--dynamic</span><dd><a name="index-dynamic-symbols-40"></a>Display the dynamic symbols rather than the normal symbols. This is
only meaningful for dynamic objects, such as certain types of shared
libraries.
<br><dt><span class="env">-f </span><var>format</var><dt><span class="env">--format=</span><var>format</var><dd><a name="index-_0040command_007bnm_007d-format-41"></a><a name="index-_0040command_007bnm_007d-compatibility-42"></a>Use the output format <var>format</var>, which can be <code>bsd</code>,
<code>sysv</code>, or <code>posix</code>. The default is <code>bsd</code>.
Only the first character of <var>format</var> is significant; it can be
either upper or lower case.
<br><dt><span class="env">-g</span><dt><span class="env">--extern-only</span><dd><a name="index-external-symbols-43"></a>Display only external symbols.
<br><dt><span class="env">-l</span><dt><span class="env">--line-numbers</span><dd><a name="index-symbol-line-numbers-44"></a>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.
<br><dt><span class="env">-n</span><dt><span class="env">-v</span><dt><span class="env">--numeric-sort</span><dd>Sort symbols numerically by their addresses, rather than alphabetically
by their names.
<br><dt><span class="env">-p</span><dt><span class="env">--no-sort</span><dd><a name="index-sorting-symbols-45"></a>Do not bother to sort the symbols in any order; print them in the order
encountered.
<br><dt><span class="env">-P</span><dt><span class="env">--portability</span><dd>Use the POSIX.2 standard output format instead of the default format.
Equivalent to <span class="samp">-f posix</span>.
<br><dt><span class="env">-S</span><dt><span class="env">--print-size</span><dd>Print size, not the value, of defined symbols for the <code>bsd</code> output format.
<br><dt><span class="env">-s</span><dt><span class="env">--print-armap</span><dd><a name="index-symbol-index_002c-listing-46"></a>When listing symbols from archive members, include the index: a mapping
(stored in the archive by <span class="command">ar</span> or <span class="command">ranlib</span>) of which modules
contain definitions for which names.
<br><dt><span class="env">-r</span><dt><span class="env">--reverse-sort</span><dd>Reverse the order of the sort (whether numeric or alphabetic); let the
last come first.
<br><dt><span class="env">--size-sort</span><dd>Sort symbols by size. The size is 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</code> output format is used the size of the symbol
is printed, rather than the value, and <span class="samp">-S</span> must be used in order
both size and value to be printed.
<br><dt><span class="env">--special-syms</span><dd>Display symbols which have a target-specific special meaning. These
symbols are usually used by the target for some special processing and
are not normally helpful when included 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.
<br><dt><span class="env">-t </span><var>radix</var><dt><span class="env">--radix=</span><var>radix</var><dd>Use <var>radix</var> as the radix for printing the symbol values. It must be
<span class="samp">d</span> for decimal, <span class="samp">o</span> for octal, or <span class="samp">x</span> for hexadecimal.
<br><dt><span class="env">--target=</span><var>bfdname</var><dd><a name="index-object-code-format-47"></a>Specify an object code format other than your system's default format.
See <a href="Target-Selection.html#Target-Selection">Target Selection</a>, for more information.
<br><dt><span class="env">-u</span><dt><span class="env">--undefined-only</span><dd><a name="index-external-symbols-48"></a><a name="index-undefined-symbols-49"></a>Display only undefined symbols (those external to each object file).
<br><dt><span class="env">--defined-only</span><dd><a name="index-external-symbols-50"></a><a name="index-undefined-symbols-51"></a>Display only defined symbols for each object file.
<br><dt><span class="env">-V</span><dt><span class="env">--version</span><dd>Show the version number of <span class="command">nm</span> and exit.
<br><dt><span class="env">-X</span><dd>This option is ignored for compatibility with the AIX version of
<span class="command">nm</span>. It takes one parameter which must be the string
<span class="option">32_64</span>. The default mode of AIX <span class="command">nm</span> corresponds
to <span class="option">-X 32</span>, which is not supported by <span class="sc">gnu</span> <span class="command">nm</span>.
<br><dt><span class="env">--help</span><dd>Show a summary of the options to <span class="command">nm</span> and exit.
</dl>
<!-- man end -->
</body></html>

View file

@ -0,0 +1,546 @@
<html lang="en">
<head>
<title>objcopy - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="nm.html#nm" title="nm">
<link rel="next" href="objdump.html#objdump" title="objdump">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="objcopy"></a>Next:&nbsp;<a rel="next" accesskey="n" href="objdump.html#objdump">objdump</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="nm.html#nm">nm</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">3 objcopy</h2>
<!-- man title objcopy copy and translate object files -->
<pre class="smallexample"> <!-- man begin SYNOPSIS objcopy -->
objcopy [<span class="option">-F</span> <var>bfdname</var>|<span class="option">--target=</span><var>bfdname</var>]
[<span class="option">-I</span> <var>bfdname</var>|<span class="option">--input-target=</span><var>bfdname</var>]
[<span class="option">-O</span> <var>bfdname</var>|<span class="option">--output-target=</span><var>bfdname</var>]
[<span class="option">-B</span> <var>bfdarch</var>|<span class="option">--binary-architecture=</span><var>bfdarch</var>]
[<span class="option">-S</span>|<span class="option">--strip-all</span>]
[<span class="option">-g</span>|<span class="option">--strip-debug</span>]
[<span class="option">-K</span> <var>symbolname</var>|<span class="option">--keep-symbol=</span><var>symbolname</var>]
[<span class="option">-N</span> <var>symbolname</var>|<span class="option">--strip-symbol=</span><var>symbolname</var>]
[<span class="option">--strip-unneeded-symbol=</span><var>symbolname</var>]
[<span class="option">-G</span> <var>symbolname</var>|<span class="option">--keep-global-symbol=</span><var>symbolname</var>]
[<span class="option">--localize-hidden</span>]
[<span class="option">-L</span> <var>symbolname</var>|<span class="option">--localize-symbol=</span><var>symbolname</var>]
[<span class="option">--globalize-symbol=</span><var>symbolname</var>]
[<span class="option">-W</span> <var>symbolname</var>|<span class="option">--weaken-symbol=</span><var>symbolname</var>]
[<span class="option">-w</span>|<span class="option">--wildcard</span>]
[<span class="option">-x</span>|<span class="option">--discard-all</span>]
[<span class="option">-X</span>|<span class="option">--discard-locals</span>]
[<span class="option">-b</span> <var>byte</var>|<span class="option">--byte=</span><var>byte</var>]
[<span class="option">-i</span> <var>interleave</var>|<span class="option">--interleave=</span><var>interleave</var>]
[<span class="option">-j</span> <var>sectionname</var>|<span class="option">--only-section=</span><var>sectionname</var>]
[<span class="option">-R</span> <var>sectionname</var>|<span class="option">--remove-section=</span><var>sectionname</var>]
[<span class="option">-p</span>|<span class="option">--preserve-dates</span>]
[<span class="option">--debugging</span>]
[<span class="option">--gap-fill=</span><var>val</var>]
[<span class="option">--pad-to=</span><var>address</var>]
[<span class="option">--set-start=</span><var>val</var>]
[<span class="option">--adjust-start=</span><var>incr</var>]
[<span class="option">--change-addresses=</span><var>incr</var>]
[<span class="option">--change-section-address</span> <var>section</var>{=,+,-}<var>val</var>]
[<span class="option">--change-section-lma</span> <var>section</var>{=,+,-}<var>val</var>]
[<span class="option">--change-section-vma</span> <var>section</var>{=,+,-}<var>val</var>]
[<span class="option">--change-warnings</span>] [<span class="option">--no-change-warnings</span>]
[<span class="option">--set-section-flags</span> <var>section</var>=<var>flags</var>]
[<span class="option">--add-section</span> <var>sectionname</var>=<var>filename</var>]
[<span class="option">--rename-section</span> <var>oldname</var>=<var>newname</var>[,<var>flags</var>]]
[<span class="option">--change-leading-char</span>] [<span class="option">--remove-leading-char</span>]
[<span class="option">--reverse-bytes=</span><var>num</var>]
[<span class="option">--srec-len=</span><var>ival</var>] [<span class="option">--srec-forceS3</span>]
[<span class="option">--redefine-sym</span> <var>old</var>=<var>new</var>]
[<span class="option">--redefine-syms=</span><var>filename</var>]
[<span class="option">--weaken</span>]
[<span class="option">--keep-symbols=</span><var>filename</var>]
[<span class="option">--strip-symbols=</span><var>filename</var>]
[<span class="option">--strip-unneeded-symbols=</span><var>filename</var>]
[<span class="option">--keep-global-symbols=</span><var>filename</var>]
[<span class="option">--localize-symbols=</span><var>filename</var>]
[<span class="option">--globalize-symbols=</span><var>filename</var>]
[<span class="option">--weaken-symbols=</span><var>filename</var>]
[<span class="option">--alt-machine-code=</span><var>index</var>]
[<span class="option">--prefix-symbols=</span><var>string</var>]
[<span class="option">--prefix-sections=</span><var>string</var>]
[<span class="option">--prefix-alloc-sections=</span><var>string</var>]
[<span class="option">--add-gnu-debuglink=</span><var>path-to-file</var>]
[<span class="option">--keep-file-symbols</span>]
[<span class="option">--only-keep-debug</span>]
[<span class="option">--extract-symbol</span>]
[<span class="option">--writable-text</span>]
[<span class="option">--readonly-text</span>]
[<span class="option">--pure</span>]
[<span class="option">--impure</span>]
[<span class="option">-v</span>|<span class="option">--verbose</span>]
[<span class="option">-V</span>|<span class="option">--version</span>]
[<span class="option">--help</span>] [<span class="option">--info</span>]
<var>infile</var> [<var>outfile</var>]
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION objcopy -->
<p>The <span class="sc">gnu</span> <span class="command">objcopy</span> utility copies the contents of an object
file to another. <span class="command">objcopy</span> uses the <span class="sc">gnu</span> <span class="sc">bfd</span> Library to
read and write the object files. It can write the destination object
file in a format different from that of the source object file. The
exact behavior of <span class="command">objcopy</span> is controlled by command-line options.
Note that <span class="command">objcopy</span> should be able to copy a fully linked file
between any two formats. However, copying a relocatable object file
between any two formats may not work as expected.
<p><span class="command">objcopy</span> creates temporary files to do its translations and
deletes them afterward. <span class="command">objcopy</span> uses <span class="sc">bfd</span> to do all its
translation work; it has access to all the formats described in <span class="sc">bfd</span>
and thus is able to recognize most formats without being told
explicitly. See <a href="../ld/BFD.html#BFD">BFD (Using LD)</a>.
<p><span class="command">objcopy</span> can be used to generate S-records by using an output
target of <span class="samp">srec</span> (e.g., use <span class="samp">-O srec</span>).
<p><span class="command">objcopy</span> can be used to generate a raw binary file by using an
output target of <span class="samp">binary</span> (e.g., use <span class="option">-O binary</span>). When
<span class="command">objcopy</span> generates a raw binary file, it will essentially produce
a memory dump of the contents of the input object file. All symbols and
relocation information will be discarded. The memory dump will start at
the load address of the lowest section copied into the output file.
<p>When generating an S-record or a raw binary file, it may be helpful to
use <span class="option">-S</span> to remove sections containing debugging information. In
some cases <span class="option">-R</span> will be useful to remove sections which contain
information that is not needed by the binary file.
<p>Note&mdash;<span class="command">objcopy</span> is not able to change the endianness of its input
files. If the input format has an endianness (some formats do not),
<span class="command">objcopy</span> can only copy the inputs into file formats that have the
same endianness or which have no endianness (e.g., <span class="samp">srec</span>).
(However, see the <span class="option">--reverse-bytes</span> option.)
<!-- man end -->
<!-- man begin OPTIONS objcopy -->
<dl>
<dt><var>infile</var><dt><var>outfile</var><dd>The input and output files, respectively.
If you do not specify <var>outfile</var>, <span class="command">objcopy</span> creates a
temporary file and destructively renames the result with
the name of <var>infile</var>.
<br><dt><span class="env">-I </span><var>bfdname</var><dt><span class="env">--input-target=</span><var>bfdname</var><dd>Consider the source file's object format to be <var>bfdname</var>, rather than
attempting to deduce it. See <a href="Target-Selection.html#Target-Selection">Target Selection</a>, for more information.
<br><dt><span class="env">-O </span><var>bfdname</var><dt><span class="env">--output-target=</span><var>bfdname</var><dd>Write the output file using the object format <var>bfdname</var>.
See <a href="Target-Selection.html#Target-Selection">Target Selection</a>, for more information.
<br><dt><span class="env">-F </span><var>bfdname</var><dt><span class="env">--target=</span><var>bfdname</var><dd>Use <var>bfdname</var> as the object format for both the input and the output
file; i.e., simply transfer data from source to destination with no
translation. See <a href="Target-Selection.html#Target-Selection">Target Selection</a>, for more information.
<br><dt><span class="env">-B </span><var>bfdarch</var><dt><span class="env">--binary-architecture=</span><var>bfdarch</var><dd>Useful when transforming a raw binary input file into an object file.
In this case the output architecture can be set to <var>bfdarch</var>. This
option will be ignored if the input file has a known <var>bfdarch</var>. You
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</var>_start, _binary_<var>objfile</var>_end and
_binary_<var>objfile</var>_size. e.g. you can transform a picture file into
an object file and then access it in your code using these symbols.
<br><dt><span class="env">-j </span><var>sectionname</var><dt><span class="env">--only-section=</span><var>sectionname</var><dd>Copy only the named section from the input file to the output file.
This option may be given more than once. Note that using this option
inappropriately may make the output file unusable.
<br><dt><span class="env">-R </span><var>sectionname</var><dt><span class="env">--remove-section=</span><var>sectionname</var><dd>Remove any section named <var>sectionname</var> from the output file. This
option may be given more than once. Note that using this option
inappropriately may make the output file unusable.
<br><dt><span class="env">-S</span><dt><span class="env">--strip-all</span><dd>Do not copy relocation and symbol information from the source file.
<br><dt><span class="env">-g</span><dt><span class="env">--strip-debug</span><dd>Do not copy debugging symbols or sections from the source file.
<br><dt><span class="env">--strip-unneeded</span><dd>Strip all symbols that are not needed for relocation processing.
<br><dt><span class="env">-K </span><var>symbolname</var><dt><span class="env">--keep-symbol=</span><var>symbolname</var><dd>When stripping symbols, keep symbol <var>symbolname</var> even if it would
normally be stripped. This option may be given more than once.
<br><dt><span class="env">-N </span><var>symbolname</var><dt><span class="env">--strip-symbol=</span><var>symbolname</var><dd>Do not copy symbol <var>symbolname</var> from the source file. This option
may be given more than once.
<br><dt><span class="env">--strip-unneeded-symbol=</span><var>symbolname</var><dd>Do not copy symbol <var>symbolname</var> from the source file unless it is needed
by a relocation. This option may be given more than once.
<br><dt><span class="env">-G </span><var>symbolname</var><dt><span class="env">--keep-global-symbol=</span><var>symbolname</var><dd>Keep only symbol <var>symbolname</var> global. Make all other symbols local
to the file, so that they are not visible externally. This option may
be given more than once.
<br><dt><span class="env">--localize-hidden</span><dd>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 <span class="option">-L</span>.
<br><dt><span class="env">-L </span><var>symbolname</var><dt><span class="env">--localize-symbol=</span><var>symbolname</var><dd>Make symbol <var>symbolname</var> local to the file, so that it is not
visible externally. This option may be given more than once.
<br><dt><span class="env">-W </span><var>symbolname</var><dt><span class="env">--weaken-symbol=</span><var>symbolname</var><dd>Make symbol <var>symbolname</var> weak. This option may be given more than once.
<br><dt><span class="env">--globalize-symbol=</span><var>symbolname</var><dd>Give symbol <var>symbolname</var> global scoping so that it is visible
outside of the file in which it is defined. This option may be given
more than once.
<br><dt><span class="env">-w</span><dt><span class="env">--wildcard</span><dd>Permit regular expressions in <var>symbolname</var>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:
<pre class="smallexample"> -w -W !foo -W fo*
</pre>
<p>would cause objcopy to weaken all symbols that start with &ldquo;fo&rdquo;
except for the symbol &ldquo;foo&rdquo;.
<br><dt><span class="env">-x</span><dt><span class="env">--discard-all</span><dd>Do not copy non-global symbols from the source file.
<!-- FIXME any reason to prefer "non-global" to "local" here? -->
<br><dt><span class="env">-X</span><dt><span class="env">--discard-locals</span><dd>Do not copy compiler-generated local symbols.
(These usually start with <span class="samp">L</span> or <span class="samp">.</span>.)
<br><dt><span class="env">-b </span><var>byte</var><dt><span class="env">--byte=</span><var>byte</var><dd>Keep only every <var>byte</var>th byte of the input file (header data is not
affected). <var>byte</var> can be in the range from 0 to <var>interleave</var>-1,
where <var>interleave</var> is given by the <span class="option">-i</span> or <span class="option">--interleave</span>
option, or the default of 4. This option is useful for creating files
to program <span class="sc">rom</span>. It is typically used with an <code>srec</code> output
target.
<br><dt><span class="env">-i </span><var>interleave</var><dt><span class="env">--interleave=</span><var>interleave</var><dd>Only copy one out of every <var>interleave</var> bytes. Select which byte to
copy with the <span class="option">-b</span> or <span class="option">--byte</span> option. The default is 4.
<span class="command">objcopy</span> ignores this option if you do not specify either <span class="option">-b</span> or
<span class="option">--byte</span>.
<br><dt><span class="env">-p</span><dt><span class="env">--preserve-dates</span><dd>Set the access and modification dates of the output file to be the same
as those of the input file.
<br><dt><span class="env">--debugging</span><dd>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.
<br><dt><span class="env">--gap-fill </span><var>val</var><dd>Fill gaps between sections with <var>val</var>. This operation applies to
the <em>load address</em> (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</var>.
<br><dt><span class="env">--pad-to </span><var>address</var><dd>Pad the output file up to the load address <var>address</var>. This is
done by increasing the size of the last section. The extra space is
filled in with the value specified by <span class="option">--gap-fill</span> (default zero).
<br><dt><span class="env">--set-start </span><var>val</var><dd>Set the start address of the new file to <var>val</var>. Not all object file
formats support setting the start address.
<br><dt><span class="env">--change-start </span><var>incr</var><dt><span class="env">--adjust-start </span><var>incr</var><dd><a name="index-changing-start-address-52"></a>Change the start address by adding <var>incr</var>. Not all object file
formats support setting the start address.
<br><dt><span class="env">--change-addresses </span><var>incr</var><dt><span class="env">--adjust-vma </span><var>incr</var><dd><a name="index-changing-object-addresses-53"></a>Change the VMA and LMA addresses of all sections, as well as the start
address, by adding <var>incr</var>. 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
that they are loaded at a different address, the program may fail.
<br><dt><span class="env">--change-section-address </span><var>section</var><span class="env">{=,+,-}</span><var>val</var><dt><span class="env">--adjust-section-vma </span><var>section</var><span class="env">{=,+,-}</span><var>val</var><dd><a name="index-changing-section-address-54"></a>Set or change both the VMA address and the LMA address of the named
<var>section</var>. If <span class="samp">=</span> is used, the section address is set to
<var>val</var>. Otherwise, <var>val</var> is added to or subtracted from the
section address. See the comments under <span class="option">--change-addresses</span>,
above. If <var>section</var> does not exist in the input file, a warning will
be issued, unless <span class="option">--no-change-warnings</span> is used.
<br><dt><span class="env">--change-section-lma </span><var>section</var><span class="env">{=,+,-}</span><var>val</var><dd><a name="index-changing-section-LMA-55"></a>Set or change the LMA address of the named <var>section</var>. 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 <span class="samp">=</span> is used, the section address is set to
<var>val</var>. Otherwise, <var>val</var> is added to or subtracted from the
section address. See the comments under <span class="option">--change-addresses</span>,
above. If <var>section</var> does not exist in the input file, a warning
will be issued, unless <span class="option">--no-change-warnings</span> is used.
<br><dt><span class="env">--change-section-vma </span><var>section</var><span class="env">{=,+,-}</span><var>val</var><dd><a name="index-changing-section-VMA-56"></a>Set or change the VMA address of the named <var>section</var>. 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, especially those where a program is held in
ROM, the two can be different. If <span class="samp">=</span> is used, the section address
is set to <var>val</var>. Otherwise, <var>val</var> is added to or subtracted
from the section address. See the comments under
<span class="option">--change-addresses</span>, above. If <var>section</var> does not exist in
the input file, a warning will be issued, unless
<span class="option">--no-change-warnings</span> is used.
<br><dt><span class="env">--change-warnings</span><dt><span class="env">--adjust-warnings</span><dd>If <span class="option">--change-section-address</span> or <span class="option">--change-section-lma</span> or
<span class="option">--change-section-vma</span> is used, and the named section does not
exist, issue a warning. This is the default.
<br><dt><span class="env">--no-change-warnings</span><dt><span class="env">--no-adjust-warnings</span><dd>Do not issue a warning if <span class="option">--change-section-address</span> or
<span class="option">--adjust-section-lma</span> or <span class="option">--adjust-section-vma</span> is used, even
if the named section does not exist.
<br><dt><span class="env">--set-section-flags </span><var>section</var><span class="env">=</span><var>flags</var><dd>Set the flags for the named section. The <var>flags</var> argument is a
comma separated string of flag names. The recognized names are
<span class="samp">alloc</span>, <span class="samp">contents</span>, <span class="samp">load</span>, <span class="samp">noload</span>,
<span class="samp">readonly</span>, <span class="samp">code</span>, <span class="samp">data</span>, <span class="samp">rom</span>, <span class="samp">share</span>, and
<span class="samp">debug</span>. You can set the <span class="samp">contents</span> flag for a section which
does not have contents, but it is not meaningful to clear the
<span class="samp">contents</span> flag of a section which does have contents&ndash;just remove
the section instead. Not all flags are meaningful for all object file
formats.
<br><dt><span class="env">--add-section </span><var>sectionname</var><span class="env">=</span><var>filename</var><dd>Add a new section named <var>sectionname</var> while copying the file. The
contents of the new section are taken from the file <var>filename</var>. 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.
<br><dt><span class="env">--rename-section </span><var>oldname</var><span class="env">=</span><var>newname</var><span class="env">[,</span><var>flags</var><span class="env">]</span><dd>Rename a section from <var>oldname</var> to <var>newname</var>, optionally
changing the section's flags to <var>flags</var> in the process. This has
the advantage over usng a linker script to perform the rename in that
the output stays as an object file and does not become a linked
executable.
<p>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:
<pre class="smallexample"> objcopy -I binary -O &lt;output_format&gt; -B &lt;architecture&gt; \
--rename-section .data=.rodata,alloc,load,readonly,data,contents \
&lt;input_binary_file&gt; &lt;output_object_file&gt;
</pre>
<br><dt><span class="env">--change-leading-char</span><dd>Some object file formats use special characters at the start of
symbols. The most common such character is underscore, which compilers
often add before every symbol. This option tells <span class="command">objcopy</span> to
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.
<br><dt><span class="env">--remove-leading-char</span><dd>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
<span class="option">--change-leading-char</span> because it always changes the symbol name
when appropriate, regardless of the object file format of the output
file.
<br><dt><span class="env">--reverse-bytes=</span><var>num</var><dd>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.
<p>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.
<p>Consider a simple file with a section containing the following eight
bytes: <code>12345678</code>.
<p>Using <span class="samp">--reverse-bytes=2</span> for the above example, the bytes in the
output file would be ordered <code>21436587</code>.
<p>Using <span class="samp">--reverse-bytes=4</span> for the above example, the bytes in the
output file would be ordered <code>43218765</code>.
<p>By using <span class="samp">--reverse-bytes=2</span> for the above example, followed by
<span class="samp">--reverse-bytes=4</span> on the output file, the bytes in the second
output file would be ordered <code>34127856</code>.
<br><dt><span class="env">--srec-len=</span><var>ival</var><dd>Meaningful only for srec output. Set the maximum length of the Srecords
being produced to <var>ival</var>. This length covers both address, data and
crc fields.
<br><dt><span class="env">--srec-forceS3</span><dd>Meaningful only for srec output. Avoid generation of S1/S2 records,
creating S3-only record format.
<br><dt><span class="env">--redefine-sym </span><var>old</var><span class="env">=</span><var>new</var><dd>Change the name of a symbol <var>old</var>, to <var>new</var>. This can be useful
when one is trying link two things together for which you have no
source, and there are name collisions.
<br><dt><span class="env">--redefine-syms=</span><var>filename</var><dd>Apply <span class="option">--redefine-sym</span> to each symbol pair "<var>old</var> <var>new</var>"
listed in the file <var>filename</var>. <var>filename</var> 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.
<br><dt><span class="env">--weaken</span><dd>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
the <span class="option">-R</span> option to the linker. This option is only effective when
using an object file format which supports weak symbols.
<br><dt><span class="env">--keep-symbols=</span><var>filename</var><dd>Apply <span class="option">--keep-symbol</span> option to each symbol listed in the file
<var>filename</var>. <var>filename</var> 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.
<br><dt><span class="env">--strip-symbols=</span><var>filename</var><dd>Apply <span class="option">--strip-symbol</span> option to each symbol listed in the file
<var>filename</var>. <var>filename</var> 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.
<br><dt><span class="env">--strip-unneeded-symbols=</span><var>filename</var><dd>Apply <span class="option">--strip-unneeded-symbol</span> option to each symbol listed in
the file <var>filename</var>. <var>filename</var> 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.
<br><dt><span class="env">--keep-global-symbols=</span><var>filename</var><dd>Apply <span class="option">--keep-global-symbol</span> option to each symbol listed in the
file <var>filename</var>. <var>filename</var> 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.
<br><dt><span class="env">--localize-symbols=</span><var>filename</var><dd>Apply <span class="option">--localize-symbol</span> option to each symbol listed in the file
<var>filename</var>. <var>filename</var> 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.
<br><dt><span class="env">--globalize-symbols=</span><var>filename</var><dd>Apply <span class="option">--globalize-symbol</span> option to each symbol listed in the file
<var>filename</var>. <var>filename</var> 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.
<br><dt><span class="env">--weaken-symbols=</span><var>filename</var><dd>Apply <span class="option">--weaken-symbol</span> option to each symbol listed in the file
<var>filename</var>. <var>filename</var> 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.
<br><dt><span class="env">--alt-machine-code=</span><var>index</var><dd>If the output architecture has alternate machine codes, use the
<var>index</var>th code instead of the default one. This is useful in case
a machine is assigned an official code and the tool-chain adopts the
new code, but other applications still depend on the original code
being used. For ELF based architectures if the <var>index</var>
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.
<br><dt><span class="env">--writable-text</span><dd>Mark the output text as writable. This option isn't meaningful for all
object file formats.
<br><dt><span class="env">--readonly-text</span><dd>Make the output text write protected. This option isn't meaningful for all
object file formats.
<br><dt><span class="env">--pure</span><dd>Mark the output file as demand paged. This option isn't meaningful for all
object file formats.
<br><dt><span class="env">--impure</span><dd>Mark the output file as impure. This option isn't meaningful for all
object file formats.
<br><dt><span class="env">--prefix-symbols=</span><var>string</var><dd>Prefix all symbols in the output file with <var>string</var>.
<br><dt><span class="env">--prefix-sections=</span><var>string</var><dd>Prefix all section names in the output file with <var>string</var>.
<br><dt><span class="env">--prefix-alloc-sections=</span><var>string</var><dd>Prefix all the names of all allocated sections in the output file with
<var>string</var>.
<br><dt><span class="env">--add-gnu-debuglink=</span><var>path-to-file</var><dd>Creates a .gnu_debuglink section which contains a reference to <var>path-to-file</var>
and adds it to the output file.
<br><dt><span class="env">--keep-file-symbols</span><dd>When stripping a file, perhaps with <span class="option">--strip-debug</span> or
<span class="option">--strip-unneeded</span>, retain any symbols specifying source file names,
which would otherwise get stripped.
<br><dt><span class="env">--only-keep-debug</span><dd>Strip a file, removing contents of any sections that would not be
stripped by <span class="option">--strip-debug</span> and leaving the debugging sections
intact. In ELF files, this preserves all note sections in the output.
<p>The intention is that this option will be used in conjunction with
<span class="option">--add-gnu-debuglink</span> 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:
<ol type=1 start=1>
<li>Link the executable as normal. Assuming that is is called
<code>foo</code> then...
<li>Run <code>objcopy --only-keep-debug foo foo.dbg</code> to
create a file containing the debugging info.
<li>Run <code>objcopy --strip-debug foo</code> to create a
stripped executable.
<li>Run <code>objcopy --add-gnu-debuglink=foo.dbg foo</code>
to add a link to the debugging info into the stripped executable.
</ol>
<p>Note&mdash;the choice of <code>.dbg</code> as an extension for the debug info
file is arbitrary. Also the <code>--only-keep-debug</code> step is
optional. You could instead do this:
<ol type=1 start=1>
<li>Link the executable as normal.
<li>Copy <code>foo</code> to <code>foo.full</code>
<li>Run <code>objcopy --strip-debug foo</code>
<li>Run <code>objcopy --add-gnu-debuglink=foo.full foo</code>
</ol>
<p>i.e., the file pointed to by the <span class="option">--add-gnu-debuglink</span> can be the
full executable. It does not have to be a file created by the
<span class="option">--only-keep-debug</span> switch.
<p>Note&mdash;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.
<br><dt><span class="env">--extract-symbol</span><dd>Keep the file's section flags and symbols but remove all section data.
Specifically, the option:
<ul>
<li>removes the contents of all sections;
<li>sets the size of every section to zero; and
<li>sets the file's start address to zero.
</ul>
<p>This option is used to build a <span class="file">.sym</span> file for a VxWorks kernel.
It can also be a useful way of reducing the size of a <span class="option">--just-symbols</span>
linker input file.
<br><dt><span class="env">-V</span><dt><span class="env">--version</span><dd>Show the version number of <span class="command">objcopy</span>.
<br><dt><span class="env">-v</span><dt><span class="env">--verbose</span><dd>Verbose output: list all object files modified. In the case of
archives, <span class="samp">objcopy -V</span> lists all members of the archive.
<br><dt><span class="env">--help</span><dd>Show a summary of the options to <span class="command">objcopy</span>.
<br><dt><span class="env">--info</span><dd>Display a list showing all architectures and object formats available.
</dl>
<!-- man end -->
</body></html>

View file

@ -0,0 +1,427 @@
<html lang="en">
<head>
<title>objdump - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="objcopy.html#objcopy" title="objcopy">
<link rel="next" href="ranlib.html#ranlib" title="ranlib">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="objdump"></a>Next:&nbsp;<a rel="next" accesskey="n" href="ranlib.html#ranlib">ranlib</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="objcopy.html#objcopy">objcopy</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">4 objdump</h2>
<p><a name="index-object-file-information-57"></a><a name="index-objdump-58"></a>
<!-- man title objdump display information from object files. -->
<pre class="smallexample"> <!-- man begin SYNOPSIS objdump -->
objdump [<span class="option">-a</span>|<span class="option">--archive-headers</span>]
[<span class="option">-b</span> <var>bfdname</var>|<span class="option">--target=</span><var>bfdname</var>]
[<span class="option">-C</span>|<span class="option">--demangle</span>[=<var>style</var>] ]
[<span class="option">-d</span>|<span class="option">--disassemble</span>]
[<span class="option">-D</span>|<span class="option">--disassemble-all</span>]
[<span class="option">-z</span>|<span class="option">--disassemble-zeroes</span>]
[<span class="option">-EB</span>|<span class="option">-EL</span>|<span class="option">--endian=</span>{big | little }]
[<span class="option">-f</span>|<span class="option">--file-headers</span>]
[<span class="option">-F</span>|<span class="option">--file-offsets</span>]
[<span class="option">--file-start-context</span>]
[<span class="option">-g</span>|<span class="option">--debugging</span>]
[<span class="option">-e</span>|<span class="option">--debugging-tags</span>]
[<span class="option">-h</span>|<span class="option">--section-headers</span>|<span class="option">--headers</span>]
[<span class="option">-i</span>|<span class="option">--info</span>]
[<span class="option">-j</span> <var>section</var>|<span class="option">--section=</span><var>section</var>]
[<span class="option">-l</span>|<span class="option">--line-numbers</span>]
[<span class="option">-S</span>|<span class="option">--source</span>]
[<span class="option">-m</span> <var>machine</var>|<span class="option">--architecture=</span><var>machine</var>]
[<span class="option">-M</span> <var>options</var>|<span class="option">--disassembler-options=</span><var>options</var>]
[<span class="option">-p</span>|<span class="option">--private-headers</span>]
[<span class="option">-r</span>|<span class="option">--reloc</span>]
[<span class="option">-R</span>|<span class="option">--dynamic-reloc</span>]
[<span class="option">-s</span>|<span class="option">--full-contents</span>]
[<span class="option">-W</span>|<span class="option">--dwarf</span>]
[<span class="option">-G</span>|<span class="option">--stabs</span>]
[<span class="option">-t</span>|<span class="option">--syms</span>]
[<span class="option">-T</span>|<span class="option">--dynamic-syms</span>]
[<span class="option">-x</span>|<span class="option">--all-headers</span>]
[<span class="option">-w</span>|<span class="option">--wide</span>]
[<span class="option">--start-address=</span><var>address</var>]
[<span class="option">--stop-address=</span><var>address</var>]
[<span class="option">--prefix-addresses</span>]
[<span class="option">--[no-]show-raw-insn</span>]
[<span class="option">--adjust-vma=</span><var>offset</var>]
[<span class="option">--special-syms</span>]
[<span class="option">-V</span>|<span class="option">--version</span>]
[<span class="option">-H</span>|<span class="option">--help</span>]
<var>objfile</var>...
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION objdump -->
<p><span class="command">objdump</span> displays information about one or more object files.
The options control what particular information to display. This
information is mostly useful to programmers who are working on the
compilation tools, as opposed to programmers who just want their
program to compile and work.
<p><var>objfile</var><small class="dots">...</small> are the object files to be examined. When you
specify archives, <span class="command">objdump</span> shows information on each of the member
object files.
<!-- man end -->
<!-- man begin OPTIONS objdump -->
<p>The long and short forms of options, shown here as alternatives, are
equivalent. At least one option from the list
<span class="option">-a,-d,-D,-e,-f,-g,-G,-h,-H,-p,-r,-R,-s,-S,-t,-T,-V,-x</span> must be given.
<dl>
<dt><span class="env">-a</span><dt><span class="env">--archive-header</span><dd><a name="index-archive-headers-59"></a>If any of the <var>objfile</var> files are archives, display the archive
header information (in a format similar to <span class="samp">ls -l</span>). Besides the
information you could list with <span class="samp">ar tv</span>, <span class="samp">objdump -a</span> shows
the object file format of each archive member.
<br><dt><span class="env">--adjust-vma=</span><var>offset</var><dd><a name="index-section-addresses-in-objdump-60"></a><a name="index-VMA-in-objdump-61"></a>When dumping information, first add <var>offset</var> 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.
<br><dt><span class="env">-b </span><var>bfdname</var><dt><span class="env">--target=</span><var>bfdname</var><dd><a name="index-object-code-format-62"></a>Specify that the object-code format for the object files is
<var>bfdname</var>. This option may not be necessary; <var>objdump</var> can
automatically recognize many formats.
<p>For example,
<pre class="example"> objdump -b oasys -m vax -h fu.o
</pre>
<p class="noindent">displays summary information from the section headers (<span class="option">-h</span>) of
<span class="file">fu.o</span>, which is explicitly identified (<span class="option">-m</span>) as a VAX object
file in the format produced by Oasys compilers. You can list the
formats available with the <span class="option">-i</span> option.
See <a href="Target-Selection.html#Target-Selection">Target Selection</a>, for more information.
<br><dt><span class="env">-C</span><dt><span class="env">--demangle[=</span><var>style</var><span class="env">]</span><dd><a name="index-demangling-in-objdump-63"></a>Decode (<dfn>demangle</dfn>) low-level symbol names into user-level names.
Besides removing any initial underscore prepended by the system, this
makes C++ function names readable. Different compilers have different
mangling styles. The optional demangling style argument can be used to
choose an appropriate demangling style for your compiler. See <a href="c_002b_002bfilt.html#c_002b_002bfilt">c++filt</a>,
for more information on demangling.
<br><dt><span class="env">-g</span><dt><span class="env">--debugging</span><dd>Display debugging information. This attempts to parse STABS and IEEE
debugging format information stored in the file and print it out using
a C like syntax. If neither of these formats are found this option
falls back on the <span class="option">-W</span> option to print any DWARF information in
the file.
<br><dt><span class="env">-e</span><dt><span class="env">--debugging-tags</span><dd>Like <span class="option">-g</span>, but the information is generated in a format compatible
with ctags tool.
<br><dt><span class="env">-d</span><dt><span class="env">--disassemble</span><dd><a name="index-disassembling-object-code-64"></a><a name="index-machine-instructions-65"></a>Display the assembler mnemonics for the machine instructions from
<var>objfile</var>. This option only disassembles those sections which are
expected to contain instructions.
<br><dt><span class="env">-D</span><dt><span class="env">--disassemble-all</span><dd>Like <span class="option">-d</span>, but disassemble the contents of all sections, not just
those expected to contain instructions.
<br><dt><span class="env">--prefix-addresses</span><dd>When disassembling, print the complete address on each line. This is
the older disassembly format.
<br><dt><span class="env">-EB</span><dt><span class="env">-EL</span><dt><span class="env">--endian={big|little}</span><dd><a name="index-endianness-66"></a><a name="index-disassembly-endianness-67"></a>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.
<br><dt><span class="env">-f</span><dt><span class="env">--file-headers</span><dd><a name="index-object-file-header-68"></a>Display summary information from the overall header of
each of the <var>objfile</var> files.
<br><dt><span class="env">-F</span><dt><span class="env">--file-offsets</span><dd><a name="index-object-file-offsets-69"></a>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
location from where the disassembly resumes. When dumping sections,
display the file offset of the location from where the dump starts.
<br><dt><span class="env">--file-start-context</span><dd><a name="index-source-code-context-70"></a>Specify that when displaying interlisted source code/disassembly
(assumes <span class="option">-S</span>) from a file that has not yet been displayed, extend the
context to the start of the file.
<br><dt><span class="env">-h</span><dt><span class="env">--section-headers</span><dt><span class="env">--headers</span><dd><a name="index-section-headers-71"></a>Display summary information from the section headers of the
object file.
<p>File segments may be relocated to nonstandard addresses, for example by
using the <span class="option">-Ttext</span>, <span class="option">-Tdata</span>, or <span class="option">-Tbss</span> options to
<span class="command">ld</span>. However, some object file formats, such as a.out, do not
store the starting address of the file segments. In those situations,
although <span class="command">ld</span> relocates the sections correctly, using <span class="samp">objdump
-h</span> to list the file section headers cannot show the correct addresses.
Instead, it shows the usual addresses, which are implicit for the
target.
<br><dt><span class="env">-H</span><dt><span class="env">--help</span><dd>Print a summary of the options to <span class="command">objdump</span> and exit.
<br><dt><span class="env">-i</span><dt><span class="env">--info</span><dd><a name="index-architectures-available-72"></a><a name="index-object-formats-available-73"></a>Display a list showing all architectures and object formats available
for specification with <span class="option">-b</span> or <span class="option">-m</span>.
<br><dt><span class="env">-j </span><var>name</var><dt><span class="env">--section=</span><var>name</var><dd><a name="index-section-information-74"></a>Display information only for section <var>name</var>.
<br><dt><span class="env">-l</span><dt><span class="env">--line-numbers</span><dd><a name="index-source-filenames-for-object-files-75"></a>Label the display (using debugging information) with the filename and
source line numbers corresponding to the object code or relocs shown.
Only useful with <span class="option">-d</span>, <span class="option">-D</span>, or <span class="option">-r</span>.
<br><dt><span class="env">-m </span><var>machine</var><dt><span class="env">--architecture=</span><var>machine</var><dd><a name="index-architecture-76"></a><a name="index-disassembly-architecture-77"></a>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
architectures with the <span class="option">-i</span> option.
<br><dt><span class="env">-M </span><var>options</var><dt><span class="env">--disassembler-options=</span><var>options</var><dd>Pass target specific information to the disassembler. Only supported on
some targets. If it is necessary to specify more than one
disassembler option then multiple <span class="option">-M</span> options can be used or
can be placed together into a comma separated list.
<p>If the target is an ARM architecture then this switch can be used to
select which register name set is used during disassembler. Specifying
<span class="option">-M reg-names-std</span> (the default) will select the register names as
used in ARM's instruction set documentation, but with register 13 called
'sp', register 14 called 'lr' and register 15 called 'pc'. Specifying
<span class="option">-M reg-names-apcs</span> will select the name set used by the ARM
Procedure Call Standard, whilst specifying <span class="option">-M reg-names-raw</span> will
just use <span class="samp">r</span> followed by the register number.
<p>There are also two variants on the APCS register naming scheme enabled
by <span class="option">-M reg-names-atpcs</span> and <span class="option">-M reg-names-special-atpcs</span> which
use the ARM/Thumb Procedure Call Standard naming conventions. (Either
with the normal register names or the special register names).
<p>This option can also be used for ARM architectures to force the
disassembler to interpret all instructions as Thumb instructions by
using the switch <span class="option">--disassembler-options=force-thumb</span>. This can be
useful when attempting to disassemble thumb code produced by other
compilers.
<p>For the x86, some of the options duplicate functions of the <span class="option">-m</span>
switch, but allow finer grained control. Multiple selections from the
following may be specified as a comma separated string.
<span class="option">x86-64</span>, <span class="option">i386</span> and <span class="option">i8086</span> select disassembly for
the given architecture. <span class="option">intel</span> and <span class="option">att</span> select between
intel syntax mode and AT&amp;T syntax mode.
<span class="option">intel-mnemonic</span> and <span class="option">att-mnemonic</span> select between
intel mnemonic mode and AT&amp;T mnemonic mode. <span class="option">intel-mnemonic</span>
implies <span class="option">intel</span> and <span class="option">att-mnemonic</span> implies <span class="option">att</span>.
<span class="option">addr64</span>, <span class="option">addr32</span>,
<span class="option">addr16</span>, <span class="option">data32</span> and <span class="option">data16</span> specify the default
address size and operand size. These four options will be overridden if
<span class="option">x86-64</span>, <span class="option">i386</span> or <span class="option">i8086</span> appear later in the
option string. Lastly, <span class="option">suffix</span>, when in AT&amp;T mode,
instructs the disassembler to print a mnemonic suffix even when the
suffix could be inferred by the operands.
<p>For PPC, <span class="option">booke</span>, <span class="option">booke32</span> and <span class="option">booke64</span> select
disassembly of BookE instructions. <span class="option">32</span> and <span class="option">64</span> select
PowerPC and PowerPC64 disassembly, respectively. <span class="option">e300</span>
selects disassembly for the e300 family. <span class="option">440</span> selects
disassembly for the PowerPC 440. <span class="option">ppcps</span> selects disassembly
for the paired single instructions of the PPC750CL.
<p>For MIPS, this option controls the printing of instruction mnemonic
names and register names in disassembled instructions. Multiple
selections from the following may be specified as a comma separated
string, and invalid options are ignored:
<dl>
<dt><code>no-aliases</code><dd>Print the 'raw' instruction mnemonic instead of some pseudo
instruction mnemonic. I.e., print 'daddu' or 'or' instead of 'move',
'sll' instead of 'nop', etc.
<br><dt><code>gpr-names=</code><var>ABI</var><dd>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.
<br><dt><code>fpr-names=</code><var>ABI</var><dd>Print FPR (floating-point register) names as
appropriate for the specified ABI. By default, FPR numbers are printed
rather than names.
<br><dt><code>cp0-names=</code><var>ARCH</var><dd>Print CP0 (system control coprocessor; coprocessor 0) register names
as appropriate for the CPU or architecture specified by
<var>ARCH</var>. By default, CP0 register names are selected according to
the architecture and CPU of the binary being disassembled.
<br><dt><code>hwr-names=</code><var>ARCH</var><dd>Print HWR (hardware register, used by the <code>rdhwr</code> instruction) names
as appropriate for the CPU or architecture specified by
<var>ARCH</var>. By default, HWR names are selected according to
the architecture and CPU of the binary being disassembled.
<br><dt><code>reg-names=</code><var>ABI</var><dd>Print GPR and FPR names as appropriate for the selected ABI.
<br><dt><code>reg-names=</code><var>ARCH</var><dd>Print CPU-specific register names (CP0 register and HWR names)
as appropriate for the selected CPU or architecture.
</dl>
<p>For any of the options listed above, <var>ABI</var> or
<var>ARCH</var> may be specified as <span class="samp">numeric</span> to have numbers printed
rather than names, for the selected types of registers.
You can list the available values of <var>ABI</var> and <var>ARCH</var> using
the <span class="option">--help</span> option.
<p>For VAX, you can specify function entry addresses with <span class="option">-M
entry:0xf00ba</span>. You can use this multiple times to properly
disassemble VAX binary files that don't contain symbol tables (like
ROM dumps). In these cases, the function entry mask would otherwise
be decoded as VAX instructions, which would probably lead the rest
of the function being wrongly disassembled.
<br><dt><span class="env">-p</span><dt><span class="env">--private-headers</span><dd>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.
<br><dt><span class="env">-r</span><dt><span class="env">--reloc</span><dd><a name="index-relocation-entries_002c-in-object-file-78"></a>Print the relocation entries of the file. If used with <span class="option">-d</span> or
<span class="option">-D</span>, the relocations are printed interspersed with the
disassembly.
<br><dt><span class="env">-R</span><dt><span class="env">--dynamic-reloc</span><dd><a name="index-dynamic-relocation-entries_002c-in-object-file-79"></a>Print the dynamic relocation entries of the file. This is only
meaningful for dynamic objects, such as certain types of shared
libraries.
<br><dt><span class="env">-s</span><dt><span class="env">--full-contents</span><dd><a name="index-sections_002c-full-contents-80"></a><a name="index-object-file-sections-81"></a>Display the full contents of any sections requested. By default all
non-empty sections are displayed.
<br><dt><span class="env">-S</span><dt><span class="env">--source</span><dd><a name="index-source-disassembly-82"></a><a name="index-disassembly_002c-with-source-83"></a>Display source code intermixed with disassembly, if possible. Implies
<span class="option">-d</span>.
<br><dt><span class="env">--show-raw-insn</span><dd>When disassembling instructions, print the instruction in hex as well as
in symbolic form. This is the default except when
<span class="option">--prefix-addresses</span> is used.
<br><dt><span class="env">--no-show-raw-insn</span><dd>When disassembling instructions, do not print the instruction bytes.
This is the default when <span class="option">--prefix-addresses</span> is used.
<br><dt><span class="env">-W</span><dt><span class="env">--dwarf</span><dd><a name="index-DWARF-84"></a><a name="index-debug-symbols-85"></a>Displays the contents of the DWARF debug sections in the file, if any
are present.
<br><dt><span class="env">-G</span><dt><span class="env">--stabs</span><dd><a name="index-stab-86"></a><a name="index-_002estab-87"></a><a name="index-debug-symbols-88"></a><a name="index-ELF-object-file-format-89"></a>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</code> debugging symbol-table entries are carried in an ELF
section. In most other file formats, debugging symbol-table entries are
interleaved with linkage symbols, and are visible in the <span class="option">--syms</span>
output.
For more information on stabs symbols, see <a href="../stabs/index.html#Top">Stabs (The &ldquo;stabs&rdquo; debug format)</a>.
<br><dt><span class="env">--start-address=</span><var>address</var><dd><a name="index-start_002daddress-90"></a>Start displaying data at the specified address. This affects the output
of the <span class="option">-d</span>, <span class="option">-r</span> and <span class="option">-s</span> options.
<br><dt><span class="env">--stop-address=</span><var>address</var><dd><a name="index-stop_002daddress-91"></a>Stop displaying data at the specified address. This affects the output
of the <span class="option">-d</span>, <span class="option">-r</span> and <span class="option">-s</span> options.
<br><dt><span class="env">-t</span><dt><span class="env">--syms</span><dd><a name="index-symbol-table-entries_002c-printing-92"></a>Print the symbol table entries of the file.
This is similar to the information provided by the <span class="samp">nm</span> 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:
<pre class="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
</pre>
<p>where the number inside the square brackets is the number of the entry
in the symbol table, the <var>sec</var> number is the section number, the
<var>fl</var> value are the symbol's flag bits, the <var>ty</var> number is the
symbol's type, the <var>scl</var> number is the symbol's storage class and
the <var>nx</var> value is the number of auxilary entries associated with
the symbol. The last two fields are the symbol's value and its name.
<p>The other common output format, usually seen with ELF based files,
looks like this:
<pre class="smallexample"> 00000000 l d .bss 00000000 .bss
00000000 g .text 00000000 fred
</pre>
<p>Here the first number is the symbol's value (sometimes refered to as
its address). The next field is actually a set of characters and
spaces indicating the flag bits that are set on the symbol. These
characters are described below. Next is the section with which the
symbol is associated or <em>*ABS*</em> if the section is absolute (ie
not connected with any section), or <em>*UND*</em> if the section is
referenced in the file being dumped, but not defined there.
<p>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.
<p>The flag characters are divided into 7 groups as follows:
<dl>
<dt><code>l</code><dt><code>g</code><dt><code>!</code><dd>The symbol is local (l), global (g), neither (a space) or both (!). A
symbol can be neither local or global for a variety of reasons, e.g.,
because it is used for debugging, but it is probably an indication of
a bug if it is ever both local and global.
<br><dt><code>w</code><dd>The symbol is weak (w) or strong (a space).
<br><dt><code>C</code><dd>The symbol denotes a constructor (C) or an ordinary symbol (a space).
<br><dt><code>W</code><dd>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.
<br><dt><code>I</code><dd>The symbol is an indirect reference to another symbol (I) or a normal
symbol (a space).
<br><dt><code>d</code><dt><code>D</code><dd>The symbol is a debugging symbol (d) or a dynamic symbol (D) or a
normal symbol (a space).
<br><dt><code>F</code><br><dt><code>f</code><br><dt><code>O</code><dd>The symbol is the name of a function (F) or a file (f) or an object
(O) or just a normal symbol (a space).
</dl>
<br><dt><span class="env">-T</span><dt><span class="env">--dynamic-syms</span><dd><a name="index-dynamic-symbol-table-entries_002c-printing-93"></a>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 <span class="samp">nm</span>
program when given the <span class="option">-D</span> (<span class="option">--dynamic</span>) option.
<br><dt><span class="env">--special-syms</span><dd>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.
<br><dt><span class="env">-V</span><dt><span class="env">--version</span><dd>Print the version number of <span class="command">objdump</span> and exit.
<br><dt><span class="env">-x</span><dt><span class="env">--all-headers</span><dd><a name="index-all-header-information_002c-object-file-94"></a><a name="index-header-information_002c-all-95"></a>Display all available header information, including the symbol table and
relocation entries. Using <span class="option">-x</span> is equivalent to specifying all of
<span class="option">-a -f -h -p -r -t</span>.
<br><dt><span class="env">-w</span><dt><span class="env">--wide</span><dd><a name="index-wide-output_002c-printing-96"></a>Format some lines for output devices that have more than 80 columns.
Also do not truncate symbol names when they are displayed.
<br><dt><span class="env">-z</span><dt><span class="env">--disassemble-zeroes</span><dd>Normally the disassembly output will skip blocks of zeroes. This
option directs the disassembler to disassemble those blocks, just like
any other data.
</dl>
<!-- man end -->
</body></html>

View file

@ -0,0 +1,78 @@
<html lang="en">
<head>
<title>ranlib - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="objdump.html#objdump" title="objdump">
<link rel="next" href="readelf.html#readelf" title="readelf">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="ranlib"></a>Next:&nbsp;<a rel="next" accesskey="n" href="readelf.html#readelf">readelf</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="objdump.html#objdump">objdump</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">5 ranlib</h2>
<p><a name="index-ranlib-97"></a><a name="index-archive-contents-98"></a><a name="index-symbol-index-99"></a>
<!-- man title ranlib generate index to archive. -->
<pre class="smallexample"> <!-- man begin SYNOPSIS ranlib -->
ranlib [<span class="option">-vVt</span>] <var>archive</var>
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION ranlib -->
<p><span class="command">ranlib</span> generates an index to the contents of an archive and
stores it in the archive. The index lists each symbol defined by a
member of an archive that is a relocatable object file.
<p>You may use <span class="samp">nm -s</span> or <span class="samp">nm --print-armap</span> to list this index.
<p>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.
<p>The <span class="sc">gnu</span> <span class="command">ranlib</span> program is another form of <span class="sc">gnu</span> <span class="command">ar</span>; running
<span class="command">ranlib</span> is completely equivalent to executing <span class="samp">ar -s</span>.
See <a href="ar.html#ar">ar</a>.
<!-- man end -->
<!-- man begin OPTIONS ranlib -->
<dl>
<dt><span class="env">-v</span><dt><span class="env">-V</span><dt><span class="env">--version</span><dd>Show the version number of <span class="command">ranlib</span>.
<br><dt><span class="env">-t</span><dd>Update the timestamp of the symbol map of an archive.
</dl>
<!-- man end -->
</body></html>

View file

@ -0,0 +1,175 @@
<html lang="en">
<head>
<title>readelf - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="ranlib.html#ranlib" title="ranlib">
<link rel="next" href="size.html#size" title="size">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="readelf"></a>Next:&nbsp;<a rel="next" accesskey="n" href="size.html#size">size</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="ranlib.html#ranlib">ranlib</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">15 readelf</h2>
<p><a name="index-ELF-file-information-126"></a><a name="index-readelf-127"></a>
<!-- man title readelf Displays information about ELF files. -->
<pre class="smallexample"> <!-- man begin SYNOPSIS readelf -->
readelf [<span class="option">-a</span>|<span class="option">--all</span>]
[<span class="option">-h</span>|<span class="option">--file-header</span>]
[<span class="option">-l</span>|<span class="option">--program-headers</span>|<span class="option">--segments</span>]
[<span class="option">-S</span>|<span class="option">--section-headers</span>|<span class="option">--sections</span>]
[<span class="option">-g</span>|<span class="option">--section-groups</span>]
[<span class="option">-t</span>|<span class="option">--section-details</span>]
[<span class="option">-e</span>|<span class="option">--headers</span>]
[<span class="option">-s</span>|<span class="option">--syms</span>|<span class="option">--symbols</span>]
[<span class="option">-n</span>|<span class="option">--notes</span>]
[<span class="option">-r</span>|<span class="option">--relocs</span>]
[<span class="option">-u</span>|<span class="option">--unwind</span>]
[<span class="option">-d</span>|<span class="option">--dynamic</span>]
[<span class="option">-V</span>|<span class="option">--version-info</span>]
[<span class="option">-A</span>|<span class="option">--arch-specific</span>]
[<span class="option">-D</span>|<span class="option">--use-dynamic</span>]
[<span class="option">-x</span> &lt;number or name&gt;|<span class="option">--hex-dump=</span>&lt;number or name&gt;]
[<span class="option">-p</span> &lt;number or name&gt;|<span class="option">--string-dump=</span>&lt;number or name&gt;]
[<span class="option">-c</span>|<span class="option">--archive-index</span>]
[<span class="option">-w[lLiaprmfFsoR]</span>|
<span class="option">--debug-dump</span>[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges]]
[<span class="option">-I</span>|<span class="option">-histogram</span>]
[<span class="option">-v</span>|<span class="option">--version</span>]
[<span class="option">-W</span>|<span class="option">--wide</span>]
[<span class="option">-H</span>|<span class="option">--help</span>]
<var>elffile</var>...
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION readelf -->
<p><span class="command">readelf</span> displays information about one or more ELF format object
files. The options control what particular information to display.
<p><var>elffile</var><small class="dots">...</small> are the object files to be examined. 32-bit and
64-bit ELF files are supported, as are archives containing ELF files.
<p>This program performs a similar function to <span class="command">objdump</span> but it
goes into more detail and it exists independently of the <span class="sc">bfd</span>
library, so if there is a bug in <span class="sc">bfd</span> then readelf will not be
affected.
<!-- man end -->
<!-- man begin OPTIONS readelf -->
<p>The long and short forms of options, shown here as alternatives, are
equivalent. At least one option besides <span class="samp">-v</span> or <span class="samp">-H</span> must be
given.
<dl>
<dt><span class="env">-a</span><dt><span class="env">--all</span><dd>Equivalent to specifying <span class="option">--file-header</span>,
<span class="option">--program-headers</span>, <span class="option">--sections</span>, <span class="option">--symbols</span>,
<span class="option">--relocs</span>, <span class="option">--dynamic</span>, <span class="option">--notes</span> and
<span class="option">--version-info</span>.
<br><dt><span class="env">-h</span><dt><span class="env">--file-header</span><dd><a name="index-ELF-file-header-information-128"></a>Displays the information contained in the ELF header at the start of the
file.
<br><dt><span class="env">-l</span><dt><span class="env">--program-headers</span><dt><span class="env">--segments</span><dd><a name="index-ELF-program-header-information-129"></a><a name="index-ELF-segment-information-130"></a>Displays the information contained in the file's segment headers, if it
has any.
<br><dt><span class="env">-S</span><dt><span class="env">--sections</span><dt><span class="env">--section-headers</span><dd><a name="index-ELF-section-information-131"></a>Displays the information contained in the file's section headers, if it
has any.
<br><dt><span class="env">-g</span><dt><span class="env">--section-groups</span><dd><a name="index-ELF-section-group-information-132"></a>Displays the information contained in the file's section groups, if it
has any.
<br><dt><span class="env">-t</span><dt><span class="env">--section-details</span><dd><a name="index-ELF-section-information-133"></a>Displays the detailed section information. Implies <span class="option">-S</span>.
<br><dt><span class="env">-s</span><dt><span class="env">--symbols</span><dt><span class="env">--syms</span><dd><a name="index-ELF-symbol-table-information-134"></a>Displays the entries in symbol table section of the file, if it has one.
<br><dt><span class="env">-e</span><dt><span class="env">--headers</span><dd>Display all the headers in the file. Equivalent to <span class="option">-h -l -S</span>.
<br><dt><span class="env">-n</span><dt><span class="env">--notes</span><dd><a name="index-ELF-notes-135"></a>Displays the contents of the NOTE segments and/or sections, if any.
<br><dt><span class="env">-r</span><dt><span class="env">--relocs</span><dd><a name="index-ELF-reloc-information-136"></a>Displays the contents of the file's relocation section, if it has one.
<br><dt><span class="env">-u</span><dt><span class="env">--unwind</span><dd><a name="index-unwind-information-137"></a>Displays the contents of the file's unwind section, if it has one. Only
the unwind sections for IA64 ELF files are currently supported.
<br><dt><span class="env">-d</span><dt><span class="env">--dynamic</span><dd><a name="index-ELF-dynamic-section-information-138"></a>Displays the contents of the file's dynamic section, if it has one.
<br><dt><span class="env">-V</span><dt><span class="env">--version-info</span><dd><a name="index-ELF-version-sections-informations-139"></a>Displays the contents of the version sections in the file, it they
exist.
<br><dt><span class="env">-A</span><dt><span class="env">--arch-specific</span><dd>Displays architecture-specific information in the file, if there
is any.
<br><dt><span class="env">-D</span><dt><span class="env">--use-dynamic</span><dd>When displaying symbols, this option makes <span class="command">readelf</span> use the
symbol table in the file's dynamic section, rather than the one in the
symbols section.
<br><dt><span class="env">-x &lt;number or name&gt;</span><dt><span class="env">--hex-dump=&lt;number or name&gt;</span><dd>Displays the contents of the indicated section as a hexadecimal dump.
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.
<br><dt><span class="env">-p &lt;number or name&gt;</span><dt><span class="env">--string-dump=&lt;number or name&gt;</span><dd>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.
<br><dt><span class="env">-c</span><dt><span class="env">--archive-index</span><dd><a name="index-Archive-file-symbol-index-information-140"></a>Displays the file symbol index infomation contained in the header part
of binary archives. Performs the same function as the <span class="option">t</span>
command to <span class="command">ar</span>, but without using the BFD library. See <a href="ar.html#ar">ar</a>.
<br><dt><span class="env">-w[lLiaprmfFsoR]</span><dt><span class="env">--debug-dump[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges]</span><dd>Displays the contents of the debug sections in the file, if any are
present. If one of the optional letters or words follows the switch
then only data found in those specific sections will be dumped.
<p>Note: the <span class="option">=decodedline</span> option will display the interpreted
contents of a .debug_line section whereas the <span class="option">=rawline</span> option
dumps the contents in a raw format.
<br><dt><span class="env">-I</span><dt><span class="env">--histogram</span><dd>Display a histogram of bucket list lengths when displaying the contents
of the symbol tables.
<br><dt><span class="env">-v</span><dt><span class="env">--version</span><dd>Display the version number of readelf.
<br><dt><span class="env">-W</span><dt><span class="env">--wide</span><dd>Don't break output lines to fit into 80 columns. By default
<span class="command">readelf</span> breaks section header and segment listing lines for
64-bit ELF files, so that they fit into 80 columns. This option causes
<span class="command">readelf</span> to print each section header resp. each segment one a
single line, which is far more readable on terminals wider than 80 columns.
<br><dt><span class="env">-H</span><dt><span class="env">--help</span><dd>Display the command line options understood by <span class="command">readelf</span>.
</dl>
<!-- man end -->
</body></html>

View file

@ -0,0 +1,132 @@
<html lang="en">
<head>
<title>size - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="readelf.html#readelf" title="readelf">
<link rel="next" href="strings.html#strings" title="strings">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="size"></a>Next:&nbsp;<a rel="next" accesskey="n" href="strings.html#strings">strings</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="readelf.html#readelf">readelf</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">6 size</h2>
<p><a name="index-size-100"></a><a name="index-section-sizes-101"></a>
<!-- man title size list section sizes and total size. -->
<pre class="smallexample"> <!-- man begin SYNOPSIS size -->
size [<span class="option">-A</span>|<span class="option">-B</span>|<span class="option">--format=</span><var>compatibility</var>]
[<span class="option">--help</span>]
[<span class="option">-d</span>|<span class="option">-o</span>|<span class="option">-x</span>|<span class="option">--radix=</span><var>number</var>]
[<span class="option">--common</span>]
[<span class="option">-t</span>|<span class="option">--totals</span>]
[<span class="option">--target=</span><var>bfdname</var>] [<span class="option">-V</span>|<span class="option">--version</span>]
[<var>objfile</var>...]
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION size -->
<p>The <span class="sc">gnu</span> <span class="command">size</span> utility lists the section sizes&mdash;and the total
size&mdash;for each of the object or archive files <var>objfile</var> in its
argument list. By default, one line of output is generated for each
object file or each module in an archive.
<p><var>objfile</var><small class="dots">...</small> are the object files to be examined.
If none are specified, the file <code>a.out</code> will be used.
<!-- man end -->
<!-- man begin OPTIONS size -->
<p>The command line options have the following meanings:
<dl>
<dt><span class="env">-A</span><dt><span class="env">-B</span><dt><span class="env">--format=</span><var>compatibility</var><dd><a name="index-_0040command_007bsize_007d-display-format-102"></a>Using one of these options, you can choose whether the output from <span class="sc">gnu</span>
<span class="command">size</span> resembles output from System V <span class="command">size</span> (using <span class="option">-A</span>,
or <span class="option">--format=sysv</span>), or Berkeley <span class="command">size</span> (using <span class="option">-B</span>, or
<span class="option">--format=berkeley</span>). The default is the one-line format similar to
Berkeley's.
<!-- Bonus for doc-source readers: you can also say -format=strange (or -->
<!-- anything else that starts with 's') for sysv, and -format=boring (or -->
<!-- anything else that starts with 'b') for Berkeley. -->
<p>Here is an example of the Berkeley (default) format of output from
<span class="command">size</span>:
<pre class="smallexample"> $ size --format=Berkeley ranlib size
text data bss dec hex filename
294880 81920 11592 388392 5ed28 ranlib
294880 81920 11888 388688 5ee50 size
</pre>
<p class="noindent">This is the same data, but displayed closer to System V conventions:
<pre class="smallexample"> $ size --format=SysV ranlib size
ranlib :
section size addr
.text 294880 8192
.data 81920 303104
.bss 11592 385024
Total 388392
size :
section size addr
.text 294880 8192
.data 81920 303104
.bss 11888 385024
Total 388688
</pre>
<br><dt><span class="env">--help</span><dd>Show a summary of acceptable arguments and options.
<br><dt><span class="env">-d</span><dt><span class="env">-o</span><dt><span class="env">-x</span><dt><span class="env">--radix=</span><var>number</var><dd><a name="index-_0040command_007bsize_007d-number-format-103"></a><a name="index-radix-for-section-sizes-104"></a>Using one of these options, you can control whether the size of each
section is given in decimal (<span class="option">-d</span>, or <span class="option">--radix=10</span>); octal
(<span class="option">-o</span>, or <span class="option">--radix=8</span>); or hexadecimal (<span class="option">-x</span>, or
<span class="option">--radix=16</span>). In <span class="option">--radix=</span><var>number</var>, only the three
values (8, 10, 16) are supported. The total size is always given in two
radices; decimal and hexadecimal for <span class="option">-d</span> or <span class="option">-x</span> output, or
octal and hexadecimal if you're using <span class="option">-o</span>.
<br><dt><span class="env">--common</span><dd>Print total size of common symbols in each file. When using Berkeley
format these are included in the bss size.
<br><dt><span class="env">-t</span><dt><span class="env">--totals</span><dd>Show totals of all objects listed (Berkeley format listing mode only).
<br><dt><span class="env">--target=</span><var>bfdname</var><dd><a name="index-object-code-format-105"></a>Specify that the object-code format for <var>objfile</var> is
<var>bfdname</var>. This option may not be necessary; <span class="command">size</span> can
automatically recognize many formats.
See <a href="Target-Selection.html#Target-Selection">Target Selection</a>, for more information.
<br><dt><span class="env">-V</span><dt><span class="env">--version</span><dd>Display the version number of <span class="command">size</span>.
</dl>
<!-- man end -->
</body></html>

View file

@ -0,0 +1,107 @@
<html lang="en">
<head>
<title>strings - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="size.html#size" title="size">
<link rel="next" href="strip.html#strip" title="strip">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="strings"></a>Next:&nbsp;<a rel="next" accesskey="n" href="strip.html#strip">strip</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="size.html#size">size</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">7 strings</h2>
<p><a name="index-strings-106"></a><a name="index-listings-strings-107"></a><a name="index-printing-strings-108"></a><a name="index-strings_002c-printing-109"></a>
<!-- man title strings print the strings of printable characters in files. -->
<pre class="smallexample"> <!-- man begin SYNOPSIS strings -->
strings [<span class="option">-afov</span>] [<span class="option">-</span><var>min-len</var>]
[<span class="option">-n</span> <var>min-len</var>] [<span class="option">--bytes=</span><var>min-len</var>]
[<span class="option">-t</span> <var>radix</var>] [<span class="option">--radix=</span><var>radix</var>]
[<span class="option">-e</span> <var>encoding</var>] [<span class="option">--encoding=</span><var>encoding</var>]
[<span class="option">-</span>] [<span class="option">--all</span>] [<span class="option">--print-file-name</span>]
[<span class="option">-T</span> <var>bfdname</var>] [<span class="option">--target=</span><var>bfdname</var>]
[<span class="option">--help</span>] [<span class="option">--version</span>] <var>file</var>...
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION strings -->
<p>For each <var>file</var> given, <span class="sc">gnu</span> <span class="command">strings</span> 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. By default, it only prints the strings from the initialized
and loaded sections of object files; for other types of files, it prints
the strings from the whole file.
<p><span class="command">strings</span> is mainly useful for determining the contents of non-text
files.
<!-- man end -->
<!-- man begin OPTIONS strings -->
<dl>
<dt><span class="env">-a</span><dt><span class="env">--all</span><dt><span class="env">-</span><dd>Do not scan only the initialized and loaded sections of object files;
scan the whole files.
<br><dt><span class="env">-f</span><dt><span class="env">--print-file-name</span><dd>Print the name of the file before each string.
<br><dt><span class="env">--help</span><dd>Print a summary of the program usage on the standard output and exit.
<br><dt><span class="env">-</span><var>min-len</var><dt><span class="env">-n </span><var>min-len</var><dt><span class="env">--bytes=</span><var>min-len</var><dd>Print sequences of characters that are at least <var>min-len</var> characters
long, instead of the default 4.
<br><dt><span class="env">-o</span><dd>Like <span class="samp">-t o</span>. Some other versions of <span class="command">strings</span> have <span class="option">-o</span>
act like <span class="samp">-t d</span> instead. Since we can not be compatible with both
ways, we simply chose one.
<br><dt><span class="env">-t </span><var>radix</var><dt><span class="env">--radix=</span><var>radix</var><dd>Print the offset within the file before each string. The single
character argument specifies the radix of the offset&mdash;<span class="samp">o</span> for
octal, <span class="samp">x</span> for hexadecimal, or <span class="samp">d</span> for decimal.
<br><dt><span class="env">-e </span><var>encoding</var><dt><span class="env">--encoding=</span><var>encoding</var><dd>Select the character encoding of the strings that are to be found.
Possible values for <var>encoding</var> are: <span class="samp">s</span> = single-7-bit-byte
characters (ASCII, ISO 8859, etc., default), <span class="samp">S</span> =
single-8-bit-byte characters, <span class="samp">b</span> = 16-bit bigendian, <span class="samp">l</span> =
16-bit littleendian, <span class="samp">B</span> = 32-bit bigendian, <span class="samp">L</span> = 32-bit
littleendian. Useful for finding wide character strings. (<span class="samp">l</span>
and <span class="samp">b</span> apply to, for example, Unicode UTF-16/UCS-2 encodings).
<br><dt><span class="env">-T </span><var>bfdname</var><dt><span class="env">--target=</span><var>bfdname</var><dd><a name="index-object-code-format-110"></a>Specify an object code format other than your system's default format.
See <a href="Target-Selection.html#Target-Selection">Target Selection</a>, for more information.
<br><dt><span class="env">-v</span><dt><span class="env">--version</span><dd>Print the program version number on the standard output and exit.
</dl>
<!-- man end -->
</body></html>

View file

@ -0,0 +1,190 @@
<html lang="en">
<head>
<title>strip - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="strings.html#strings" title="strings">
<link rel="next" href="c_002b_002bfilt.html#c_002b_002bfilt" title="c++filt">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="strip"></a>Next:&nbsp;<a rel="next" accesskey="n" href="c_002b_002bfilt.html#c_002b_002bfilt">c++filt</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="strings.html#strings">strings</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">8 strip</h2>
<p><a name="index-strip-111"></a><a name="index-removing-symbols-112"></a><a name="index-discarding-symbols-113"></a><a name="index-symbols_002c-discarding-114"></a>
<!-- man title strip Discard symbols from object files. -->
<pre class="smallexample"> <!-- man begin SYNOPSIS strip -->
strip [<span class="option">-F</span> <var>bfdname</var> |<span class="option">--target=</span><var>bfdname</var>]
[<span class="option">-I</span> <var>bfdname</var> |<span class="option">--input-target=</span><var>bfdname</var>]
[<span class="option">-O</span> <var>bfdname</var> |<span class="option">--output-target=</span><var>bfdname</var>]
[<span class="option">-s</span>|<span class="option">--strip-all</span>]
[<span class="option">-S</span>|<span class="option">-g</span>|<span class="option">-d</span>|<span class="option">--strip-debug</span>]
[<span class="option">-K</span> <var>symbolname</var> |<span class="option">--keep-symbol=</span><var>symbolname</var>]
[<span class="option">-N</span> <var>symbolname</var> |<span class="option">--strip-symbol=</span><var>symbolname</var>]
[<span class="option">-w</span>|<span class="option">--wildcard</span>]
[<span class="option">-x</span>|<span class="option">--discard-all</span>] [<span class="option">-X</span> |<span class="option">--discard-locals</span>]
[<span class="option">-R</span> <var>sectionname</var> |<span class="option">--remove-section=</span><var>sectionname</var>]
[<span class="option">-o</span> <var>file</var>] [<span class="option">-p</span>|<span class="option">--preserve-dates</span>]
[<span class="option">--keep-file-symbols</span>]
[<span class="option">--only-keep-debug</span>]
[<span class="option">-v</span> |<span class="option">--verbose</span>] [<span class="option">-V</span>|<span class="option">--version</span>]
[<span class="option">--help</span>] [<span class="option">--info</span>]
<var>objfile</var>...
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION strip -->
<p><span class="sc">gnu</span> <span class="command">strip</span> discards all symbols from object files
<var>objfile</var>. The list of object files may include archives.
At least one object file must be given.
<p><span class="command">strip</span> modifies the files named in its argument,
rather than writing modified copies under different names.
<!-- man end -->
<!-- man begin OPTIONS strip -->
<dl>
<dt><span class="env">-F </span><var>bfdname</var><dt><span class="env">--target=</span><var>bfdname</var><dd>Treat the original <var>objfile</var> as a file with the object
code format <var>bfdname</var>, and rewrite it in the same format.
See <a href="Target-Selection.html#Target-Selection">Target Selection</a>, for more information.
<br><dt><span class="env">--help</span><dd>Show a summary of the options to <span class="command">strip</span> and exit.
<br><dt><span class="env">--info</span><dd>Display a list showing all architectures and object formats available.
<br><dt><span class="env">-I </span><var>bfdname</var><dt><span class="env">--input-target=</span><var>bfdname</var><dd>Treat the original <var>objfile</var> as a file with the object
code format <var>bfdname</var>.
See <a href="Target-Selection.html#Target-Selection">Target Selection</a>, for more information.
<br><dt><span class="env">-O </span><var>bfdname</var><dt><span class="env">--output-target=</span><var>bfdname</var><dd>Replace <var>objfile</var> with a file in the output format <var>bfdname</var>.
See <a href="Target-Selection.html#Target-Selection">Target Selection</a>, for more information.
<br><dt><span class="env">-R </span><var>sectionname</var><dt><span class="env">--remove-section=</span><var>sectionname</var><dd>Remove any section named <var>sectionname</var> from the output file. This
option may be given more than once. Note that using this option
inappropriately may make the output file unusable.
<br><dt><span class="env">-s</span><dt><span class="env">--strip-all</span><dd>Remove all symbols.
<br><dt><span class="env">-g</span><dt><span class="env">-S</span><dt><span class="env">-d</span><dt><span class="env">--strip-debug</span><dd>Remove debugging symbols only.
<br><dt><span class="env">--strip-unneeded</span><dd>Remove all symbols that are not needed for relocation processing.
<br><dt><span class="env">-K </span><var>symbolname</var><dt><span class="env">--keep-symbol=</span><var>symbolname</var><dd>When stripping symbols, keep symbol <var>symbolname</var> even if it would
normally be stripped. This option may be given more than once.
<br><dt><span class="env">-N </span><var>symbolname</var><dt><span class="env">--strip-symbol=</span><var>symbolname</var><dd>Remove symbol <var>symbolname</var> from the source file. This option may be
given more than once, and may be combined with strip options other than
<span class="option">-K</span>.
<br><dt><span class="env">-o </span><var>file</var><dd>Put the stripped output in <var>file</var>, rather than replacing the
existing file. When this argument is used, only one <var>objfile</var>
argument may be specified.
<br><dt><span class="env">-p</span><dt><span class="env">--preserve-dates</span><dd>Preserve the access and modification dates of the file.
<br><dt><span class="env">-w</span><dt><span class="env">--wildcard</span><dd>Permit regular expressions in <var>symbolname</var>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:
<pre class="smallexample"> -w -K !foo -K fo*
</pre>
<p>would cause strip to only keep symbols that start with the letters
&ldquo;fo&rdquo;, but to discard the symbol &ldquo;foo&rdquo;.
<br><dt><span class="env">-x</span><dt><span class="env">--discard-all</span><dd>Remove non-global symbols.
<br><dt><span class="env">-X</span><dt><span class="env">--discard-locals</span><dd>Remove compiler-generated local symbols.
(These usually start with <span class="samp">L</span> or <span class="samp">.</span>.)
<br><dt><span class="env">--keep-file-symbols</span><dd>When stripping a file, perhaps with <span class="option">--strip-debug</span> or
<span class="option">--strip-unneeded</span>, retain any symbols specifying source file names,
which would otherwise get stripped.
<br><dt><span class="env">--only-keep-debug</span><dd>Strip a file, removing contents of any sections that would not be
stripped by <span class="option">--strip-debug</span> and leaving the debugging sections
intact. In ELF files, this preserves all note sections in the output.
<p>The intention is that this option will be used in conjunction with
<span class="option">--add-gnu-debuglink</span> 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:
<ol type=1 start=1>
<li>Link the executable as normal. Assuming that is is called
<code>foo</code> then...
<li>Run <code>objcopy --only-keep-debug foo foo.dbg</code> to
create a file containing the debugging info.
<li>Run <code>objcopy --strip-debug foo</code> to create a
stripped executable.
<li>Run <code>objcopy --add-gnu-debuglink=foo.dbg foo</code>
to add a link to the debugging info into the stripped executable.
</ol>
<p>Note&mdash;the choice of <code>.dbg</code> as an extension for the debug info
file is arbitrary. Also the <code>--only-keep-debug</code> step is
optional. You could instead do this:
<ol type=1 start=1>
<li>Link the executable as normal.
<li>Copy <code>foo</code> to <code>foo.full</code>
<li>Run <code>strip --strip-debug foo</code>
<li>Run <code>objcopy --add-gnu-debuglink=foo.full foo</code>
</ol>
<p>i.e., the file pointed to by the <span class="option">--add-gnu-debuglink</span> can be the
full executable. It does not have to be a file created by the
<span class="option">--only-keep-debug</span> switch.
<p>Note&mdash;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.
<br><dt><span class="env">-V</span><dt><span class="env">--version</span><dd>Show the version number for <span class="command">strip</span>.
<br><dt><span class="env">-v</span><dt><span class="env">--verbose</span><dd>Verbose output: list all object files modified. In the case of
archives, <span class="samp">strip -v</span> lists all members of the archive.
</dl>
<!-- man end -->
</body></html>

View file

@ -0,0 +1,146 @@
<html lang="en">
<head>
<title>windmc - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="windres.html#windres" title="windres">
<link rel="next" href="dlltool.html#dlltool" title="dlltool">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="windmc"></a>Next:&nbsp;<a rel="next" accesskey="n" href="dlltool.html#dlltool">dlltool</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="windres.html#windres">windres</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">12 windmc</h2>
<p><span class="command">windmc</span> may be used to generator Windows message resources.
<blockquote>
<em>Warning:</em> <span class="command">windmc</span> is not always built as part of the binary
utilities, since it is only useful for Windows targets.
</blockquote>
<!-- man title windmc generates Windows message resources. -->
<pre class="smallexample"> <!-- man begin SYNOPSIS windres -->
windmc [options] input-file
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION windmc -->
<p><span class="command">windmc</span> 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:
<dl>
<dt><code>h</code><dd>A C header file containing the message definitions.
<br><dt><code>rc</code><dd>A resource file compilable by the <span class="command">windres</span> tool.
<br><dt><code>bin</code><dd>One or more binary files containing the resource data for a specific
message language.
<br><dt><code>dbg</code><dd>A C include file that maps message id's to their symbolic name.
</dl>
<p>The exact description of these different formats is available in
documentation from Microsoft.
<p>When <span class="command">windmc</span> converts from the <code>mc</code> format to the <code>bin</code>
format, <code>rc</code>, <code>h</code>, and optional <code>dbg</code> it is acting like the
Windows Message Compiler.
<!-- man end -->
<!-- man begin OPTIONS windmc -->
<dl>
<dt><span class="env">-a</span><dt><span class="env">--ascii_in</span><dd>Specifies that the input file specified is ANSI. This is the default
behaviour.
<br><dt><span class="env">-A</span><dt><span class="env">--ascii_out</span><dd>Specifies that messages in the output <code>bin</code> files should be in ANSI
format.
<br><dt><span class="env">-b</span><dt><span class="env">--binprefix</span><dd>Specifies that <code>bin</code> filenames should have to be prefixed by the
basename of the source file.
<br><dt><span class="env">-c</span><dt><span class="env">--customflag</span><dd>Sets the customer bit in all message id's.
<br><dt><span class="env">-C </span><var>codepage</var><dt><span class="env">--codepage_in </span><var>codepage</var><dd>Sets the default codepage to be used to convert input file to UTF16. The
default is ocdepage 1252.
<br><dt><span class="env">-d</span><dt><span class="env">--decimal_values</span><dd>Outputs the constants in the header file in decimal. Default is using
hexadecimal output.
<br><dt><span class="env">-e </span><var>ext</var><dt><span class="env">--extension </span><var>ext</var><dd>The extension for the header file. The default is .h extension.
<br><dt><span class="env">-F </span><var>target</var><dt><span class="env">--target </span><var>target</var><dd>Specify the BFD format to use for a bin file as output. This
is a BFD target name; you can use the <span class="option">--help</span> option to see a list
of supported targets. Normally <span class="command">windmc</span> will use the default
format, which is the first one listed by the <span class="option">--help</span> option.
<a href="Target-Selection.html#Target-Selection">Target Selection</a>.
<br><dt><span class="env">-h </span><var>path</var><dt><span class="env">--headerdir </span><var>path</var><dd>The target directory of the generated header file. The default is the
current directory.
<br><dt><span class="env">-H</span><dt><span class="env">--help</span><dd>Displays a list of command line options and then exits.
<br><dt><span class="env">-m </span><var>characters</var><dt><span class="env">--maxlength </span><var>characters</var><dd>Instructs <span class="command">windmc</span> to generate a warning if the length
of any message exceeds the number specified.
<br><dt><span class="env">-n</span><dt><span class="env">--nullterminate</span><dd>Terminate message text in <code>bin</code> files by zero. By default they are
terminated by CR/LF.
<br><dt><span class="env">-o</span><dt><span class="env">--hresult_use</span><dd>Not yet implemented. Instructs <code>windmc</code> to generate an OLE2 header
file, using HRESULT definitions. Status codes are used if the flag is not
specified.
<br><dt><span class="env">-O </span><var>codepage</var><dt><span class="env">--codepage_out </span><var>codepage</var><dd>Sets the default codepage to be used to output text files. The default
is ocdepage 1252.
<br><dt><span class="env">-r </span><var>path</var><dt><span class="env">--rcdir </span><var>path</var><dd>The target directory for the generated <code>rc</code> script and the generated
<code>bin</code> files that the resource compiler script includes. The default
is the current directory.
<br><dt><span class="env">-u</span><dt><span class="env">--unicode_in</span><dd>Specifies that the input file is UTF16.
<br><dt><span class="env">-U</span><dt><span class="env">--unicode_out</span><dd>Specifies that messages in the output <code>bin</code> file should be in UTF16
format. This is the default behaviour.
<br><dt><span class="env">-v</span><br><dt><span class="env">--verbose</span><dd>Enable verbose mode.
<br><dt><span class="env">-V</span><br><dt><span class="env">--version</span><dd>Prints the version number for <span class="command">windmc</span>.
<br><dt><span class="env">-x </span><var>path</var><dt><span class="env">--xdgb </span><var>path</var><dd>The path of the <code>dbg</code> C include file that maps message id's to the
symbolic name. No such file is generated without specifying the switch.
</dl>
<!-- man end -->
</body></html>

View file

@ -0,0 +1,183 @@
<html lang="en">
<head>
<title>windres - GNU Binary Utilities</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Binary Utilities">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="nlmconv.html#nlmconv" title="nlmconv">
<link rel="next" href="windmc.html#windmc" title="windmc">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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
section entitled ``GNU Free Documentation License''.
man end-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family: serif; font-weight: normal; }
--></style>
</head>
<body>
<div class="node">
<p>
<a name="windres"></a>Next:&nbsp;<a rel="next" accesskey="n" href="windmc.html#windmc">windmc</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="nlmconv.html#nlmconv">nlmconv</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">13 windres</h2>
<p><span class="command">windres</span> may be used to manipulate Windows resources.
<blockquote>
<em>Warning:</em> <span class="command">windres</span> is not always built as part of the binary
utilities, since it is only useful for Windows targets.
</blockquote>
<!-- man title windres manipulate Windows resources. -->
<pre class="smallexample"> <!-- man begin SYNOPSIS windres -->
windres [options] [input-file] [output-file]
<!-- man end -->
</pre>
<!-- man begin DESCRIPTION windres -->
<p><span class="command">windres</span> reads resources from an input file and copies them into
an output file. Either file may be in one of three formats:
<dl>
<dt><code>rc</code><dd>A text format read by the Resource Compiler.
<br><dt><code>res</code><dd>A binary format generated by the Resource Compiler.
<br><dt><code>coff</code><dd>A COFF object or executable.
</dl>
<p>The exact description of these different formats is available in
documentation from Microsoft.
<p>When <span class="command">windres</span> converts from the <code>rc</code> format to the <code>res</code>
format, it is acting like the Windows Resource Compiler. When
<span class="command">windres</span> converts from the <code>res</code> format to the <code>coff</code>
format, it is acting like the Windows <code>CVTRES</code> program.
<p>When <span class="command">windres</span> generates an <code>rc</code> file, the output is similar
but not identical to the format expected for the input. When an input
<code>rc</code> file refers to an external filename, an output <code>rc</code> file
will instead include the file contents.
<p>If the input or output format is not specified, <span class="command">windres</span> will
guess based on the file name, or, for the input file, the file contents.
A file with an extension of <span class="file">.rc</span> will be treated as an <code>rc</code>
file, a file with an extension of <span class="file">.res</span> will be treated as a
<code>res</code> file, and a file with an extension of <span class="file">.o</span> or
<span class="file">.exe</span> will be treated as a <code>coff</code> file.
<p>If no output file is specified, <span class="command">windres</span> will print the resources
in <code>rc</code> format to standard output.
<p>The normal use is for you to write an <code>rc</code> file, use <span class="command">windres</span>
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</code> file available to Windows.
<!-- man end -->
<!-- man begin OPTIONS windres -->
<dl>
<dt><span class="env">-i </span><var>filename</var><dt><span class="env">--input </span><var>filename</var><dd>The name of the input file. If this option is not used, then
<span class="command">windres</span> will use the first non-option argument as the input file
name. If there are no non-option arguments, then <span class="command">windres</span> will
read from standard input. <span class="command">windres</span> can not read a COFF file from
standard input.
<br><dt><span class="env">-o </span><var>filename</var><dt><span class="env">--output </span><var>filename</var><dd>The name of the output file. If this option is not used, then
<span class="command">windres</span> will use the first non-option argument, after any used
for the input file name, as the output file name. If there is no
non-option argument, then <span class="command">windres</span> will write to standard output.
<span class="command">windres</span> can not write a COFF file to standard output. Note,
for compatibility with <span class="command">rc</span> the option <span class="option">-fo</span> is also
accepted, but its use is not recommended.
<br><dt><span class="env">-J </span><var>format</var><dt><span class="env">--input-format </span><var>format</var><dd>The input format to read. <var>format</var> may be <span class="samp">res</span>, <span class="samp">rc</span>, or
<span class="samp">coff</span>. If no input format is specified, <span class="command">windres</span> will
guess, as described above.
<br><dt><span class="env">-O </span><var>format</var><dt><span class="env">--output-format </span><var>format</var><dd>The output format to generate. <var>format</var> may be <span class="samp">res</span>,
<span class="samp">rc</span>, or <span class="samp">coff</span>. If no output format is specified,
<span class="command">windres</span> will guess, as described above.
<br><dt><span class="env">-F </span><var>target</var><dt><span class="env">--target </span><var>target</var><dd>Specify the BFD format to use for a COFF file as input or output. This
is a BFD target name; you can use the <span class="option">--help</span> option to see a list
of supported targets. Normally <span class="command">windres</span> will use the default
format, which is the first one listed by the <span class="option">--help</span> option.
<a href="Target-Selection.html#Target-Selection">Target Selection</a>.
<br><dt><span class="env">--preprocessor </span><var>program</var><dd>When <span class="command">windres</span> reads an <code>rc</code> file, it runs it through the C
preprocessor first. This option may be used to specify the preprocessor
to use, including any leading arguments. The default preprocessor
argument is <code>gcc -E -xc-header -DRC_INVOKED</code>.
<br><dt><span class="env">-I </span><var>directory</var><dt><span class="env">--include-dir </span><var>directory</var><dd>Specify an include directory to use when reading an <code>rc</code> file.
<span class="command">windres</span> will pass this to the preprocessor as an <span class="option">-I</span>
option. <span class="command">windres</span> will also search this directory when looking for
files named in the <code>rc</code> file. If the argument passed to this command
matches any of the supported <var>formats</var> (as described in the <span class="option">-J</span>
option), it will issue a deprecation warning, and behave just like the
<span class="option">-J</span> option. New programs should not use this behaviour. If a
directory happens to match a <var>format</var>, simple prefix it with <span class="samp">./</span>
to disable the backward compatibility.
<br><dt><span class="env">-D </span><var>target</var><dt><span class="env">--define </span><var>sym</var><span class="env">[=</span><var>val</var><span class="env">]</span><dd>Specify a <span class="option">-D</span> option to pass to the preprocessor when reading an
<code>rc</code> file.
<br><dt><span class="env">-U </span><var>target</var><dt><span class="env">--undefine </span><var>sym</var><dd>Specify a <span class="option">-U</span> option to pass to the preprocessor when reading an
<code>rc</code> file.
<br><dt><span class="env">-r</span><dd>Ignored for compatibility with rc.
<br><dt><span class="env">-v</span><dd>Enable verbose mode. This tells you what the preprocessor is if you
didn't specify one.
<br><dt><span class="env">-c </span><var>val</var><br><dt><span class="env">--codepage </span><var>val</var><dd>Specify the default codepage to use when reading an <code>rc</code> file.
<var>val</var> should be a hexadecimal prefixed by <span class="samp">0x</span> or decimal
codepage code. The valid range is from zero up to 0xffff, but the
validity of the codepage is host and configuration dependent.
<br><dt><span class="env">-l </span><var>val</var><br><dt><span class="env">--language </span><var>val</var><dd>Specify the default language to use when reading an <code>rc</code> file.
<var>val</var> should be a hexadecimal language code. The low eight bits are
the language, and the high eight bits are the sublanguage.
<br><dt><span class="env">--use-temp-file</span><dd>Use a temporary file to instead of using popen to read the output of
the preprocessor. Use this option if the popen implementation is buggy
on the host (eg., certain non-English language versions of Windows 95 and
Windows 98 are known to have buggy popen where the output will instead
go the console).
<br><dt><span class="env">--no-use-temp-file</span><dd>Use popen, not a temporary file, to read the output of the preprocessor.
This is the default behaviour.
<br><dt><span class="env">-h</span><br><dt><span class="env">--help</span><dd>Prints a usage summary.
<br><dt><span class="env">-V</span><br><dt><span class="env">--version</span><dd>Prints the version number for <span class="command">windres</span>.
<br><dt><span class="env">--yydebug</span><dd>If <span class="command">windres</span> is compiled with <code>YYDEBUG</code> defined as <code>1</code>,
this will turn on parser debugging.
</dl>
<!-- man end -->
</body></html>