http://bugs.winehq.org/show_bug.cgi?id=17497
Summary: Xfire crashes with latest version (1.104) Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: nwarrenfl@gmail.com
Xfire was running fine, but since version 1.104 it doesn't work anymore!
The Wine output shows no error or important message, so it is not really relevant. But Xfire shows a window to send a bug report, and it seems to be this error: C0000005. This is an access violation error.
As i would like to see this fixed, you can ask me to make other logs with other Wine debug channels and i hope devs will find a solution! :D
I've attached the Wine output and the Xfire log.
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #1 from Warren Dumortier nwarrenfl@gmail.com 2009-02-21 15:21:22 --- Created an attachment (id=19597) --> (http://bugs.winehq.org/attachment.cgi?id=19597) Wine output when launching Xfire
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #2 from Warren Dumortier nwarrenfl@gmail.com 2009-02-21 15:21:49 --- Created an attachment (id=19598) --> (http://bugs.winehq.org/attachment.cgi?id=19598) Xfire debug log when launching Xfire
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #3 from Jeff Zaroyko jeffz@jeffz.name 2009-02-21 22:25:44 --- Where are the results of your regression test?
The bug reporting instructions ask you to do this. http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #4 from Warren Dumortier nwarrenfl@gmail.com 2009-02-22 01:44:01 --- Is this really a regression? It seems to be a Xfire regression, as it stopped working after updating Xfire and not Wine.
http://bugs.winehq.org/show_bug.cgi?id=17497
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
--- Comment #5 from Jeff Zaroyko jeffz@jeffz.name 2009-02-22 02:39:46 --- (In reply to comment #4)
Is this really a regression? It seems to be a Xfire regression, as it stopped working after updating Xfire and not Wine.
ok, I misunderstood your bug report title
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #6 from Warren Dumortier nwarrenfl@gmail.com 2009-02-22 14:34:03 --- What is needed to debug this bug?
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #7 from Warren Dumortier nwarrenfl@gmail.com 2009-03-19 15:43:15 --- It might be the wrong place to discuss this, but Xfire worked for me on Zenwalk, but i returned to Ubuntu, and here it crashes with the same version, can this be an Ubuntu-specific problem, and if possible, how to be sure?
http://bugs.winehq.org/show_bug.cgi?id=17497
Justin Soulia rockinup1231@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rockinup1231@gmail.com
--- Comment #8 from Justin Soulia rockinup1231@gmail.com 2009-04-08 22:57:43 --- (In reply to comment #7)
It might be the wrong place to discuss this, but Xfire worked for me on Zenwalk, but i returned to Ubuntu, and here it crashes with the same version, can this be an Ubuntu-specific problem, and if possible, how to be sure?
Well, I've tested recent xfire releases that have this problem, once on Kubuntu 8.04 and once on Xubuntu 8.04 under the same cases with a recent version of wine, and in both cases this bug occurs. The program itself works fine, until you need to click a button or element of any window of the program.
I tried Xfire 1.105 with Wine 1.1.3 and got the same result as with Wine 1.1.18 using Xfire 1.106.
It looks like an issue with Ubuntu...
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #9 from Warren Dumortier nwarrenfl@gmail.com 2009-04-09 04:46:20 --- Or maybe not...
I was developing my program and it worked well on Intrepid, but crashed on Jaunty and it seems the security has been changed on Jaunty. There is maybe a bug in Wine, that worked well earlier, but due to the security, will crash on Jaunty now.
My problem was a buffer overflow, no idea what the problem is here.
http://bugs.winehq.org/show_bug.cgi?id=17497
Andrey Turkin andrey.turkin@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |andrey.turkin@gmail.com
--- Comment #10 from Andrey Turkin andrey.turkin@gmail.com 2009-10-21 08:56:40 --- Xfire hooks quite a few functions with 5 bytes long "jmpl" instruction. To do this, it copies instructions from function start to its own memory and sets up a trampoline back into a function; the problem is that Xfire doesn't recognize relative"call" instructions so when such instruction is copied and executed at different address it will lead to invalid code being executed. Unfortunately, since Wine dlls are usually compiled with -fPIC option, function prologue can sometimes look like:
func+0: push ebp func+1: mov ebp, esp func+3: push ebx func+4: call thunk
which, when hooked, will lead to a crash.
Technically this is Xfire hook bug (it should recognize instructions that depends on their address and fix/emulate them accordingly) but on Windows this bug is never triggered.
Stefan Dösinger recently submitted set of patches into Wine and GCC which force GCC to emit specific prologue for some functions hooked by Xfire. So compile very latest GCC (from CVS) and use it to compile Wine (from GIT) and that should fix this bug.
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #11 from Warren Dumortier nwarrenfl@gmail.com 2009-10-22 05:33:22 --- After compiling Wine with the latest gcc and binutils versions Xfire works again. It runs without any problems, if the ms_hook_prologue is indeed enabled (is by default i see if you use latest gcc from CVS)
As this bug is fixed in Wine itself, i presume it's time to fix it? Thanks for fixing it ;)
http://bugs.winehq.org/show_bug.cgi?id=17497
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #12 from Austin English austinenglish@gmail.com 2009-10-22 12:21:03 --- Fixed. Great work Stefan!
http://bugs.winehq.org/show_bug.cgi?id=17497
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #13 from Alexandre Julliard julliard@winehq.org 2009-10-23 13:18:51 --- Closing bugs fixed in 1.1.32.
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #14 from Justin Soulia rockinup1231@gmail.com 2009-10-25 11:40:37 --- I hate to rain on everybody's parade but, Xfire still crashes in this fashion with Wine 1.1.32 using a fresh wineprefix on Ubuntu 9.04 x86_64. Perhaps this is a problem with Ubuntu, but I can't be sure. I'm using Xfire version 1.116. I'll attach the terminal output I get (which is waiting for Xfire to detect games, and trying to exit the first run register window, which leads to the crash).
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #15 from Andrey Turkin andrey.turkin@gmail.com 2009-10-25 11:44:57 --- (In reply to comment #14)
I hate to rain on everybody's parade but, Xfire still crashes in this fashion with Wine 1.1.32 using a fresh wineprefix on Ubuntu 9.04 x86_64.
Did you self-compiled Wine with bleeding-edge gcc from cvs repo (did check for ms_hook_prologue during configure positive)?
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #16 from Justin Soulia rockinup1231@gmail.com 2009-10-25 11:45:12 --- Created an attachment (id=24345) --> (http://bugs.winehq.org/attachment.cgi?id=24345) Wine terminal output upon crash - Wine 1.1.32
Crashes out with a segmentation fault. Again, probably another issue related to Ubuntu.
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #17 from Justin Soulia rockinup1231@gmail.com 2009-10-25 11:46:12 --- Oops late comment. No I did not, I used the package from the wine repository.
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #18 from Warren Dumortier nwarrenfl@gmail.com 2009-10-25 13:43:52 --- People, please read it first! It is explained on the appdb test data i've submitted.
It is fixed in WINE, but not fixed in MOST DISTROS. To have it working again Wine needs to be compiled with latest gcc and binutils, who are not out yet (no stable version out).
When distros will ship those future versions, it will work again.
However if someone has problems or wants a pre-compiled Wine to test, simply contact me, i'll be glad to help.
http://bugs.winehq.org/show_bug.cgi?id=17497
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sanders3cg@yahoo.com
--- Comment #19 from Jeff Zaroyko jeffz@jeffz.name 2009-10-25 22:24:34 --- *** Bug 20468 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=17497
Kyle Sanderson kyle.leet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle.leet@gmail.com
--- Comment #20 from Kyle Sanderson kyle.leet@gmail.com 2009-10-29 18:05:55 --- This is NOT fixed wine-1.1.32-213-g1be9903.
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #21 from Justin Soulia rockinup1231@gmail.com 2009-10-29 19:07:35 --- I can confirm it's working for me now in Wine-1.1.32 compiling with the latest gcc as instructed on here.
If anyone needs xfire to work correctly, I've put a link up for a download to a wine .deb package I built that will run Xfire correctly, on the appdb entry for the latest version of xfire. I'm going to continue building these packages til it's unnecessary.
It's definately fixed, though. I was wrong ^_^.
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #22 from Kyle Sanderson kyle.leet@gmail.com 2009-10-29 20:54:12 --- (In reply to comment #21)
I can confirm it's working for me now in Wine-1.1.32 compiling with the latest gcc as instructed on here.
If anyone needs xfire to work correctly, I've put a link up for a download to a wine .deb package I built that will run Xfire correctly, on the appdb entry for the latest version of xfire. I'm going to continue building these packages til it's unnecessary.
It's definately fixed, though. I was wrong ^_^.
I'm sorry man, it most definately isn't. Although Xfire now allows you to use the main menu such as Tools > Options, it crashes almost instantly when you try to talk to someone (Click once on their name, or twice), or click on the servers button on the left. See the log file below.
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #23 from Kyle Sanderson kyle.leet@gmail.com 2009-10-29 20:55:38 --- Created an attachment (id=24438) --> (http://bugs.winehq.org/attachment.cgi?id=24438) Xfire Crashing when attempting to do absolutely anything.
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #24 from Andrew Nguyen arethusa26@gmail.com 2009-10-29 21:00:55 --- If the problem occurs with Xfire run on Wine appropriately built with SVN gcc, then the new crash behavior should be a separate bug.
http://bugs.winehq.org/show_bug.cgi?id=17497
Kyle Sanderson kyle.leet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever Confirmed|0 |1
--- Comment #25 from Kyle Sanderson kyle.leet@gmail.com 2009-10-29 21:11:34 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #26 from Kyle Sanderson kyle.leet@gmail.com 2009-10-29 22:34:53 --- (In reply to comment #24)
If the problem occurs with Xfire run on Wine appropriately built with SVN gcc, then the new crash behavior should be a separate bug.
This happened regardless before, I'm assuming with what was posted above was only directed at accessing Menus? That's the only difference between what was wrong then and what is wrong now. As far as I know, this is still the same issue at hand just improperly fixed.
System Specs: [josh@Jacko ~]$ gcc --version gcc (GCC) 4.5.0 20091029 (experimental) Copyright (C) 2009 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [josh@Jacko ~]$ wine --version wine-1.1.32-213-g1be9903 [josh@Jacko ~]$ uname -r 2.6.31-ARCH
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #27 from Justin Soulia rockinup1231@gmail.com 2009-10-29 22:40:17 --- Perhaps it's a problem brought on by something in your distro? What distro are you running?
On Ubuntu 9.10 I encounter no issues of the sort whatsoever with Xfire. I haven't encountered a crash accessing anything in the menus, chatting, or anything of the sort.
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #28 from Kyle Sanderson kyle.leet@gmail.com 2009-10-29 23:11:05 --- (In reply to comment #27)
Perhaps it's a problem brought on by something in your distro? What distro are you running?
On Ubuntu 9.10 I encounter no issues of the sort whatsoever with Xfire. I haven't encountered a crash accessing anything in the menus, chatting, or anything of the sort.
Hmm, interesting.
I'm running Arch Linux (Kernel:2.6.31-ARCH) Ubuntu is too bloated with junk for my tastes.
Any chance this could be reopened?
http://bugs.winehq.org/show_bug.cgi?id=17497
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #24438|application/octet-stream |text/plain mime type| | Attachment #24438|Xfire.log |Xfire.txt filename| |
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #29 from Jeff Zaroyko jeffz@jeffz.name 2009-10-29 23:55:03 --- (In reply to comment #28)
Any chance this could be reopened?
I don't see a crash in your attachment. Terminal output is different to the op's. Test in a clean prefix with gecko installed before running xfire.
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #30 from Vitaliy Margolen vitaliy@kievinfo.com 2009-10-30 00:46:58 --- (In reply to comment #28)
Any chance this could be reopened?
Probably not. This bug is fixed. Please open a new one. There are could be numerous reasons for an app to crash. Don't pile them all into one bug.
http://bugs.winehq.org/show_bug.cgi?id=17497
--- Comment #31 from Warren Dumortier nwarrenfl@gmail.com 2009-10-30 06:37:58 --- Please read my comment (#11) and check if you did like i described. Also check the ms_hook_prologue gets enabled.
http://bugs.winehq.org/show_bug.cgi?id=17497
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rabidweezle@gmail.com
--- Comment #32 from Vitaliy Margolen vitaliy@kievinfo.com 2010-07-08 18:19:42 --- *** Bug 23553 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=17497
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Enrico_m@gmx.de
--- Comment #33 from Vitaliy Margolen vitaliy@kievinfo.com 2010-07-08 18:20:34 --- *** Bug 22032 has been marked as a duplicate of this bug. ***
-
wine-bugs＠winehq.org