http://bugs.winehq.org/show_bug.cgi?id=12099
Summary: .NET Framework 1.1 installer requires loadperf.dll in
case of AeDebug -> Auto=0 (unhandled exception dialog)
Product: Wine
Version: CVS/GIT
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Created an attachment (id=11486)
--> (http://bugs.winehq.org/attachment.cgi?id=11486)
example patch to add loadperf.dll and simple UnloadPerfCounterTextStringsW stub
preventing .NET 1.1 installer exception
Hello,
VS.NET 7.x installers modify AeDebug which results in error message box from
.NET Framework 1.1 installer due to an unhandled exception.
With default AeDebug Auto=1 and standalone .NET 1.1 installation you won't
notice it because this exception doesn't affect overall "success" result of
installer.
You can capture output from console to see winedbg actually spawned.
VS.NET 7.x installers add/modify the following JIT debugging keys:
--- snip ---
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\AeDebug\Debugger
Auto: 1 -> 0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger
Default: cordbg.exe !a 0x%x8
--- snip ---
Extract from .msi file:
--- snip ---
_FldbVs7eve_RegFile_887_00017.3643236F_FC70_11D3_A536_0090278A1BB8 2
SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug Auto 0
_VS_Debugging___VS7JIT_____X86.3643236F_FC70_11D3_A536_0090278A1BB8)
..
--- snip ---
You can simulate the behaviour on clean ~/.wine if you manually set
AeDebug/Auto=0 (default is 1) and then execute the standalone .NET 1.1
installer.
--- snip ---
002d:Call KERNEL32.lstrlenA(0034f55c "2008-03-17
21:20:25\t\tStarting\tUninstalling performance counters\r\n") ret=79e88b92
..
002d:Call KERNEL32.LoadLibraryA(79e61310 "loadperf.dll") ret=79e907ed
002d:Ret KERNEL32.LoadLibraryA() retval=00000000 ret=79e907ed
002d:Call KERNEL32.GetLastError() ret=79e907f9
002d:Ret KERNEL32.GetLastError() retval=0000007e ret=79e907f9
002d:Call KERNEL32.RaiseException(c06d007e,00000000,00000001,0034f960)
ret=79e9082c
002d:trace:seh:raise_exception code=c06d007e flags=0 addr=0x7b8419a0
002d:trace:seh:raise_exception info[0]=0034f910
002d:trace:seh:raise_exception eax=7b82c3e9 ebx=7b8af3e4 ecx=00000000
edx=0034f904 esi=0034f904 edi=0034f880
002d:trace:seh:raise_exception ebp=0034f868 esp=0034f804 cs=0073 ds=007b
es=007b fs=0033 gs=003b flags=00200212
002d:trace:seh:call_stack_handlers calling handler at 0x402518 code=c06d007e
flags=0
..
002d:Call KERNEL32.UnhandledExceptionFilter(0034f350) ret=7c34c456
wine: Unhandled exception 0xc06d007e at address 0x7b8419a0 (thread 002d),
starting debugger...
002d:Call user32.MessageBoxA(00000000,0034efd8 "Unhandled exception 0xc06d007e
at address 0x7b8419a0.\nDo you wish to debug it?",7b8a3e47 "Exception
raised",00000014) ret=7b841deb
--- snip ---
The message box is shown with the option to dismiss the exception or to debug
it.
This can be pretty confusing to users who have no knowledge how to deal with
this.
Well, actually this exception should never occur.
Wine can prevent this problem by providing a simple loadperf.dll and
UnloadPerfCounterTextStringsW stub.
Output after patch:
--- snip ---
0041:Ret KERNEL32.LoadLibraryA() retval=607d0000 ret=79e907ed
0041:Call KERNEL32.InterlockedExchange(79e96fa8,607d0000) ret=79e9083e
0041:Ret KERNEL32.InterlockedExchange() retval=00000000 ret=79e9083e
0041:Call KERNEL32.GetProcAddress(607d0000,79e919b4
"UnloadPerfCounterTextStringsW") ret=79e908c4
0041:Ret KERNEL32.GetProcAddress() retval=607d8808 ret=79e908c4
0041:Call loadperf.UnloadPerfCounterTextStringsW(0034f9d0 L"u
\"ASP.NET_1.1.4322\"",00000001) ret=79e86e64
0041:fixme:loadperf:UnloadPerfCounterTextStringsW (L"u \"ASP.NET_1.1.4322\"",
1): stub!
0041:Ret loadperf.UnloadPerfCounterTextStringsW() retval=00000000 ret=79e86e64
--- snip ---
Please add this dll and the UnloadPerfCounterTextStringsW stub.
The attached patch is provided as example to quickly validate the problem
solution.
Regards
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44704
Bug ID: 44704
Summary: Screenhero installer runs into crash window (Access
Violation)
Product: Wine
Version: 3.3
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: ---
The Screenhero installer runs into a crash window (Access Violation) while
calling FormatMessageW with id 0x800b0109 which apparently is
CERT_E_UNTRUSTEDROOT
I don`t know where this error comes from but with the patch it gets further to
install all files***, though there`s still a crash in the end.
Patch is at:
https://bugs.winehq.org/attachment.cgi?id=60704&action=diff
***: It also suffers from bug 34989, so you need workaround from here to avoid
a hang: https://bugs.winehq.org/attachment.cgi?id=60702&action=diff
--
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=45841
Bug ID: 45841
Summary: Battleye's BEDaisy.sys requires that PsThreadType and
PsProcessType are defined
Product: Wine
Version: 3.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: dereklesho52(a)Gmail.com
Distribution: ---
Without these two structures, battleye's BEDaisy.sys will crash on an
EXCEPTION_ACCESS_VIOLATION.
Alongside the fixes for #45664 and #44912, Battleye will launch the game.
I will commit my fix to my github shortly after posting this bug:
https://github.com/Guy1524/wine/commits/battleye-work-stable
--
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=44911
Bug ID: 44911
Summary: BattlEye 'BEDaisy' kernel service crashes on
unimplemented function ntoskrnl.exe.PsGetProcessId
Product: Wine
Version: 3.5
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
continuation of bug 44910
--- snip ---
$ WINEDEBUG=+seh,+relay,+ntoskrnl wine net start BEDaisy >>log.txt 2>&1
...
0034:Call driver init 0x78d000
(obj=0x11cc28,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy")
...
0034:Ret ntdll.NtQuerySystemInformation() retval=00000000 ret=7bc803ab
0034:Ret ntoskrnl.exe.ZwQuerySystemInformation() retval=00000000 ret=0082d9b5
...
0034:Call KERNEL32.RaiseException(80000100,00000001,00000002,0065eb78)
ret=7ec1ace2
...
0034:trace:seh:raise_exception code=80000100 flags=1 addr=0x7b446c33
ip=7b446c33 tid=0034
0034:trace:seh:raise_exception info[0]=7ec1ad00
0034:trace:seh:raise_exception info[1]=7ec1e697
wine: Call from 0x7b446c33 to unimplemented function
ntoskrnl.exe.PsGetProcessId, aborting
wine: Unimplemented function ntoskrnl.exe.PsGetProcessId called at address
0xf7c30023:0x7b446c33 (thread 0034), starting debugger...
--- snip ---
$ sha1sum Tibia_Setup.exe
50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe
$ du -sh Tibia_Setup.exe
5.2M Tibia_Setup.exe
$ wine --version
wine-3.5-107-gf4573adb0f
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=44912
Bug ID: 44912
Summary: Tibia client reports 'Failed to launch game', needs
'ntdll.RtlCreateUserProcess' implementation
Product: Wine
Version: 3.5
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
besides the traditional 'KERNEL32.CreateProcessW()' API it also uses native API
to create process(es).
--- snip ---
$ pwd
/home/focht/winetest/drive_c/users/focht/Local Settings/Application
Data/Tibia/packages/Tibia/bin
$ WINEDEBUG=+seh,+relay,+ntoskrnl,+ntdll wine ./client.exe >>log.txt 2>&1
...
003d:Call KERNEL32.CreateProcessW(00000000,001c8630 L"\"C:\\users\\focht\\Local
Settings\\Application Data\\Tibia\\packages\\Tibia\\bin\\client_launcher.exe\"
",00000000,00000000,00000000,00000410,00000000,01d7c6b8 L"C:/users/focht/Local
Settings/Application Data/Tibia/packages/Tibia/bin",0033cf2c,0033cf1c)
ret=0047235f
...
0044:Call KERNEL32.__wine_kernel_init() ret=7bc6d171
...
003d:Ret KERNEL32.CreateProcessW() retval=00000001 ret=0047235f
...
0044:Call KERNEL32.CreateProcessW(00000000,0033d6cc L"\"C:\\users\\focht\\Local
Settings\\Application Data\\Tibia\\packages\\Tibia\\bin\\client_launcher.exe\"
3",00000000,00000000,00000000,00000410,00000000,00000000,0033d1a0,0033d190)
ret=7e72e854
...
0044:Ret KERNEL32.CreateProcessW() retval=00000001 ret=7e72e854
...
0044:Call ntdll.RtlInitUnicodeString(0033e75c,00162030
L"\"C:\\users\\focht\\Local Settings\\Application
Data\\Tibia\\packages\\Tibia\\bin\\client_launcher.exe\" 6 ") ret=0045e9fe
0044:Ret ntdll.RtlInitUnicodeString() retval=0033e75c ret=0045e9fe
...
0044:Call
ntdll.RtlCreateProcessParameters(0033e770,0033e764,00000000,00000000,0033e75c,00000000,00000000,00000000,00000000,00000000)
ret=004519b8
...
0044:Ret ntdll.RtlCreateProcessParameters() retval=00000000 ret=004519b8
...
0044:Call
ntdll.RtlCreateUserProcess(0033e764,00000040,00390000,00000000,00000000,00000000,00000000,00000000,00000000,0033e780)
ret=0046fb4d
0044:fixme:ntdll:RtlCreateUserProcess (0x33e764 64 0x390000 (nil) (nil) (nil) 0
(nil) (nil) 0x33e780): stub
0044:Ret ntdll.RtlCreateUserProcess() retval=c0000002 ret=0046fb4d
...
0048:Call KERNEL32.GetStringTypeW(00000001,00162fe8 L"00:52:30: Launching
game...\r\n00:52:30: Failed to launch game.\r\n",00000001,005bf46a)
ret=7dde5042
--- snip ---
Wine currently has the process creation sequence not implemented at native API
level (albeit it uses some native API calls). It would require a bit
redesign/moving code (dlls/kernel32/process.c:create_process, ...) around but
into places that would make Wine more compatible with Windows with regards to
process creation (although the heavy lifting is done in Windows kernel).
* ntdll.NtCreateProcess
* ntdll.RtlCreateUserProcess
...
Also related: bug 23451 ("VMWare Thinapps (packaged with version >4.5) and
XenoCode wrapped apps fail to run (differences in process creation sequence at
native API level)")
$ sha1sum Tibia_Setup.exe
50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe
$ du -sh Tibia_Setup.exe
5.2M Tibia_Setup.exe
$ wine --version
wine-3.5-107-gf4573adb0f
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=45844
Bug ID: 45844
Summary: Battleye's BEDaisy.sys requires correct
KeGetCurrentThread implementation
Product: Wine
Version: 3.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: dereklesho52(a)Gmail.com
Distribution: ---
Battleye tries to access the KTHREAD structure it gets from KeGetCurrentThread,
put because it is not present in our implementation there is a page fault. My
implementation on github fixes this issue:
https://github.com/Guy1524/wine/commits/battleye-work-stable
--
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=44811
Bug ID: 44811
Summary: BattlEye 'BEDaisy' kernel service requires _chkstk
implementation.
Product: Wine
Version: 3.4
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
Distribution: ---
When the stack goes over a 4k on x86 or 8k for x64 boundary then this function
is used to resolve this issue.
https://msdn.microsoft.com/en-us/library/ms648426(v=vs.85).aspx
--
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=45843
Bug ID: 45843
Summary: Battleye's BEDaisy.sys expects memory allocated by
ExAllocatePoolWithTag to be executable
Product: Wine
Version: 3.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: dereklesho52(a)Gmail.com
Distribution: ---
In the NT Kernel, non-paged memory is executable, and BEDaisy.sys crashes on a
page fault if this is not the case.
My patch is located here:
https://github.com/Guy1524/wine/commits/battleye-work-stable
--
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.