5 ms·
Seems like mentioning the sorts of bugs this can detect should be the most important thing on the landing page.
by adamnemecek 11y ago
Seems like mentioning the sorts of bugs this can detect should be the most important thing on the landing page.
- amirmc 11y agoI found a list at http://fbinfer.com/docs/infer-bug-types.html http://fbinfer.com/docs/infer-bug-types.html
- adamnemecek 11y agothanks.
- hiou 11y ago> At present, the analyzer reports problems caused by null pointer access and resource and memory leaks, which cause a large percentage of app crashes. Did you mean you were looking for something more specific?
- adamnemecek 11y agoI was looking for something like this http://fbinfer.com/docs/infer-bug-types.html http://fbinfer.com/docs/infer-bug-types.html
- jdp23 11y agoThe list is at http://fbinfer.com/docs/infer-bug-types.html http://fbinfer.com/docs/infer-bug-types.html For Java, it's Resource leaks and Null dereferences For C and Objective C, the list is Resource leak Memory leak Null dereference Parameter not null checked Ivar not null checked Premature nil termination argument
- Animats 11y agoUnfortunately, it doesn't detect the big one in C - out of range subscripts/buffer overflows. That's hard, but other verifiers have done it.