February 2019 - Wine-Bugs - list.winehq.org

[Bug 14415] New: Monkey Island 3 demo slow
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

http://bugs.winehq.org/show_bug.cgi?id=14415 Summary: Monkey Island 3 demo slow Product: Wine Version: 1.1.0 Platform: PC URL: ftp://ftp.lucasarts.com/demos/pc/cursedemo.exe OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: tsalacinski(a)gmail.com Monkey Island 3 works pretty slow with Wine 1.1.0. It happens only in complex locations, where there is a waterfall etc. COMI works very slow, even on my Core2Duo 2.53 GHZ (which is pretty good for that game I think). The strange thing is, when the screen is scrolling (eg. the character moves to the other part of the scene and the scene is scrolling) it work properly. When the scene is static (eg. no scrolling, only animated parts like waterfall or rain etc) it works very bad. In this demo you can see this when you are shooting with the cannon. A part of walkthrough (on how to get to the cannon): After the intro you'll find yourself captive in LeChuck's ship. Start talking to the small pirate and you'll realize that it's your old friend Wally. Make him see that he is no good as a pirate and he will soon drop his hook and start crying. Pick up the plastic hook from the floor and pick up the ramrod from the wall. Use the cannon and sink the four boats full of skeletons. Thanks -- 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.

1 22

