Bug 143871 - system() fails randomly in a threaded environment
system() fails randomly in a threaded environment
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: file (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Radek Vokal
Mike McLean
Depends On:
Blocks: 168429
  Show dependency treegraph
Reported: 2004-12-30 09:51 EST by Brian Stein
Modified: 2013-03-01 00:14 EST (History)
3 users (show)

See Also:
Fixed In Version: RHBA-2006-0012
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-07 13:08:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
testcase main program (4.57 KB, text/plain)
2004-12-30 10:43 EST, Arjan van de Ven
no flags Details

  None (edit)
Description Arjan van de Ven 2004-12-30 09:51:53 EST
my rpm test app uses threads to spawn off a lot of it's work.
In such threads I use popen() frequently, and system() occasionally.
On the RHEL3 8way machine, about 30 threads are used.

Symptom: system() returns -1 fairly frequently

Does not seem to reproduce on my fc3 dual machine at home
Comment 1 Arjan van de Ven 2004-12-30 10:43:32 EST
Created attachment 109187 [details]
testcase main program

testcase program
in addition you need
and potentially 
(which comes from FC3)
Comment 2 Arjan van de Ven 2004-12-30 10:45:49 EST
the testcase.tar.bz needs to be untarred in /tmp fwiw
Comment 3 Jakub Jelinek 2004-12-31 11:23:15 EST
This turned out to be a bug (well, lots of bugs) in libmagic.so's compress.c.
Comment 5 Radek Vokal 2005-01-03 04:56:18 EST
Fixed in file-4.12-2. 
Comment 14 Red Hat Bugzilla 2006-03-07 13:08:41 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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