https://bugs.winehq.org/show_bug.cgi?id=56912
--- Comment #16 from stormtrackertony@gmail.com --- (In reply to Zeb Figura from comment #13)
I tried to look in static disassembly to find out whether that instruction is supposed to be there or whether we're indeed jumping to the middle of invalid memory or something. That instruction isn't there, it's in the middle of a .text section that's in the executable's mapped address space, but on disk the section is filled with zeroes. It's evidently jitted, and filled from some portion of memory that's also jitted.
Is this application embedding some scripting runtime or copy-protection scheme?
May be getting somewhere now! You wouldn't happen to know which .text section (or something I could share with the developer to point him in the right direction)?
I know he's not going to put much time into figuring it out until if/when we can document it happening on an actual Windows install. Even with previous versions of the software in years past, people have tried to troubleshoot issues of getting it to work on WINE and he would tell them "I only support direct Windows issues. You're on your own getting it to work with emulation. Just too much on my plate to be spending time dealing with issues on alternative platforms." That's why I'm a little surprised he's spent as much time as he already has reviewing code and such based on my WINE report. The quicker/easier it is for him to find, the better odds of him fixing it. Too much time/effort and it'll get pushed to the back burner until if/when actual Windows users start complaining. Keep in mind, he's not some hobbyist making a cheap weather app. This program is officially used at all the United States government National Weather Service offices, as well as emergency managers, TV stations and other high-profile clients. So this is the real deal with lots of official duties with managing that program.