From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) by sourceware.org (Postfix) with ESMTPS id 872DD38930CC for ; Wed, 29 Apr 2020 04:55:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 872DD38930CC Received: by mail-wr1-x42b.google.com with SMTP id j1so876856wrt.1 for ; Tue, 28 Apr 2020 21:55:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=7To/RQSsAD33+876O5V7dPbIaKm8gtnXXKL+SJNZKdc=; b=UtxX9ZndeTwrmhd4y2DFWAQlYAyvwqbPgbDUWwNz66eKJFgxzMTZ9pt169ablq2xyX tqHZIfT6jR3J6z5SOSWiJZTvRH+9yXBGpTRyt0VbuKk9IeMoas2rFT7bMPsHbSMeEOJm Wttyfdk8hsJJbBu+p3KiXaq01Rht1ZU5JaNbpFM1D/O98ftpNj+zsjbzGus1AQhn0uuZ 3u8lP//+5/C7K3UTW1J0sH8kcMxqvGfZO6WqqD8CTKsAn+Ebb3A8/HfG/c+WcHoXyWDB SN1ca4CtOhQTYy0SnFOUfuvVSqHja+zJQJGwL/0gJFEBgUFsEat2DFYGKgJqPWXnXd85 g08Q== X-Gm-Message-State: AGi0PubviwlccdwE7iGLoZgmHohgUkNN4hVyAotQpgM8GCUg0ENcqwPC +zQxBl40Ed8mKEQVzi7lVsMtY0sF X-Google-Smtp-Source: APiQypK2313jHEBPeUzwAhhbNBZ6zLweMvkQX9ltnIPFPNCJM4XhT4Cvl7GrZ6F6OQj/hTWlL1WfQA== X-Received: by 2002:a5d:68cf:: with SMTP id p15mr38364199wrw.139.1588136104261; Tue, 28 Apr 2020 21:55:04 -0700 (PDT) Received: from [192.168.2.121] (p5DDA1DC3.dip0.t-ipconnect.de. [93.218.29.195]) by smtp.gmail.com with ESMTPSA id h1sm6426376wme.42.2020.04.28.21.55.03 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 28 Apr 2020 21:55:03 -0700 (PDT) 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: Marco Atzeri Message-ID: <02da4ccb-3188-157e-2834-340c62ccd70e@gmail.com> Date: Wed, 29 Apr 2020 06:55:01 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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:55:06 -0000 Am 29.04.2020 um 06:06 schrieb Shaddy Baddah: > 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??? > I bet on some BLODA interfering on execution and creating a time glitch. Unfortunately is not new. Can you teach you AV to avoid the cygwin directories ? Marco