bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/27850] New: It looks like strip command cannot be run simu


From: mikhail.v.gavrilov at gmail dot com
Subject: [Bug binutils/27850] New: It looks like strip command cannot be run simultaneous
Date: Tue, 11 May 2021 12:16:51 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=27850

            Bug ID: 27850
           Summary: It looks like strip command cannot be run simultaneous
           Product: binutils
           Version: 2.36.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: mikhail.v.gavrilov at gmail dot com
  Target Milestone: ---

Created attachment 13438
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13438&action=edit
strip backtrace

Description of problem:
Fedora build system uses script `/usr/lib/rpm/brp-strip` for removing debug
symbols.
And xargs can run strip command simultaneously several times. Here is
copy-paste of code from `/usr/lib/rpm/brp-strip`:

> # Strip ELF binaries
> find "$RPM_BUILD_ROOT" -type f \! -regex "${RPM_BUILD_ROOT}/*usr/lib/debug.*" 
> -print0 | \
>     xargs -0 -r -P$NCPUS -n32 sh -c "file \"\$@\" | sed -n -e 's/^\(.*\):[    
> ]*ELF.*, not stripped.*/\1/p' | xargs -I\{\} $STRIP -g \{\}" ARG0

I found file combination which cause strip error on simultaneous execution.

https://drive.google.com/file/d/1UlkJu2bg26c6Iooa60ruRvWiNzTrhgmM/view?usp=sharing

Here is archive with files and demo script test.sh
When my test script will be launched all files from the "assets1" directory
would successfully processed, but the same files from "assets2" directory
processing would failed with exit code 123.

The identical of files in directories was verified by the diff utility:

[mikhail@fedora brp-strip-bug-demo]$ diff -r assets1 assets2
[mikhail@fedora brp-strip-bug-demo]$

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]