On Wed, Jan 31, 2024 at 2:41 PM David Allsopp via Cygwin wrote:
>
> Starting with this very trivial C program:
>
> #include <stdio.h>
> #include <zstd.h>
>
> 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.
>
> Thanks!
>
>
> David
>
x86_64-w64-mingw32-gcc produces a Windows program, why Cygwin should
be involved in the execution ?
--
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