[Bug 46205] New: Multiple kernel drivers need implementation of ' ntoskrnl.ObReferenceObjectByHandle' for 'PsThreadType' (PETHREAD)
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=46205 Bug ID: 46205 Summary: Multiple kernel drivers need implementation of 'ntoskrnl.ObReferenceObjectByHandle' for 'PsThreadType' (PETHREAD) Product: Wine Version: 3.21 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 44588 (and partially bug 44910) --- snip --- $ WINEDEBUG=+seh,+loaddll,+process,+service,+ntoskrnl wineboot >>log.txt 2>&1 ... 000f:trace:service:scmdatabase_load_services Loading service L"bizVSerial" 000f:trace:service:load_service_config Image path = L"System32\\drivers\\bizVSerialNT.sys" 000f:trace:service:load_service_config Group = (null) 000f:trace:service:load_service_config Service account name = L"LocalSystem" 000f:trace:service:load_service_config Display name = L"Franson VSerial" 000f:trace:service:load_service_config Service dependencies : (none) 000f:trace:service:load_service_config Group dependencies : (none) ... 0017:trace:service:service_thread 0x10d60 0017:trace:service:SERV_OpenSCManagerW ((null),(null),0x00000001) 0015:trace:service:svcctl_OpenSCManagerW ((null), (null), 1) 0017:trace:service:SERV_OpenSCManagerW returning 0x11920 0017:trace:service:RegisterServiceCtrlHandlerExW L"winedevice" 0x7f47d7011ab0 0x11800 0017:trace:service:SetServiceStatus 0x110c0 30 4 5 0 0 0 0 ... 000f:trace:service:process_send_start_message 0x143b0 L"bizVSerial" (nil) 0 0016:trace:service:service_handle_control L"winedevice" control 2147483648 data 0x11bb2 data_size 22 0016:trace:ntoskrnl:ZwLoadDriver (L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\bizVSerial") ... 0016:trace:service:QueryServiceConfigW Image path = L"System32\\drivers\\bizVSerialNT.sys" 0016:trace:service:QueryServiceConfigW Group = L"" 0016:trace:service:QueryServiceConfigW Dependencies = L"" 0016:trace:service:QueryServiceConfigW Service account name = L"LocalSystem" 0016:trace:service:QueryServiceConfigW Display name = L"Franson VSerial" 0016:trace:ntoskrnl:open_driver opened service for driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\bizVSerial" 0016:trace:service:SetServiceStatus 0x12e50 30 2 0 0 0 0 2710 0014:trace:service:svcctl_SetServiceStatus (0x15e80, 0x15754) 0016:trace:ntoskrnl:IoCreateDriver (L"\\Driver\\bizVSerial", 0x7f47c8c949c0) 0016:trace:ntoskrnl:load_driver loading driver L"System32\\drivers\\bizVSerialNT.sys" 0016:trace:loaddll:load_native_dll Loaded L"C:\\windows\\System32\\drivers\\bizVSerialNT.sys" at 0x460000: native 0016:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x468034 ip=468034 tid=0016 0016:trace:seh:NtRaiseException info[0]=0000000000000000 0016:trace:seh:NtRaiseException info[1]=fffff78000000320 0016:trace:seh:NtRaiseException rax=fffff78000000320 rbx=0000000000013178 rcx=0000000000013010 rdx=0000000000013178 0016:trace:seh:NtRaiseException rsi=00007f47d73b84b1 rdi=00007f47c8cd1c71 rbp=000000000033f8a0 rsp=000000000033f788 0016:trace:seh:NtRaiseException r8=0000000000466100 r9=00002b992ddfa232 r10=000000000000a000 r11=0000000000012ee0 0016:trace:seh:NtRaiseException r12=0000000000013010 r13=0000000000000000 r14=0000000000011b18 r15=0000000000468008 0016:trace:seh:call_vectored_handlers calling handler at 0x7f47c8c93260 code=c0000005 flags=0 0016:trace:seh:call_vectored_handlers handler at 0x7f47c8c93260 returned ffffffff 0016:trace:ntoskrnl:IoCreateDevice (0x13010, 496, L"\\Device\\bizvSerialMgr", 34, 0, 0, 0x33f790) 0016:trace:ntoskrnl:IoCreateSymbolicLink L"\\DosDevices\\bizSerialMgr" -> L"\\Device\\bizvSerialMgr" 0016:trace:ntoskrnl:KeInitializeEvent event 0x136e8, type 0, state 0. 0016:trace:ntoskrnl:KeInitializeEvent event 0x136c8, type 0, state 0. 0016:fixme:ntoskrnl:ObReferenceObjectByHandle stub: 0x3c 1fffff (nil) 0 0x136e0 (nil) 0016:trace:ntoskrnl:init_driver init done for L"bizVSerial" obj 0x13010 0016:trace:ntoskrnl:init_driver - DriverInit = 0x468008 0016:trace:ntoskrnl:init_driver - DriverStartIo = (nil) 0016:trace:ntoskrnl:init_driver - DriverUnload = 0x4613c0 0016:trace:ntoskrnl:init_driver - MajorFunction[0] = 0x461180 0016:trace:ntoskrnl:init_driver - MajorFunction[1] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[2] = 0x461228 0016:trace:ntoskrnl:init_driver - MajorFunction[3] = 0x46133c 0016:trace:ntoskrnl:init_driver - MajorFunction[4] = 0x461304 0016:trace:ntoskrnl:init_driver - MajorFunction[5] = 0x461398 0018:trace:ntoskrnl:KeWaitForMultipleObjects count 2, objs 0x56fd80, wait_type 1, reason 0, mode 0, alertable 0, timeout (nil), wait_blocks 0x56fd90. 0016:trace:ntoskrnl:init_driver - MajorFunction[6] = 0x461398 0016:trace:ntoskrnl:init_driver - MajorFunction[7] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[8] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[9] = 0x461398 0016:trace:ntoskrnl:init_driver - MajorFunction[10] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[11] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[12] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[13] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[14] = 0x4612e0 0016:trace:ntoskrnl:init_driver - MajorFunction[15] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[16] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[17] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[18] = 0x461374 0016:trace:ntoskrnl:init_driver - MajorFunction[19] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[20] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[21] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[22] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[23] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[24] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[25] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[26] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[27] = 0x7f47c8c997b0 0016:trace:service:SetServiceStatus 0x12e50 30 4 5 0 0 0 0 0015:trace:service:svcctl_SetServiceStatus (0x15e80, 0x15cf4) ... 0017:trace:ntoskrnl:unload_driver L"\\Driver\\bizVSerial" 0017:trace:service:SetServiceStatus 0x12e50 30 3 0 0 0 0 0 ... 0017:trace:ntoskrnl:KeSetEvent event 0x136c8, increment 0, wait 0. 0017:trace:ntoskrnl:KeWaitForMultipleObjects count 1, objs 0x44f900, wait_type 1, reason 6, mode 0, alertable 0, timeout (nil), wait_blocks (nil). 0018:trace:ntoskrnl:KeResetEvent event 0x136c8. 0017:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x7f47c8ca3183 ip=7f47c8ca3183 tid=0017 0017:trace:seh:NtRaiseException info[0]=0000000000000001 0017:trace:seh:NtRaiseException info[1]=00000000deadbeb7 0017:trace:seh:NtRaiseException rax=00000000deadbeaf rbx=000000000044f900 rcx=00007f47d6aed879 rdx=0000000000000000 0017:trace:seh:NtRaiseException rsi=000000000044f5c0 rdi=0000000000000000 rbp=000000000044f8a0 rsp=000000000044f580 0017:trace:seh:NtRaiseException r8=0000000000000000 r9=0000000000000000 r10=000000000044f340 r11=0000000000000246 0017:trace:seh:NtRaiseException r12=0000000000013010 r13=0000000000000001 r14=000000000044f908 r15=000000000044f900 0017:trace:seh:call_vectored_handlers calling handler at 0x7f47c8c93260 code=c0000005 flags=0 ... wine: Unhandled page fault on write access to 0xdeadbeb7 at address 0x7f47c8ca3183 (thread 0017), starting debugger... 0017:trace:seh:start_debugger Starting debugger "winedbg --auto 17 60" 0017:trace:process:CreateProcessInternalW app (null) cmdline L"winedbg --auto 17 60" 0017:trace:process:find_exe_file looking for L"winedbg" 0017:trace:process:find_exe_file Trying native exe L"C:\\windows\\system32\\winedbg.exe" 0017:trace:process:CreateProcessInternalW starting L"C:\\windows\\system32\\winedbg.exe" as Win64 binary (10000000-10018000, x86_64) 0017:err:seh:start_debugger Couldn't start debugger ("winedbg --auto 17 60") (1115) --- snip --- The kernel driver creates a secondary thread via 'PsCreateSystemThread' and wait s in driver unload routine for the thread to exit. Wine's 'ObReferenceObjectByHandle' is currently a stub, returning a fake (invalid) handle. This causes 'KeWaitForSingleObject' to dereference an invalid handle later. The sequence is pretty standard for Windows kernel drivers. One of the many driver examples on Github: https://github.com/Microsoft/Windows-driver-samples/blob/master/general/can… --- snip --- ... NTSTATUS DriverEntry(_In_ PDRIVER_OBJECT DriverObject, _In_ PUNICODE_STRING RegistryPath) { ... // // Start the polling thread. // devExtension->ThreadShouldStop = FALSE; status = PsCreateSystemThread(&threadHandle, (ACCESS_MASK)0, NULL, (HANDLE) 0, NULL, CsampPollingThread, deviceObject ); if ( !NT_SUCCESS( status )) { IoDeleteSymbolicLink( &unicodeDosDeviceName ); IoDeleteDevice( deviceObject ); return status; } // // Convert the Thread object handle into a pointer to the Thread object // itself. Then close the handle. // ObReferenceObjectByHandle(threadHandle, THREAD_ALL_ACCESS, NULL, KernelMode, &devExtension->ThreadObject, NULL ); ZwClose(threadHandle); } ... VOID CsampPollingThread( _In_ PVOID Context) { ... // // Now enter the main IRP-processing loop // for(;;) { ... // // See if thread was awakened because driver is unloading itself... // if ( DevExtension->ThreadShouldStop ) { PsTerminateSystemThread( STATUS_SUCCESS ); } ... } ... } ... VOID CsampUnload( _In_ PDRIVER_OBJECT DriverObject) { ... // // Set the Stop flag // devExtension->ThreadShouldStop = TRUE; ... // // Wait for the thread to terminate // KeWaitForSingleObject(devExtension->ThreadObject, Executive, KernelMode, FALSE, NULL ); ObDereferenceObject(devExtension->ThreadObject); ... } --- snip --- Microsoft docs: https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/wdm/n… Wine source: https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/ntoskrnl.exe/ntoskrn… --- snip --- 2580 /*********************************************************************** 2581 * ObReferenceObjectByHandle (NTOSKRNL.EXE.@) 2582 */ 2583 NTSTATUS WINAPI ObReferenceObjectByHandle( HANDLE obj, ACCESS_MASK access, 2584 POBJECT_TYPE type, 2585 KPROCESSOR_MODE mode, PVOID* ptr, 2586 POBJECT_HANDLE_INFORMATION info) 2587 { 2588 FIXME( "stub: %p %x %p %d %p %p\n", obj, access, type, mode, ptr, info); 2589 2590 if(ptr) 2591 *ptr = UlongToHandle(0xdeadbeaf); 2592 2593 return STATUS_SUCCESS; 2594 } --- snip --- $ sha1sum GpsGateClient.exe bd5ac140199054a7b4502994439fcc78009fee35 GpsGateClient.exe $ du -sh GpsGateClient.exe 2.5M GpsGateClient.exe $ wine --version wine-3.21-87-g65677e2b2f 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.

1 4

[Bug 11056] New: TAB key counted twice
by wine-bugs＠winehq.org April 10, 2019

April 10, 2019

http://bugs.winehq.org/show_bug.cgi?id=11056 Summary: TAB key counted twice Product: Wine Version: 0.9.44. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: choppy(a)free.fr In various dialg boxes, the <TAB> key is counted twice, i.e. you're not put on the next field but on the next-after-next one. This bug appears in the application NoteWorthy, which is a music score editor. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 27

[Bug 33463] New: Alan Wake : No sound in cinematics
by wine-bugs＠winehq.org April 7, 2019

April 7, 2019

http://bugs.winehq.org/show_bug.cgi?id=33463 Bug #: 33463 Summary: Alan Wake : No sound in cinematics Product: Wine Version: 1.5.28 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: xvachon(a)gmail.com Classification: Unclassified GOG.com version of the game Wine 1.5.28 Nvidia hardware Arch Linux x64 d3dx9_36 override to get around http://bugs.winehq.org/show_bug.cgi?id=31701 There is sound during gameplay, but none in the cinematics. Sound should be expected at all times. The log does not show anything related to sound. There is a loop of these two lines. fixme:xinput:XInputSetState (0 0x32cd00) Stub! err:d3d_shader:shader_glsl_select >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glUseProgramObjectARB @ ../../../wine/dlls/wined3d/glsl_shader.c / 5829 Which channels should I be looking for to help you debug 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.

1 33

[Bug 40860] New: In Lazarus (for Windows) on Wine, the function keys F11 and F12 don't work correctly
by wine-bugs＠winehq.org April 3, 2019

April 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=40860 Bug ID: 40860 Summary: In Lazarus (for Windows) on Wine, the function keys F11 and F12 don't work correctly Product: Wine Version: 1.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ramonrafe(a)gmail.com Distribution: --- Problem: In Lazarus (for Windows) on Wine, the function keys F11 and F12 don't work correctly. Importance: Normal. ------------------------------------------------------------------------ Hello. I've installed Lazarus 1.6 for Windows on Wine in Linux Mint 17. Lazarus compiles well, although the function keys F11 and F12 don't work like in Windows. F11 (en Windows) makes visible and active the window with the component inspector. The cursor goes to the window and the window changes to be on top. F12 (en Windows) switch betwen the editor of code and the form associated to that code. The cursor goes to the window and the window changes to be on top. When F11 or F12 are pressed (in Lazarus on Wine), the cursor goes to the window, although the window doesn't change to be on top. So, if there are other windows over it, you won't be able to see the window with the cursor. It doesn't happen in Windows. In Windows, when you press F11, the window component inspector pass to be the window with the cursor and the window pass to be the window on top. It looks like a minor problem, although this limitation makes Lazarus not usable in the practice or very unfriendly for use it. Sorry for my basic English. Thank you very much. Ramón. ---------------------------------------------------------------------- Linux Mint: Linux Mint 17 Qiana Wine: version 1.6 and 1.8 . Lazarus 1.6: - File: lazarus-1.6.0-fpc-3.0.0-win32.exe - Link: http://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2032%20bits… -- 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.

1 9

[Bug 41664] New: Visual Basic 6.0 fails to show hints while typing keywords
by wine-bugs＠winehq.org April 1, 2019

April 1, 2019

https://bugs.winehq.org/show_bug.cgi?id=41664 Bug ID: 41664 Summary: Visual Basic 6.0 fails to show hints while typing keywords Product: Wine Version: 1.8.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rizalmart.98(a)gmail.com Distribution: --- When typing functions in visual basic 6.0 like "msgbox(" it does not show any function hint or guide. -- 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.

1 2

[Bug 16574] New: Turbocad 7.1 does not display dialog window properly
by wine-bugs＠winehq.org April 1, 2019

April 1, 2019

http://bugs.winehq.org/show_bug.cgi?id=16574 Summary: Turbocad 7.1 does not display dialog window properly Product: Wine Version: 1.1.10 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: tedhansen(a)sasktel.net Created an attachment (id=18082) --> (http://bugs.winehq.org/attachment.cgi?id=18082) terminal messages running turbocad The "edit entity properties" window in Turbocad 7.1 does not display properly; the menu bar at the bottom of the window is scaled off to the right so that the "OK" button is off screen. -- 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.

1 22

[Bug 36097] New: valgrind shows leaks in d3d9/stateblock tests on i965
by wine-bugs＠winehq.org March 31, 2019

March 31, 2019

https://bugs.winehq.org/show_bug.cgi?id=36097 Bug ID: 36097 Summary: valgrind shows leaks in d3d9/stateblock tests on i965 Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Depends on: 36096 Created attachment 48285 --> https://bugs.winehq.org/attachment.cgi?id=48285 valgrind log ==11765== 32,768 bytes in 1 blocks are definitely lost in loss record 787 of 790 ==11765== at 0x6F8F6F1: ??? (in /usr/lib/libdrm_intel.so.1.0.0) ==11765== by 0x6F8B378: drm_intel_bo_map (in /usr/lib/libdrm_intel.so.1.0.0) ==11765== by 0x6CBEB10: ??? (in /usr/lib/dri/i965_dri.so) ==11765== by 0x6CBED32: ??? (in /usr/lib/dri/i965_dri.so) ==11765== by 0x6CC2BA1: ??? (in /usr/lib/dri/i965_dri.so) ==11765== by 0x6CE45A3: ??? (in /usr/lib/dri/i965_dri.so) ==11765== by 0x6C833C4: ??? (in /usr/lib/dri/i965_dri.so) ==11765== by 0x65E46BB: ??? (in /usr/lib/libGL.so.1.2.0) ==11765== by 0x65B3E14: ??? (in /usr/lib/libGL.so.1.2.0) ==11765== by 0x5CE995A: create_glxcontext (opengl.c:1254) ==11765== by 0x5CEC2DB: X11DRV_wglCreateContextAttribsARB (opengl.c:2071) ==11765== by 0x5269E0D: wglCreateContextAttribsARB (wgl.c:268) ==11765== by 0x4EABA19: wined3d_caps_gl_ctx_create_attribs (directx.c:300) ==11765== by 0x4EBC4C2: wined3d_adapter_init (directx.c:5178) ==11765== by 0x4EBCA26: wined3d_init (directx.c:5272) ==11765== by 0x4F66387: wined3d_create (wined3d_main.c:105) ==11765== by 0x4E30771: d3d8_init (directx.c:413) ==11765== by 0x4E24804: Direct3DCreate8 (d3d8_main.c:47) ==11765== by 0x497E268: test_state_management (stateblock.c:1801) ==11765== by 0x497E5D0: func_stateblock (stateblock.c:1868) ==11765== -- 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.

1 5

[Bug 46251] New: some (all?) crinkler compressed executables crash because they parse in-memory DLL export tables
by wine-bugs＠winehq.org March 31, 2019

March 31, 2019

https://bugs.winehq.org/show_bug.cgi?id=46251 Bug ID: 46251 Summary: some (all?) crinkler compressed executables crash because they parse in-memory DLL export tables Product: Wine Version: 3.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: p2(a)psychaos.be Distribution: --- Created attachment 62950 --> https://bugs.winehq.org/attachment.cgi?id=62950 crash dump and disassembly of decompressor and symbol resolver Some crinkler compressed executables crash when building the imported symbol table. The routine which does this relies on parsing the in-memory copy of KERNEL32.DLL first to retrieve the address for LoadModuleA. This is later used to load other DLLs. Symbol name matching is done using a hash function. The executable only stores the hashes of the symbols it wants to import. For each symbol has in the executable, the symbol resolver routine iterates over all exported symbol names of the DLL and stores the symbol address if the hashes match. The symbol resolver routine crashes because it seems the in-memory copy of KERNEL32.DLL does not have a exported symbol names table. Attached: winhello_asm.txt: the crash dump and a dissassembly of both the decompressor and the symbol resolver. winhello.zip: source code for the trivial program, obj file, normally linked executable (winhello.exe), crinkler linked executable (winhello_cr.exe)_and the msvcrt.lib as recommended by the crinkler manual. Toolchain used was VS2013 community edition. crinker can be found here: http://crinkler.net/ -- 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.

1 13

[Bug 39815] New: BitComet 1.4 crashed on launch
by wine-bugs＠winehq.org March 31, 2019

March 31, 2019

https://bugs.winehq.org/show_bug.cgi?id=39815 Bug ID: 39815 Summary: BitComet 1.4 crashed on launch Product: Wine-staging Version: 1.8-rc4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: litimetal(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 53151 --> https://bugs.winehq.org/attachment.cgi?id=53151 terminal_output.txt 0. Download BitComet(a BitTorrent client) from http://www.bitcomet.com/ $ sha1sum BitComet_1.40_x86_setup.exe 47ebec6261ec6d06c058fc10260016b889478aa5 BitComet_1.40_x86_setup.exe 1. wine BitComet_1.40_x86_setup.exe You can choose the installer's language 2. cd ~/.wine/drive_c/Program Files/BitComet wine BitComet.exe With wine, it works (mostly well) With wine-staging, it crashed at start up -- 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.

1 9