4 ms·
So is there some documentation on the "behavioral problems" their checker finds? If we know what to look out for, we can simply write some clippy lints to repli
by llogiq 11y ago
So is there some documentation on the "behavioral problems" their checker finds? If we know what to look out for, we can simply write some clippy lints to replicate the checks.
(https://github.com/Manishearth/rust-clippy https://github.com/Manishearth/rust-clippy)
- nickpsecurity 11y agoCpeterso already posted this link: https://msdn.microsoft.com/en-us/library/windows/hardware/ff550572(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/hardware/ff...
- _delirium 11y agoAnd here's a paper on the research underlying those tools: http://cacm.acm.org/magazines/2011/7/109893-a-decade-of-software-model-checking-with-slam/fulltext http://cacm.acm.org/magazines/2011/7/109893-a-decade-of-soft... One of the more successful cases of research out of Microsoft Research making it into production use in regular-Microsoft.
- nickpsecurity 11y agoI had the original papers on SLAM and driver verification. Didn't have this one. It's a great write-up with lots of useful data on a few, related topics. Thanks for the link.
- nickpsecurity 11y agoI just had time to look at clippy itself. Funny name given I imagined redoing Microsoft's Clippy in Rust still wouldn't fix it. :) I'm keeping the page in case I field Rust stuff as it's a nice list of things to look for. Not just for this tool but other developers applying CompSci solutions to Rust. They'll need a list of issues to encode in those.