[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: freeze due to interrupted futex system calls
From: |
Richard Stallman |
Subject: |
Re: freeze due to interrupted futex system calls |
Date: |
Wed, 25 Aug 2004 00:41:06 -0400 |
stopped (status 'S') and using 'strace -p' I get repeatedly the
following trace:
futex(0x407d9860, FUTEX_WAIT, 2, NULL) = -1 EINTR (Interrupted system
call)
--- SIGIO (I/O possible) @ 0 (0) ---
sigreturn() = ? (mask now [SEGV])
This sort of information isn't useful for debugging.
To get useful info, could you please start running under GDB all the
time, so you can make a C and Lisp backtraces using the `backtrace'
and `xbacktrace' commands? See etc/DEBUG.