[Bug 31910] New: KiUserExceptionDispatcher stub crashes Battleye > 1.176
http://bugs.winehq.org/show_bug.cgi?id=31910 Bug #: 31910 Summary: KiUserExceptionDispatcher stub crashes Battleye > 1.176 Product: Wine Version: 1.5.14 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: mgg+winehqbugzilla(a)nobodymuch.org Classification: Unclassified Created attachment 42011 --> http://bugs.winehq.org/attachment.cgi?id=42011 Backtrace of crash on 1.5.13 (can create later ones if needed) DayZ on Arma2 ran well (with graphical glitches) until ~1/Oct/2012, when a new release (1.176) of the anti-cheat software Battleye (http://battleye.com/) came out. Previously, Battleye ran perfectly under wine. Apparently, this new version hooks into the scripting engine functions of Arma2 to monitor for illegitimate use of script calls. This hooking appears to be implemented by the insertion of breakpoints/exceptions. I contacted Battleye about this and related issues, and Bastian Suter was kind enough to reply with: "yes, this problem is related to new BE features and I'm afraid I can't do anything about it when it comes to Wine. Maybe you could report this as a bug/problem to the Wine devs? Let them know that the KiUserExceptionDispatcher function is not called in Wine when exceptions happen, which it is on Windows." I've confirmed that this function is a stub according to the documentation at http://source.winehq.org/WineAPI/ntdll.html Reproduction steps: 0. Get a running version of DayZ on Wine (see AppDB) - http://appdb.winehq.org/objectManager.php?sClass=version&iId=26387&iTestingI... 1. connect to a server with BE enabled (non-BE servers work fine, confirming this is related to BE) 2. (optional) wait in the lobby for BE to reply with the GUUID message, indicating BE is fully initialised and the engine is hooked 3. join the game 4. at 80% on the loading bar, presumably when the first scripts run, arma2 crashes with "wine: Unhandled exception 0x80000003 at address 0x6b88dd (thread 0009), starting debugger..." on the instruction "0x006b88dd: int $3" (breakpoint) Presumably, this crash occurs because BE's exception handler is not being called when the exception occurs. Tested versions: - wine 1.5.9+raw - 1.5.14 - Battleye 1.176 - 1.179 - Arma2 1.62.97771, DayZ 1.7.2.6 Impact: Arma2 and DayZ just reached runnable status in 1.5.13 with the inclusion of the raw input patches (runnable previously by building these patches in). This issue prevents playing on BE-enabled servers (probably >95% of servers). Other Battleye games are certain to be affected, if they run on wine. Battleye prior to 1.176 was working fine, but this is a new BE development so cannot be counted as a regression. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 lyleunderwood(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lyleunderwood(a)gmail.com --- Comment #1 from lyleunderwood(a)gmail.com 2012-10-12 23:07:15 CDT --- ya, i'm definitely seeing this. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 Mike Grant <mgg+winehqbugzilla(a)nobodymuch.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|1.5.14 |1.5.15 --- Comment #2 from Mike Grant <mgg+winehqbugzilla(a)nobodymuch.org> 2012-10-13 08:24:31 CDT --- Confirmed issue remains present in 1.5.15. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 Mike Grant <mgg+winehqbugzilla(a)nobodymuch.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|1.5.15 |1.5.16 --- Comment #3 from Mike Grant <mgg+winehqbugzilla(a)nobodymuch.org> 2012-10-26 20:02:26 CDT --- Present in 1.5.16 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 pmulligan <doctorstrangelove(a)runbox.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |doctorstrangelove(a)runbox.co | |m --- Comment #4 from pmulligan <doctorstrangelove(a)runbox.com> 2012-12-29 03:54:39 CST --- I'm running across this same problem in 1.5.20 as well -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 Calum La Croix <vaerraent(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vaerraent(a)gmail.com -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 chizu(a)spicious.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chizu(a)spicious.com -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 --- Comment #5 from Mike Grant <mgg+winehqbugzilla(a)nobodymuch.org> 2013-04-22 18:50:21 CDT --- Confirmed still present in 1.5.24. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 Kai Patient <kpatient(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kpatient(a)gmail.com --- Comment #6 from Kai Patient <kpatient(a)gmail.com> 2013-09-06 08:14:50 CDT --- Present here in 1.6. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 nefarious.aurifier(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nefarious.aurifier(a)gmail.co | |m -- 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, obfuscation Status|UNCONFIRMED |NEW URL| |http://battleye.com/ CC| |focht(a)gmx.net Summary|KiUserExceptionDispatcher |anti-cheat software |stub crashes Battleye > |Battleye > 1.176 expects |1.176 |call to | |KiUserExceptionDispatcher | |during exception handling | |(user mode SEH dispatcher) Ever confirmed|0 |1 --- Comment #7 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, adjusting some fields... Obviously still present in Wine 1.7.10 Source: http://source.winehq.org/git/wine.git/blob/2a3932a0a22f5f5fb8a90d718e00ae735... --- snip --- 50 @ stub KiUserExceptionDispatcher --- snip --- --- quote --- Let them know that the KiUserExceptionDispatcher function is not called in Wine when exceptions happen, which it is on Windows." --- quote --- Most likely they want a hook as early as possible in usermode exception handling. So just providing a stub is not enough. Maybe small wrapper around raise_exception() or just call KiUserExceptionDispatcher() at raise_exception() entry to simulate it. 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 --- Comment #8 from matt <matt(a)devsub.net> --- Created attachment 47322 --> http://bugs.winehq.org/attachment.cgi?id=47322 dummy call to KiUserExceptionDispatcher -- 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 matt <matt(a)devsub.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matt(a)devsub.net --- Comment #9 from matt <matt(a)devsub.net> --- Adding a dummy call to KiUserExceptionDispatcher removes the crash with the latest git version, but I get immediately kicked from servers due to "WinAPI Error #3". Sadly I have no idea how/where to dig further, debugging this stuff is way over my head. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 Jesse Browne <jessebrowne(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jessebrowne(a)gmail.com -- 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 john_stewart20(a)yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |john_stewart20(a)yahoo.com -- 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 Tom Englund <tomenglund26(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomenglund26(a)gmail.com --- Comment #10 from Tom Englund <tomenglund26(a)gmail.com> --- i tried to implent some basic KiUserExceptionDispatcher based on this pseudocode http://www.microsoft.com/msj/0197/exception/exceptiontextfigs.htm#fig14 however i hit the same thing as Comment 9, i get kicked out of servers because of "WinAPI Error #3" -- 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.
http://bugs.winehq.org/show_bug.cgi?id=31910 hanska2(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hanska2(a)luukku.com --- Comment #11 from hanska2(a)luukku.com --- still stub 1.7.23 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 Razzaline Reindell <razzylaqui(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |razzylaqui(a)gmail.com --- Comment #12 from Razzaline Reindell <razzylaqui(a)gmail.com> --- Created attachment 53234 --> https://bugs.winehq.org/attachment.cgi?id=53234 KiUserEventDispatcher implementation with unfinished/stub implementation of KiContinue and NtContinue I used matt's patch as a starting point and wrote out code based on the link provided by Tom Englund. KiUserExceptionDispatcher calls NtContinue, which calls KiContinue so I created method stubs for both (I had the basic implementations written, using modified ReactOS source code, but decided to leave it out as it was incomplete and wouldn't work anyway). I'm not certain I put everything in the right place, but hopefully it provides a starting point at least. To have this fully working, it seems several ntdll and ntoskrnl functions would have to be implemented. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 Reiny Nyt <razzylaqui(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #53234|0 |1 is obsolete| | --- Comment #13 from Reiny Nyt <razzylaqui(a)gmail.com> --- Created attachment 53238 --> https://bugs.winehq.org/attachment.cgi?id=53238 KiUserEventDispatcher implementation, KiContinue and NtContinue as stubs in same format as other Wine functions I accidentally uploaded the wrong file, sorry. This one should have just the stubs now. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 madcat777(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madcat777(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 Reiny Nyt <razzylaqui(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #53238|0 |1 is obsolete| | --- Comment #14 from Reiny Nyt <razzylaqui(a)gmail.com> --- Created attachment 53290 --> https://bugs.winehq.org/attachment.cgi?id=53290 KiUserEventDispatcher implementation, KiContinue and NtContinue stubs (redid as git patch) No real code changes, I just changed the spec files so KiContinue and NtContinue are marked as stdcall instead of stub, and reformatted it as a git patch. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 dosboss64(a)yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dosboss64(a)yahoo.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 Jan Havran <havran.jan(a)email.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |havran.jan(a)email.cz -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 agrecascino123(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |agrecascino123(a)gmail.com --- Comment #15 from agrecascino123(a)gmail.com --- (In reply to Reiny Nyt from comment #14)
Created attachment 53290 [details] KiUserEventDispatcher implementation, KiContinue and NtContinue stubs (redid as git patch)
No real code changes, I just changed the spec files so KiContinue and NtContinue are marked as stdcall instead of stub, and reformatted it as a git patch.
This won't be enough anymore, as the game now uses a rootkit to prevent writes to it's process memory. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 Chiitoo <escomk3(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |escomk3(a)hotmail.com --- Comment #16 from Chiitoo <escomk3(a)hotmail.com> --- I wonder if bug 41670 and bug 42571 are actually duplicates of this one. The description of what is going on seems to differ a bit here, but a bunch of time has gone by, so maybe it's more or less the same now? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 daedmen(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daedmen(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.org -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 mirh <mirh(a)protonmail.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh(a)protonmail.ch -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 Robert Walker <bob.mt.wya(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob.mt.wya(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 jonwsb(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonwsb(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Staged patchset| |https://github.com/wine-sta | |ging/wine-staging/tree/mast | |er/patches/ntdll-NtContinue Summary|anti-cheat software |anti-cheat software |Battleye > 1.176 expects |Battleye 1.176 expects call |call to |to |KiUserExceptionDispatcher |KiUserExceptionDispatcher |during exception handling |during exception handling |(user mode SEH dispatcher) |(user mode SEH | |dispatcher)(Arma2, DayZ) Status|NEW |STAGED --- Comment #17 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, do you still have the old software archived to reproduce this? As comment #15 indicated: BattlEye has been rewritten, using 'BEDaisy' kernel service for some time now. I'm linking the Wine-Staging patchset https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-NtCon... here which is needed for 'KiUserExceptionDispatcher' implementation to make this ticket somewhat useful. There seem to be no other apps/bug reports referring to this native API. $ wine --version wine-3.4 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 --- Comment #18 from Jan Havran <havran.jan(a)email.cz> --- Anastasius Focht: I have made few tests. I am not much familiar with BattlEye, but I tried my best. All my tests were made on both wine-3.6 and wine-3.6 (Staging) with the same effect. Because I could not find any working compatible server (none of listed servers on BI's master server [1] is online or working for me), I tested it on my own dedicated server (localhost). Running client: wine arma2oa.exe Running server: wine arma2oaserver.exe -config=server.cfg $ cat server.cfg maxPlayers=4; BattlEye=1; Arma 2 OA 1.59/Battleye server 1.115/Battleye client 1.145 -server shows message: Could not connect to BE Master Update attempt failed -client shows message: BattlEye Client: Initialized (v1.145) -I am able to connect and play Arma 2 OA 1.60/Battleye server 1.126/Battleye client 1.146 -save as above Arma 2 OA 1.62/Battleye server 1.148/Battleye client 1.164 -everything working as above, until servers updates itself: BattlEye Server: Update successfully completed. Restarting... BattlEye Server: Initialized (v1.217) -after the server update, client is kicked off few secs after joining with message "kicked off by BattlEye: Client not responding" -I guess the problem is that servers was updated but client is using old version 164 and I do not know how to update it. I tried to update it manually from [2], [3] and [4] but after that client says (after joining the game) that the BattlEye is not initialized and restarts themself I also tried Steam version (Arma 2 OA 1.63), but the game stucks with message "Starting BattlEye Service..." during start-up I can do more test, if you tell me how... [1] http://master.bistudio.com/?page=1&count=10&sorting%5Bplayers%5D=desc&game_i... [2] http://battleye.com/downloads/arma2oa/BEClient.dll [3] http://battleye.com/downloads/arma2oa/BEService.exe [4] http://battleye.com/downloads/arma2oa/BEServer.dll -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 --- Comment #19 from Anastasius Focht <focht(a)gmx.net> --- Hello Jan, thanks for the effort of reproducing. I've spent a few hours trying to see if I can get the old BattlEye client to run to that interesting point without game/server just with the few files you posted links to - but no avail. I wrote a hosting process that emulates certain parts of the game process environment, also using some partially reverse-engineered/documented structures/callbacks from a game-hacker forum. My client process also takes care of automatic BEService installation/startup etc. I'm at least able to initialize the client, and starts talking to the BE service via named pipe but it seems I need the real thing to trigger more code/event callbacks. --- snip --- $ wine ./beclient.exe.so ... BattlEye client dll loaded at 0x10000000 BattlEye client version: 239 Created service 'BEService' in SCM. Started service 'BEService' via SCM. chat_print: Initialized (v1.239) BattlEye client init result: 1 be_gamedata = { 0x11111111, 0x222, 0x7effc7a0 } be_callback = { 0x10017210, 0x10017560, 0x10017790, 0x10017890 } sleeping for 10s... arma2oa_be: sleeping for 10s... sleeping for 10s... arma2oa_be: sleeping for 10s... ... --- snip --- The client dll you posted link to is at v1.239 It still has some code that looks like it makes use of ntdll.dll KiUserExceptionDispatcher / NtContinue but I'm not able to trigger it without full game/proper server setup. --- quote --- I tried to update it manually from [2], [3] and [4] but after that client says (after joining the game) that the BattlEye is not initialized and restarts themself --- quote --- Could you try to provide full relay logs from that use-case, that is both, server and client at 1.2xx ? Make sure it also includes the service traces (no prefix "warmup", let the game bootstrap the whole prefix). Compress if too large. 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 --- Comment #20 from Jan Havran <havran.jan(a)email.cz> --- Hi Anastasius, that stuff you are doing sounds very interesting. You are right, patched client is at v1.239, while server v1.217. Do you want full WINEDEBUG=+relay report? The lowest log size after xz -z compression is 5715 KiB (attachment limit is 5000) when starting by following command: WINEDEBUG=+relay wine arma2oa.exe -nosplash -connect=127.0.01 -port=2302 > arma2oa_+relay 2>&1 Do you need whole report (I can upload it as two parts or on 3rd server) or is head/tail enough for you? Are you interested also in Steam version (1.63) log? And is client v1.239 log even useful for you since this report is about 1.176? Thanks, Jan -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 --- Comment #21 from Robert Walker <bob.mt.wya(a)gmail.com> --- (In reply to Jan Havran from comment #20) ...
The lowest log size after xz -z compression is 5715 KiB (attachment limit is 5000) ...
You want: xz -9 -e to get maximum log file compression... -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 --- Comment #22 from Jan Havran <havran.jan(a)email.cz> --- Created attachment 61378 --> https://bugs.winehq.org/attachment.cgi?id=61378 arma2oa +relay battleye client v1.239 First 27500000 lines of total 29287749 from arma2oa.exe log (+relay). Can not add full log because of 5 MiB limit, so I hope this is enough. WINEDEBUG=+relay wine arma2oa.exe -nosplash -connect=127.0.01 -port=2302 > arma2oa_+relay 2>&1 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 --- Comment #23 from Anastasius Focht <focht(a)gmx.net> --- Hello Jan, --- quote --- First 27500000 lines of total 29287749 from arma2oa.exe log (+relay). Can not add full log because of 5 MiB limit, so I hope this is enough. --- quote --- unfortunately the log doesn't anything related to Battleye. Maybe the remainder part does (attach?). 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 --- Comment #24 from Jan Havran <havran.jan(a)email.cz> --- Created attachment 61393 --> https://bugs.winehq.org/attachment.cgi?id=61393 arma2oa +relay battleye client v1.239 (part 2) Hi Anastasius, I hope there is what you need. If not, I will try capture another log. What strings are you looking for btw? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 --- Comment #25 from Anastasius Focht <focht(a)gmx.net> --- Hello Jan, --- quote --- I hope there is what you need. If not, I will try capture another log. What strings are you looking for btw? --- quote --- well, for a start you go for 'beclient' pattern. Since the app is heavily multi-threaded you go like this: 1) figure out the thread that first loads 'BEClient.dll': --- snip --- $ egrep -i "LoadLibrary.*beclient.*" arma2oa_+relay.strip-tail 00da:Call KERNEL32.LoadLibraryA(00c4bf9c "Expansion\\BattlEye\\BEClient.dll") ret=004bae0f 00da:Call KERNEL32.LoadLibraryA(018ccae8 "C:\\users\\f_wine\\Local Settings\\Application Data\\ArmA 2 OA\\BattlEye\\BEClient.dll") ret=004bae63 --- snip --- 2) Get all trace messages from that thread ('00da'): --- snip --- $ grep 00da: arma2oa_+relay.strip-tail > 00da.txt --- snip --- With this the noisy multi-threaded interleaving is gone. Now your check for any suspicious stuff such as exceptions (':seh:') etc. that causes a process/thread exit. If not present "normal exit" one just forward searches for 'PROCESS_DETACH' pattern which yields this: --- snip --- ... 00da:Ret PE DLL (proc=0x9566bdb,module=0x94b0000 L"BEClient.dll",reason=PROCESS_ATTACH,res=(nil)) retval=1 00da:Ret KERNEL32.LoadLibraryA() retval=094b0000 ret=004bae0f 00da:Call KERNEL32.GetProcAddress(094b0000,00c4a148 "GetVer") ret=004d62f9 00da:Ret KERNEL32.GetProcAddress() retval=094c7ab0 ret=004d62f9 00da:Call KERNEL32.FreeLibrary(094b0000) ret=004bae27 00da:Call PE DLL (proc=0x9566bdb,module=0x94b0000 L"BEClient.dll",reason=PROCESS_DETACH,res=(nil)) 00da:Call KERNEL32.GetModuleFileNameW(094b0000,018cc60c,00000104) ret=094c9d81 00da:Ret KERNEL32.GetModuleFileNameW() retval=0000005f ret=094c9d81 ... --- snip --- Looks like it doesn't like the client version which causes process exit. The version/comparison is hard-coded in the app code hence not visible in trace log. You need to ensure that the binaries/versions match ('arma2oa.exe' + 'BEClient.dll'). 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 --- Comment #26 from Jan Havran <havran.jan(a)email.cz> --- Hello Anastasius, thank you very much for info about logging thread stuff, this is very useful for me. So, I will try new tests, this time without manual patching. Problem is that there are so many versions and sometimes it tries to update itself... -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 Jasmin Buchert <jbuchert+wine(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbuchert+wine(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 Vijay Kamuju <infyquest(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |infyquest(a)gmail.com --- Comment #27 from Vijay Kamuju <infyquest(a)gmail.com> --- NtContinue is now implemented in Wine. https://source.winehq.org/git/wine.git/commitdiff/95e2d05e5d6b92a2f6b28e00f3... -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |e561ce4b9259071f79d219dddf6 | |2f05cdd8dd07b Status|STAGED |RESOLVED Resolution|--- |FIXED --- Comment #28 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, --- quote --- NtContinue is now implemented in Wine. https://source.winehq.org/git/wine.git/commitdiff/95e2d05e5d6b92a2f6b28e00f3... --- quote --- I rather propose to use commit https://source.winehq.org/git/wine.git/commitdiff/e561ce4b9259071f79d219dddf... ("ntdll: Move NtRaiseException() implementation to the Unix library.") as resolution here to avoid overlapping with bug 45572 ("League of Legends 8.12+ fails to start a game (anticheat engine, hooking of NtContinue)"). It's kinda buried but that commit contains changes to hook up KiUserExceptionDispatcher(). Thanks Alexandre @Jan (comment #18 , comment #26) Are you still able to test with Arma 2 + old Battleye 1.1.xxx and recent Wine from today (or wait until Wine 5.11)? $ wine --version wine-5.10-39-g1752958240 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 --- Comment #29 from Jan Havran <havran.jan(a)email.cz> --- (In reply to Anastasius Focht from comment #28)
@Jan (comment #18 , comment #26)
Are you still able to test with Arma 2 + old Battleye 1.1.xxx and recent Wine from today (or wait until Wine 5.11)?
$ wine --version wine-5.10-39-g1752958240
Regards
Hi, yes I can try to do some tests with Arma and manually built Wine (I still have non-steam version somewhere), but not before this weekend because of technical problems (I do not have my PC where I can install Arma here ATM). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 jonwsb(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|jonwsb(a)gmail.com | -- 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.
https://bugs.winehq.org/show_bug.cgi?id=31910 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #30 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 5.11. -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla