https://bugs.winehq.org/show_bug.cgi?id=52131
--- Comment #8 from Eric eric.wheez@gmail.com --- Another clue: I renamed ".../RMS\ Express/PropagationPrediction.dll" to "xPropagationPrediction.dll" and then pressed RMS Express's HF Channel Selector's "Update Via Internet" button, which would normally crash (I was unable to test the "SFI" button). The HF Channel Selector downloads info from the internet and then hangs on "Updating propagation estimates..." but doesn't crash.
So, I think that the crash must happen in a method within PropagationPrediction.dll or soon after that.
Therefore, I believe the crash must happen within one of these methods (which we learned from the Windows traces are attempted to be run after pushing either the "SFI" or "Update Via Internet" buttons): [Load PropagationPrediction.dll] PropagationPrediction.PredictionClass..ctor PropagationPrediction.PredictionClass.LoadDll RMS_Express.Propagation.GetPathQualityIndicesFast PropagationPrediction.PredictionClass.PredictPropagation PropagationPrediction.PredictionClass.RangeAndBearing PropagationPrediction.PredictionClass.GridSquareToLatitudeLongitude PropagationPrediction.PredictionClass.ValidateGridSquare PropagationPrediction.PredictionClass.CreateDVOACapQuery PropagationPrediction.PredictionClass.GridSquareToDecimalDegrees RMS_Express.Propagation.CheckHours System.Runtime.InteropServices.SEHException -> PropagationPrediction.PredictionClass.PredictPropagation PropagationPrediction.PredictionClass.UnloadDll RMS_Express.INIFile.WriteInteger
I'm wondering if the System.Runtime.InteropServices.SEHException that pops up when tracing on Windows might be the problem? Maybe it's some less elegantly-implemented code which dotnet skirts around but which throws a wrench into the works for wine-mono?