From owner-freebsd-current Tue Jan 12 21:28:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06606 for freebsd-current-outgoing; Tue, 12 Jan 1999 21:28:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06586 for ; Tue, 12 Jan 1999 21:28:44 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id VAA23729; Tue, 12 Jan 1999 21:27:37 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma023725; Tue, 12 Jan 99 21:27:12 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id VAA10163; Tue, 12 Jan 1999 21:27:12 -0800 (PST) From: Archie Cobbs Message-Id: <199901130527.VAA10163@bubba.whistle.com> Subject: Re: Weird file corruption? In-Reply-To: from Brian Feldman at "Jan 12, 99 08:59:04 pm" To: green@unixhelp.org (Brian Feldman) Date: Tue, 12 Jan 1999 21:27:12 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman writes: > Then I experienced problems compiling i86.c, which should have been (once > extracted again, this part of the archive wasn't corrupted) > static void i_xchg_axcx(void) /* Opcode 0x91 */ > { > XchgAXReg(CX); > } > but was > static > static voidaxcx(void) /* Opcode 0x91 */ > { > XchgAXReg(CX); > } > > So far, I really haven't seen this much, but I'm getting worried. Anyone have > any idea wha the problem is? Bad memory? Overclocking? Wasn't libz recently updated? (Does gzip use it?) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message