Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site sdcarl.UUCP
Path: utzoo!watmath!clyde!cbosgd!ukma!psuvm.bitnet!psuvax1!burdvax!sdcrdcf!sdcsvax!sdcc3!sdcarl!rusty
From: rusty@sdcarl.UUCP (rusty c. wright)
Newsgroups: net.emacs
Subject: gnu emacs malloc bug on suns
Message-ID: <277@sdcarl.UUCP>
Date: Wed, 1-Jan-86 14:28:10 EST
Article-I.D.: sdcarl.277
Posted: Wed Jan  1 14:28:10 1986
Date-Received: Fri, 3-Jan-86 02:10:17 EST
Reply-To: rusty@sdcarl.UUCP (Rusty Wright)
Organization: Computer Audio Research Lab, UCSD, San Diego, Calif.
Lines: 14

I've had this problem with the last few versions of emacs.  The
current version that we are using is 17.36.  It only happens on our
suns; it works fine on our vax.  What happens is that after you've
been using emacs for a while, editing various files and such, it
starts complaining when you give it valid commands (e.g. C-x k).  The
error message is "Attempt to modify read-only object".

An easy way to get it into this state is to edit a large number of
files and then kill all of those buffers (beat on malloc and free)
then do C-h C-n (view-emacs-news).  I'm not positive that it's a
malloc bug, but that's where I suspect it is.
--
        rusty c. wright
        {ucbvax,ihnp4,akgua,hplabs,sdcsvax}!sdcarl!rusty