Comment 35 for bug 539772

Revision history for this message
In , Pauli (paniemin) wrote :

(In reply to comment #11)
> The reporters say this is all they can get on this bug:
>
> .
> Thread 1 (Thread 7382):
> #0 0x002b5fb6 in ?? () from /lib/tls/i686/cmov/libc.so.6
> No symbol table info available.
> #1 0x00000000 in ?? ()
> No symbol table info available.

It doesn't look like that this is caused by same bug. This looks like stack overflow.

But in any case valgrind is the best tool for debugging stack overflows. Running xserver in valgrind and collecting the output to a file would be best way to collect info.

something like:
valgrind X <X params> > /tmp/valgrind.crash.report.txt