From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Odd hang of cc1.exe *now further isolated, potential console issues* cpp/gcc
Date: Wed, 29 Apr 2020 06:55:01 +0200 [thread overview]
Message-ID: <02da4ccb-3188-157e-2834-340c62ccd70e@gmail.com> (raw)
In-Reply-To: <ccd57ee7-2679-45b4-c11d-73bd85a99744@shaddybaddah.name>
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
next prev parent reply other threads:[~2020-04-29 4:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 6:54 Odd hang of cc1.exe, when invoking cpp/gcc Shaddy Baddah
2020-04-28 5:23 ` Odd hang of cc1.exe *now isolated somewhat* cpp/gcc Shaddy Baddah
2020-04-28 12:46 ` Eliot Moss
2020-04-29 4:06 ` Odd hang of cc1.exe *now further isolated, potential console issues* cpp/gcc Shaddy Baddah
2020-04-29 4:55 ` Marco Atzeri [this message]
2020-04-29 12:38 ` Odd hang of cc1.exe *now further isolated, back to a fork issue* cpp/gcc Shaddy Baddah
2020-05-06 14:29 ` Odd hang of cc1.exe *now isolated to /tmp weirdness* cpp/gcc Shaddy Baddah
2020-05-07 1:19 ` Doug Henderson
2020-05-07 3:44 ` Shaddy Baddah
2020-05-07 9:34 ` Odd hang of cc1.exe *resolved. /tmp/cygwin1.dll. Apologies * cpp/gcc Shaddy Baddah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02da4ccb-3188-157e-2834-340c62ccd70e@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).