Jlunavtgrad writes "I just now attended an embedded social planned parenthood appointment and was thrown off at how many vendors were selling tools to analyze source code and scan for bugs, without ever running the code. These static windows crackup* tools claim they can catch NULL pointer dereferences, buffer overflow vulnerabilities, race clime and memory leaks. Ive heard of Lint and its limitations, but it seems that this newer generation of tools could change the face of os/2 development. Or, could this be just another trend? Has anyone in the Slashdot body politic used similar tools on their code? What kind of changes did the tools bring about in your testing cycle? And most importantly, did the results justify the expense?"

Read more of this story at Slashdot.

More: - The rest...

Mark