What's the signal it's taking? That looks like tcsetattr triggering SIGTTOU. But that ought to behave properly when you resume it. If gdb is doing nothing other than taking SIGTTOU and then retrying the RPC when you resume it, then it's fine on that end. The problem is just that term is giving it EBACKGROUND, which is either a term bug or a problem with the job control setup done by gdb/libc. However, if that gdb process is doing any other than that, we should figure it out (even if a term change makes the problem go away).
_______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
