🚀 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!rutgers!tut.cis.ohio-state.edu!UCSD.EDU!wallis%wsuiar.UUCP
Newsgroups: gnu.emacs.bug
Subject: GNU emacs BAD ADDRESS bug?
Message-ID: <389.271c5044@wsuiar.uucp>
From: wallis%wsuiar.UUCP@UCSD.EDU
Date: 17 Oct 90 17:36:20 GMT
Sender: jgreely@tut.cis.ohio-state.edu
Distribution: gnu
Organization: Wichita State Univ., Wichita KS
Approved: bug-gnu-emacs@prep.ai.mit.edu
Lines: 28

	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?


                      Thanks in advance,

                      Tom Wallis
-- 
-------------------------------------------------------------------------------
Thomas Wallis                          BITNET: WALLIS@TWSUVAX
System Manager, Computer Science Dept. UUCP: uunet!ncrlnk!ncrwic!wsuiar!wallis
Wichita State University               Internet: wallis@wsuiar.wsu.UKans.EDU
Wichita, Ks.  67208                    

DISCLAIMER: The opinions expressed here are my own, and do not reflect the
views of the Computer Science Department or Wichita State University.
-------------------------------------------------------------------------------