Branden Robinson <[EMAIL PROTECTED]> writes:
> It may be necessary to attach gdb to the XFree86-debug server from a
> remote terminal to locate the source of the problem.
>
> Unless you can ulimit -c unlimited and get a good backtrace off the
> core from XFree86-debug?
Given that it kills the kernel, both methods don't seem very viable...
the best I could try is redirect the log to the networks somehow and
see what occurs last. Do you have any recommendation how to do so? In
case the console output of the X process contains everything
/var/log/XFree.log contains, I could just use ssh.
--
Falk
