Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!cmcl2!philabs!ttidca!ttidcc!mab
From: mab@ttidcc.UUCP (Michael A. Bloom)
Newsgroups: net.emacs
Subject: Re: GNU Emacs help needed for Pyramid
Message-ID: <215@ttidcc.UUCP>
Date: Mon, 10-Mar-86 17:05:23 EST
Article-I.D.: ttidcc.215
Posted: Mon Mar 10 17:05:23 1986
Date-Received: Sat, 15-Mar-86 02:04:15 EST
References: <168@gsg.UUCP>
Reply-To: mab@ttidcb.UUCP (Michael A. Bloom)
Organization: Transaction Technology, Inc. (CitiCorp), Santa Monica
Lines: 27
Summary: new compiler fix

In article <168@gsg.UUCP> lew@gsg.UUCP (Paul Lew) writes:

|We just got the latest GNU emacs version 17.49.1.  We are running Pyramid 2.5.
|When I ran it, it gave me fatal error and existed when I typed C-X 2 to enter
|two window mode.  Anyone out there have this experience?

We have two Pyramids, one runing Osx 2.5, one running Osx 3.0.

I had the same experience on the 2.5 system but not on the 3.0 system.
Examining the core dump, I found that the global Qnil (nil) did not
point to the same place in all modules! Meaning: nil was not always
nil!  

Unfortunately, a 3.0 binary won't run on a 2.5 system, so I couldnt
just bring either the other compiler, or the other emacs binary over.

Anyway,  I submitted this problem to pyramid last week as SR# 8494,
which became their internal SPR# 1923.  

Today, I got a message from Pyramid Corporate headquarters, saying that they
are sending me down a tape of their "latest and greatest" C compiler, version
3.1.7, which they say fixes the problem.  After I recieve it, I'll post the
results.

If you have this problem,  you might wish to ask for this compiler version,
referencing the above SR and SPR numbers.