facebook/infer

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

Open

#1083 opened on Apr 10, 2019

View on GitHub
 (8 comments) (0 reactions) (0 assignees)HTML (12,410 stars) (1,688 forks)batch import
cgood first taskhelp wanted

Description

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?

Contributor guide

Tech stack
None
Domain
tooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with InferBasic knowledge of static analysis
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
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.