Re: [PATCH 15/17] msvc: do not pretend to support all signals
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Jun 19, 2019, 04:10 UTC
- Message-ID
- <CAPig+cRW+1dEUe1=7=5G-HziJOA2UpYVKsnMdBpkpcU6D8O95A@mail.gmail.com>
- In-Reply-To
- <1491ea4140518d76d4619fa2da7ec20250da1404.1560860634.git.gitgitgadget@gmail.com>
On Tue, Jun 18, 2019 at 8:24 AM Jeff Hostetler via GitGitGadget <gitgitgadget@gmail.com> wrote:
Show 19 quoted lines
> This special-cases various signals that are not supported on Windows, > such as SIGPIPE. These cause the UCRT to throw asserts (at least in > debug mode). > > Signed-off-by: Jeff Hostetler <jeffhost@microsoft.com> > Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> > --- > diff --git a/compat/mingw.c b/compat/mingw.c > @@ -2119,8 +2119,34 @@ int mingw_raise(int sig) > +#if defined(_MSC_VER) > + /* > + * <signal.h> in the CRT defines 8 signals as being > + * supported on the platform. Anything else causes > + * an "Invalid signal or error" (which in DEBUG builds > + * causes the Abort/Retry/Ignore dialog). We by-pass > + * the CRT for things we already know will fail. > + */ > + /*case SIGINT:*/ > + case SIGILL:
Why is SIGINT commented out?
And, the comment block seems over-indented.
Show 10 quoted lines
> + case SIGFPE: > + case SIGSEGV: > + case SIGTERM: > + case SIGBREAK: > + case SIGABRT: > + case SIGABRT_COMPAT: > + return raise(sig); > + default: > + errno = EINVAL; > + return -1;