[Bug 37585] 64-bit Chromium browser engine with native API sandboxing/hooking scheme fails if 64-bit ntdll.dll.so is not mapped at desired fixed address (Google Chrome 38+ crashes)

wine-bugs at winehq.org wine-bugs at winehq.org
Thu Nov 12 10:51:35 CST 2015


https://bugs.winehq.org/show_bug.cgi?id=37585

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |erich.e.hoover at wine-staging
                   |                            |.com

--- Comment #2 from Anastasius Focht <focht at gmx.net> ---
Hello folks,

I've read some older mailing list posts and came around this:

https://www.winehq.org/pipermail/wine-devel/2015-November/110134.html

--- quote ---
...
Most of this idea is in my patch 6
(https://dl.dropboxusercontent.com/u/195059/wine/ntdll-Syscall_Wrappers/0006-winebuild-Add-support-for-x86-32-XP-WoW64-system-cal.patch),
which I have tested with Steam pretty extensively.  However, I cannot
get the WoW64 version to "work" because of the 64-bit "webhelper" crap
- for some reason it cannot read the 64-bit ntdll memory.
--- quote ---

and

--- quote ---
I have support for xp and xp-WoW64 in my prototype, the difficulty is
that the xp-WoW64 doesn't work with Steam because of the 64-bit
"helper".
https://dl.dropboxusercontent.com/u/195059/wine/ntdll-Syscall_Wrappers/index.html

The most interesting patches are 5 and 6, 7 is trying to figure out
what is going on with the 64-bit version (it fails to even read the
function memory at all).  Michael has a brilliant scheme for getting
the sysenter to work, but I'll leave that up to him to discuss.
--- snip ---

Maybe you are encountering the problem that I have analysed here?

If it's a different problem and still present, please create another ticket and
provide information how to exactly reproduce (or alternatively +server traces).

Regards

-- 
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.



More information about the wine-bugs mailing list