Re: [PATCH v2 0/1] MR2126: ntdll: Print an error if we receive a signal not on the signal stack.

[Paul Gofman]

On 2/8/23 12:55, Rémi Bernon (@rbernon) wrote:
> USR1 / USR2 / INT for instance could be blocked in non-Wine threads, raising them again until they reach a Wine thread.

I think USR1 may only be received by a non-Wine thread if it was 
originated by some native library and not by wineserver which sends that 
only to threads it knows? In that case, not sure how that can be handled 
better in a Wine thread?

Also, is there a good way to block signals in threads which are created 
by native libraries, I think we don't know anything about those threads?