Same here:
Unhandled exception: page fault on write access to 0x7bf02fe8 in 32-bit
code (0x7df2821a).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:7df2821a ESP:0032ccb0 EBP:0014 EFLAGS:00010202( R- -- I - - - )
EAX:7e58dd20 EBX:7bf02fe8 ECX:7e58dd20 EDX:
The behavior is somewhat different since the latest nvidia-driver update
(340.65-2) hit testing. The segfault is gone and replaced by:
Unhandled exception: page fault on write access to 0x7bf02fe8 in 32-bit
code (0x7df1a21a).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
I also get the SIGUSR1 signal sometimes with wine version
1.6.2-10. This seems to be a timing issue and not a difference
between the wine versions 1.6.2-10 and 1.6.2-11. Please ignore
the remarks about the signal behavior in my last mail.
Sorry for the confusion!
Uwe
--
To UNSUBSCRIBE, email
Hi
This bug is not fixed in wine32 version 1.6.2-17 for me too. Only
wine is affected by the bug, but not wine-development.
On Dec 07, Michael Gilbert wrote:
The original report indicates that the nvidia proprietary driver was
used. Is this true for everyone running into the problem?
I also
Hi
On 12/08/2014 11:05 PM, Uwe Storbeck wrote:
When I understand the package version numbers in Debian correctly
the wine32 package versions 1.6.2-10 and 1.6.2-11 are produced
from the same upstream sources. So the bug has been introduced in
the Debian part of the wine32 package between
Package: wine32
Version: 1.6.2-11
Severity: normal
Dear Maintainer,
Running a win32 program which require OpenGL/Direct3D using wine32
will cause segmentation fault happen. This program may be a game
require Direct3D, a testing OpenGL program which only display OpenGL
information, or dxdiag.exe
6 matches
Mail list logo
