X-Recipient: archive-cygwin@delorie.com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 44E853858433 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1672637941; bh=KCs2xUyv4wuRsEb/s0G/kf10WO6sXQw6Fus/su/zonE=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=RiU2f6khohH2T85+PsDSvh5AkWvhFPxUbPZsf26FU/LHucZc2e3xvIkcjntokhZzP 78/Q77wZxH8Z/2Zo3FRJ/iu1ThMXF4wxyRVpEWaFNkn2LIZG8o+wV8UCdlWV1jMjav uWeO60r5dE6Go/UiWSizKd7P45GnvyMFQRuWyiec= X-Original-To: cygwin@cygwin.com Delivered-To: cygwin@cygwin.com DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-02.nifty.com 3025c26L008449 X-Nifty-SrcIP: [220.150.135.41] Date: Mon, 2 Jan 2023 14:38:03 +0900 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 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 X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Takashi Yano via Cygwin Reply-To: Takashi Yano Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com Sender: "Cygwin" 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 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple