Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site pur-ee.UUCP
Path: utzoo!linus!philabs!cmcl2!floyd!harpo!eagle!mhuxl!ihnp4!inuxc!pur-ee!isrnix!greg
From: greg@isrnix.UUCP
Newsgroups: net.bugs.2bsd
Subject: 2.8 exec bug fix wanted - (nf)
Message-ID: <1271@pur-ee.UUCP>
Date: Fri, 16-Dec-83 18:28:03 EST
Article-I.D.: pur-ee.1271
Posted: Fri Dec 16 18:28:03 1983
Date-Received: Sun, 18-Dec-83 03:08:14 EST
Sender: notes@pur-ee.UUCP
Organization: Electrical Engineering Department , Purdue University
Lines: 24

#N:isrnix:3500001:000:1007
isrnix!greg    Dec 16 13:38:00 1983

    We are running a heavily modified version of UCB 2.8BSD on our
11/44.  I have noticed (as have others running 2.8 on other machines)
that an executable file containing nothing but the 16 byte header and
a magic word (407, 410, ...) will crash the system when executed.  I
should say that as long as the text/data/bss sizes in the header
are 0, the system will bite it.  I have done *some* debugging, but
nothing really substantial.  I >think< that the bug happens when the
system starts up the process - something like the machine faults when
the PC tries to read the first instruction (since the Memory Management
is set up with 0 length segments all around) and the trap code (or somebody
else) tries to find out what went wrong but messes up. Before I go
digging around, has anyone fixed this problem (that is, fixed the REAL
bug, not just put a patch in getxfile to disallow 0 length programs)?

		Thanks,

		Gregory Travis
		ihnp4!inuxc!isrnix!greg
		pur-ee!isrnix!greg
		cbosgd!qusavx!isrnix!greg