From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-02.nifty.com (conssluserg-02.nifty.com [210.131.2.81]) by sourceware.org (Postfix) with ESMTPS id 554E03858D32 for ; Mon, 2 Jan 2023 05:38:23 +0000 (GMT) Received: from HP-Z230 (aj135041.dynamic.ppp.asahi-net.or.jp [220.150.135.41]) (authenticated) by conssluserg-02.nifty.com with ESMTP id 3025c26L008449 for ; Mon, 2 Jan 2023 14:38:02 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-02.nifty.com 3025c26L008449 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp; s=dec2015msa; t=1672637882; bh=nCqRfGX/twTfVMxF6KTVsBuM6CO9g0z7mxhChY78SQc=; h=Date:From:To:Subject:In-Reply-To:References:From; b=Zu+6l05MCoF1v/V5MMO1x4q2q3Kg+Q4SabjUhb1LSl5PQtfnU0fZYZ/FRUh2d25/P BPjnQucuPWwmM/2WtxD20LNUmCERmbbw4lrrjR0ozzflGGqB47nBlkGc2WG53XU0/u XRvtvpUBug8Qk6fdOLrGf8Te1JcWPU5MiZDWewU+5C8O8dub0+3OjyfLAIWso/RCMD 5C2UquBDMhu7549VOYlNsxXEJL7OfGlq1Tj69AxxVNrvBgNYAnTS3jO2P7YReq3yEl mwCZM7VS/dLVtDKSAlYNTUPyq916PhBqvi7lhPLOnhBz3tPluwPOlC8Ze9cuJvpN+m oWOi8EFh0KFMw== X-Nifty-SrcIP: [220.150.135.41] Date: Mon, 2 Jan 2023 14:38:03 +0900 From: Takashi Yano To: cygwin@cygwin.com Subject: Re: Cygwin 3.4.3 and 3.5.0... hangs in make, top, procps, ls /proc/PID/... Message-Id: <20230102143803.53f89d07a545a1bdd596e1e8@nifty.ne.jp> In-Reply-To: <20230102113201.476c10bef7a5643bddc00762@nifty.ne.jp> References: <4a4427cc-422b-1d14-015e-26523e620d9b@Shaw.ca> <20230102113201.476c10bef7a5643bddc00762@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=-6.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP 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 Mon, 2 Jan 2023 11:32:01 +0900 Takashi Yano wrote: > On Sat, 31 Dec 2022 13:01:29 -0700 > Brian Inglis wrote: > > was also getting the messages below locally and still on GitHub scallywag: > > > > cygcheck (6936) child_copy: cygheap read copy failed, > > > > ../curl/scallywag/1_x86_64 build.log:2022-12-26T00:39:35.6163236Z 0 > > [main] cygcheck (6936) child_copy: cygheap read copy failed, 0x0..0x80003B5F0, > > done 0, windows pid 6936, Win32 error 299 > > ../curl/scallywag/1_x86_64 build.log:2022-12-26T00:48:03.4525278Z 0 > > [main] cygcheck (568) child_copy: cygheap read copy failed, 0x0..0x80003BA48, > > done 0, windows pid 568, Win32 error 299 > > ../dialog/scallywag/1_x86_64 build.log:2022-12-31T18:42:37.0939902Z 0 > > [main] cygcheck (6992) child_copy: cygheap read copy failed, 0x0..0x80003CB38, > > done 0, windows pid 6992, Win32 error 299 > > I guess this is another problem. I found this issue occurs after the commit 30add3e6b3e3: "Cygwin: exec: don't access cygheap before it's initialized" . Reverting this commit solves the issue. To reproduce the problem relatively frequently, try: while true; do cygcheck -cd cygwin > /dev/null; done in bash. Corinna, could you please have a look at this issue as well? -- Takashi Yano