Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-unix!hplabs!decwrl!pyramid!prls!philabs!ttidca!mb
From: mb@ttidca.UUCP
Newsgroups: comp.unix.wizards,comp.emacs
Subject: building a.outs in COFF format
Message-ID: <358@ttidca.UUCP>
Date: Thu, 29-Jan-87 02:33:47 EST
Article-I.D.: ttidca.358
Posted: Thu Jan 29 02:33:47 1987
Date-Received: Sat, 31-Jan-87 05:48:44 EST
Reply-To: mb@ttidca.UUCP (Michael Bloom)
Organization: CitiCorp TTI, Santa Monica, Ca.
Lines: 36
Xref: watmath comp.unix.wizards:753 comp.emacs:373

Has anyone succeeded in getting either the emacs version of unexec.c
or any other version of unexec to work with SysV Release 2?  

What checks does the USG release 2 kernel make on header fields or
other attributes of a COFF binary that were not made in earlier
releases?

And why does the exec apparently succeed before it has finished making
all such checks?  This seems to be the case; it tries to load the binary
produced by unexec, but the entry point does not get called. 

In trying to build emacs on a National Semi ICM3216, I have run against
several problems.  

The first was that malloc itself would crap out.  This was because for
some bizarre reason, ulimit(3,0) was returning a number in the 300,000
range rather than the 8 meg it should in Nationals release of unix.
This was fixed by "#define ULIMIT_BUG 8192000" in the appropriate .h file,
and conditionalizing the code that calls ulimit.

The second was that unexec would crap out with a SEGV when it got to the 
point of trying to copy the memory between text and data.  snarfing the
code from the v18 unexec which understands such events fixed this problem.

After the above fixes were done, temacs would successfully create a new
a.out file, but an unusable one.

The reason I have been working with v17, rather than v18, is that it
is documented that something broke for release 2 systems between
version 17 and version 18 of unexec. 

If anyone has had success with unexec, or has some suggestions on
things to check, I'd like to hear from you.

mb@ttidca.tti.com (if you are not on the internet)
mb@ttidca.uucp (if you are on the internet - we're waiting for a forwarder)