Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!rpi!uwm.edu!bionet!agate!garnet.berkeley.edu!cliff
From: cliff@garnet.berkeley.edu (Cliff Frost)
Newsgroups: comp.sys.mac.comm
Subject: Re: bug in berkeley "popper" program
Keywords: bug fix
Message-ID: <1991Mar20.231616.27116@agate.berkeley.edu>
Date: 20 Mar 91 23:16:16 GMT
References: <DA.91Mar8111526@igor.cs.brown.edu> <1991Mar8.185229.20456@ux1.cso.uiuc.edu> <1991Mar9.002825.5868@parc.xerox.com> <1991Mar13.215151.5173@ux1.cso.uiuc.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Reply-To: cliff@garnet.berkeley.edu (Cliff Frost)
Organization: ucb
Lines: 21

The problem with popper reported here last week is real, and serious.  It
appears to have been introduced into popper around September, 1990.  It
would occur if you had compiled popper with -DDEBUG, and then run popper
without the "-d" (debug) flag.

If you compiled popper without -DDEBUG then you are not vulnerable to this
particular bug.  Unfortunately, the Makefile in the popper-1.7.tar.Z file
has -DDEBUG set as the default.

I have changed the default in the makefile in popper-1.7.tar.Z in the ftp
repository.  There is also a popper-1.81beta.tar.Z there which fixes two
other problems.  I believe 1.81 is stable, but will wait for some time
before removing the 1.7 file.

The ftp repository is ftp.CC.Berkeley.EDU.  Its current addresses are:
128.32.136.9, 128.32.206.9, 128.32.206.12, 128.32.136.38.

Many thanks to Steve Dorner and others who pointed this out to us.

	Cliff Frost
	UC Berkeley