[CUWiN] code audit; testing

[Arun Bhalla]

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