[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#547496: backtrace for another crash...



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.
> 
> #0  0xffffe410 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  0xb7ba0a85 in abort () from /lib/i686/cmov/libc.so.6
> No symbol table info available.
> #3  0x080ad3a5 in ddxGiveUp ()
> at ../../../../hw/xfree86/common/xf86Init.c:1417
>         i = <value optimized out>
> #4  0x0813b5fd in AbortServer () at ../../os/log.c:397
> No locals.
> #5  0x0813bbfe in FatalError (f=0x81c9150 "Caught signal %d.  Server
> aborting\n")
>     at ../../os/log.c:522
>         beenhere = 1
> #6  0x080c1c73 in xf86SigHandler (signo=11)
>     at ../../../../hw/xfree86/common/xf86Events.c:387
> No locals.
> #7  <signal handler called>
> No symbol table info available.
> #8  0x080b77b5 in xf86SIGIO (sig=29)
>     at ../../../../../hw/xfree86/os-support/linux/../shared/sigio.c:110
>         i = <value optimized out>
>         ready = {fds_bits = {3072, -65536, 0, 0, 65535, 0, -65536,
> 16711935, 16711935, 
>             8454143, 8388736, -65408, 0, 0, 16777215, 16711935, -65281,
> 16416, 1075839871, 
>             0, 0, 0, 0, 0, 8064, 0, -2102793, 0, 65535, 0, -1209998559,
> 0}}
>         to = {tv_sec = 0, tv_usec = 0}
>         save_errno = 0
>         r = -1
> #9  <signal handler called>

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 how this would segfault...

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.

Cheers,
Julien



Reply to: