Eugene V. Lyubimkin, le Tue 03 May 2011 21:22:03 +0300, a écrit : > #0 0x018232bc in _hurd_intr_rpc_msg_in_trap (msg=0x1dfec5c, option=3, > send_size=44, rcv_size=2092, rcv_name=19, timeout=0, notify=0) at > intr-msg.c:134 > #1 0x01a371f5 in __io_read (io_object=49, data=0x1dff568, dataCnt=0x1dff56c, > offset=-1, amount=2)
This is the actual system call to request a read() from the Unix socket translator. > A search for '_hurd_intr_rpc_msg_in_trap' showed that GHC and ps have/had > some similar "hangs" problems with similar backtraces: [1] and [2]. > > [1] http://lists.debian.org/debian-hurd/2011/04/msg00060.html > [2] http://lists.debian.org/debian-hurd/2000/01/msg00093.html I think the ps backtrace is unrelated: in that case the call is to a tty translator, not the unix socket translator. > @porters: Does it look like a bug in application or libc? According to the backtrace above, it would be in the unix local translator, pflocal (which would also explain the garbage). You however need to be root to run gdb on pflocal (in non-invasive mode, else gdb will probably hang, waiting for its own local unix communications). Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
