https://bugs.winehq.org/show_bug.cgi?id=56912 --- Comment #13 from Zeb Figura <z.figura12(a)gmail.com> --- 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? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.