This is the mail archive of the gdb@sourceware.cygnus.com mailing list for the GDB project. See the GDB home page for more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
This bug report is my responsibility. I'm working my way through them, don't worry. > What happened to this bug report and patch? I don't know for sure > if it is a gdb or glibc bug. > > The problem is with gdb's 'tty' command. The gdb manual reads: > > [...] It also resets the controlling terminal for the child > process, for future `run' commands. For example, > > tty /dev/ttyb > > directs that processes started with subsequent `run' commands default > to do input and output on the terminal `/dev/ttyb' and have that as > their controlling terminal. > > However on this system 'tty' has no effect on the controlling terminal. > The controlling terminal of the child appears the same as that of gdb. > See the original report below for a resulting real-life problem > (a program under gdb tries to read from /dev/tty and fails with SIGTTIN).