Shawn Walker wrote: > On 15/09/2007, David Powell <David.Powell at sun.com> wrote: > > Shawn Walker wrote: > > > Greetings, > > > > > > Clean install of SXDE b72: > > > > > > I've discovered if I: > > > 1) set ksh93 as my login shell > > > > > > 2) Open a gnome-terminal > > > > > > 3) bldenv -d opensolaris.sh > > > > > > 4) clear > > > > > > I get: > > > > > > [1] + Stopped(SIGTTOU) clear > > > > I'm seeing this on build 73. My steps to reproduce are: > > > > (in xterm) > > 1) ksh93 > > 2) clear > > > > Trussing ksh93 indeed shows it receiving a SIGCLD indicating > > its child was stopped with a SIGTTOU: > > > > Received signal #18, SIGCLD [caught] > > siginfo: SIGCLD CLD_STOPPED pid=1825 status=0x001B > > Received signal #18, SIGCLD [caught] > > siginfo: SIGCLD CLD_CONTINUED pid=1825 status=0x0019 > > > > Instead of just: > > > > Received signal #18, SIGCLD [caught] > > siginfo: SIGCLD CLD_EXITED pid=1830 status=0x0000 > > > > which I get when I run some other command under ksh93 that writes to > > the terminal or when I run clear under ksh88. > > > > Curiously, both 'clear' and 'tput clear' are sent SIGTTOU, though > > 'tput clear' doesn't reproduce the problem. > > > > Additionally, trussing ksh93 with -f causes the problem to go away. > > Smells like a race to me. > > I agree, because I notice if I do it really fast repeatedly, it > happens *almost* every time, but not every time.
Groan... I hoped we killed that... ... problem is that I can't reproduce it here, even if I try hard... ... which kind of machine do you have (e.g. CPU type, number of CPUs, MHZ, installed memory etc.) ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
