On Sun, Aug 14, 2005 at 01:14:44PM -0400, Daniel Jacobowitz wrote: > On Sun, Aug 14, 2005 at 12:13:48AM -0400, Justin Pryzby wrote: > > reassign 322966 gdb > > thanks > > > > $ stty -a |grep -i tostop > > isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt > > > > In fact, I have: > > $ grep -i tostop .bash_profile > > stty tostop > > > > which I tried to find before sending this report, but failed in search > > the bash manpage. > > > > So, is this a bug? Gdb _wasn't_ backgrounded, right?, and so, it > > shouldn't have gotten sigstop (or SIGTTOU or whatever). Or, do I need > > to know more about stty tostop before using it? > > GDB had set the inferior program (ps in this case) to be the foreground > job on the terminal. Then it wrote a status message to the terminal. > Normally this is harmless, but with tostop asserted it gets SIGTTOU. > > It's a bug, just not a very important one. Why do you set tostop > anyway? I remember setting it, a long time ago, so I don't remember the context.
I think I read about it randomly one day, and said, "hey, this would be neat". So I got into the habbit of running bg processes, and waiting to see that they'd been stopped so I could check the output. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
