4.[123]bsd csh script handling bug--who's got the "right" fix?

P. Tucker Withington ptw at encore.UUCP
Wed Mar 26 02:26:16 AEST 1986


>If you
>    repeat 25 echo oops 6789012345678901234567890123456789012345678901 >> file
>and then either
>    csh file
>or
>    cat file | csh
>you get this output:
>    oops: Command not found.
>    789012345678901: Command not found.
>where "780912345678901" turns out to be what's stored in "file" starting at the
>1025th byte.  Could be disastrous if you had something such as...

<Toot, toot!>

This bug does not occur in Encore's UMAX 4.2, the proprietary natur of the code prevents me from posting a fix, however.



More information about the Comp.bugs.4bsd.ucb-fixes mailing list