From owner-freebsd-questions Mon Oct 19 09:24:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20592 for freebsd-questions-outgoing; Mon, 19 Oct 1998 09:24:15 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from castor.chuck (lucy.bedford.net [206.99.145.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20586 for ; Mon, 19 Oct 1998 09:24:12 -0700 (PDT) (envelope-from listread@bedford.net) Received: (from listread@localhost) by castor.chuck (8.8.8/8.8.8) id MAA15950; Mon, 19 Oct 1998 12:13:05 -0400 (EDT) (envelope-from listread) Message-Id: <199810191613.MAA15950@castor.chuck> Subject: Re: Is there a ) in mktemp.c ? In-Reply-To: <36293A77.D95CFF87@pc.jaring.my> from Jahan at "Oct 17, 98 05:46:47 pm" To: jahan@pc.jaring.my Date: Mon, 19 Oct 1998 12:13:05 -0400 (EDT) Cc: freebsd-questions@FreeBSD.ORG X-no-archive: yes X-Echelon: aerosol dispersal modalities Reply-to: djv@bedford.net From: "Woodchuck" X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jahan wrote: > Hi all, > Have you all got a ")" in /usr/src/lib/libc/stdlib/mktemp.c line > 98 int p)d,rval ? > > Jahan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > The file is in ..../stdio/mktemp.c, not stdlib. The line in question should read int pid,rval; This is a single bit error, ')' = 051 or 0x29, 'i' = 0151 or 0x69. Somebody, somewhere, dropped the ball -- the usual suspect is the memory on your machine; second suspect is a bad block on a disk drive. I usually suspect memory. Are you getting SIGSEGV (Sig 11) or Bus Errors (Sig 8) when compiling? On a machine with known bad memory, I have seen these single-bit errors in the intermediate asm files produced when compiling, and in object files as well, sometimes producing mysteriously unworking executables. It could have been a glitch anywhere in the history of this file. If you are using a SCSI disk, you might want to do a surface scan from the BIOS. (I think it's memory though -- If everybody used ECC memory, these problems would vanish). Dave -- Strangers know my loved ones' phone numbers!!!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message