From owner-freebsd-bugs  Sun Aug 18 12:50:16 2002
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C53B137B400
	for <freebsd-bugs@hub.freebsd.org>; Sun, 18 Aug 2002 12:50:14 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 593FF43E7B
	for <freebsd-bugs@hub.freebsd.org>; Sun, 18 Aug 2002 12:50:14 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g7IJo5JU046549
	for <freebsd-bugs@freefall.freebsd.org>; Sun, 18 Aug 2002 12:50:05 -0700 (PDT)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g7IJo5iR046548;
	Sun, 18 Aug 2002 12:50:05 -0700 (PDT)
Date: Sun, 18 Aug 2002 12:50:05 -0700 (PDT)
Message-Id: <200208181950.g7IJo5iR046548@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Bruce Evans <bde@zeta.org.au>
Subject: Re: i386/41723: Copying files to filesystem causes "integer divide
 fault" and panic.
Reply-To: Bruce Evans <bde@zeta.org.au>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR i386/41723; it has been noted by GNATS.

From: Bruce Evans <bde@zeta.org.au>
To: Tha KreAture <Tha_KreAture@hotmail.com>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/41723: Copying files to filesystem causes "integer divide
 fault" and panic.
Date: Mon, 19 Aug 2002 05:52:11 +1000 (EST)

 On Sat, 17 Aug 2002, Tha KreAture wrote:
 
 >  Well.  It looks like a change from int to long was enough.  Now the system
 >  is acting fine.
 
 Er, int is the same as long on i386's.
 
 >  I understand this is one of the things already fixed in 5.0 ?
 
 I don't know if this particular bug was fixed.  Some similar bugs were
 probably fixed without really noticing by changing int and long typedefed
 types to int64_t.  int64_t really is longer than int on i386's :-).
 
 Bruce
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message