Re: [PATCH v2 0/2] MR10250: Call abort if _wassert error behavior is set to _OUT_TO_STDERR and trigger a debug break.

[Santino Mazza (＠tati)]

On Fri Mar  6 13:40:13 2026 +0000, Piotr Caban wrote:
> I have tested it with ucrtbase and calling `DebugBreak` looks wrong. I'm
> getting 0xc0000409 exception. While the code of the exception may be
> misleading - this is the result of calling
> `fastfail(FAST_FAIL_FATAL_APP_EXIT)`
> (https://learn.microsoft.com/en-us/shows/inside/c0000409). I don't know
> what should happen if `fastfail` is not supported and I'm not sure if
> it's easily testable (maybe with msvcrt.dll, if it behaves differently).
> `raise(SIGABRT)` should be called before handling `_CALL_REPORTFAULT` flag.
> On Windows, if I set a signal handler for SIGABRT it doesn't get called when `_CALL_REPORTFAULT` is set.

-- 
https://gitlab.winehq.org/wine/wine/-/merge_requests/10250#note_131481