From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from gatech.edu (gatech.edu [130.207.244.244]) by werple.net.au (8.7/8.7) with SMTP id DAA14155 for ; Mon, 16 Oct 1995 03:13:24 +1000 (EST) Received: from gauss (gauss.skiles.gatech.edu) by gatech.edu with SMTP id AA03099 (5.65c/Gatech-10.0-IDA for ); Sun, 15 Oct 1995 13:06:19 -0400 Received: by gauss (5.x/SMI-SVR4) id AA20969; Sun, 15 Oct 1995 13:05:33 -0400 Resent-Date: Sun, 15 Oct 1995 13:02:07 -0400 Old-Return-Path: Message-Id: <9510151702.AA12629@redwood.skiles.gatech.edu> X-Mailer: exmh version 1.6.4 10/10/95 To: "Seth M. LaForge" Cc: zsh-workers@math.gatech.edu Subject: Re: Fix for zsh signal problems with Slakware In-Reply-To: Your message of "Sat, 14 Oct 1995 00:57:26 PDT." <199510140757.AAA00927@envy.ugcs.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Oct 1995 13:02:07 -0400 From: Richard Coleman Resent-Message-Id: <"tJE9M.0.Y75.SzJWm"@gauss> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/457 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu > Under newer versions of slakware, zsh has the really annoying habit of > totally freezing whenever a child process gets a signal. I've finally > found the cause. > > The problem is that zsh tries to generate signames.h, a list of signal > names, from /usr/include/linux/signal.h. In recent releases of > slakware, /usr/include/linux/signal.h consists solely of > #include . Thus signames.h contains no signal names, > and zsh runs off the end of the signal name array when trying to look > up a signal name. This problem has already been fixed in the baseline zsh sources and will show up in the next beta release (whenever that is). I've given up guessing when that will be. Richard Coleman coleman@math.gatech.edu