Disassembly For Code Clone Detection System

Authors

  • Barkha Singh Deapartment of Computer Science, Gautam Buddha University, Greater Noida, India

DOI:

https://doi.org/10.37591/josettt.v2i2.414

Abstract

It is important to detect the clones in any software as there are various reasons for it. Code clones can affect the quality and maintainability of software. If there exists any bug in the code fragment then every similar cloned fragment will have to be detected to find the bug. Code cloning can also affect other things like design of the system and the size of the software system. Maintenance cost and resource requirements are also increased if there are a lot of code clones in any software. The detection of code clones require the disassembly of the code and then use it further to detect clones in the software. This proposed work presents the code clone detection system (CCDS) which is a process of how the disassembly of a program can be done using various tools that are available easily to the user. The disassembly involves instruction mnemonics (n-gram or n-perm) and control flow diagram. After this the disassembly can be incorporated into any open source search engine to find the code clones.

Keywords: Code clones, software, code clone detection system (CCDS), detection, mnemonics

 

 

Cite this Article
Barkha, Arun Solanki. Disassembly for Code Clone Detection System. Journal of Software Engineering Tools & Technology Trends. 2015; 2(2): 26–31p.

Author Biography

  • Barkha Singh, Deapartment of Computer Science, Gautam Buddha University, Greater Noida, India
    computer science (software engineering)

References

Roy CK, Cordy JR. A survey on code clone detection research. Queen's

University at Kingston Ontario, Canada; 2007. 01–115p.

Andreas S, Willcock J, Panas T, et al. Detecting code clones in binary

executables. Proceedings of the eighteenth international symposium on software testing and analysis. 2010. 01–11p.

Kodhai E, Perumal A, Kanmani S. Clone detection using textual and metric analysis to figure out all types of clones. International Journal of Computer Communication and Information System. 2010; 2(1): 01–05p.

Kumar R, Shilpa. Token based clone detection using program slicing. Int. J.ComputerTechnology & Applications. 2014; 5(4): 01–05p.

Raheja K, Tekchandani R. An emerging approach towards code clone detection: Metric based approach on byte code. International Journal of Advanced Research inComputer Science and Software Engineering. 2013; 3(5): 01–08p.

Khoo WM, Mycroft A, Anderson R. Rendezvous: A search engine for binary code. Proceedings of the 10th Working Conference on Mining Software; 2013. 01–10p.

Smith R, Horwitz S. Detecting and measuring similarity in code clones; 01–07p.

Designs S, Information D, Corporation E. Clone detection using abstract syntax trees; 1998. 01–11p.

Devi DG, Punithavalli M. An effective software clone detection using distance clustering. International Journal of Engineering and Technology. 2013; 5(1): 01–07p .

Aziz MA, North S. Retrieving software components using clone detection and program slicing; 2007: 01–38p.

Downloads

Published

2015-08-06

Issue

Vol. 2 No. 2 (2015)

Section

Review Articles

License

Declaration and Copyright Transfer Form

(to be completed by authors)

I/ We, the undersigned author(s) of the submitted manuscript, hereby declare, that the above manuscript which is submitted for publication in the STM Journals(s), is not published already in part or whole (except in the form of abstract) in any journal or magazine for private or public circulation, and, is not under consideration of publication elsewhere.

  • I/We will not withdraw the manuscript after 1 week of submission as I have read the Author Guidelines and will adhere to the guidelines.
  • I/We Author(s ) have niether given nor will give this manuscript elsewhere for publishing after submitting in STM Journal(s).
  • I/ We have read the original version of the manuscript and am/ are responsible for the thought contents embodied in it. The work dealt in the manuscript is my/ our own, and my/ our individual contribution to this work is significant enough to qualify for authorship.
  •  I/We also agree to the authorship of the article in the following order:

Author’s name                                    

 

1. ________________

2. ________________

3. ________________

4. ________________

 

We  Author(s) tick this box and would request you to consider it as our signature as we agree to the terms of this Copyright Notice, which will apply to this submission if and when it is published by this journal.