http://bugs.winehq.com/show_bug.cgi?id=1514
Summary: ddraw regression bug
Product: Wine
Version: CVS
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: hatky(a)users.sf.net
CC: fenix@club-internet.fr,lionel.ulmer@free.fr
As I said in wine-devel
(http://www.winehq.org/hypermail/wine-devel/2003/06/0232.html), since the lasts to
burst of commits (in the middle of alexanders vacation) some games give out a
ddraw crash as:
Unhandled exception: page fault on read access to 0x00000004 in 32-bit code
(0x40ac0ad3).
In 32-bit mode.
0x40ac0ad3 (HAL_DirectDrawSurface_Construct+0xd3 [hal.c:127] in ddraw.dll.so):
cmpb $0x0,0x4(%eax)
127 if (!(dd_gbl->dwFlags & DDRAWI_MODECHANGED)) {
a trace will be attached...
--
Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.com/show_bug.cgi?id=1513
Summary: WM_HELP sent at wrong time; needs to support 0x4d
message
Product: Wine
Version: 20030508
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: wine-user
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: jr-winebugs(a)quo.to
For consistency with Windows (95 and 2000, at least), when you press F1 on a
control, it should not immediately send a WM_HELP message to the control as it
does now (see process_cooked_keyboard_message() in windows/message.c). Rather,
it should _post_ an 0x4d message to itself with wParam=0 and lParam=0.
DefWindowProc should then handle 0x4d by sending a WM_HELP message.
0x4d seems to be undocumented but is still useful to third-party apps: they can
swallow 0x4d messages in their message loop to prevent WM_HELP messages from
being sent.
--
Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.com/show_bug.cgi?id=1511
------- Additional Comments From mike(a)theoretic.com 2003-06-06 09:25 -------
We know about the compile problem - I suggest you subscribe to wine-devel.
Please send your patch to wine-patches, the submission process is documented on
winehq.com (we use email rather than bugzilla for patches as there are so many).
It's easier to review there.
many thanks for the patch! -mike
--
Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.com/show_bug.cgi?id=1511
------- Additional Comments From kellyleahy(a)swbell.net 2003-05-06 10:43 -------
Created an attachment (id=279)
--> (http://bugs.winehq.com/attachment.cgi?id=279&action=view)
Proposed patch - please test!
I'm unable to adequately test this on my machine, since I've managed to really
@#$!-up my X and my wine config. Going to RH9 this afternoon.
BTW, there is a compile problem with the version of X included in RH8 and the
openGL stuff in the current wine source.
--
Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.com/show_bug.cgi?id=1511
------- Additional Comments From kellyleahy(a)swbell.net 2003-05-06 09:02 -------
I've got a patch for this... I just can't get some other stuff to work on my
machine right now, so I want to make sure it's not in my patch before
submitting.
--
Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.com/show_bug.cgi?id=1511
mike(a)theoretic.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
------- Additional Comments From mike(a)theoretic.com 2003-05-06 05:16 -------
Confirming. Patches welcome.
--
Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.com/show_bug.cgi?id=1480
mike(a)theoretic.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From mike(a)theoretic.com 2003-05-06 05:11 -------
The lack of the FDI cabinet functions is a known problem, Greg said he'd hack on
this. Until then running wine like this:
wine --dll cabinet=n foo.exe
may work better (obviously you'll need a native cabinet.dll from somewhere).
The other problem is a dupe of 1456, I'll mark this bug as such. If you want to
open another bug for the cabinet FDI* functions go ahead, but patches are more
useful :)
*** This bug has been marked as a duplicate of 1456 ***
--
Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.com/show_bug.cgi?id=1512
Summary: Segmentation fault. Wine failed with return code 139
Product: Wine
Version: 20030508
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P1
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: jagt28(a)latinmail.com
Hello, when I am trying to run any windows aplication, I got the followign error:
/usr/bin/wine: line 468: 1456 Segmentation fault $WINEBIN/$WINE_BIN_NAME
$DASH "$@"
Wine failed with return code 139
Thank you for your help.
Regards,
Jose Antonio
--
Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.