The Checker postings are appreciated by the kernel developers, since they have pointed out a large number of real bugs. It would be even nicer if the Checker were available for others to use, but that is not the case. The MC group still has not released its work, which, it claims, remains incomplete. So there is little to do except to wait for the next posting.
Dan Carpenter, however, got tired of waiting and set out to create his own MC-like system. The result is Smatch, which was announced on the kernel janitors' list on January 1. Smatch attempts to duplicate the techniques used in the Stanford Checker, as derived from papers published by the MC group. It is still very much a work in progress; rather than producing nice reports, Smatch creates large amounts of raw data which must then be filtered with Perl scripts. An initial set of scripts exists, but quite a bit of work remains to be done in that area.
So Smatch probably will not be putting the Stanford Checker out of business
anytime soon. But it will provide a platform for the development of
freely-available checking tool with similar capabilities. With luck, and
some development time, Smatch should help in the creation of more stable
kernels in the near future.
Posted Jan 13, 2003 5:01 UTC (Mon)
by jzbiciak (guest, #5246)
[Link]
Posted Jan 16, 2003 14:30 UTC (Thu)
by MikeDiack (guest, #3036)
[Link]
www.splint.org Also GPLed - it's the standard C lint tool but with a number of enhancements, including memory allocation checking (leaks, overruns etc).
What would be really interesting is if Smatch gets cleaned up enough to become part of GCC itself. I think such a development could lead to a more robust system overall, since the checks it performs could be applied to userspace utilities.Smatch - a Stanford Checker for the rest of us
Other good tools for source checking:Smatch - a Stanford Checker for the rest of us
Copyright © 2003, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds