It looks to me like maybe the vid mode extension allows
switching modes while switched away? I had a bug report that
VT switching while playing a certain game (Sid Meier's Alpha
Centauri) that uses the vidmode extension causes the server
to SIGV. This is with the "nv" driver.
Should VidModeSwitchMode be doing all this when switched
away?
Mark.
#0 0x40071fe1 in __kill ()
#1 0x40071dba in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2 0x40073582 in abort () at ../sysdeps/generic/abort.c:88
#3 0x806eac1 in ddxGiveUp () at xf86Init.c:1061
#4 0x806eb66 in AbortDDX () at xf86Init.c:1112
#5 0x80d7ecc in AbortServer () at utils.c:437
#6 0x80d9406 in FatalError (
f=0x81824e0 "Caught signal %d. Server aborting\n") at utils.c:1400
#7 0x8081261 in xf86SigHandler (signo=11) at xf86Events.c:1085
#8 <signal handler called>
#9 0xc7fffeeb in ?? ()
#10 0x80766b2 in pciBusAccessEnable (ptr=0x82c1338) at xf86pciBus.c:647
#11 0x807673d in pciSetBusAccess (ptr=0x82c1338) at xf86pciBus.c:678
#12 0x8072792 in xf86EnableAccess (pScrn=0x82c1628) at xf86Bus.c:755
#13 0x8073dc3 in xf86EnterServerState (state=SETUP) at xf86Bus.c:2141
#14 0x80a494a in VidModeSwitchMode (scrnIndex=0, mode=0x8314c68)
at xf86VidMode.c:346
#15 0x82368a7 in ProcXF86VidModeSwitchToMode (client=0x8405b20)
at xf86vmode.c:1241
#16 0x8237641 in ProcXF86VidModeDispatch (client=0x8405b20) at xf86vmode.c:1682
#17 0x80b2d16 in Dispatch () at dispatch.c:462
#18 0x80c33fb in main (argc=2, argv=0xbffff874, envp=0xbffff880) at main.c:454
#19 0x40060fd1 in __libc_start_main (main=0x80c2e98 <main>, argc=2,
ubp_av=0xbffff874, init=0x806caec <_init>, fini=0x817deb4 <_fini>,
rtld_fini=0x4000e254 <_dl_fini>, stack_end=0xbffff86c)
at ../sysdeps/generic/libc-start.c:118
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
