_shb

3 ms·

1.
by _shb 10y ago
Infer has a thread-safety checker that identifies races in classes annotated with `@ThreadSafe` ( http://fbinfer.com/docs/experimental-checkers.html ).
2.
by _shb 10y ago
I added some documentation on using Inferbo and other experimental checkers we are working on: http://fbinfer.com/docs/experimental-checkers.html . All you need to do to use Inferbo is add `-a bufferoverrun` to your nor
3.
by _shb 10y ago
Thanks for pointing this out! Fixed in an update to the post.
4.
Inferbo: Infer-based buffer overrun analyzer(research.fb.com)
25 points by _shb 10y ago|6 comments
5.
by _shb 11y ago
Infer does bottom-up analysis: it starts at the bottom of the call graph and analyzes each procedure once independently of its callers. Analyzing the procedure produces a concise summary of its behavior that can be used in each calling proc
6.
by _shb 11y ago
There was indeed a typo in the description; it has been fixed. Sorry for the confusion!
7.
by _shb 11y ago
To paint these tools with an overfly broad brush, they linter-like in that they perform shallow intra-procedural analysis to identify common bug patterns (e.g., if (x != null) { y = x.f } z = x.f // possible NPE; x was previousl
8.
by _shb 11y ago
Yes, it can be used with most Java code you can build on the command line. Just run "infer -- <your_build_command>". Currently, this works with javac, Ant, Maven, and Gradle. See http://fbinfer.com/docs/
9.
by _shb 11y ago
This paper describes some aspects of the system: http://research.microsoft.com/pubs/189242/pldi097-burckhardt...