|--target=bfdname||Treat the original objfile as a file with the object code format bfdname, and rewrite it in the same format.|
|--help||Show a summary of the options to strip and exit.|
|--info||Display a list showing all architectures and object formats available.|
|--input-target=bfdname||Treat the original objfile as a file with the object code format bfdname.|
|--output-target=bfdname||Replace objfile with a file in the output format bfdname.|
|--remove-section=sectionname||Remove any section named sectionname from the output file. This option may be given more than once. Note that using this option inappropriately may make the output file unusable.|
|--strip-all||Remove all symbols.|
|--strip-debug||Remove debugging symbols only.|
|--strip-unneeded||Remove all symbols that are not needed for relocation processing.|
|--keep-symbol=symbolname||Keep only symbol symbolname from the source file. This option may be given more than once.|
|--strip-symbol=symbolname||Remove symbol symbolname from the source file. This option may be given more than once, and may be combined with strip options other than -K.|
|-o file||Put the stripped output in file, rather than replacing the existing file. When this argument is used, only one objfile argument may be specified.|
|--preserve-dates||Preserve the access and modification dates of the file.|
Permit regular expressions in symbolnames 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.
would cause strip to only keep symbols that start with the letters fo, but to discard the symbol foo.
|--discard-all||Remove non-global symbols.|
|--discard-locals||Remove compiler-generated local symbols. (These usually start with L or ..)|
Strip a file, removing any sections that would be stripped by
--strip-debug and leaving the debugging sections.
The intention is that this option will be used in conjunction with --add-gnu-debuglink to create a two part executable. One a stripped binary which will occupy less space in RAM and in a distribution and the second a debugging information file which is only needed if debugging abilities are required. The suggested procedure to create these files is as follows:
Note - the choice of .dbg as an extension for the debug info file is arbitrary. Also the --only-keep-debug step is optional. You could instead do this:
ie the file pointed to by the --add-gnu-debuglink can be the full executable. It does not have to be a file created by the --only-keep-debug switch.
|--version||Show the version number for strip.|
|--verbose||Verbose output: list all object files modified. In the case of archives, strip -v lists all members of the archive.|
the Info entries for binutils.
Copyright (c) 1991, 92, 93, 94, 95, 96, 97, 98, 99, 2000, 2001, 2002, 2003 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.1 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.