On Fri Aug 19 17:31:41 2022 +0000, **** wrote:
Paul Gofman replied on the mailing list:
On 8/19/22 11:57, Jakub Staro�� (@js6pak) wrote: >> It is interesting what's wrong with CopyContext. > It returns early here https://gitlab.winehq.org/wine/wine/-/blob/a34a403723661a3bf9c958c2431d58cce6c392bf/dlls/ntdll/exception.c#L1001 and causes coreclr to failfast. > >> Is there any app which reproduces the issue? > I'd assume all x86 .NET 6.0 apps that use threading in anyway. > I wasn't able to get a very minimal repro so I just copied over code that was causing issues for me here: https://github.com/js6pak/CoreclrWineCrash > Thanks. Sorry, I don't have dot net core building toolchains in hands, is it possible to download a binary version of reproducer from somewhere? I guess it is most interesting to fix CopyContext at the first place, even if that is not used on the main path in .Net core. _______________________________________________ wine-gitlab mailing list -- wine-gitlab@winehq.org To unsubscribe send an email to wine-gitlab-leave@winehq.org
https://github.com/js6pak/CoreclrWineCrash/actions/runs/2891163269