Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.ultrix
Subject: Re: egrep dies [Was: Still buggy after all these years?]
Message-ID: <8067@cbmvax.UUCP>
Date: 3 Oct 89 17:25:41 GMT
References: <12066@polya.Stanford.EDU> <12070@polya.Stanford.EDU>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 21

In article <12070@polya.Stanford.EDU> maslen@Neon.Stanford.EDU (Thomas Maslen) writes:
> In article <12066@polya.Stanford.EDU> casley@neon.stanford.edu (Ross Casley) writes:
> >There seems to be a bug in calendar.  When I try to run it today I wait a
> >long time, then I get several messages that egrep has run out of swap
> >space.  Now, calendar works by first running /usr/lib/calendar, which
> >generates a pattern that is then fed to egrep.  The pattern is supposed to
> >pick out the relevant lines from the calendar file.  My best guess is that
> >since today is a Friday and the month changes over the weekend,
> >/usr/lib/calendar generates an unusually long pattern.  Then egrep barfs

This sounds like manifestation of the problem that was reported previously
with *grep, when DEC changed the regexp code to handle 8-bit data and
didn't increase the area for storeing the compiled expressions.

Please file an SPR describing the problem and pointing at egrep.  Maybe
DEC will deign to fix it this time...

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)