--On June 16, 2008 1:20:28 PM +0200 Jasper Lievisse Adriaanse
<[EMAIL PROTECTED]> wrote:
according to dlg who also spent some time on this issue, it's some
syscall going crazy. if you have the time to dig into this, please don't
hesitate and debug devel/vte (where gnome-pty-helper comes from),
Is this happening only on amd64?
kdump(1) reveals it is continuously retrying to read(2) from stdin without
need.
read(2) returns EAGAIN:
[EAGAIN] The file was marked for non-blocking I/O, and no data
were
ready to be read.
The bug in gnome-pty-helper is triggered by some input from gnome-terminal
(g-p-h communicates via STDIN/STDOUT with g-t) when g-p-h is spawned by
g-t. I need a wrapper to intercept g-p-h soon enough with gdb and see which
input causes g-p-h to obsessively read stdin.
I'll let you know if I come up with a solution.
ciao
Luca
