From owner-freebsd-bugs  Fri Jun 11 14: 0: 6 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 650A514C93
	for <freebsd-bugs@FreeBSD.org>; Fri, 11 Jun 1999 14:00:02 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id OAA08657;
	Fri, 11 Jun 1999 14:00:02 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Date: Fri, 11 Jun 1999 14:00:02 -0700 (PDT)
Message-Id: <199906112100.OAA08657@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: "David Schwartz" <davids@webmaster.com>
Subject: Re: kern/12141: libc_r passes negative tv_usec values to setitimer -- crash
Reply-To: "David Schwartz" <davids@webmaster.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

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

From: "David Schwartz" <davids@webmaster.com>
To: <freebsd-gnats-submit@freebsd.org>,
	"David Schwartz" <davids@webmaster.com>
Cc:  
Subject: Re: kern/12141: libc_r passes negative tv_usec values to setitimer -- crash
Date: Fri, 11 Jun 1999 13:50:44 -0700

 	Even that is not enough. Apparently tv_sec can be <0 too:
 
 Cannot set scheduling timer, errno=22, v.s=-1, v.us=1000
 
 	Presumable, usec was set to 1,000 by my hack. But the seconds were negative
 too! This crash is rarer than the one where just the usec value is negative.
 Here's my new hacked fix:
 
                                 if ( (itimer.it_value.tv_usec<0) ||
                                      (itimer.it_value.tv_sec<0) )
                                 {
                                  itimer.it_value.tv_usec=1000;
                                  itimer.it_value.tv_sec=0;
                                 }
 
 	David Schwartz
 
 


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