https://bugs.winehq.org/show_bug.cgi?id=51052
Bug ID: 51052
Summary: 6.4 regression: 32-bit Cheat Engine attaching its
debugger leads to the target process crashing
Product: Wine
Version: 6.4
Hardware: x86-64
URL: https://cheatengine.org/downloads.php
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: subgraph93(a)gmail.com
Regression SHA1: af74bd31229e0f065448253b248ec0cb3b51af26
Distribution: Ubuntu
Steps to reproduce:
1) Install Cheat Engine (version 7.2 is affected, so is 7.1).
2) Start up cheatengine-i386.exe.
3) In the same prefix, start up the target process. No other software is
needed, because the issue can be reproduced with CE tutorials. To start up the
tutorial, open the "Help" dropdown menu and click the "Cheat Engine Tutorial"
entry.
4) Open the process selection window: File > Open Process; or just click the
flashing icon that shows the computer display with a magnifying glass.
5) In the "Applications" view (it is probably default), there should be an
entry for Cheat Engine itself, and one for "Tutorial-i386". Select the latter
entry, then click "Attach debugger to process", then click "Yes" in the
confirmation modal.
6) When the debugger attaches (should be near-instant for release builds, but
unoptimized builds can take about a minute), the process selection window will
close. At this point, the target process may crash already, but in some cases
it may still work. If the tutorial window still displays, switching focus to it
should cause the crash. In some cases, the target process crashes before this
happens, and Cheat Engine gives a "failed to attach debugger" error instead.
Logs almost always have the following entry (thread ID and the address may
vary):
013c:err:seh:NtRaiseException Unhandled exception code c000008f flags 0 addr
0xf7b80644
In one case (on a dirty prefix, which may or may not matter; the issue
otherwise still happens on a clean prefix), the error code was not c000008f,
but c00002b5. In some cases as well, in addition to the above error and
immediately before it, the following is output:
01d0:fixme:seh:fpe_handler untested SIMD exception: 0x6. Might not work
correctly
I didn't notice other major differences in console logs compared to working
Wine versions, so I didn't attach complete terminal outputs.
Regression testing (which I hope I did correctly) points to:
commit af74bd31229e0f065448253b248ec0cb3b51af26
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Tue Mar 2 18:52:44 2021 +0100
ntdll: Use syscall dispatcher to restore context in NtSetContextThread.
Signed-off-by: Jacek Caban <jacek(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
Other notes:
1) Ubuntu 20.10
2) Wine 6.7 (devel and staging) are still affected.
3) 64-bit Cheat Engine crashed neither 64-bit nor 32-bit target processes,
though it has issues working with 32-bit target processes.
4) This can be reproduced with most, but not all target processes. I think
targeting a 64-bit process doesn't cause the issue, though I wouldn't expect
debugging to work anyway with 32-bit CE. For example of a process that didn't
crash, I couldn't crash winecfg. My testing seems to indicate that the behavior
of a process is consistent in terms of whether or not it crashes, how it
crashes, and what terminal messages are output; however, different processes
may have slightly different behavior.
--
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=49935
Bug ID: 49935
Summary: mismatch behavior in API function GetOpenFileName
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comdlg32
Assignee: wine-bugs(a)winehq.org
Reporter: ch.panel(a)free.fr
Distribution: ---
GetOpenFileName with filter show all files instead of filtering files : ex:
("PDF files|*.PDF" as filter show not only PDF files. We have to validate the
dialog for the filter to oper.
--
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=46960
Bug ID: 46960
Summary: Mono's interactive C# shell crashes when typing a
character
Product: Wine
Version: 4.5
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Distribution: ---
Mono ships with an interactive C# interpreter, located at
lib/mono/4.5/csharp.exe. This can be run directly from inside a Wine Mono
install.
It crashes with an ArgumentOutOfRangeException the first time a character is
typed.
System.ArgumentOutOfRangeException: Console key values must be between 0 and
255 inclusive.
Parameter name: key
at System.ConsoleKeyInfo..ctor (System.Char keyChar, System.ConsoleKey key,
System.Boolean shift, System.Boolean alt, System.Boolean control) [0x0000c] in
<72b294be54bc4854bce603b664bafd63>:0
at System.WindowsConsoleDriver.ReadKey (System.Boolean intercept) [0x00079]
in <72b294be54bc4854bce603b664bafd63>:0
--
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=28393
Summary: WiX light can't find files in deeply-nested
directories
Product: Wine
Version: 1.3.28
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sam(a)robots.org.uk
Created an attachment (id=36407)
--> (http://bugs.winehq.org/attachment.cgi?id=36407)
depth.tar
The attached test case fails to run under Wine with the following error:
Z:\home\sam\src\wix-test\depth\A.wxs(8) : error LGHT0103 : The system cannot
find the file
'Z:\home\sam\src\wix-test\depth\A\AOL\Aachen\Aaliyah\Aaron\Abbas\Abbasid\Abbott\Abby\Abdul\Abe\Abel\Abelard\Abelson\Aberdeen\Abernathy\Abidjan\Abigail\Abilene\Abner\Abraham\Abram\Abrams\Absalom\Abuja\Abyssinia\readme.txt'.
This happens with both Mono 2.10.5 and Microsoft .NET 2.0. Unpack the test case
and run 'make' and it should create a fresh WINEPREFIX in which it will install
the test pre-requisites before running the test itself.
On a Windows 7 machine, light is able to correctly build B.msi.
--
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=50209
Bug ID: 50209
Summary: S.T.A.L.K.E.R.: Call of Pripyat needs
D3DX10CreateTextureFromMemory implementation
Product: Wine
Version: 5.22
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: directx-d3d-util
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Enhanced full dynamic lighting (DX10)
fixme:d3dx:D3DX10CreateTextureFromMemory device 00196A3C, src_data 08E05427,
src_data_size 65664, loadinfo 0031D09C, pump 00000000, texture 0031D098,
hresult 00000000, stub!
wine-5.22-195-gcbca9f847f6
--
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=27133
Summary: WiX 3.5 generates broken MSI files when 2 files of
identical size are added to the same installer
Product: Wine
Version: 1.3.19
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sam(a)robots.org.uk
Created an attachment (id=34643)
--> (http://bugs.winehq.org/attachment.cgi?id=34643)
test case
The attached test case will generate an installer that installs two files to
'ProgramFilesFolder\duplicate file test'.
when run on Windows, the installer works fine. When run under Wine, the
installer installs the contents of file1.txt into file2.txt.
This only happens with Wix 3.5. This version added a feature called "smart
cabbing" that detects duplicate files in an installer and only embeds one copy.
This may be going haywire when run under Wine.
To run the test case, you will need Mono
<http://ftp.novell.com/pub/mono/archive/2.10.2/windows-installer/5/mono-2.10…>
and WiX 3.5 <http://wix.codeplex.com/releases/view/60102#DownloadId=204417>.
You
will need to put WiX's tools in Wine's PATH, or modify build.sh to give the
full path to the WiX tools when it invokes light and candle.
--
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=21259
Summary: Visual C++ 2005 Trial build hangs on first run after a
reboot
Product: Wine
Version: 1.1.35
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, testcase
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Created an attachment (id=25560)
--> (http://bugs.winehq.org/attachment.cgi?id=25560)
Shell script to download an example project, install Visual C++ 2005 trial, and
build the project.
Visual C++ can build projects from the commandline with
devenv projectname.sln /build Debug
but oddly, the first time you try this on Wine, it hangs.
^C and rerunning fixes it. After the ^C, you can see
mspdbsrv.exe -start -spawn
running, so evidently the first run spawned the
pdb service but then stumbled trying to connect to it;
the second run connected fine.
I'll attach a canned script that reproduces the problem from scratch.
--
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=49395
Bug ID: 49395
Summary: Altium Designer 20 crashes with E_NOINTERFACE
apparently from CreateDxgiSurfaceRenderTarget
Product: Wine
Version: 5.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: me+wine(a)shane.sh
Distribution: ---
Created attachment 67463
--> https://bugs.winehq.org/attachment.cgi?id=67463
Crash log from Altium
I'm trying to get Altium Designer 20 running in wine. I'm using wine-staging
5.10 with the msxml6 and dotnet461 winetricks. The winetricks are necessary to
get the application to start, and wine-staging because it includes a fix for
https://bugs.winehq.org/show_bug.cgi?id=46568. I'm also using the patch from
https://bugs.winehq.org/show_bug.cgi?id=49379.
The crash log from Altium indicates says that the C# function
SharpDX.Direct2D1.Factory.CreateDxgiSurfaceRenderTarget received a HRESULT of
E_NOINTERFACE. I don't understand how FFI works in C#, but SharpDX is
open-source and
https://github.com/sharpdx/SharpDX/blob/master/Source/SharpDX.Direct2D1/Map…
and
https://github.com/sharpdx/SharpDX/blob/master/Source/SharpDX.Direct2D1/Ren…
seem like relevant parts of the code. Presumably though this just gets mapped
to d2d_factory_CreateDxgiSurfaceRenderTarget from dlls/d2d1/factory.c.
Also relevant is that the following shows up in STDERR when running wine at the
same time as the crash:
00c4:fixme:d2d:d2d_d3d_create_render_target Ignoring render target usage 0x2.
And d2d_d3d_create_render_target is indeed called at the end of
d2d_factory_CreateDxgiSurfaceRenderTarget, so it seems to get at least that
far.
But from reading the source of d2d_d3d_create_render_target, I don't see how it
could ever return E_NOINTERFACE without at least printing some additional
warnings, but I don't see any.
Any help would be greatly appreciated!
--
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.