Tags: waooog/infer
Tags
[infer][java] Always consider the close() method to be potentially cl… …osing a resource Summary: It seems that the `close()` method that should normally be called on an object `obj` of type `java.io.Closeable` is sometimes called on `obj` of type `java.lang.Object`. It did not fully understand in which case this happens but it could be coming from a bug in Sawja since the type of `obj` in the bytecode is correct, but the Sawja reciever expression given to the Java frontend has the type `java.lang.Object`. In any case, it does not hurt to always consider that `obj.close()` will replace the `FILE` attribute on `obj` by a `MEM` attribute. Reviewed By: sblackshear Differential Revision: D4540627 fbshipit-source-id: 71f9c95
do not print infer.py usage message on wrong arguments Summary: On wrong arguments (or on no arguments at all), `infer` would spew the error message of `infer.py`, which makes no sense. Make the python code swallow error messages and exit with a special code on errors coming from command line parsing so that the OCaml side is in charge of printing usage messages. Reviewed By: cristianoc Differential Revision: D3731594 fbshipit-source-id: fe49cda
update clang command-line flags that we filter out Summary:Open-source clang has caught up a bit with apple's clang, so we don't need to filter as many compilation flags as we used to. Reviewed By: akotulski, martinoluca Differential Revision: D3212553 fb-gh-sync-id: 5638dc8 fbshipit-source-id: 5638dc8
PreviousNext