https://bugs.winehq.org/show_bug.cgi?id=56357
Bug ID: 56357
Summary: Zero sized writes using WriteProcessMemory succeed on
Windows, but fail on Wine. testcase source
Product: Wine
Version: 9.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: admin(a)sewer56.dev
Distribution: ---
Created attachment 76082
--> https://bugs.winehq.org/attachment.cgi?id=76082
Precompiled sample C program.
[ testcase source ]
Zero sized writes using WriteProcessMemory succeed on Windows, but fail on
Wine.
Build the following program:
```c
#include <windows.h>
#include <stdio.h>
int main() {
// Allocate a buffer in memory
char* buffer = (char*) VirtualAlloc(NULL, 1024, MEM_COMMIT | MEM_RESERVE,
PAGE_READWRITE);
if (buffer == NULL) {
printf("Memory allocation failed\n");
return 1;
}
// Sample data to write (not actually used due to 0-byte length)
const char* data = "Sample data";
SIZE_T writtenBytes = 0;
// Get a handle to the current process
HANDLE processHandle = GetCurrentProcess();
// Attempt to write memory with 0 byte length
BOOL result = WriteProcessMemory(processHandle, buffer, data, 0,
&writtenBytes);
if (result == FALSE) {
printf("WriteProcessMemory failed: %lu\n", GetLastError());
} else {
printf("WriteProcessMemory succeeded, but 0 bytes were written.\n");
}
VirtualFree(buffer, 0, MEM_RELEASE);
return 0;
}
```
Commandline:
```
x86_64-w64-mingw32-gcc write_process_memory.c -o write_process_memory.exe
-lkernel32
```
When running on Linux, this prints `WriteProcessMemory failed: 87`.
When running on Windows, this succeeds `WriteProcessMemory succeeded, but 0
bytes were written`.
Tested on x86_64 Archlinux using latest git version of Wine
(wine-9.2-286-g232b18d820e).
-----------
Extra Notes:
I encountered this bug while unit testing a Rust DLL Injection library against
Wine: https://github.com/OpenByteDev/dll-syringe/pull/19
--
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=56054
Bug ID: 56054
Summary: Microsoft Safety Scanner crashes on exit on
unimplemented function tbs.dll.GetDeviceIDString
Product: Wine
Version: 9.0-rc2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 75710
--> https://bugs.winehq.org/attachment.cgi?id=75710
Terminal output
All you have to do to reproduce the crash is open the program and immediately
close it.
$ sha256sum MSERT.exe
8a885021b8c41fb8578cfa50a0c3a706c6b1b7fb7fd3faddcc48bd8eb7f8f091
--
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=51599
Bug ID: 51599
Summary: cmd.exe incorrectly parses an all-whitespace line
followed by a closing parenthesis
Product: Wine
Version: 6.14
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 70449
--> https://bugs.winehq.org/attachment.cgi?id=70449
Example batch file
The attached batch file works on Windows, but Wine says:
Can't recognize ')' as an internal or external command, or batch script.
Wine's cmd.exe doesn't have a problem with entirely blank lines, but something
about having spaces on the line is tripping it 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.
https://bugs.winehq.org/show_bug.cgi?id=56367
Bug ID: 56367
Summary: Tomb Raider 3 GOG crashes at start
Product: Wine
Version: 9.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: dkk089(a)gmail.com
Distribution: ---
Created attachment 76108
--> https://bugs.winehq.org/attachment.cgi?id=76108
Tomb3.exe backtrace with Wine 9.3
Tomb Raider 3 GOG crashes in Wine 9.3 with the attached backtrace.
Last known working version in AppDB is Wine 4.2. Working upwards from that
identified Wine 5.7 as the last working release, and bisecting between 5.7 and
5.8 identified commit 100ca518055c0e9edb68aa370f15a2768cf2c74f as the cause.
Reverting this commit from current master
(1b32ac45f821ee1fe06a3dc4f903a81a190216c7) makes the game work normally. Tested
with Windows version set to 98, WINEARCH is win32.
This is also reproducible with the demo version available at
https://archive.org/details/TombRaiderIiiAdventuresOfLaraCroftDemo .
--
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=55897
Bug ID: 55897
Summary: cpython 3.12.0 crashes due to unimplemented CopyFile2
Product: Wine
Version: 8.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: tobias-winehq(a)23.gs
Distribution: ---
Newer Python versions (starting with 3.12.0) contain an optimized
implementation of shutil.copy2
(https://devdocs.io/python~3.11/library/shutil#shutil.copy2), which uses
kernel32.CopyFile2 in the background (Implementation:
https://github.com/python/cpython/pull/105086/files#diff-db8ac5932616071392…).
This leads to crashes if this method is used. Unfortunatly, this method is used
by pip in some cases, so a random `wine pip install pysftp` leads to a crash...
To reproduce:
1. Install Python 3.12.0 from https://www.python.org/
2. Run `wine python -c 'import shutil; shutil.copy2("a", "b")'`
--
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=56361
Bug ID: 56361
Summary: Geovision Parashara's Light (PL9.exe) still crashes in
wine
Product: Wine
Version: 9.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yafoce6821(a)giratex.com
Distribution: ---
Separating the bugs, on request from @Vijay Kamuju
continuing from the discussion in Bug56299:
https://bugs.winehq.org/show_bug.cgi?id=56299
Impacted Application: PL9.exe (Parashara's Light 9.0 from Geovision Software)
Bug56299 fixed the imm32.dll required stub.
However, the application still crashes spinning up the wine debugger after the
initial splash screen.
I tried a wmic hack proposed by @Louis Lenders, but unfortunately no matter
what amount I made wmic sleep, the splash screen would stay active by the same
amount, and then it crashes as usual with the wine debugger spinning up.
Bug56299 has some relevant log files.
--
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=55619
Bug ID: 55619
Summary: VOCALOID AI Shared Editor v.6.1.0 crashes with
System.Management.ManagementObject object construction
Product: Wine
Version: 8.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: theboomtnt46(a)gmail.com
Distribution: ---
Created attachment 75156
--> https://bugs.winehq.org/attachment.cgi?id=75156
Crash log
VOCALOID AI Shared Editor v.6.1.0 crashes while initializing.
Logs attached.
wine-8.16 (Staging)
kubuntu linux 23.04
--
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=55268
Bug ID: 55268
Summary: user32:cursoricon - LoadImageA() fails in
test_monochrome_icon() on Windows 8+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:cursoricon - LoadImageA() fails in test_monochrome_icon() on Windows 8+:
cursoricon.c:2853: monochrome, bitmap info
cursoricon.c:2917: Test failed: LoadImage() failed with 0.
See https://test.winehq.org/data/patterns.html#user32:cursoricon
The call below has been failing systematically on Windows 8+ for more than 8
months:
handle = LoadImageA(NULL, "icon.ico", IMAGE_ICON, 0, 0,
LR_LOADFROMFILE);
ok(handle != NULL ||
broken(use_core_info && handle == NULL), /* Win 8, 10 */
"LoadImage() failed with %lu.\n", GetLastError());
So on Windows 8+ we expect to get NULL only if use_core_info is true but in
fact we get NULL even if it is false. That makes this test pretty pointless.
--
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=55724
Bug ID: 55724
Summary: mfmediaengine:mfmediaengine sometimes gets a
threadpool assertion in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
mfmediaengine:mfmediaengine sometimes gets a threadpool assertion in Wine:
mfmediaengine.c:147: created L"C:\\users\\winetest\\Temp\\rgb32frame.bmp"
Unhandled exception: assertion failed in 32-bit code (0x7bc24980).
[...]
Backtrace:
=>0 0x7bc24980 raise_status+0x30(status=0x80000101, rec=00000000)
[/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/exception.c:201]
in ntdll (0x0499fd20)
1 0x7bc249a9 in ntdll (+0x249a9) (0x0499fd40)
2 0x7bc24d7b debugstr_a(str="!object->num_running_callbacks",
file="../wine/dlls/ntdll/threadpool.c", line=0x84c)
[/home/winetest/tools/testbot/var/wine-win32/../wine/include/wine/debug.h:507]
in ntdll (0x0499fd70)
3 0x7bc24d7b _assert+0x1b(str="!object->num_running_callbacks",
file="../wine/dlls/ntdll/threadpool.c", line=0x84c)
[/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/exception.c:627]
in ntdll (0x0499fd70)
4 0x7bc5cb88 tp_object_release+0x198(object=<register EBX not accessible in
this frame>)
[/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/threadpool.c:2123]
in ntdll (0x0499fdb0)
5 0x7bc60645 TpReleaseWait+0x35(wait=013E32C8)
[/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/threadpool.c:2117]
in ntdll (0x0499fde0)
6 0x6b141a08 work_item_Release+0x6e(iface=<internal error>)
[/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/rtworkq/queue.c:567]
in rtworkq (0x0499fe00)
7 0x6b141a08 work_item_Release+0x88(iface=009E7EA0)
[/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/rtworkq/queue.c:580]
in rtworkq (0x0499fe00)
8 0x6b142f9a waiting_item_cancelable_callback+0x2a(instance=0499FE90,
context=009E7EA0, wait=013E32C8, wait_result=0)
[/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/rtworkq/queue.c:769]
in rtworkq (0x0499fe30)
9 0x7bc5d55a tp_object_execute+0x14a(object=<register EDI not accessible in
this frame>, wait_thread=<register EBX not accessible in this frame>)
[/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/threadpool.c:2248]
in ntdll (0x0499fed0)
10 0x7bc5daf0 threadpool_worker_proc+0x100(param=00249938)
[/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/threadpool.c:2356]
in ntdll (0x0499ff30)
11 0x7b829770 in kernel32 (+0x29770) (0x0499ff48)
12 0x7bc5a557 in ntdll (+0x5a557) (0x0499ff5c)
13 0x7bc5ada0 RtlCreateUserThread(entry=7BC5D9F0, arg=00249938)
[/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/thread.c:315]
in ntdll (0x0499ffec)
0x7bc24980 raise_status+0x30
[/home/winetest/tools/testbot/var/wine-win32/../wine/dlls/ntdll/exception.c:201]
in ntdll: sub $0x04, %esp
201 for (;;) RtlRaiseException( &ExceptionRec ); /* never returns */
See https://test.winehq.org/data/patterns.html#mfmediaengine:mfmediaengine
There are only two instances so far but both are only days old and the GitLab
CI is impacted too:
2023-10-04 MR!4012 (test-linux-32)
2023-10-02 debian11-fr-32
--
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.