Bug#547496: backtrace for another crash...
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 how this would segfault...
The way I read the backtrace:
#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>
No symbol table info available.
#10 0xb7bea5fd in memmove () from /lib/i686/cmov/libc.so.6
No symbol table info available.
#11 0x08133682 in FlushClient (who=0x8b18ec8, oc=0x8b18e58,
__extraBuf=0x868fba8,
extraCount=51876) at ../../os/io.c:959
before = <value optimized out>
remain = <value optimized out>
i = <value optimized out>
len = <value optimized out>
memmove segfaults due to invalid arguments, the signal handler just gets
called afterwards.
Reply to: