Advanced

Squashing Bugs at the Source

Posted by dave on · 3 comments
Linux Magazine		Mail this story
Print this story

Based on new research, source code analysis has been used to find thousands of bugs in the Linux 2.6.x kernel. Here's how the technology works, what it can find, and why coding may never be the same again.

Full Story

  Nav
» Read more about: Groups: Kernel; Story Type: News Story

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

  Related stories
» More like this

Comments (3)

chris ·
Static code analysis is hardly interesting as it has been around for ages. They made a lint-like tool that has less "noise" and are selling it as a product. The article is just a real-world case-study of a few Linux bugs the tool has found. I'm not saying the tool isn't useful (I haven't tried it), but it should be properly labeled as "advertisement" and not "news." IMHO. Well, unless finding some bugs in the linux kernel is newsworthy...
tzafrir ·
This is now new, however this article is about the Stanford Checker, and the Stanford Checker has indeed found many problems in the kernel code. It is also worth mentioning that Linux is also working on a home-brew static-code testing of his own and that framework (albeit more limited) has also found its share of issues.
chris ·
Hmm, it would have been nice for the article to have at least mentioned the Stanford Checker. After reading your post, I see that Stanford is only even mentioned in the works cited section after the article end.

Did you mean "Linus" instead of Linux, regarding a home-brew?

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post