From owner-cvs-usrbin Thu Apr 24 22:32:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA25412 for cvs-usrbin-outgoing; Thu, 24 Apr 1997 22:32:15 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA25368; Thu, 24 Apr 1997 22:31:59 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id PAA16680; Fri, 25 Apr 1997 15:29:02 +1000 Date: Fri, 25 Apr 1997 15:29:02 +1000 From: Bruce Evans Message-Id: <199704250529.PAA16680@godzilla.zeta.org.au> To: bde@zeta.org.au, se@freebsd.org Subject: Re: vfork problem in gcc (was: Re: cvs commit: src/usr.bin/vacation vacation.c) Cc: ache@freebsd.org, cvs-all@freebsd.org, CVS-committers@freebsd.org, cvs-usrbin@freebsd.org Sender: owner-cvs-usrbin@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I had just fail "gcc -pipe" with an "vfork: interrupted system call" >(from memory) message. This happened reproducible with one certain >source file, removing "-pipe" allowed to compile that file, too ... >This might affect people doing a "make world" with "-pipe", I guess. >There is only one use of vfork in gcc.c (on line 2061). Lots of files >that are closed in the child, and it does call exit(), if the exec() >fails ... It seems OK except for the exit(). The exit code of -1 is also fishy. 127 might be right. Bruce