https://bugs.winehq.org/show_bug.cgi?id=37585
--- Comment #9 from Erich E. Hoover erich.e.hoover@wine-staging.com --- (In reply to Erich E. Hoover from comment #8)
...
Ok, figured it out. It wasn't doing a rebuild of wine64, after touching loader/main.c it's in the right place and it can read the memory (hurray!). Something else is going on that prevents it from continuing, but at least now the memory is being read correctly. Is there some reason wine64 isn't mapped at this address to start with? It seems like it should be mapped so that it doesn't interfere with ntdll...