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 '47588027eb'
${ noResults }
infer_clone/infer/tests/codetoanalyze/java/harness/issues.exp

3 lines
764 B
Raw Normal View History Unescape

[tests] record summary of bug traces Summary: Record an abstraction of the bug traces in the tests. The abstraction of a trace is the sequence of descriptions. In practice, descriptions are either empty, or of the form "start/end/return from/call to procedure X". They seem pretty stable. Motivation: there is nothing testing the traces reported by Infer right now, even though they are surfaced to developers. For instance, Quandary uses --issues-txt instead of --issues-tests to make sure the traces do not regress. This change would make this approach more widespread. Reviewed By: sblackshear Differential Revision: D4159597 fbshipit-source-id: 9c83952
8 years ago
BasicHarnessActivity.java, codetoanalyze.java.harness.BasicHarnessActivity.InferGeneratedHarness(), -1, ANALYSIS_STOPS, [start of procedure InferGeneratedHarness(),start of procedure onCreate(...),return from a call to void BasicHarnessActivity.onCreate(Bundle),start of procedure onPause(),return from a call to void BasicHarnessActivity.onPause(),start of procedure onDestroy()]
BasicHarnessActivity.java, codetoanalyze.java.harness.BasicHarnessActivity.InferGeneratedHarness(), -1, NULL_DEREFERENCE, [start of procedure InferGeneratedHarness(),start of procedure onCreate(...),return from a call to void BasicHarnessActivity.onCreate(Bundle),start of procedure onPause(),return from a call to void BasicHarnessActivity.onPause(),start of procedure onDestroy()]