http://bugs.winehq.org/show_bug.cgi?id=13706
Summary: Mankind encounters a page fault on startup Product: Wine Version: 1.0-rc2 Platform: PC-x86-64 URL: http://appdb.winehq.org/objectManager.php?sClass=version &iId=12412 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: boeser.wolff@web.de
Created an attachment (id=13721) --> (http://bugs.winehq.org/attachment.cgi?id=13721) backtrace for pagefault on startup
When trying to launch Mankind version 1.8 "international", it encounters a page fault right on startup.
http://bugs.winehq.org/show_bug.cgi?id=13706
Georg Wolff boeser.wolff@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #1 from Georg Wolff boeser.wolff@web.de 2008-06-12 12:30:51 --- this seems to be fixed in wine "1.0"rc4
http://bugs.winehq.org/show_bug.cgi?id=13706
Michael Karcher wine@mkarcher.dialup.fu-berlin.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine@mkarcher.dialup.fu- | |berlin.de
--- Comment #2 from Michael Karcher wine@mkarcher.dialup.fu-berlin.de 2008-06-13 02:30:26 --- Does not work for me. Current git wine, clean wineprefix, installed Mankind 1.8 International, copied mfc42.dll (Version 6.00.8447) into windows/system32. I get exactly this crash. It seems to be an empty variant where Mankind expects a pointer-containing variant, probably VT_BSTR. md5sum of the installer is 63fc55be3211ba75e4f7e558a8f24d9e, just to make sure we talk about the same version.
http://bugs.winehq.org/show_bug.cgi?id=13706
--- Comment #3 from Michael Karcher wine@mkarcher.dialup.fu-berlin.de 2008-06-13 05:51:44 --- Created an attachment (id=13973) --> (http://bugs.winehq.org/attachment.cgi?id=13973) Possible fix
This patch fixes the crash on startup. I don't know whether this patch is right, and did not check against windows, let alone writing a test case. Thats why I don't submit it yet (except for the 1.0 freeze of course).
http://bugs.winehq.org/show_bug.cgi?id=13706
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|FIXED |
--- Comment #4 from Alexandre Julliard julliard@winehq.org 2008-06-13 05:54:28 --- Not fixed yet.
http://bugs.winehq.org/show_bug.cgi?id=13706
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
http://bugs.winehq.org/show_bug.cgi?id=13706
--- Comment #5 from Michael Karcher wine@mkarcher.dialup.fu-berlin.de 2008-06-13 17:19:45 --- The patch is wrong. It breaks a test that specifically tests for the behaviour the patch changes. The test passes on windows.
The bug that makes Mankind crash nevertheless is probably in shdocvw, as native shdocvw+shlwapi (from XP SP3) makes Mankind run.
http://bugs.winehq.org/show_bug.cgi?id=13706
Michael Karcher wine@mkarcher.dialup.fu-berlin.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #13973|0 |1 is obsolete| |
--- Comment #6 from Michael Karcher wine@mkarcher.dialup.fu-berlin.de 2008-06-14 07:10:39 --- Created an attachment (id=13997) --> (http://bugs.winehq.org/attachment.cgi?id=13997) New fix
This seems to be an application bug. It checks the pointer in the variant against NULL instead of checking the variant type against VT_EMPTY. With native libraries, the whole var_post_data variant structure is filled with zeroes. Native also allocates it on the stack, so I think it just works by accident.
The attached patch fixes the start of Mankind. This kind of bug explains why it is reproducible only by some people: The contents of uninitialized stack variables is highly dependent on compiler version and switches.
http://bugs.winehq.org/show_bug.cgi?id=13706
--- Comment #7 from Austin English austinenglish@gmail.com 2008-12-13 17:32:08 --- Is this still an issue in current (1.1.10) or newer wine?
http://bugs.winehq.org/show_bug.cgi?id=13706
--- Comment #8 from Georg Wolff boeser.wolff@web.de 2008-12-14 15:22:39 --- The fix does help. The launcher can be started. So Id say this fixes it for wine 1.1.10.
http://bugs.winehq.org/show_bug.cgi?id=13706
--- Comment #9 from Austin English austinenglish@gmail.com 2008-12-15 11:26:09 --- That patch is a hack. A proper implementation is welcome.
http://bugs.winehq.org/show_bug.cgi?id=13706
--- Comment #10 from Austin English austinenglish@gmail.com 2009-06-16 14:23:03 --- Is this still an issue in current (1.1.23 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=13706
--- Comment #11 from Georg Wolff boeser.wolff@web.de 2009-06-21 06:03:29 --- Didnt encounter with Wine 1.1.23.
http://bugs.winehq.org/show_bug.cgi?id=13706
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #12 from Austin English austinenglish@gmail.com 2009-06-22 01:24:46 --- (In reply to comment #11)
Didnt encounter with Wine 1.1.23.
Fixed then.
http://bugs.winehq.org/show_bug.cgi?id=13706
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #13 from Alexandre Julliard julliard@winehq.org 2009-07-03 12:19:28 --- Closing bugs fixed in 1.1.25.
http://bugs.winehq.org/show_bug.cgi?id=13706
--- Comment #14 from Michael Karcher wine@mkarcher.dialup.fu-berlin.de 2011-03-30 03:22:53 CDT --- This bug reappeared in later versions of wine (see bug 19643). I believe my patch is the only way to fix that in Wine, although the real cause of this bug is an application relying on undocumented or random behaviour.
-
wine-bugs＠winehq.org