Bug 78596 - strip fails to process arguments after --strip-debug flag
strip fails to process arguments after --strip-debug flag
Product: Red Hat Linux
Classification: Retired
Component: binutils (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Depends On:
  Show dependency treegraph
Reported: 2002-11-26 00:02 EST by Michael Fratoni
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-07 09:34:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Fratoni 2002-11-26 00:02:47 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
The following fails to strip the target file:
strip --strip-debug -R .comment $file
strip --strip-debug $file && strip -R .comment $file
works as expected.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.execute strip --strip-debug -R .comment $file
2.Check the target file, it is not stripped.

Actual Results:  The given file contains no debug symbols, and processing
appears to stop at that point.The -R .comment flag appears to be ignored.
The man page indicates that --strip-debug removes debugging symbols only, but
makes no mention of ignoring any remaining flags.

Expected Results:  The .comment field should have been stripped.

Additional info:

This is entered at the request of a Red Hat developer. While building an rpm
package, I found that the executables were not stripped. The command used in the
specfile is:
strip --strip-debug -R .comment $file
Changing the command to:
--strip-debug $file && strip -R .comment $file
Works as expected.
Comment 1 Jakub Jelinek 2004-10-07 09:34:52 EDT
Can't reproduce this with binutils-
Assume it is fixed.

Note You need to log in before you can comment on or make changes to this bug.