X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B666238582B8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1706740051; bh=zAB9HRoV+PdAqT+hO/kgoCdaCSzGRsm3uUGzgd3zExU=; 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=DP+92f+CpB9iXU82bbuR5n01NppcyUvLx2xtejrkKX+gn8uZQ6Mw+uvAJ9EwxIpoL Ig71yZnP6OYOU6or7SONN1muw9Ag5Ffphl9yKInK/VQSeoXqNXYj4Vp/gLBkcRDtjy TQPE3dUfVyEdEZ4akeVG2ktgzMcOgv/F4rLpJzTU= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org AF49E38582A4 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org AF49E38582A4 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1706740028; cv=none; b=uduzmg1KEYYURcrys3ZiKFHtS8PAvD/1Wh7bWqZDsW37zbm5yk3u+Xbr/LHHKV7XvsdJVTU+cGavu7UfKRbOzjE2MzYgFCn7rNjl9PbXyYnZRNvOSUSFHwS+/NGCcd+oO7M6er/lZ5cqxus8LBZq1PYpkpjfzpP+qttJGFApHPk= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1706740028; c=relaxed/simple; bh=PWP8GYF9FfIcOVSTGfXAGiUsAorH1CbvpB+uI5TF5TI=; h=Message-ID:Date:MIME-Version:Subject:To:From; b=nUeVaTUv930xcDJQ2KJbBANo9cIL4EqGrZ85+HgCP5cTvFIMD0CsEH8eGZ2yVaoIphXhR5uQeYxAzsiDtFky6nz6Ex5li1/C8vD5bUtq89HUTNJ47YFb5UfCSPaYkFR7ITFCU2sQZDh5AErX6kgZVTCeceNpBfIi4adIgHyQc+0= ARC-Authentication-Results: i=1; server2.sourceware.org Message-ID: <4aa47264-70df-42ff-bf74-70da021a8d82@SystematicSW.ab.ca> Date: Wed, 31 Jan 2024 15:27:02 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Aren't Windows System Error popups meant to be disabled in Cygwin? Content-Language: en-CA To: cygwin AT cygwin DOT com References: Organization: Systematic Software In-Reply-To: X-Rspamd-Queue-Id: BC4778000E X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE, UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.6 X-Rspamd-Server: rspamout08 X-Stat-Signature: 7f6598msomx3j6uzod81heg7zk6rzp5d X-Session-Marker: 427269616E2E496E676C69734053797374656D6174696353572E61622E6361 X-Session-ID: U2FsdGVkX1+KVzX28Xp6Zznlt5j3LdjZblgiFxkN64Q= X-HE-Tag: 1706740023-14381 X-HE-Meta: U2FsdGVkX1+f1CgKOrY28+ds5/OreS5G+ozza7Jh3BY4/ZLcwrZpJXrH2xFgmSDi/VoaJ7VG6z4nyjV3Vrq9FcDPGKwdt7bpiy34/BjbB47va3mxLMJNZ17bVE0BGZjAGnwbnBQh/xyc9M4vc3BF6u7StwAKqJa4UiyZtYXe4grPOrpE+9a9oOlEXD2x+kNGBUZpoLHo5b5Qwr4NVyDZ7Bpn2ikLi9OpiWm77VxRW4G+82SaprZJBl/pLqs2SnCdtJNjDsczcfoBlThRMVMXXwZhekl8KvG6pxyj9aPL39QpFsyVnjWBQskQ3e2AqJ+HpqInelAEhC/B3oqnrJSIhcgElOqNBRR/s4pQS58erRQ3/xIWY9F2bQ== X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org 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: cygwin AT cygwin DOT com 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 40VMRXYY001450 On 2024-01-31 06:40, David Allsopp via Cygwin wrote: > Starting with this very trivial C program: > > #include > #include > > int main(void) { > printf("Zstandard v%d\n", ZSTD_versionNumber()); > } > > and compiling with > > x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd > > when I then run ./test.exe, I get the Windows critical-error-handler > dialog stating "The code execution cannot proceed because > libzstd-1.dll was not found. Reinstalling the program may fix this > problem." > > My question is not how to fix the problem (I'm well aware of that), > but rather why that message is being displayed at all, and is it a bug > in Cygwin somewhere? All I could find Googling was previous > suggestions that Cygwin routinely calls SetErrorMode with, amongst > other things, SEM_FAILCRITICALERRORS with the intention of suppressing > this dialog. > > Is that correct, and if so is this just me? :o) > > Windows 10 22H2, Cygwin 3.4.10, running all the commands from mintty. > I also get the same popup if I run C:\cygwin64\bin\sh -c > "/cygdrive/c/path/to/test" either from a Command Prompt or even from > "Start -> Run". Running this via "sh" called from a non-Cygwin process > (itself invoked from a Command Prompt) which has also called > SetErrorMode is how I hit this. Better to let you know that there is a problem, and what the problem is, so you can fix it! I have spent hours trying to track down initialization failures, when daemons just ignored that a library they needed was not found or loaded! Install the following package: $ cygcheck -f /usr/x86_64-w64-mingw32/sys-root/mingw/bin/libzstd-1.dll mingw64-x86_64-zstd-1.5.5-1 -- 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 à retirer 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