Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!snorkelwacker.mit.edu!stanford.edu!rutgers!ucsd!mvb.saic.com!ncr-sd!SanDiego.NCR.COM!tortuga!rns
From: rns@tortuga.SanDiego.NCR.COM (Rick Schubert)
Newsgroups: comp.sys.ncr
Subject: Re: bugs on s486 SysVr4
Message-ID: <1991Jun7.154210.15834@donner.SanDiego.NCR.COM>
Date: 7 Jun 91 15:42:10 GMT
References: <21112@cadillac.CAD.MCC.COM>
Sender: news@donner.SanDiego.NCR.COM (News Owner)
Reply-To: rns@tortuga.SanDiego.NCR.COM (Rick Schubert)
Organization: NCR Corporation, Rancho Bernardo
Lines: 52

In article <21112@cadillac.CAD.MCC.COM> beihl@cadillac.cad.mcc.com () writes:
>On an S486 system running System V release 4.0.2.0, I have encountered
>a few problems on an otherwise quite nice machine/system.  Perhaps
>others who have bumped into these might be interested:

>(1) setjmp() is broken!  The following program dumps core:

[Program deleted]

I compiled and ran it on an NCR 3345 (I think) running 4.0.2.0, and it
ran successfully.

>As a workaround, here is a replacement setjmp.s:

I ran this through uudecode and got the message "Short file."  After
uncompressing the resulting file, the resulting setjmp.s had some
garbage in it.

>(2) readdir() is broken.  The following program prints garbage
>instead of directory entry names.

[Program deleted]

The program worked fine for me.

>(3)  The following file will hang the Csh when sourced:

>#! /bin/csh -f
>#
>echo $path | grep -s "/usr/ucb/bin"
>exit $status

>Workaround is to say 

>echo $path > tmp$$; grep -s "/usr/ucb/bin" tmp$$

I have encountered similar problems.  The general problem seems to
be piping a csh built-in command into some process.  "echo", "set", and
"history" (and probably others) all suffer from this problem.  The
commands don't have to be in a file that is source-d; they can be
entered directly from the keyboard.  And interrupting seems to be
impossible.  I always have to log in again somewhere else and kill one
of the processes that are hung.

In the case of "echo", an each workaround is to use "/bin/echo,"
which is a real, live program (as opposed to a shell built-in),
so it doesn't suffer from this bug.

Disclaimer: I work for NCR but have nothing to do with the products
involved.

-- Rick Schubert (rns@tortuga.SanDiego.NCR.COM)