Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!uakari.primate.wisc.edu!ctrsol!ginosko!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.sources.bugs
Subject: Re: Sun4os4 /bin/sh dumps core. (was: perl 3.0 dumps core)
Message-ID: <2431@auspex.auspex.com>
Date: 9 Sep 89 18:23:53 GMT
References: <550@caldwr.UUCP> <SCHWARTZ.89Sep7220013@shire.cs.psu.edu> <FLEE.89Sep7225002@shire.cs.psu.edu> <2256@hydra.Helsinki.FI>
Reply-To: guy@auspex.auspex.com (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 16

>Probably not so.  I have perl 3.0-beta running on Sun 3's (under SunOS 4.0.3)
>but it (or actually sh) dumps core

Uhh, excuse me, but please do NOT assume that because the string "sh:"
appears in the "core dumped" message that it's the shell that's dumping
core.  In fact, in the case I saw when running "make test" on a Sun-4,
it's the shell that's telling you that something *else*, namely Perl,
dumped core - yes, even if your shell is the C shell, since "make" is
running Perl from the Makefile and it uses the Bourne shell for
everything on SunOS. 

If you want to know what program generated a core file on SunOS 3.x or
4.x, do "file core".

The problem is, as Larry Wall and I noted, a "vfork"-related problem
(and merely including <vfork.h> doesn't seem to fix it).