Flow analysis to detect blocked statements

Malenfant, Bruno; Antoniol, G.; Merlo, Ettore; Dagenais, Michel R.

doi:10.1109/icsm.2001.972712

Cited by 2 publications

(2 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Slicing tends to follow one of two strategies. First, static slicing identifies all candidate dependencies of a given statement, relying purely on analysis of the source code . The static approach tends to create very large slices, between 30 and 60% of the program .…”

Section: Related Workmentioning

confidence: 99%

Pragmatic source code reuse via execution record and replay

Armaly

McMillan

2016

J Software Evolu Process

View full text Add to dashboard Cite

A key problem during copy-paste source code reuse is that, to reuse even a small section of code from a program as opposed to an API, a programmer must include a huge amount of additional source code from elsewhere in the same program. This additional code is notoriously large and complex, and portions can only be identified at runtime. In this paper, we propose execution record/replay as a solution to this problem. We describe a novel reuse technique that allows programmers to reuse functions from a C or C++ program, by recording the execution of the program and selectively modifying how its functions are replayed. We have implemented our technique and evaluated it in an empirical study in which eight programmers used our tool to complete four tasks over four hours each. The participants found our technique to be easier than manually reusing the code as part of their project. We also found that the resulting code was smaller and less complex than it would have been had the participants manually reused the code.

show abstract

Section: Related Workmentioning

confidence: 99%

Pragmatic source code reuse via execution record and replay

Armaly

McMillan

2016

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…This article presents new and original flow equations used to perform the data flow analysis that extracts "blocked levels" information and which is based on a previously defined boolean blocked statements analysis [10]. A standard exchange format is used for input and output of the software: GXL (Graph eXchange Language), an XML standard for graph representation [5].…”

Section: Introductionmentioning

confidence: 99%

Fast flow analysis to compute fuzzy estimates of risk levels

Merlo

Antoniol²,

Brunelle³

Seventh European Conference onSoftware Maintenance and Reengineering, 2003. Proceedings.

Self Cite

View full text Add to dashboard Cite

In the context of software quality assessment, this paper proposes original flow analyses which propagate numerical estimates of blocking risks along an inter-procedural Control Flow Graph (CFG) and which combine these estimates along the different CFG paths using fuzzy logics operations.Two specialized analyses can be further defined in terms of definite and possible flow analysis. The definite analysis computes the minimum blocking risk levels that statements may encounter on every path, while the possible analysis computes the highest blocking risk levels encountered by statements on at least one path. This paper presents original flow equations to compute the definite and possible blocking risk levels for statements in source code. The described fix-point algorithm presents a linear execution time and memory complexity and it is also fast in practice.The experimental context used to validate the presented approach is described and results are reported and discussed for eight publicly available systems written in C whose total size is about 300 KLOC. Results show that the analyses can be used to compute, identify and compare definite and possible blocking risks in software systems. Furthermore, programs which are known to be synchronized like "samba" show a relatively high level of blocking risks. On the other hand, the approach allows to identify even low levels of blocking risks as those presented by programs like "gawk".Suggestions for further research are also presented.

show abstract

Flow analysis to detect blocked statements

Cited by 2 publications

References 13 publications

Pragmatic source code reuse via execution record and replay

Pragmatic source code reuse via execution record and replay

Fast flow analysis to compute fuzzy estimates of risk levels

Contact Info

Product

Resources

About