DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 62MEtKpv2636657 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 62MEtKpv2636657 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=j9/7mxHQ X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 441D84BAD175 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1774191319; bh=31yiuo6OJfNCPGfijpX2ye2ANaXNoFpYUjUOGVyEI3Q=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=j9/7mxHQ6ML0n1uCPdRoQRp3s1JAi/QsKfdgridBZ8cv9T5npwP3OX6OY1s0Z0tq1 12ZaNBuXh+R3gad57utnV8on3qy3E++9YiAHo/Fs06YY7OJftQiXhOHbjW+sVmJPNe MlGH8vQMET611EKegz3dh0ynPU56C6KBwZd0yJHo= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org EF2A64BAD169 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org EF2A64BAD169 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1774191268; cv=none; b=FJfxPBrx0xf8nyMekfMpXtwP6Ng1zCi3bWKcamwpN4122vgEB3Dt6LYF67qoFzUvX1LE6FpVooq99vcZ4I5ZA84f+PgIWWH8mJgDpjf1P8p5HokhzllJ9frGwrc7MSk3us92QT/eN8lwcyn/1DT0mk1pGJ5PdWb9XFgNkOnTYes= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1774191268; c=relaxed/simple; bh=d3+pwyyHVG7iCm9vh3xsf2S1jRttXWJxGU8knehLgxA=; h=Message-ID:Date:MIME-Version:Subject:To:From; b=gRvSMk7re29h+QNQb+g7VHxwLH2Ha/8w6Q0hoZGzdWDUpbUei1DiyZ/HQhmDa+b0sETqFLZd8Sjq9jgLpwRcmmhhz6WpSvEXEZzkiWwdyyNhrm6340qZ+qxexQOpeoR4InCoj7Z2B8nzxRdXBhlS1yvvF0UmX8NTLb3uejVQWVU= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EF2A64BAD169 X-Virus-Scanned: amavisd-new at mackenty.com Message-ID: <8b80d73f-8ff6-402c-b214-870c1f1d9335@cartchunk.org> Date: Sun, 22 Mar 2026 10:54:23 -0400 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: gcc hangs even on simple compile tasks To: Brian Inglis via Cygwin References: <3b1aa006-d7db-4e6d-8519-9eb86a9f29ec AT SystematicSW DOT ab DOT ca> Content-Language: en-US Organization: Diverse Pursuits In-Reply-To: <3b1aa006-d7db-4e6d-8519-9eb86a9f29ec@SystematicSW.ab.ca> X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Dick Pierce via Cygwin Reply-To: Dick Pierce Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On 3/10/2026 9:08 AM, Brian Inglis via Cygwin wrote: > On 2026-03-06 17:29, Annihilannic via Cygwin wrote: >> On 07/03/2026 09:37, Dick Pierce via Cygwin wrote: >>> Starting the end of last week, gcc has started behaving badly. Whether I invoke >>> it from a makefile or directly from bash, almost ALL of the timer, it hangs >>> forever, and Task Manager shows cc1 as "running", but consuming no CPU as >>> far as I can tell. If I kill it through task manager, the prompt returns >>> in bash (or make dies with an "interrupted" error. > >>> But I'm stumped. > >> Smells like a hardware problem to me - I'd suggest testing it thoroughly with >> memtest86 or similar. >> >> Also run it through `strace -f gcc -o hello.exe hello.c` a few times and see >> if it's sticking in the same spot every time (which would indicate software)? > > Never blame hardware until you have eliminated the likelihood of BLODA (Big List > Of Dodgy Apps : FAQ 4.44. > I went so far as wiping the machine completely of cygwin, pulled all references to cygwin out of the registry[1], and reinstalled cygwin from scratch: no change in behavior at all. After multiple dead end rabbit holes (redundant?), the problem was none of what anyone thought it was: it was MUCH simpler. Out of desperation and on a hunch, I did a search of the machine for all instances cygwin1.dll on the machine. I had 6 copies spread all over the place. Crucially, there was one in c:/windows/system. Got rid of that one, all of a sudden, gcc started working just fine. And since /windows/system has near the head of PATH, it was the one that got done first. Did a compare of that one to the one in /cygwin64/bin and, yes, it was different. So I then did a purge of my system of every instance of cygwin1.dll across the system I could find EXCEPT the one that came with the latest cygwin installation. How the crucial one ended up in /windows/system, I have NO idea. But often, looking at the simplest and, perhaps, dumbest cause of a problem is best done first. FOOTNOTES ========== [1] What does the Windows registry and Florida have in common? it's a place where things go to die. -- +-----------------------------------+ | Dick Pierce | | Diverse Pursuits | | Technical Engineering/Development | | cartchunk.org | | Boston - Spruce Head | +-----------------------------------+ -- 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