Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!philmtl!philabs!gotham!ursa!jmd From: jmd@ursa.UUCP (Josh Diamond) Newsgroups: comp.sources.bugs Subject: Re: Sun4os4 /bin/sh dumps core. (was: perl 3.0 dumps core) Message-ID: <1837@ursa.UUCP> Date: 12 Sep 89 16:18:02 GMT References: <550@caldwr.UUCP> <2256@hydra.Helsinki.FI> <2431@auspex.auspex.com> Reply-To: jmd@theodore.UUCP (Josh Diamond) Organization: Bear Stearns, New York Lines: 34 In article <2431@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes: >>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". Ah, but I _have_ managed to get /bin/sh to core dump with a segmentation fault under SunOS 4.0*. "file core" tells me that the core file is indeed from /bin/sh. It occurs when either the command line is very long or the environment is very large. It has bitten me several times in "make". Sun sent us a patched version of /bin/sh to fix it, and I beleive it has fixed the problem. If you are running into this, you should probably get in touch with Sun about it... Josh Diamond AKA Spidey!!! -- /\ \ / /\ Josh Diamond {philabs.phillips.com, sun.com}!gotham!ursa!jmd //\\ .. //\\ AKA Spidey!!! ...!{sun, pwcmrd, philabs, pyrnj}!gotham!ursa!jmd //\(( ))/\\ / < `' > \ Beauty is the purgation of superfluities. -- Michaelangelo