https://bugs.winehq.org/show_bug.cgi?id=54341
Bug ID: 54341 Summary: dotnet-dump data collection or some other backtrace for dotnet applications? Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: mjevans1983@gmail.com Distribution: ---
Created attachment 73910 --> https://bugs.winehq.org/attachment.cgi?id=73910 winedbg.exe dump during the livelock
I'm trying to figure out why a game (Cosmoteer again) freezes when multi-threading is enabled. The current work around is to run it in 'single core' ( --cores 1 ) mode, but obviously the performance is quite inferior for an application intended to run on multiple cores. On my system when it's briefly working it uses between 300 and 500% of a core (so 3-5 physical cores on a 4c8t system).
I need to collect more data to isolate if it's an issue with the game or with wine, and I don't even know where to begin looking for Wine data since I can't get a backtrace from any tools.
gdb doesn't know about applications that run through wine.
winedbg doesn't appear to understand dotnet managed applications (attachment)
I tried to run dotnet-dump but the tool installed in Linux doesn't locate any applications that it can interact with, while the 64-bit (matches the program) version of the tool inside wine appears to want a full dotnet install.
https://github.com/dotnet/diagnostics/blob/main/documentation/single-file-to...
So much for a single file tool ~.~
Is there some way I could collect more data without help from the program's creator? I've already suggested they please trap SIGTERM, SIGINT, SIGQUIT, and SIGHUP but I don't even know if that will work for an application using wine. https://steamcommunity.com/app/799600/discussions/1/3762228045904230736/