Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!rutgers!ames!ucbcad!ucbvax!UTORPHYS.BITNET!Postmaster From: Postmaster@UTORPHYS.BITNET (PMDF Mail Server) Newsgroups: comp.emacs Subject: Undeliverable mail Message-ID: <8708030029.AA22394@ucbvax.Berkeley.EDU> Date: Sun, 2-Aug-87 20:14:00 EDT Article-I.D.: ucbvax.8708030029.AA22394 Posted: Sun Aug 2 20:14:00 1987 Date-Received: Sun, 2-Aug-87 23:51:27 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 50 The message could not be delivered to: Addressee: QUINN Reason: %MAIL-E-LOGLINK, error creating network link to node MCL2 ---------------------------------------- Received: from JNET-DAEMON by UTORPHYS; Sun, 2 Aug 87 20:14 EDT Received: From CANADA01(MAILER) by UTORPHYS with RSCS id 5506 for QUINN@UTORPHYS; Sun, 2-AUG-1987 20:14 EDT Received: by CANADA01 (Mailer X1.24) id 5504; Sun, 02 Aug 87 20:11:31 EDT Date: Sun, 2 Aug 87 19:30:09 edt From: Keith Moore Subject: Re: GNU/VMS Question (bug in GNU Emacs under VMS 4.5) Sender: UNIX-EMACS distribution list To: your name Reply-to: UNIX-EMACS@BBN.COM Comments: To: Carl Fussell Comments: cc: unix-emacs@BBN.COM, bug-gnu-emacs@PREP.AI.MIT.EDU >We have been running GNUEMACS 18.47 for the last few weeks on a >VAX 8650/VMS V4.4 system. This morning we upgraded to V4.5 and >emacs "broke" with an Access Violation from the routine >fatal_signal_error (or maybe sys_getenv). I tried recompiling >and linking the sources to no avail. I tried VAX C ver 2.2 >and ver 2.3 with the same results (our original working emacs >was compiled with C ver 2.2 under VMS 4.4). > >Has anyone else managed to get gnuemacs running under VMS 4.5? >If you have, I would very much appreciate hearing about your >experiences. Any info would be helpful. > >Thanx for any help or advice... > >Carl Fussell >Santa Clara University >CARL@SCU.BITNET The same thing happened to me. I tried relinking - no luck. So I went into the debugger and found out that the environ variable gets garbaged when Emacs maps emacs.dump to its address space. So I relinked again (/nodebug this time), ran build.com, installed the new copies of (t)emacs.exe and (t)emacs.dump, and all seems to be well. This is with GNU Emacs v18.46 for VMS, compiled with VAX C v2.2. Keith Moore Internet: moore@utkcs2.cs.utk.edu UT Computer Science Dept. CSnet: moore@tennessee Knoxville Tennessee BITNET: moore@utkcs1