[CUWiN] code audit; testing

[Zachary C. Miller]

The guy who runs coverity actually already offered to run their
analysis on our code when we're ready. If we're ready, I'll let him
know.

Arun Bhalla wrote:
> David Young writes:
> > Is anybody interested in auditing CUWiN's HSLS/ETX code for memory leaks,
> > buffer overflows, and other flaws?  I get the feeling that the routing
> > code has had very few eyes on it, apart from Bryan's and mine.
> 
> This sounds like you'd be best off with Coverity
> (http://www.coverity.com/).  Zach and I know one of the founders; maybe
> Zach could convince him to run their code analysis software on CUWiN's
> code.
> 
> Barring that, you might give http://smatch.sourceforge.net/ a try.  It's
> based on the same papers as Coverity, but uh, the Coverity peeps wrote
> those papers.
> 
> Arun
> _______________________________________________
> CU-Wireless mailing list
> CU-Wireless at lists.groogroo.com
> http://lists.cu.groogroo.com/cgi-bin/listinfo/cu-wireless
> Project Page: http://cuwireless.ucimc.org
> 

-- 
Zachary C. Miller - @= - http://wolfgang.groogroo.com/
IMSA 1995 - UIUC 2000 - Just Another Leftist Muppet - Ya Basta!
 Social Justice, Community, Nonviolence, Decentralization, Feminism,
 Sustainability, Responsibility, Diversity, Democracy, Ecology