On Mon, 2009-09-28 at 16:58 +0200, Julien Cristau wrote:
>
> Does this still happen with server 1.6.3.901? There's a
> signal-related
> fix in there, although it's kind of a long shot.
Yes, it does still happen after upgrade (last time ~ 5 minutes ago).
A gdb session is attached, with as much i
On Mon, 2009-09-28 at 16:58 +0200, Julien Cristau wrote:
> hw/xfree86/os-support/linux/../shared/sigio.c:110 seems to be:
> SYSCALL (r = select (xf86SigIOMaxFd, &ready, 0, 0, &to));
> where SYSCALL() is defined as:
> #define SYSCALL(call) while(((call) == -1) && (errno == EINTR))
>
> No idea
severity 547496 important
kthxbye
This doesn't seem to be extremely common, so downgrading.
On Sun, Sep 20, 2009 at 21:21:44 +0200, Thomas Koenig wrote:
> Here's a backtrace from another crash, obtained as described on
> http://wiki.debian.org/XStrikeForce/XserverDebugging from
> a core file.
>
Here's a backtrace from another crash, obtained as described on
http://wiki.debian.org/XStrikeForce/XserverDebugging from
a core file.
#0 0xe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb7b9d3d0 in raise () from /lib/i686/cmov/libc.so.6
No symbol table info available.
#2
4 matches
Mail list logo
