pghs975uc
/
infer_clone
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '76ad9915a1'
${ noResults }
infer_clone/infer/tests/codetoanalyze/objc/linters/issues.exp

52 lines
5.9 KiB
Raw Normal View History Unescape

[tests] record error bucket in expected output Summary: It's useful to test that the bucket a given error is classified as doesn't change over time without notice. This records the bucket for *all* the tests, even though some never produce a bucket. This is to be on the safe size instead of risking to forget adding the bucket information when the test changes, or when copy/pasting from a test that doesn't have buckets to one that does. The implementation is pretty crude: it greps the beginning of the qualifier string for a `[bucket]`. Reviewed By: mbouaziz Differential Revision: D8236393 fbshipit-source-id: b3b1eb9
7 years ago
codetoanalyze/objc/linters/Pointer_to_const_objc_class.m, Linters_dummy_method, 11, POINTER_TO_CONST_OBJC_CLASS, no_bucket, WARNING, []
[IR] Fix the function hashable_name for ObjC methods Summary: This function had been computing the name for ObjC methods wrong, with only the class name. This was causing wrong error messages in Pulse. The main issue was that `Procname.to_simplified_string` was writing `Classname::methodname` for ObjC methods, which is not the convention. This confused the `hashable_name` funtion. So changing the method name to `Classname.methodname` which is more standard, and this also fixes `hashable_name`. Reviewed By: ngorogiannis, jvillard Differential Revision: D21570880 fbshipit-source-id: 13ed62cf8
5 years ago
codetoanalyze/objc/linters/Weak_property_setter.m, Derived.setBaseAlternate, 65, DISCOURAGED_WEAK_PROPERTY_CUSTOM_SETTER, no_bucket, WARNING, []
codetoanalyze/objc/linters/Weak_property_setter.m, Derived.setBaseProp, 62, DISCOURAGED_WEAK_PROPERTY_CUSTOM_SETTER, no_bucket, WARNING, []
codetoanalyze/objc/linters/Weak_property_setter.m, Derived.setBaseWillBeImplementedInCategory, 93, DISCOURAGED_WEAK_PROPERTY_CUSTOM_SETTER, no_bucket, WARNING, []
codetoanalyze/objc/linters/Weak_property_setter.m, Derived.setDerivedCategoryProp, 89, DISCOURAGED_WEAK_PROPERTY_CUSTOM_SETTER, no_bucket, WARNING, []
codetoanalyze/objc/linters/Weak_property_setter.m, Derived.setDerivedProp, 68, DISCOURAGED_WEAK_PROPERTY_CUSTOM_SETTER, no_bucket, WARNING, []
codetoanalyze/objc/linters/Weak_property_setter.m, Derived.setProtocolProp, 71, DISCOURAGED_WEAK_PROPERTY_CUSTOM_SETTER, no_bucket, WARNING, []
codetoanalyze/objc/linters/Weak_property_setter.m, Derived.setWillBeImplementedInCategory, 97, DISCOURAGED_WEAK_PROPERTY_CUSTOM_SETTER, no_bucket, WARNING, []
[tests] record error bucket in expected output Summary: It's useful to test that the bucket a given error is classified as doesn't change over time without notice. This records the bucket for *all* the tests, even though some never produce a bucket. This is to be on the safe size instead of risking to forget adding the bucket information when the test changes, or when copy/pasting from a test that doesn't have buckets to one that does. The implementation is pretty crude: it greps the beginning of the qualifier string for a `[bucket]`. Reviewed By: mbouaziz Differential Revision: D8236393 fbshipit-source-id: b3b1eb9
7 years ago
codetoanalyze/objc/linters/assign_pointer.m, Linters_dummy_method, 16, ASSIGN_POINTER_WARNING, no_bucket, WARNING, []
codetoanalyze/objc/linters/assign_pointer.m, Linters_dummy_method, 18, ASSIGN_POINTER_WARNING, no_bucket, WARNING, []
codetoanalyze/objc/linters/assign_pointer.m, Linters_dummy_method, 20, ASSIGN_POINTER_WARNING, no_bucket, WARNING, []
codetoanalyze/objc/linters/assign_pointer.m, Linters_dummy_method, 36, ASSIGN_POINTER_WARNING, no_bucket, WARNING, []
[IR] Fix the function hashable_name for ObjC methods Summary: This function had been computing the name for ObjC methods wrong, with only the class name. This was causing wrong error messages in Pulse. The main issue was that `Procname.to_simplified_string` was writing `Classname::methodname` for ObjC methods, which is not the convention. This confused the `hashable_name` funtion. So changing the method name to `Classname.methodname` which is more standard, and this also fixes `hashable_name`. Reviewed By: ngorogiannis, jvillard Differential Revision: D21570880 fbshipit-source-id: 13ed62cf8
5 years ago
codetoanalyze/objc/linters/atomic_prop.m, A.bla, 97, DIRECT_ATOMIC_PROPERTY_ACCESS, no_bucket, WARNING, []
codetoanalyze/objc/linters/atomic_prop.m, A.bla, 98, DIRECT_ATOMIC_PROPERTY_ACCESS, no_bucket, WARNING, []
codetoanalyze/objc/linters/atomic_prop.m, A.readP, 76, DIRECT_ATOMIC_PROPERTY_ACCESS, no_bucket, WARNING, []
codetoanalyze/objc/linters/atomic_prop.m, A.readP, 76, POINTER_TO_INTEGRAL_IMPLICIT_CAST, no_bucket, WARNING, []
codetoanalyze/objc/linters/atomic_prop.m, A.readP, 77, POINTER_TO_INTEGRAL_IMPLICIT_CAST, no_bucket, WARNING, []
codetoanalyze/objc/linters/atomic_prop.m, A.readQ, 85, DIRECT_ATOMIC_PROPERTY_ACCESS, no_bucket, WARNING, []
codetoanalyze/objc/linters/atomic_prop.m, A.readQ, 85, POINTER_TO_INTEGRAL_IMPLICIT_CAST, no_bucket, WARNING, []
codetoanalyze/objc/linters/atomic_prop.m, A.writeQ, 81, DIRECT_ATOMIC_PROPERTY_ACCESS, no_bucket, WARNING, []
[objc frontend] Keep the counter for block names local to each procedure Reviewed By: skcho Differential Revision: D17282572 fbshipit-source-id: 116857a7e
5 years ago
codetoanalyze/objc/linters/atomic_prop.m, objc_block, 113, DIRECT_ATOMIC_PROPERTY_ACCESS, no_bucket, WARNING, []
[tests] record error bucket in expected output Summary: It's useful to test that the bucket a given error is classified as doesn't change over time without notice. This records the bucket for *all* the tests, even though some never produce a bucket. This is to be on the safe size instead of risking to forget adding the bucket information when the test changes, or when copy/pasting from a test that doesn't have buckets to one that does. The implementation is pretty crude: it greps the beginning of the qualifier string for a `[bucket]`. Reviewed By: mbouaziz Differential Revision: D8236393 fbshipit-source-id: b3b1eb9
7 years ago
codetoanalyze/objc/linters/badpointer.m, bad1, 15, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
Fix false positive BAD_POINTER for objcpp Reviewed By: dulmarod Differential Revision: D8658824 fbshipit-source-id: e582ce8
7 years ago
codetoanalyze/objc/linters/badpointer.m, bad10, 130, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
codetoanalyze/objc/linters/badpointer.m, bad11, 139, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
codetoanalyze/objc/linters/badpointer.m, bad12, 152, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
[tests] record error bucket in expected output Summary: It's useful to test that the bucket a given error is classified as doesn't change over time without notice. This records the bucket for *all* the tests, even though some never produce a bucket. This is to be on the safe size instead of risking to forget adding the bucket information when the test changes, or when copy/pasting from a test that doesn't have buckets to one that does. The implementation is pretty crude: it greps the beginning of the qualifier string for a `[bucket]`. Reviewed By: mbouaziz Differential Revision: D8236393 fbshipit-source-id: b3b1eb9
7 years ago
codetoanalyze/objc/linters/badpointer.m, bad2, 24, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
codetoanalyze/objc/linters/badpointer.m, bad3, 31, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
codetoanalyze/objc/linters/badpointer.m, bad4, 83, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
codetoanalyze/objc/linters/badpointer.m, bad5, 97, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
codetoanalyze/objc/linters/badpointer.m, bad6, 104, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
Fix false positive BAD_POINTER for objcpp Reviewed By: dulmarod Differential Revision: D8658824 fbshipit-source-id: e582ce8
7 years ago
codetoanalyze/objc/linters/badpointer.m, bad8, 119, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
codetoanalyze/objc/linters/badpointer.m, bad9, 126, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
[IR] Fix the function hashable_name for ObjC methods Summary: This function had been computing the name for ObjC methods wrong, with only the class name. This was causing wrong error messages in Pulse. The main issue was that `Procname.to_simplified_string` was writing `Classname::methodname` for ObjC methods, which is not the convention. This confused the `hashable_name` funtion. So changing the method name to `Classname.methodname` which is more standard, and this also fixes `hashable_name`. Reviewed By: ngorogiannis, jvillard Differential Revision: D21570880 fbshipit-source-id: 13ed62cf8
5 years ago
codetoanalyze/objc/linters/dispatch.m, B.sharedInstanceBAD, 33, WRONG_SCOPE_FOR_DISPATCH_ONCE_T, no_bucket, WARNING, []
codetoanalyze/objc/linters/implicit_cast.m, Implicit_cast.call_with_boxed_int, 67, POINTER_TO_INTEGRAL_IMPLICIT_CAST, no_bucket, WARNING, []
codetoanalyze/objc/linters/implicit_cast.m, Implicit_cast.call_with_string, 60, POINTER_TO_INTEGRAL_IMPLICIT_CAST, no_bucket, WARNING, []
codetoanalyze/objc/linters/implicit_cast.m, Implicit_cast.ivar_dictionary_item_call_funct_with_int, 45, POINTER_TO_INTEGRAL_IMPLICIT_CAST, no_bucket, WARNING, []
codetoanalyze/objc/linters/implicit_cast.m, Implicit_cast.property_with_int, 49, POINTER_TO_INTEGRAL_IMPLICIT_CAST, no_bucket, WARNING, []
[tests] record error bucket in expected output Summary: It's useful to test that the bucket a given error is classified as doesn't change over time without notice. This records the bucket for *all* the tests, even though some never produce a bucket. This is to be on the safe size instead of risking to forget adding the bucket information when the test changes, or when copy/pasting from a test that doesn't have buckets to one that does. The implementation is pretty crude: it greps the beginning of the qualifier string for a `[bucket]`. Reviewed By: mbouaziz Differential Revision: D8236393 fbshipit-source-id: b3b1eb9
7 years ago
codetoanalyze/objc/linters/implicit_cast.m, calling_funct_with_pointer, 15, POINTER_TO_INTEGRAL_IMPLICIT_CAST, no_bucket, WARNING, []
codetoanalyze/objc/linters/implicit_cast.m, calling_funct_with_pointer1, 20, POINTER_TO_INTEGRAL_IMPLICIT_CAST, no_bucket, WARNING, []
codetoanalyze/objc/linters/implicit_cast.m, calling_funct_with_pointer_from_a_method, 28, POINTER_TO_INTEGRAL_IMPLICIT_CAST, no_bucket, WARNING, []
codetoanalyze/objc/linters/implicit_cast.m, integer_nil, 23, POINTER_TO_INTEGRAL_IMPLICIT_CAST, no_bucket, WARNING, []
codetoanalyze/objc/linters/nsnumber.m, bad1, 11, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
codetoanalyze/objc/linters/nsnumber.m, bad2, 16, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
codetoanalyze/objc/linters/nsnumber.m, bad3, 21, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
codetoanalyze/objc/linters/nsnumber.m, bad4, 41, BAD_POINTER_COMPARISON, no_bucket, WARNING, []
[IR] Fix the function hashable_name for ObjC methods Summary: This function had been computing the name for ObjC methods wrong, with only the class name. This was causing wrong error messages in Pulse. The main issue was that `Procname.to_simplified_string` was writing `Classname::methodname` for ObjC methods, which is not the convention. This confused the `hashable_name` funtion. So changing the method name to `Classname.methodname` which is more standard, and this also fixes `hashable_name`. Reviewed By: ngorogiannis, jvillard Differential Revision: D21570880 fbshipit-source-id: 13ed62cf8
5 years ago
codetoanalyze/objc/linters/optional.m, Bar.unsafeAction, 21, UNSAFE_CALL_TO_OPTIONAL_METHOD, no_bucket, ERROR, []
[tests] record error bucket in expected output Summary: It's useful to test that the bucket a given error is classified as doesn't change over time without notice. This records the bucket for *all* the tests, even though some never produce a bucket. This is to be on the safe size instead of risking to forget adding the bucket information when the test changes, or when copy/pasting from a test that doesn't have buckets to one that does. The implementation is pretty crude: it greps the beginning of the qualifier string for a `[bucket]`. Reviewed By: mbouaziz Differential Revision: D8236393 fbshipit-source-id: b3b1eb9
7 years ago
codetoanalyze/objc/linters/strong_delegate.m, Linters_dummy_method, 13, STRONG_DELEGATE_WARNING, no_bucket, WARNING, []
codetoanalyze/objc/linters/strong_delegate.m, Linters_dummy_method, 17, STRONG_DELEGATE_WARNING, no_bucket, WARNING, []
codetoanalyze/objc/linters/strong_delegate.m, Linters_dummy_method, 19, STRONG_DELEGATE_WARNING, no_bucket, WARNING, []
codetoanalyze/objc/linters/strong_delegate.m, Linters_dummy_method, 21, STRONG_DELEGATE_WARNING, no_bucket, WARNING, []
codetoanalyze/objc/linters/strong_delegate.m, Linters_dummy_method, 23, STRONG_DELEGATE_WARNING, no_bucket, WARNING, []