Date: Wed, 13 Jan 1999 17:26:40 -0500 (EST) From: Brian Feldman <green@unixhelp.org> To: Archie Cobbs <archie@whistle.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Weird file corruption? Message-ID: <Pine.BSF.4.05.9901131724420.19040-100000@janus.syracuse.net> In-Reply-To: <199901130527.VAA10163@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Jan 1999, Archie Cobbs wrote:
> 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)
Wait a second here: I extracted it once and the archive reported no errors!
Gzip and tar were fine with it.
> > 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?)
How could it be memory when it's written to disk, extracted, then after a nearly
full build read again? Why would it extract completely the first time with no
errors?
>
> -Archie
>
> ___________________________________________________________________________
> Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
>
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9901131724420.19040-100000>