Re: gdb, libio, readline

[Marcus Brinkmann]

On Sat, Mar 30, 2002 at 02:17:01PM -0500, Roland McGrath wrote:
> 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).

Oops.  I am sorry for giving such a misleading backtrace.  Of course, to
produce the backtrace I had to suspend gdb, so it got backgrounded and then
I could run gdb with the batch option on the suspended gdb to see where it
is hanging.  So what you saw was simply the suspended gdb.

I have now set up a neighbourhurd (our new name for subhurd ;) and can do
proper debugging.  But now it is hanging in poll.  And I have tried the
latest term in stdio environment, which works, too.

Thanks,
Marcus

-- 
`Rhubarb is no Egyptian god.' Debian http://www.debian.org brinkmd@debian.org
Marcus Brinkmann              GNU    http://www.gnu.org    marcus@gnu.org
Marcus.Brinkmann@ruhr-uni-bochum.de
http://www.marcus-brinkmann.de