3 ms·

I don't know why it's surprising. Reverse engineering an executable is quite a jump in skill level from guesswork.

• nneonneo 4y ago
  That, and Windows is *huge*. The best bet would probably be to reverse engineer the patch in question, but if it’s a typical combo patch then you’re probably looking at changes across a dozen system files. If you’re unlucky, the patch is just flipping a flag or something for a feature that already existed: it wouldn’t surprise me if Windows already had hacks specifically for “chrome.exe” (for compatibility or anti-compatibility reasons). In that case it becomes much more time consuming to isolate the one component that is responsible for the problem.
  • deleted 4y ago
    [deleted]
  • saagarjha 4y ago
    I’d reverse engineer the API they were calling. Generally this kind of thing yields good results quickly.
• userbinator 4y ago
  "Reverse engineering" is vague and means anywhere from "poke at it randomly to see what it does" to "read the binary".
  • justinclift 4y ago
    Isn't the more widely accepted meaning to de-compile it back to source code (of some form), and go from there?