On Sam, 2002-02-16 at 16:50, Joe Krahn wrote: > > > > > Here's an example backtrace, that seems to me like somthing > > > deeper than XFree86 code being at fault: > > > > > > (gdb) bt > > > #0 0x40139012 in __writev (fd=20, vector=0xbffff6fc, count=1) > > > at ../sysdeps/unix/sysv/linux/writev.c:51 > > > #1 0x080d5ad4 in _XSERVTransSocketWritev () > > > #2 0x080d61cc in _XSERVTransWritev () > > > #3 0x080d0248 in StandardFlushClient () > > > #4 0x080cea8f in CloseDownConnection () > > > #5 0x080b2f69 in CloseDownClient () > > > #6 0x080addbd in Dispatch () > > > #7 0x080bd6d8 in main () > > > #8 0x4006e627 in __libc_start_main (main=0x80bd1f0 <main>, argc=1, > > > ubp_av=0xbffffc04, init=0x806cc5c <_init>, fini=0x816f94c <_fini>, > > > rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbffffbfc) > > > at ../sysdeps/generic/libc-start.c:129 > > > > A backtrace from the server would probably be more interesting, or does > > only the client hang? > This is a backtrace from the server,
D'oh, should have noticed. :) > but it's not the XFree86 gdb, so it won't catch module bugs. > > I tried installing RedHat's RawHide XFree86-4.2, and the same crash > occurs. I'll re-install mine, which has debug symbols, and try > the XFree86 gdb on it. Modules aren't even involved here; the hang occurs in a glibc function so it seems the problem isn't in the X server at all. -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
