Bug 5291

Summary: X server segfaults when starting a vmware machine with vmplayer
Product: xorg Reporter: Mikael Magnusson <mikachu>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: high    
Version: 6.99.99.903 (7.0 RC3)   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 1690    

Description Mikael Magnusson 2005-12-09 06:44:26 UTC 
When running vmplayer on a virtual machine, X segfaults when the machine is
about to start. After much fiddling i managed to get the following backtrace
without getting locked in X:

#0  0x080d13bf in MiscExtGetMouseSettings (mouse=0xaf941a58,
    devname=0xaf941a5c) at xf86MiscExt.c:172
#1  0xa7e171af in ProcXF86MiscGetMouseSettings (client=0x86f4b88)
    at xf86misc.c:277
#2  0xa7e182f4 in ProcXF86MiscDispatch (client=0x86f4b88) at xf86misc.c:645
#3  0x08085906 in Dispatch () at dispatch.c:459
#4  0x0806fad7 in main (argc=12, argv=0xaf941ff4, envp=0xaf942028)
    at main.c:450
(gdb) frame 0
#0  0x080d13bf in MiscExtGetMouseSettings (mouse=0xaf941a58,
    devname=0xaf941a5c) at xf86MiscExt.c:172
172             mseptr->type =          MapMseProtoToMisc(pMse->protocolID);
(gdb) print devname
$1 = (char **) 0xaf941a5c
(gdb) print *devname
$2 = 0x82b9318 "/dev/input/mx510event"

I haven't tried with using the normal mouse driver yet, going to do that now. If
there is anything you want to know from this backtrace, let me know the exact
gdb commands you want me to run and i'll reproduce the crash.
Comment 1 Adam Jackson 2005-12-09 06:49:03 UTC 
would be good to know if pInfo and pMse are valid.
Comment 2 Mikael Magnusson 2005-12-09 06:52:11 UTC 
I'm sorry for the noise, after it successfully started with the mouse driver
(which i had to install first), i realized i was using a very old version of the
evdev driver. Upgrading it completely seems to have solved the problem. Again,
sorry.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.