Saulius Krasuckas

@lazka, maybe that [MSDN page](https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/signal?view=msvc-170#requirements:~:text=The%20SIGILL%20and%20SIGTERM%20signals%20aren%27t%20generated%20under%20Windows.%20They%27re%20included%20for%20ANSI%20compatibility.%20Therefore%2C%20you%20can%20set%20signal%20handlers%20for%20these%20signals%20by%20using%20signal%2C%20and%20you%20can%20also%20explicitly%20generate%20these%20signals%20by%20calling%20raise.) could shed some light: > The `SIGILL` and `SIGTERM` signals aren't generated under Windows. They're included for ANSI compatibility. Therefore, you can set signal handlers...

@lazka, that was a hypothetical case, and I didn't generated it whole. The part I omitted might be a guarding thread/process that logs the stack traces of the remaining threads/child...

Printing CR and LF characters using `echo -e` works as expected in all tested environments: - Cygwin 3.4.6-1 (2023-02-14) - Midipix 2022.11.18 - MSYS2 3.4.6 (2023-04-01) - Ubuntu 20.04.06 LTS...

Ping @lazka: do you (or someone of other core devs) agree with my summary (the last line) ?

The behavior is the same on MSYS2 `3.4.8.x86_64 2023-08-18 23:11`.

Ping @lazka @elieux. We've got a bug in the build of Bash at handling CRs. Cygwin build is fine. Maybe we should keep this issue open (even if you are...

Also ping @MehdiChinoune.

I could do some R'n'D about the Cygwin-vs-MSYS2 difference. But I have no idea about how to do it / where to start.

Still present: ``` $ uname -a MINGW64_NT-10.0-19044 DESKTOP-O7JE7JE 3.4.10.x86_64 2023-12-22 10:06 UTC x86_64 Msys ```

@AntumDeluge commented [1 hour ago](https://github.com/msys2/msys2-runtime/issues/207#issuecomment-1993861170): > > The idea of MSYS2's path conversion is to _guess_ how to handle command-line arguments passed between MSYS and non-MSYS programs... > > Something...