Hacker News Reader

> It only happens when the program is called SS14.Loader.exe.

Could you have a SS14.Loader.arm.exe for arm? Then the exe name wouldn't match and it woildn't trigger the crash?

You could. The fix is easy. The problem was the painfully long debugging in order to find the root cause of the issue.

I understand and aprechiate the writeup, I just don't see why the conclusion is to delay the release until the detour bug is fixed, when it's easy to work around it once it has been understood?

I suspect that the fix to the detour bug will be unevenly distributed as well, so avoiding it would help user experience regardless.

Until microsoft ships the .arm.exe name in the list. pretty much a ticking time bomb.

Microsoft has done a lot of bad releases since they eliminated engineering in test, but it seems a little bit above and beyond to expect them to specifically add an arm executable to a list of executables to patch with x86(64) code and then not confirm that it does what it's supposed to do.

The current situation is derpy, but understandable. The patching system was ported with the rest of the arm stuff, and the executable for arm matches the name list so it makes sense to do the patch, but nobody ported the patch data. Whoops.

Y'know it would be nice if stuff would log it somewhere when it applies patches like this.

Reply on news.ycombinator.com