Why this name?



strip − Discard symbols from object files.


strip [−F bfdname |−−target=bfdname]
[−I bfdname |−−input−target=bfdname]
[−O bfdname |−−output−target=bfdname]
[−K symbolname |−−keep−symbol=symbolname]
[−N symbolname |−−strip−symbol=symbolname]
[−x|−−discard−all] [−X |−−discard−locals]
[−R sectionname |−−remove−section=sectionname]
[−o file] [−p|−−preserve−dates]
[−v |−−verbose] [−V|−−version]
[−−help] [−−info]





−F bfdname



Show a summary of the options to strip and exit.


Display a list showing all architectures and object formats available.

−I bfdname


−O bfdname

Replace objfile with a file in the output format bfdname.

−R sectionname

Remove any section named sectionname from the output file, in addition to whatever sections would otherwise be removed. This option may be given more than once. Note that using this option inappropriately may make the output file unusable. The wildcard character * may be given at the end of sectionname. If so, then any section starting with sectionname will be removed.



Remove all symbols.





Remove debugging symbols only.




Remove all symbols that are not needed for relocation processing.

−K symbolname


−N symbolname


−o file




Preserve the access and modification dates of the file.




If binutils was configured with −−enable−deterministic−archives, then this mode is on by default. It can be disabled with the −U option, below.



Do not operate in deterministic mode. This is the inverse of the −D option, above: when copying archive members and writing the archive index, use their actual UID, GID, timestamp, and file mode values.

This is the default unless binutils was configured with −−enable−deterministic−archives.




          −w −K !foo −K fo*

would cause strip to only keep symbols that start with the letters "fo", but to discard the symbol "foo".



Remove non-global symbols.





When stripping a file, perhaps with −−strip−debug or −−strip−unneeded, retain any symbols specifying source file names, which would otherwise get stripped.


Strip a file, emptying the contents of any sections that would not be stripped by −−strip−debug and leaving the debugging sections intact. In ELF files, this preserves all the note sections in the output as well.

Note − the section headers of the stripped sections are preserved, including their sizes, but the contents of the section are discarded. The section headers are preserved so that other tools can match up the debuginfo file with the real executable, even if that executable has been relocated to a different address space.

The intention is that this option will be used in conjunction with −−add−gnu−debuglink to create a two part executable. One a stripped binary which will occupy less space in RAM and in a distribution and the second a debugging information file which is only needed if debugging abilities are required. The suggested procedure to create these files is as follows:

"foo" then...

1.<Run "objcopy −−only−keep−debug foo foo.dbg" to>

create a file containing the debugging info.

1.<Run "objcopy −−strip−debug foo" to create a>

stripped executable.

1.<Run "objcopy −−add−gnu−debuglink=foo.dbg foo">


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:
1.<Link the executable as normal.>
1.<Copy "foo" to "foo.full">
1.<Run "strip −−strip−debug foo">
1.<Run "objcopy −−add−gnu−debuglink=foo.full foo">

i.e., the file pointed to by the −−add−gnu−debuglink can be the full executable. It does not have to be a file created by the −−only−keep−debug switch.




Show the version number for strip.



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−2015 Free Software Foundation, Inc.



No Banana Union - No Software Patents