Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site trwrba.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!trwrba!jnelson
From: jnelson@trwrba.UUCP
Newsgroups: net.unix-wizards
Subject: Make makes shell dump core....
Message-ID: <905@trwrba.UUCP>
Date: Wed, 29-Aug-84 12:19:38 EDT
Article-I.D.: trwrba.905
Posted: Wed Aug 29 12:19:38 1984
Date-Received: Sat, 1-Sep-84 11:15:08 EDT
Organization: TRW EDS, Redondo Beach, CA
Lines: 37

Subject: Memory fault in shell using make...
Newsgroups: net.unix-wizards

	Subject: bug in 4.2 /bin/make

	SYSNOPSIS:
	    make sometimes dumps core with a memory fault or segmentation fault

Yes, I have seen the same behavior with our make, however
our shell blows up ONLY when make tries to do a make depend.

Needless to say, I'm somewhat concerned... especially if the
bug is in the kernel.

Using our brand new friend, Mr. DBX, I find that the command string
from the makefile is passed properly to the Bourne Shell, by make.
After the shell is vforked we suddenly intercept a trap and a maze of
4.2 signal routines are called (apparently due to some sort of
memory problem from within the shell) with a core dumped.

Make performs fine when I try to remake, say ''make'' or
any other particular piece of code.  When I try to remake the
kernel, however, the bourne shell goes bonkers.  But what
could be making the Bourne shell barf like this?

The makefiles in /usr/sys look okay, and I haven't made any
kernel changes yet.  Only reconfiguration of the system
hardware.  I don't think it has anything to do with swap space.

Now, I'm not exactly desparate or anything.... I took the cheap
and easy way out and reloaded the system code from tape (heh heh).
But I still find it disconcerting that such can happen.
Thanks in advance if you have any suggestions or fixes.



						- John