From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mta-snd-e08.mail.nifty.com (mta-snd-e08.mail.nifty.com [106.153.226.40]) by sourceware.org (Postfix) with ESMTPS id C74913858433 for ; Sun, 17 Mar 2024 12:35:50 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C74913858433 Authentication-Results: sourceware.org; dmarc=fail (p=none dis=none) header.from=nifty.ne.jp Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=nifty.ne.jp ARC-Filter: OpenARC Filter v1.0.0 sourceware.org C74913858433 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=106.153.226.40 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710678955; cv=none; b=XOUU408BJcCroN0/qWFmVG9GwFimf3n7eFbBEtp88A/sEnuqFQBP5Czij1MZGSWF+dj7GLqY1P8suH831quUh5j4N9R6DYHCoZdUT0ER+xjJZhavTnZNKWKuVeSQWmxR2Dn+Jy976Xmg73wJTxSZhapYZH6MJQzuIzBNQs2jTxM= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710678955; c=relaxed/simple; bh=UhiYqKYjP2VVweYKwyqzX0ohHGpvi95sLSYmTKu8Efo=; h=Date:From:To:Subject:Message-Id:Mime-Version; b=GX/q4TDgkLW1H1orcBfCKKzeK1QqP3zEoaTEsGkayKnZt3VWwRv7XC7Yc+nJWTfe+9oSLCjAZ0/TGrG1CXLJf3S4aE797DwO+u+OVdtI8xc3zIj629H11escmRCs926hmMZ5VC9ZlJVHiEa+CLW2ojquwlcuXJJ8IXzAXLpESWA= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from HP-Z230 by dmta0008.nifty.com with ESMTP id <20240317123548931.CGEY.17758.HP-Z230@nifty.com> for ; Sun, 17 Mar 2024 21:35:48 +0900 Date: Sun, 17 Mar 2024 21:35:48 +0900 From: Takashi Yano To: cygwin@cygwin.com Subject: Re: Bogus exit code 127 from a child process Message-Id: <20240317213548.652be777a51f00108414d9bf@nifty.ne.jp> In-Reply-To: <20240317211517.40cfbe0a664f7c7fe3d6e73d@nifty.ne.jp> References: <20240317174402.4a3e73a7fca2f5978ac93913@nifty.ne.jp> <61d4fca73047915567fc9b4aac2860a3@ispras.ru> <20240317182757.84b41a596c344f395c1d8f9a@nifty.ne.jp> <20240317192116.b00f24c9ee065f16d6ac6673@nifty.ne.jp> <20240317210358.ad701873dc5cfc9a3026dc0c@nifty.ne.jp> <20240317211517.40cfbe0a664f7c7fe3d6e73d@nifty.ne.jp> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Sun, 17 Mar 2024 21:15:17 +0900 Takashi Yano wrote: > On Sun, 17 Mar 2024 21:03:58 +0900 > Takashi Yano wrote: > > On Sun, 17 Mar 2024 19:21:16 +0900 > > Takashi Yano wrote: > > > On Sun, 17 Mar 2024 13:03:40 +0300 > > > Alexey Izbyshev wrote: > > > > On 2024-03-17 12:27, Takashi Yano wrote: > > > > > On Sun, 17 Mar 2024 12:01:55 +0300 > > > > > Alexey Izbyshev wrote: > > > > >> On 2024-03-17 11:44, Takashi Yano wrote: > > > > >> > On Sun, 17 Mar 2024 11:14:16 +0300 > > > > >> > Alexey Izbyshev wrote: > > > > >> >> Hello, > > > > >> >> > > > > >> >> I've been getting occasional "Error 127" from make -jN on seemingly > > > > >> >> random jobs. After reducing the set of jobs and eventually eliminating > > > > >> >> make, I've arrived to this one-liner: > > > > >> >> > > > > >> >> bash -c 'true & true & wait -n || echo 1: $? && wait -n || echo 2: $?' > > > > >> >> > > > > >> >> When run repeatedly, the second "wait -n" often reports 127. > > > > >> >> > > > > >> >> I've reproduced this in the following environments: > > > > >> >> > > > > >> >> * Cygwin 3.5.1, Windows 10 22H2 x64 > > > > >> >> * Cygwin 3.4.6, Windows 10 22H2 x64 and Windows 7 x64 > > > > >> >> > > > > >> >> I couldn't reproduce it in Cygwin 3.3.6 (WOW64) on Windows 7 x64. > > > > >> > > > > > >> > Could you please try latest cygwin 3.6.0 (TEST) ? > > > > >> > > > > >> Tested with 3.6.0-0.82.gfc691d0246b9 on Windows 10 22H2 x64, the > > > > >> problem > > > > >> still occurs. > > > > > > > > > > In my evrironmen, trial for 1 hour does not reproduce the issue. > > > > > Could you please let us know your environment, i.e. CPU, amount of > > > > > memory, and so on? > > > > > > > > It's been reproduced in a variety of environments: > > > > > > > > * Windows 10 22H2 x64, Intel Core i7 11700, 32 GB RAM > > > > * Windows 10 22H2 x64, Intel Core i7 9700, 32 GB RAM > > > > * Windows 10 22H2 x64, Intel Core i7 6700, 32 GB RAM > > > > * Windows 7 SP1 x64, Intel Core i7 6700, 32 GB RAM > > > > > > > > I'm surprised that you're not hitting it very quickly. The following > > > > loop usually fails after a few iterations (rarely a hundred or so) in my > > > > tests: > > > > > > > > while bash -c 'true & true & wait -n || { echo 1: $?; exit 1; } && wait > > > > -n || { echo 2: $?; exit 1; }'; do echo $((i++)); done > > > > > > Thanks. My main PC still runs the above test for more than 15000 counts. > > > So, I tried another PC which CPU is Core i5 540M and could reproduce > > > the issue about 1 time per a few hundreds count. > > > > > > I also tried to run sleep 0.1 instead of true, then, the issue happens > > > 1 time per a few decades counts. > > > > > > I'll look into this problem. Thanks for the report. > > > > In my environment, the issue is reproducible even with cygwin 3.3.6 > > (32bit, i.e. WOW64) and bash 4.4.12(3)-release (i686-pc-cygwin). > > > > What are the versions of bash in each systems? > > And, the attached simple test case in C which does very similar things > with bash command could not reproduce the problem. > > Can you reproduce the issue with attached STC? I also test your test case: while bash -c 'true & true & wait -n || { echo 1: $?; exit 1; } && wait -n || { echo 2: $?; exit 1; }'; do echo $((i++)); done in Linux (Debian 12.5), and the issue reproduced! It seems that this is a bug of upstream of bash. Eric, Corinna, any idea? -- Takashi Yano