Bling!
David Malcolm
dmalcolm at redhat.com
Wed Feb 22 01:18:52 UTC 2006
On Wed, 2006-02-08 at 23:05 -0500, Ray Strode wrote:
[snip]
> Things are still quite raw, so expect things to crash, your system to
> lock up, effects to be unpolished, etc.
Is there a bugzilla component I should file problems against?
Are there debuginfo packages for the repo?
I'm getting the Xair server apparently crashing during the login. Upon
investigation, it's an exit here:
(gdb) bt
#0 0x00b718c6 in exit () from /lib/libc.so.6
#1 0x00f4cb96 in intelAllocateMemoryMESA ()
from /usr/lib/dri/i915_dri.so
#2 0x00f4d708 in intelWaitForIdle () from /usr/lib/dri/i915_dri.so
#3 0x00f4d732 in intelFinish () from /usr/lib/dri/i915_dri.so
#4 0x00f6aaf2 in _mesa_Finish () from /usr/lib/dri/i915_dri.so
#5 0x003e6423 in __glXSwapBuffers ()
from /usr/lib/xair/modules/extensions/libglx.so
#6 0x003ec750 in __glXForceCurrent ()
from /usr/lib/xair/modules/extensions/libglx.so
#7 0x008a8ddc in DRIUnlockedCallback ()
from /usr/lib/xair/modules/extensions/libdri.so
#8 0x003ec8e1 in __glXForceCurrent ()
from /usr/lib/xair/modules/extensions/libglx.so
#9 0x080845d6 in Dispatch ()
#10 0x0806e2f9 in main ()
Top tip for debugging: ssh into the test machine from another host,
locate the Xair process, and run a "gdb attach" onto that process from
there, type "cont" to get the X server to continue. You then have a
vaguely sane debug environment, and can "break exit" (how I got the
above).
Should these notes be on the wiki?
Dave
More information about the test
mailing list