facebook/infer

DEAD STORE reports many harmless cases like int i = 0xFFFFFFFF; i = SomeFunc();

Open

#1,083 建立於 2019年4月10日

在 GitHub 查看
 (8 留言) (0 反應) (0 負責人)HTML (12,410 star) (1,688 fork)batch import
cgood first taskhelp wanted

描述

infer version v0.15.0 in my case, 0xFFFF or 0xFFFFFFFF is a common initializer and there are a lot of this semantics in our code. I would like to ignore those harmless. but if I turn off liveness checker, I worry about missing some truely harmful bugs. Does Infer provide some filtering option or method?

貢獻者指南

技術棧
無
領域
tooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Familiarity with InferBasic knowledge of static analysis
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Investigate Infer's dead store detection logic in the liveness checker (likely in OCaml source). Determine if there is an existing filtering mechanism or if one can be added via command line options. Review the discussion in issue comments for maintainer suggestions. Propose a configuration option to ignore initializations with constant literals like 0xFFFFFFFF prior to overwriting.