Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!RODAN.ACS.SYR.EDU!jdpeek
From: jdpeek@RODAN.ACS.SYR.EDU (Jerry Peek)
Newsgroups: comp.unix.questions
Subject: ksh-i bombs on a Gould NP1 with "ksh: no space"... help, pleeeze
Message-ID: <8905191353.AA07318@rodan.acs.syr.edu>
Date: 19 May 89 14:53:25 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 35

I'm trying to install ksh-i (Korn Shell) on our Gould NP1 (BSD-type UNIX,
UTX/32 Version 3.0E).  It builds and installs fine.  It runs fine, almost all
the time.  Typing ^V in "emacs" mode says the shell is Version 06/03/86a.

But sometimes, and I haven't been able to see a pattern, it goes crazy
and starts printing
	ksh: no space
	ksh: no space
	ksh: no space
	...
forever, until I kill it.

David Korn gave me some advice, but it sounds like it might take some time:

> The nospace messages in the 06/03/86a release are usually the result
> of segmentation violation faults.  With the old version of ksh,
> I would catch these and try to grow memory as is done with the
> Bourne shell.
> 
> Withe the ksh-88 release, I eliminated this completely so that you
> would get a core dump in this case the the stack trace would point
> out the problem.
> 
> You could run with the lines in sh/fault.c that catch SIGSEGV removed
> and see whether you can get a memory fault - core dumped and then
> look at the stack.
> 
> As an alternative, you could get ksh-88 from the UNIX system Toolchest.

We can't afford ksh-88 now, sigh, and I'm no good with stack traces.  Has
anybody fixed this, or have any ideas?  Thanks a lot!

--Jerry Peek; Syracuse University Academic Computing Services; Syracuse, NY
  jdpeek@rodan.acs.syr.edu, jdpeek@suvm.bitnet
  +1 315 443-3995