1994
DOI: 10.1109/32.286418
|View full text |Cite
|
Sign up to set email alerts
|

Interprocedural def-use associations for C systems with single level pointers

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
60
0
2

Year Published

1996
1996
2012
2012

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 122 publications
(62 citation statements)
references
References 44 publications
0
60
0
2
Order By: Relevance
“…We also find a suitable contextsensitivity for points-to analysis to differentiate invocations in different execution paths, and define the rule to handle API invocations with multi-source arguments, in order to ensure that for each different way of API invocation, a corresponding object is constructed. Finally, we record the group of arguments used in each way of API invocation, and designed a slicing algorithm to locate the relevant instructions from the recorded argument objects and the def-relation [6] between instructions and objects, without constructing the full execution traces from scratch.…”
Section: Approach Overviewmentioning
confidence: 99%
See 1 more Smart Citation
“…We also find a suitable contextsensitivity for points-to analysis to differentiate invocations in different execution paths, and define the rule to handle API invocations with multi-source arguments, in order to ensure that for each different way of API invocation, a corresponding object is constructed. Finally, we record the group of arguments used in each way of API invocation, and designed a slicing algorithm to locate the relevant instructions from the recorded argument objects and the def-relation [6] between instructions and objects, without constructing the full execution traces from scratch.…”
Section: Approach Overviewmentioning
confidence: 99%
“…We believe the deeper points-to analysis techniques, such as the consideration of reflections [18], will improve the application scope of our approach, but we leave this for future work. The inference of different API invocations is related to the def-use analysis [6], but we also need to clarify all the individual and sufficient compositions of the used objects. The construction of snippet contents is a typical data-flowbased code slicing [4].…”
Section: User Studymentioning
confidence: 99%
“…This problem has been extensively investigated and several coverage criteria have been defined [13]. In particular, a widely used coverage criterion is "all def-use pairs" [14], which requires a test suite that executes all possible pairs of definition and uses for variables in the program under test.…”
Section: Generation Of Tests For Sequences Of Operationsmentioning
confidence: 99%
“…The development of efficient and precise dependence analysis algorithms continues as an active area of research in the programming languages and software engineering communities (e.g., [3,8,10,19]). …”
Section: Refining Chainsmentioning
confidence: 99%