From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 16 21:00:08 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08BE916A4CF for ; Fri, 16 Jan 2004 21:00:07 -0800 (PST) Received: from mx01.netapp.com (mx01.netapp.com [198.95.226.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAD9443D60 for ; Fri, 16 Jan 2004 20:59:57 -0800 (PST) (envelope-from kmacy@netapp.com) Received: from frejya.corp.netapp.com (frejya [10.57.157.119]) i0H4xuKw021737; Fri, 16 Jan 2004 20:59:56 -0800 (PST) Received: from cranford (cranford-fe.eng.netapp.com [10.56.10.106]) i0H4xups016749; Fri, 16 Jan 2004 20:59:56 -0800 (PST) Date: Fri, 16 Jan 2004 20:59:56 -0800 (PST) From: Kip Macy X-Sender: kmacy@cranford-fe.eng.netapp.com To: Xin LI In-Reply-To: <03f801c3dcaf$aa099c90$0401a8c0@phantasm205> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: [CHECKER] bugs in FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2004 05:00:08 -0000 Dawson is the man. http://www.stanford.edu/~engler/ ================================================================ If I have not seen as far as others, it is because I have been standing in the footprints of giants. -- from Usenet On Fri, 16 Jan 2004, Xin LI wrote: > Hello, > > The tool is amazing :) > > I am very interested in how does it work, is there any paper published on > this topic? > Thanks in advance! > > Xin LI, > Beijing University of Technology > > ----- Original Message ----- > From: "Paul Twohey" > To: > Sent: Saturday, January 17, 2004 8:01 AM > Subject: [CHECKER] bugs in FreeBSD > > > > Hi, > > > > I'm with the Stanford Metacompilation research group. We have a suite of > > checkers that find bugs at compile time and we've had quite a bit of > > success checking the Linux kernel code for errors. Since our checkers can > > emit false alarms we filter the reports before we give them to the kernel > > developers. While some false alarms slip past us to the developers, our > > limited knowledge of the kernel allows us to recognize most of them. > > > > We are currently trying to extend our checker to automatically find > > functions which allocate resources and to make sure those resources are > > properly disposed of. > > > > Enclosed is a list of potential bugs in FreeBSD where a value is returned > > from a function (like malloc) that should be owned by the caller and the > > caller does not properly dispose of the value with the appropriate > > disposal routine (like free). > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >