Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!usc!cs.utexas.edu!milano!uudell!sequoia!rpp386!jfh
From: jfh@rpp386.cactus.org (John F. Haugh II)
Newsgroups: comp.unix.wizards
Subject: Re: sed bug?
Message-ID: <18499@rpp386.cactus.org>
Date: 16 Aug 90 04:40:16 GMT
References: <24172@adm.BRL.MIL>
Reply-To: jfh@rpp386.cactus.org (John F. Haugh II)
Organization: Lone Star Cafe and BBS Service
Lines: 33
X-Clever-Slogan: Recycle or Die.

In article <24172@adm.BRL.MIL> stanonik@nprdc.navy.mil (Ron Stanonik) writes:
>We've run into what appears to be a sed bug in sunos4.X (sun3 snd sun4)
>and in sysVr3 (on a 3b2).  Here's a little sed program to demonstrate it
>
>1 s/.*/&/p
>d
>
>I'd expect this to print only the first line, and indeed that's what happens
>in 4.3bsd (on a vax 780).  In sunos4.X and sysVr3, however, nothing is printed.

By all accounts it is fixed in BSD 4.3 and broken in every other version of
SED I've had my hands on.

The way the bug was reported for AIX 3.1 was

% sed -e 's/abc/ABC/p' -e d << EOF
abc
abc123
EOF

and the output should have been

ABC
ABC123

but instead, nothing at all was printed.

>Bug?

Yes.  Bug.
-- 
John F. Haugh II                             UUCP: ...!cs.utexas.edu!rpp386!jfh
Ma Bell: (512) 832-8832                           Domain: jfh@rpp386.cactus.org