News for hackers. Stuff that matters.
Re:A common bug in published code by bnewbold on Thursday April 21, 2011 @07:04PM (#2472711)
I've been thinking of doing something and i'm looking for people to work with! Notes here: http://memeschemes.com/code_search/
Re:A common bug in published code by mbenjaminsmith on Thursday April 21, 2011 @10:38PM (#2473137)
A bug in that program would certainly be wonderful. Have fun when it files a few million unnecessary bug reports while you're sleeping.
Re:A common bug in published code by mail2345 on Thursday April 21, 2011 @11:00PM (#2473165)
Have it require approval for each bug report. While it isn't as fast as a fully automatic bug finding system, it is faster than a manual find and file. Plus it takes care of those situations where it was intended(poor coding, but it works).
Re:A common bug in published code by bobds on Friday April 22, 2011 @12:54AM (#2473321)
I've had some similar ideas myself, consider me interested. I've written some (very little) code to search projects among the big open source hosts (SF, Google, Github etc). Also have a nice domain for it.
Re:A common bug in published code by wladimir on Friday April 22, 2011 @05:24AM (#2473622)
This will be very useful as long as it finds confirmed bugs. Otherwise it will be more like an unasked-for code style check (For example, one can argue using functions like strcpy are unsafe, but unless it's really possible to get too many characters in the buffer, it's not a bug)