DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 62AD9kRF2479689 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 62AD9kRF2479689 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=yY1Xep4o X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 65BDE4BA23D3 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1773148184; bh=vDaQASuYraEd7AmQaAElrhG9MxPkpLhLGVfZ018plkU=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=yY1Xep4oB5SO8B44ulZCwv/+UZsBFVSPTI3VkUb7/GkM18NZ1a+vAViBfBq+oVNSy lBfvKLpn4uNnjbm4wkMTObqnYPqPP2MYJY+WppKv+2drqpRpkYVjPA43bmG/Ee5dPq 217IzSFpcA2ybVqbogklulgHyDAiEXGNmOFRqzNU= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org CC4134B9DB5D ARC-Filter: OpenARC Filter v1.0.0 sourceware.org CC4134B9DB5D ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1773148127; cv=none; b=LL1fzIA+9XEGLvteSTsaqu7KTg90wqHjtkqexT3av5yfTDL2+kuREFn/Ax5Rf8lrkD3CLbODdId12lZrFLqrlNQIw9S4ORu24LFoqmL1/2I6MZqQ2dHeiSWyOfRw0Oo/Po8WegHyBnCALOm8NoErboInAwSxtqDHWkScO3/0pbw= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1773148127; c=relaxed/simple; bh=Yoa6tTFkXDWRrDVCK7ODmXwwyu0HRNV0FONhYK1uCZk=; h=Message-ID:Date:MIME-Version:From:Subject:To:DKIM-Signature; b=N/gLHwiiTu3+xOAKEw4h/3SgwjhNW+kHF/VGdqUWgVPKM21KmnQCMg5jzsJnf2IJIerJ/Ht0cZNNVZeivgHCjFQEbGF5T6lWpoRkIH9ZJYF2lF7NB5KVnoUnnLRTw0XmTDa6tQXqJVqkmSVyME5VYzhiwsoMGk/ijePIzXAtdR4= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CC4134B9DB5D Message-ID: <3b1aa006-d7db-4e6d-8519-9eb86a9f29ec@SystematicSW.ab.ca> Date: Tue, 10 Mar 2026 07:08:44 -0600 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: gcc hangs even on simple compile tasks Content-Language: en-CA To: General Cygwin discussions and problem reports References: Organization: Systematic Software In-Reply-To: X-Stat-Signature: cg6tbejrmbb5aticrjpdh55f6rm1utcz X-Rspamd-Server: rspamout04 X-Rspamd-Queue-Id: CD1A030 X-Session-Marker: 427269616E2E496E676C69734053797374656D6174696353572E61622E6361 X-Session-ID: U2FsdGVkX1/mah0vdDMlVgW8LNVnYQ9gBXRpz53Xmo8= X-HE-Tag: 1773148125-224534 X-HE-Meta: U2FsdGVkX1/HBlim/ag7z+8wpb5OYCqH6wCSGg26PNykucKbNumXbCZzHu4Uk1SQiRa0fBfh/A/pGX8M03fB3FHxggzef0UbgqtsI6QLO830xX/M7RjGQGw3aE8WYDFXKJ3kDCJanKGlrYJabIrZKlcDJBfeJFeToBzcTznUkGj/xAXTfipd6vHwkp6+6HulzBXjDTizhoG4MnZTreNlJRCDZUxYCZYj584PRJ4IQtRNs3IiP8aN7djA8d+XPgj0r2avF+Q0vVL/EYivw0Zw3fYK7sl0choTxTA0/rm+mEw5VHd9xjjVJMRQRUT5mIeF22fMoqm2aXT+WaVk4sGWgo/z1zENTMu/jVZqpWCIuGEhT/Yz/7T7z5yQYJKBHvKGy6yycwYe7elcG+nIAQW4IQirEFaR6EY1pBjUec8poKX/AFooXIb1zu0nqRVFXykOB7WCunuKTtu1FhEf0X++4u+4Kvc1OZ1CcAvrstgssdg= 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: Brian Inglis via Cygwin Reply-To: General Cygwin discussions and problem reports Cc: Brian Inglis Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 62AD9kRF2479689 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. What applications have been found to interfere with Cygwin? ): poorly written employee monitoring and control software, often marketed as "End Point Protection", "Security", or AV products, which can not deal with, and must bypass interfering with emulators, like Cygwin or Git for Windows MSYS2. Export CYGWIN=detect_bloda (BLODA detection code ) and/or run gcc under strace 'strace -o gcc.strace gcc -o hello hello.c' to see if there are any non-Cygwin and non-Windows (may still be installed under /Windows/Systems32/) DLLs loaded. If you can, bypass products interfering with Cygwin programs under its , or /*bin/..., /lib/..., /libexec/... paths. -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut -- Antoine de Saint-Exupéry -- 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