X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
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 AT shaddybaddah DOT name
X-RG-Spam:	Unknown
X-RazorGate-Vade:	gggruggvucftvghtrhhoucdtuddrgeduhedriedvgdejjecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfupfevtfgpvffgnffuvffttedpqfgfvfenuceurghilhhouhhtmecugedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefuhhgrugguhicuuegruggurghhuceolhhithhhihhumhdqtgihghifihhnsehshhgrugguhigsrgguuggrhhdrnhgrmhgvqeenucfkphepvddtfedrgedtrdduieekrddvhedvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgdtrddtrddtrddtngdpihhnvghtpedvtdefrdegtddrudeikedrvdehvddpmhgrihhlfhhrohhmpeeolhhithhhihhumhdqtgihghifihhnsehshhgrugguhigsrgguuggrhhdrnhgrmhgvqecuuefqffgjpeekuefkvffokffogfdprhgtphhtthhopeeotgihghifihhnsegthihgfihinhdrtghomheq
X-RazorGate-Vade-Verdict:	clean 0
X-RazorGate-Vade-Classification:	clean
X-RG-VS-CLASS:	clean
Subject:	Re: Odd hang of cc1.exe *now further isolated, potential console
	issues* cpp/gcc
To:	cygwin AT cygwin DOT com
References:	<514e1a5d-7173-c6f0-a205-d8f207befc06 AT shaddybaddah DOT name>
	<9e450e76-6bc8-407a-89d4-edcc934edc5a AT shaddybaddah DOT name>
	<0dc18394-6194-118a-d3f1-3055c51a352f AT cs DOT umass DOT edu>
From:	Shaddy Baddah <lithium-cygwin AT shaddybaddah DOT name>
Message-ID:	<ccd57ee7-2679-45b4-c11d-73bd85a99744@shaddybaddah.name>
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>
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 AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<http://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<http://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 03T46u1b007362

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
<nothing happens>
<enter ctrl-d>
|
| Analyzing compilation unit
| Performing interprocedural optimizations
|  <*free_lang_data> <visibility> <build_ssa_passes> <opt_local_passes> 
<remove_symbols> <targetclone> <free-fnsummary> <emutls>Streaming LTO
|  <whole-program> <fnsummary> <inline> <free-fnsummary> 
<single-use>Assembling functions:
|  <materialize-all-clones> <simdclone>
| 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
--
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

- Raw text -