https://bugs.winehq.org/show_bug.cgi?id=48023
Lorenzo Ferrillo lorenzofer@live.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lorenzofer@live.it
--- Comment #4 from Lorenzo Ferrillo lorenzofer@live.it --- I was able to make the Login UI come on screen, but it hang/close immediatly after. The hang/close seems related to an ACCESS_VIOLATION_EXCPETION being rised, sometimes failing in a seh overflow. Most times the resulting logs is different that seems to suggest that there is an initialization failure that is preventing some threaded operations to run. (For example the SetBlanket, QueryBlanket pair apeared in the log 2 times in 10 runs). Using schedtool -a0 seem to make this better, but still close/hang. +relay traces aren't useful. VS in that case exit with "Some component not found" failing to find some registry keys (in normal +reg log we can see it check for a key in VisualStudio\16.xxxxxx\Packages and then in VisualStudio\16.xxx_Config\Packages, the key being in the second one, while in +relay trace it only check the first location).
Startng devenv seems to trigger a "Unhandled page fault on execute access" in winedevice.exe, then it's trying to start vsjitdebugger.exe (unlcear if it's failing to start it or just can't debug the exception) Remade winedbg the default debugger, still no info appears. (Maybe devenv is changing the protection of some memory page?)