http://bugs.winehq.org/show_bug.cgi?id=6550
Summary: Segfault (coredump)
Product: Wine
Version: 0.9.24.
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P5
Component: wine-programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: geoffrey.mathieu(a)free.fr
After compiling wine on AMD64 with ubuntu, i have this message when i launch
wine : Erreur de segmentation (core dumped)
No error in compilation
LDFLAGS="-L/lib32 -L/usr/lib32 -Wl,-rpath,/lib32 -Wl,-rpath,/usr/lib32"
./configure
make depend
make all
sudo make install
--
Configure bugmail: http://bugs.winehq.org/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.org/show_bug.cgi?id=6547
------- Additional Comments From ajackso2(a)connect.carleton.ca 2006-29-10 04:19 -------
The hangup is definitely occurring in wine-preloader. Each time I attempt to
run a Wine application, after I ctrl-c the hung application a wine-preloader
process is left behind which will only die if I kill -9 it (just kill'ing it
leaves it [defunct]). All of these processes turn out to be stopped at the
exact same (kernel space?) address when I attach gdb to them.
--
Configure bugmail: http://bugs.winehq.org/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.org/show_bug.cgi?id=6364
------- Additional Comments From alex(a)thehandofagony.com 2006-29-10 04:16 -------
If you get that message, Heroes V is not correctly installed; its registry
keys are missing. Does it show up if you run 'wine uninstaller'?
--
Configure bugmail: http://bugs.winehq.org/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.org/show_bug.cgi?id=6082
alex(a)thehandofagony.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alex(a)thehandofagony.com
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Keywords| |download
Version|CVS |0.9.24.
------- Additional Comments From alex(a)thehandofagony.com 2006-29-10 04:10 -------
In Wine 0.9.24, the actual gameplay starts, but the window is still in the
upper left corner of the screen, with the top of it being outside the desktop.
--
Configure bugmail: http://bugs.winehq.org/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.org/show_bug.cgi?id=6547
------- Additional Comments From ajackso2(a)connect.carleton.ca 2006-29-10 04:08 -------
Every Wine-related process appears to be stopped at "0xffffe405 in ?? ()" Isn't
that a (Linux) kernel space address...? I don't have kernel-debuginfo
installed; please tell me if I'm mistaken so I can spare myself the fairly
enormous download.
--
Configure bugmail: http://bugs.winehq.org/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.org/show_bug.cgi?id=3312
------- Additional Comments From dmitry(a)codeweavers.com 2006-29-10 03:54 -------
Becuase for instance I've fixed the bugs in Gnome to properly handle
fullscreening requests from Wine.
Or, again, at least some investigation should be done to see what is going on.
Until we know why this happens we can't do anything to improve it.
--
Configure bugmail: http://bugs.winehq.org/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.org/show_bug.cgi?id=3312
------- Additional Comments From rush(a)u.one.pl 2006-29-10 03:47 -------
Why do the WMs should be fixed if it's wine specific ? Read: Any native Linux
fullscreen apps work just fine, at least for me.
--
Configure bugmail: http://bugs.winehq.org/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.org/show_bug.cgi?id=6547
------- Additional Comments From julliard(a)winehq.com 2006-29-10 03:37 -------
If you see the hang with winecfg or notepad then there should only be one thread
running. Otherwise a 'bt all' will show a backtrace for all the threads, you can
then see which one is inside an X11 call.
--
Configure bugmail: http://bugs.winehq.org/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.org/show_bug.cgi?id=5503
------- Additional Comments From Ronny.Standtke(a)gmx.net 2006-29-10 03:21 -------
I used your patch against 0.9.24. winhelp doesn't crash anymore but the help
is still unuseable (i.e. layout is broken, following links doesn't work, ...)
--
Configure bugmail: http://bugs.winehq.org/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.org/show_bug.cgi?id=6547
------- Additional Comments From ajackso2(a)connect.carleton.ca 2006-29-10 03:10 -------
How do I do that? I assume that I use winedbg, but how do I identify the thread
which is hung up? I'm semi-familiar with gdb on Un*x but I have no experience
with winedbg and no experience debugging (or programming really) in Windows-land
either.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.