From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nsstlmta30p.bpe.bigpond.com (nsstlmta30p.bpe.bigpond.com [203.38.21.30]) by sourceware.org (Postfix) with ESMTPS id 66FEE385DC0A for ; Wed, 29 Apr 2020 04:06:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 66FEE385DC0A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=shaddybaddah.name Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=lithium-cygwin@shaddybaddah.name Received: from smtp.telstra.com ([10.10.24.4]) by nsstlfep30p-svc.bpe.nexus.telstra.com.au with ESMTP id <20200429040622.NCSF353.nsstlfep30p-svc.bpe.nexus.telstra.com.au@smtp.telstra.com> for ; Wed, 29 Apr 2020 14:06:22 +1000 X-RG-Spam: Unknown X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgeduhedriedvgdejjecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfupfevtfgpvffgnffuvffttedpqfgfvfenuceurghilhhouhhtmecugedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefuhhgrugguhicuuegruggurghhuceolhhithhhihhumhdqtgihghifihhnsehshhgrugguhigsrgguuggrhhdrnhgrmhgvqeenucfkphepvddtfedrgedtrdduieekrddvhedvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgdtrddtrddtrddtngdpihhnvghtpedvtdefrdegtddrudeikedrvdehvddpmhgrihhlfhhrohhmpeeolhhithhhihhumhdqtgihghifihhnsehshhgrugguhigsrgguuggrhhdrnhgrmhgvqecuuefqffgjpeekuefkvffokffogfdprhgtphhtthhopeeotgihghifihhnsegthihgfihinhdrtghomheq X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean X-RG-VS-CLASS: clean Received: from [0.0.0.0] (203.40.168.252) by smtp.telstra.com (5.8.420) id 5E853F7F0AF010AC for cygwin@cygwin.com; Wed, 29 Apr 2020 14:06:22 +1000 Subject: Re: Odd hang of cc1.exe *now further isolated, potential console issues* cpp/gcc To: cygwin@cygwin.com References: <514e1a5d-7173-c6f0-a205-d8f207befc06@shaddybaddah.name> <9e450e76-6bc8-407a-89d4-edcc934edc5a@shaddybaddah.name> <0dc18394-6194-118a-d3f1-3055c51a352f@cs.umass.edu> From: Shaddy Baddah Message-ID: Date: Wed, 29 Apr 2020 14:06:19 +1000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <0dc18394-6194-118a-d3f1-3055c51a352f@cs.umass.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_ABUSEAT, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_SOFTFAIL, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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: , X-List-Received-Date: Wed, 29 Apr 2020 04:06:29 -0000 Hi Eliot, On 28/4/20 10:46 pm, Eliot Moss wrote: > Could it be a cygwin fork problem?  Definitely possible > in a 32-bit environment.  I had to rebase all the time. > Now that I'm mostly in the 64-bit environment it's not > such an issue. I suspected so and did trigger a rebaseall... it hasn't helped. As mysterious as this problem is, I can't rule out fork issues, but I have new information that suggests it might be something odd with console/pty I/O??? So, if I run cc1 from bash, under a command prompt window, it will will seemingly hang. However if I enter ctrl-d, the command resumes and seems to run (I can't say if correct or not). Here's what I mean: | $ /usr/lib/gcc/x86_64-pc-cygwin/9.3.0/cc1.exe -E -quiet -v -idirafter /usr/lib/gcc/x86_64-pc-cygwin/9.3.0/../../../../lib/../include/w32api -idirafter /usr/lib/gcc/x86_64-pc-cygwin/9.3.0/../../../../x86_64-pc-cygwin/lib/../lib/../../include/w32api hello.c -mtune=generic -march=x86-64 | | Analyzing compilation unit | Performing interprocedural optimizations | <*free_lang_data> Streaming LTO | Assembling functions: | | Time variable usr sys wall GGC | phase setup : 0.01 (100%) 0.00 ( 0%) 0.01 ( 40%) 1224 kB ( 90%) | phase opt and generate : 0.00 ( 0%) 0.00 ( 0%) 0.01 ( 28%) 2 kB ( 0%) | TOTAL : 0.01 0.00 0.03 1357 kB | | $ If I try this in mintty, the ctrl-d isn't accepted, and the hard hang continues. ctrl-c doesn't work, and I have to resort to killing processes in taskmgr (haven't tried just using Cygwin kill. Can if it makes a difference). So, it seems like even though cc1 is probably not reading the console, Windows things it needs events from that source for some reason??? It's all a bit above my pay grade at the moment. Also, for completeness, I went back to Cygwin DLL 3.0.6-1, and the problem persisted. Mind you, until recent modifications to the desktop (Windows updates, and whatever other agents pushed by corporate IT) gcc/cc1 was working with 3.1 series DLLs... go figure :-( Any ideas? -- Regards, Shaddy