http://bugs.winehq.org/show_bug.cgi?id=18352
Summary: Overgrowth (Lugaru2): Segfault while starting Product: Wine Version: 1.1.20 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: infernux@web.de
Overgrowth¹ is an upcoming game by indie developer Wolfire. Preordering (there's even a way to get it for free² right now!) the game gets you access to weekly alpha releases.
Alpha releases up to A16 worked flawlessly in wine but starting with A17 the game crashes while starting:
$ wine Lugaru2.exe fixme:keyboard:X11DRV_LoadKeyboardLayout L"00000409", 0080: stub! fixme:keyboard:X11DRV_LoadKeyboardLayout L"00000407", 0001: stub! fixme:wgl:X11DRV_wglChoosePixelFormatARB unused pfAttribFList wine: Unhandled exception 0xc000000d at address 0xe960073:0x7814e769 (thread 0009), starting debugger...
A blog post describing changes in A17 can be found here³.
It would be nice if someone could help me debugging this crash further.
[1] http://www.wolfire.com/overgrowth [2] http://blog.wolfire.com/2008/11/preorder-overgrowth-for-free/ [3] http://blog.wolfire.com/2009/03/overgrowth-alpha-17/
http://bugs.winehq.org/show_bug.cgi?id=18352
--- Comment #1 from Michael Monreal infernux@web.de 2009-05-04 15:48:26 --- I was wondering if the crash is caused by the V8 integration. Here's what one of the developers told me: "we only have one v8, the one in chrome, which we use from awesomium". I have already tested that V8 works fine in the standalone Awesomium 1.0 Demo¹ under wine. On the other hand, I can't really tell if V8 integration is even to blame here on my own ;)
[1] http://princeofcode.com/awesomium.php
http://bugs.winehq.org/show_bug.cgi?id=18352
--- Comment #2 from Vitaliy Margolen vitaliy@kievinfo.com 2009-05-04 16:36:17 --- Attach complete terminal output, including the exact command you used to start it.
http://bugs.winehq.org/show_bug.cgi?id=18352
--- Comment #3 from Michael Monreal infernux@web.de 2009-05-04 19:04:52 --- (In reply to comment #2)
Attach complete terminal output, including the exact command you used to start it.
What I posted above *is* the complete output (there's nothing after "starting debugger...") and the command I used is just "wine Lugaru2.exe". I tried running with various DEBUG= settings but it always produces way to much output for me to make any sense of :(
If you suggest a special DEBUG= line or something I will gladly attach the output.
Btw my wine is 1.1.20~winehq0~ubuntu~8.10-0ubuntu1
http://bugs.winehq.org/show_bug.cgi?id=18352
--- Comment #4 from Michael Monreal infernux@web.de 2009-05-05 04:07:24 --- Created an attachment (id=20919) --> (http://bugs.winehq.org/attachment.cgi?id=20919) winedbg output
This is the output when running in winedbg. I wonder how to get a backtrace :/
http://bugs.winehq.org/show_bug.cgi?id=18352
Michael Monreal infernux@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Overgrowth (Lugaru2): |Overgrowth (Lugaru2): |Segfault while starting |Crashes while starting
http://bugs.winehq.org/show_bug.cgi?id=18352
--- Comment #5 from Michael Monreal infernux@web.de 2009-05-05 05:56:47 --- Started to test again using a fresh WINEPREFIX. This revealed that the game needs vcomp.dll (VS2005 OpenMP lib) to run (a16) or crash (a17 and up), I didn't really notice before because it was already installed in my old WINEPREFIX.
This seems to be part of the problem actually... looks like A17 introduced some new threading stuff. How to debug this?
http://bugs.winehq.org/show_bug.cgi?id=18352
Michael Monreal infernux@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #20919|0 |1 is obsolete| |
--- Comment #6 from Michael Monreal infernux@web.de 2009-05-05 08:07:34 --- Created an attachment (id=20923) --> (http://bugs.winehq.org/attachment.cgi?id=20923) Relevant part of debug +all
lol... scratch what I said, I found the problem. For some reason, Overgrowth does not create a file before trying to write to it. This works in windows so I assume there must be a bug in wine.
If I just "touch localcode.txt" before running, everything works fine.
http://bugs.winehq.org/show_bug.cgi?id=18352
--- Comment #7 from Austin English austinenglish@gmail.com 2009-11-19 12:53:31 --- This is your friendly reminder that there has been no bug activity for 6 months. Is this still an issue in current (1.1.33 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=18352
--- Comment #8 from Michael Monreal infernux@web.de 2009-11-22 05:45:21 --- In newer alphas the problem is masked because they actually ship a placeholder localcode.txt now. Feel free to close this bug.
http://bugs.winehq.org/show_bug.cgi?id=18352
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |ABANDONED
--- Comment #9 from Austin English austinenglish@gmail.com 2009-11-22 12:49:00 --- (In reply to comment #8)
In newer alphas the problem is masked because they actually ship a placeholder localcode.txt now. Feel free to close this bug.
There's probably still a bug in wine, but without a download to reproduce, it would be hard to find...marking abandoned.
http://bugs.winehq.org/show_bug.cgi?id=18352
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Dmitry Timoshkov dmitry@codeweavers.com 2009-11-23 06:32:55 --- Closing abandoned.
http://bugs.winehq.org/show_bug.cgi?id=18352
Luke Bratch l_bratch@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |l_bratch@yahoo.co.uk
-
wine-bugs＠winehq.org