🚀 go-pugleaf

Relay-Version: VMS News - V5.9C 19/12/89 VAX/VMS V5.3; site vax1.cc.lehigh.edu
Path: vax1.cc.lehigh.edu!vax1.cc.lehigh.edu!netnews.upenn.edu!dsinc!unix.cis.pitt.edu!zaphod.mps.ohio-state.edu!wuarchive!uunet!tut.cis.ohio-state.edu!MPRGATE.MPR.CA!morse
Newsgroups: gnu.emacs.bug
Subject: Re: GNU emacs BAD ADDRESS bug?
Message-ID: <MORSE.90Oct19092910@quark.mpr.ca>
From: morse@MPRGATE.MPR.CA (Daryl Morse)
Date: 19 Oct 90 16:29:10 GMT
Sender: gadkari@tut.cis.ohio-state.edu
References: <389.271c5044@wsuiar.uucp>
Distribution: gnu
Organization: MPR Teltech Ltd., Burnaby, BC, Canada.
Approved: bug-gnu-emacs@prep.ai.mit.edu
Lines: 30

Sorry about my previous post. I slipped on the ^C key.

In article <389.271c5044@wsuiar.uucp> wallis%wsuiar.UUCP@UCSD.EDU writes:

   Dear GNUers:

   I successfully compiled GNU EMACS on a DECstation 5000 runnig ULTRIX
   4.0.  I have users with DECstation 3100s running ULTRIX 4.0 as well.  I NFS
   serve GNU EMACS up to their DS3100 and they occasionally have problems
   getting into emacs.  The message they get is:

   /usr/local/bin/emacs:  bad address  

   This seems to be an intermittant problem.  What causes a "bad address" 
   message?   If they get into emacs one time, then if they invoke it again
   immediately afterwards, then it doesn't work.  However, if they do an
   ls  in between, it seems to work.  Could it be a physical memory limitation?

We regularly encounter this problem. According to Ultrix Software
Support, a patch is available from DEC for Ultrix 3.1d to correct this
problem. One for Ultrix 4.0 is supposedly on the way, though I do not
have any idea when. You should contact DEC.

Daryl

--
Daryl Morse                     | Voice : (604) 293-5476
MPR Teltech Ltd. 		| Fax   : (604) 293-5787
8999 Nelson Way, Burnaby, BC    | E-Mail: morse@quark.mpr.ca
Canada, V5A 4B5                 |         quark.mpr.ca!morse@uunet.uu.net