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" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > 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). > > _______________________________________________ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"