[ksh93-integration-discuss] Problems with stty erase <backspace>

[James Carlson]

Dan Price writes:
> > we're still trying to reproduce this
> > did you get it to fail without attaching dtrace?
> 
> I would hope so: dtrace is instrumenting the kernel in Roland's example
> (in other words we're seeing all calls on the system to pgsignal());
> it's just a passive observer here.

It failed in a different way with dtrace running, but only because ksh
seemed quite confused about having a job started with '&' and ended up
waiting for it to exit.  Something's definitely wrong with job
control.

When I get a spare moment, I'll reinstall ksh93 and try again.

But the original poster's problem is easy to reproduce, as is the
dtrace calamity.  Just tossing dtrace in the background and running
the original stty test case causes ksh to wedge in a waitpid.

> If you think there might be a race, this could be an opportunity
> to try out the chill() action in dtrace, which means "sit here for
> a little while".  It can be useful for getting races and timing
> bugs to pop up.

I don't think it's really a race, though I suppose anything's
possible.

-- 
James Carlson, KISS Network                    <james.d.carlson at sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677