From owner-freebsd-current@FreeBSD.ORG Mon Mar 15 14:29:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BB2316A4CE for ; Mon, 15 Mar 2004 14:29:03 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E16D43D1D for ; Mon, 15 Mar 2004 14:29:01 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 4545372DD2; Mon, 15 Mar 2004 14:29:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 40D8072DB5; Mon, 15 Mar 2004 14:29:01 -0800 (PST) Date: Mon, 15 Mar 2004 14:29:01 -0800 (PST) From: Doug White To: Steve Kargl In-Reply-To: <20040314213758.GA39459@troutmask.apl.washington.edu> Message-ID: <20040315142137.V33489@carver.gumbysoft.com> References: <20040314213758.GA39459@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: internal compiler error? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2004 22:29:03 -0000 On Sun, 14 Mar 2004, Steve Kargl wrote: > Anyone else see problems with collect2? Um, I don't have a /usr/libexec/collect2 on ANY system at my workplace, which is FreeBSD 4.x, FreeBSD 5.x, Solaris 8, and Debian 3.0. Perhaps you better check if your gcc has been modified. > > kargl[203] gcc -o h h.c > gcc: Internal error: Bad system call (program collect2) > Please submit a full bug report. > See for instructions. > kargl[204] cat h.c > #include > int main(void) { > printf("Hello world.\n"); > return 0; > } > > kargl[204] truss gcc -o h h.c > stat("/usr/libexec/collect2",0xbfbfe630) = 0 (0x0) > access("/usr/libexec/collect2",1) = 0 (0x0) > fork() = 938 (0x3aa) > SIGNAL 20 > wait4(0xffffffff,0xbfbfe73c,0x0,0x0) = 938 (0x3aa) > gcc: write(2,0xbfbfdfd0,5) = 5 (0x5) > Internal error: Bad system call (program collect2) > Please submit a full bug report. > See for instructions.write(2,0xbfbfdff0,140) = 140 (0x8c) > > write(2,0x806d4f3,1) = 1 (0x1) > stat("/var/tmp/cc7im6mN.o",0xbfbfe630) = 0 (0x0) > unlink("/var/tmp/cc7im6mN.o") = 0 (0x0) > stat("/var/tmp/cc2Mhzku.s",0xbfbfe630) = 0 (0x0) > unlink("/var/tmp/cc2Mhzku.s") = 0 (0x0) > exit(0x1) > process exit, rval = 256 > > Could this be caused by the Intel C/C++ compiler commits or the > recent commits by Peter to push gaint down into fork? > > > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org