[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    [BusyBox] Re: cmdedit revision 1.52
From:       Erik Andersen <andersen () lineo ! com>
Date:       2001-05-23 8:24:55
[Download RAW message or body]

On Sun May 20, 2001 at 08:19:15PM +0400, Vladimir N. Oleynik wrote:
> Eric,
> 
> > Diff to previous 1.51 
> 
> > It turns out job control in both hush and lash was broken by the
> > signal handling in cmdedit.c.  Disabling it makes the shells behave
> > themselves again.  hush isn't quite there, but is getting close...
> 
> Hmm, I not found this problem with old revision.
> But you addition new problem:
> 
> console 1:
> busybox $ editing...
> 
> console 2:
> $ kill PID_SHELL_CONSOLE_1
> 
> init restarted 1-st shell
> 
> Brrr...

Try this.  Revert cmdedit.c signal handling to how it was.
Then run something like "grep foo &" from the shell.  Now
the shell is completely locked solid.  

> Current lash and hush not have processing signals. 
> After addition parse "terminates" (traps) parser, I get ready rewrite cmdedit
> with
> restore previous signal handlers for this signals, but current situations best
> with
> blocked this signals in edition mode and restore SIG_DFL in running mode.

I know.  The signal handling needs to be fixed.

 -Erik

--
Erik B. Andersen   email:  andersen@lineo.com
--This message was written using 73% post-consumer electrons--



[prev in list] [next in list] [prev in thread] [next in thread]