https://bugs.winehq.org/show_bug.cgi?id=49529
Bug ID: 49529 Summary: 5.12 regression: Wine segfaults if the +heap debug channel is enabled Product: Wine Version: 5.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: subgraph93@gmail.com Distribution: ---
Created attachment 67662 --> https://bugs.winehq.org/attachment.cgi?id=67662 Contains the 2 log files; the commands to produce them are provided in the report
OS: Ubuntu 20.04
Found the bug in the Wine 5.12-devel package from winehq. Did not happen in 5.11-devel.
If WINEDEBUG=+heap (or warn+heap) is used, Wine crashes immediately after trying to start any program. The segfault is the only line that is output, apparently the program itself doesn't even get to start. After I upgraded from 5.11, the first thing I did in one of my prefixes was to start a program with +heap debugging enabled (it crashed otherwise; though that's a separate issue). The "updating your prefix" message didn't even get to appear.
Bisection points to this commit:
commit 8a169390c9ef4d8a43b604558c4194a052473c0c Author: Alexandre Julliard julliard@winehq.org Date: Tue Jun 30 12:01:37 2020 +0200
ntdll: Build with msvcrt.
Signed-off-by: Alexandre Julliard julliard@winehq.org
--------
I tried poking around the issue with a clean prefix on 5.12-devel. Attached logs for commands: 1) WINEDEBUG=+all wine winecfg.exe 2) valgrind --trace-children=yes wine xcopy.exe (sorry for that second one, I'm new to Wine debugging, and that was the first time I did anything like that; not sure it's even relevant)
As of the moment of submitting this bug report, new patches committed to Git after the release of 5.12 do not fix the issue.