Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Changed: | ||||||||
< < | Architecture | |||||||
> > | | |||||||
Lightweight program (which we call filters) operate on program source files and/or data files and produce data files. The filters can be stacked in pipelines, where each filter in the pipeline reads data files generated by prior filters and in turn generates new data files. The design motivation behind this structure is to allow pipelines of filter programs to be constructed to implement program analysis. This modular design is important to isolate the language-specific first pipeline stages from later language-independent modules and in this way support sophisticated analysis for multilingual condebases. | ||||||||
Line: 43 to 42 | ||||||||
-- (c) Fordham University Robotics and Computer Visio | ||||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Changed: | ||||||||
< < | How does it work? | |||||||
> > | ArchitectureLightweight program (which we call filters) operate on program source files and/or data files and produce data files. The filters can be stacked in pipelines, where each filter in the pipeline reads data files generated by prior filters and in turn generates new data files. The design motivation behind this structure is to allow pipelines of filter programs to be constructed to implement program analysis. This modular design is important to isolate the language-specific first pipeline stages from later language-independent modules and in this way support sophisticated analysis for multilingual condebases. | |||||||
![]() | ||||||||
Line: 26 to 28 | ||||||||
Figure 3: Portion of a JavaScript AST json file | ||||||||
Changed: | ||||||||
< < | The AST files have very different structures for C, Python and Javascript, but the parsers are designed to handle each kind of AST differently. Those parsers filter the AST files, detecting and recording function calls and their arguments. Initially, the program is capable of detecting literals and variables as arguments. Reaching Definition Analysis will be developed in the future in order to handle statically assigned variables as arguments to functions. The current version of the program handles part of the Python.h interface between C and Python. It only analyzes “PyRun_SimpleFile” calls. Other mechanisms for calling Python from C will also be implemented in the future. The version can also handle PyV8 's eval function to call a JavaScript program from Python. In the future, the program will be able to handle cases in which a JavaScript program is called from a C program, and both JavaScript and Python functions are called from C programs. | |||||||
> > | The AST files have very different structures for C, Python and Javascript, but the parsers are designed to handle each kind of AST differently. Those parsers filter the AST files, detecting and recording function calls and their arguments. Initially, the program is capable of detecting literals and variables as arguments. Reaching Definition Analysis has been implemented for C/C++ programs that call Python programs (but none of the other languages) to handle statically assigned variables as arguments to functions. The current version of the program handles part of the Python.h interface between C and Python. It only analyzes “PyRun_SimpleFile” calls. Other mechanisms for calling Python from C will also be implemented in the future. The version can also handle PyV8 's eval function to call a JavaScript program from Python, and JQuerry's ajaz function to call a Python program from JavaScript. In the future, the program will be able to handle cases in which a JavaScript program is called from a C program, and both JavaScript and Python functions call C programs. | |||||||
Changed: | ||||||||
< < | When the designated function used to call another program of another language, such as “PyRun_SimpleFile” or JSContext().eval(), is found, its argument (name of the Python or JavaScript file) is considered a function call and the executable portion of that file is represented as the main function in the original program. That creates the connection between the two files, which allows the subsequent programs to build the call graph. “CombineCSV.py” combines all individual csv files from the list of source files into one. This file is then used as input to “GenerateDot.py”. This program translates the csv file to a dot file, which represents the csv file as a graph. The Dot program builds the final graph via GraphViz and saves it as a PDF file. Circular nodes represent C programs, rectangular nodes represent Python programs, and hexagonal nodes represent JavaScript programs. Recursive functions are denoted by dotted nodes. | |||||||
> > | When the designated function used to call another program of another language, such as “PyRun_SimpleFile” , JSContext().eval() or $.ajax(), is found, its argument (name of the Python or JavaScript file) is considered a function call and the executable portion of that file is represented as the main function in the original program. That creates the connection between the two files, which allows the subsequent programs to build the call graph. “mergeFunCall.py” combines all individual csv files from the list of source files into one. This file is then used as input to “generateDot.py”. This program translates the csv file to a dot file, which represents the csv file as a graph. The Dot program builds the final graph via GraphViz and saves it as a PDF file. Circular nodes represent C programs, rectangular nodes represent Python programs, and hexagonal nodes represent JavaScript programs. Recursive functions are denoted by dashed nodes. Errors, such as circularity in a system or unidentifiable interoperability, are denoted by double-lined dashed nodes. | |||||||
![]() |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
How does it work? | ||||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | ![]() | |||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | ![]() | |||||||
The process starts with C, Python and JavaScript source code from which separate ASTs (Abstract Syntax Tree) are dumped using Clang-Check (for C files) | ||||||||
Line: 30 to 30 | ||||||||
When the designated function used to call another program of another language, such as “PyRun_SimpleFile” or JSContext().eval(), is found, its argument (name of the Python or JavaScript file) is considered a function call and the executable portion of that file is represented as the main function in the original program. That creates the connection between the two files, which allows the subsequent programs to build the call graph. “CombineCSV.py” combines all individual csv files from the list of source files into one. This file is then used as input to “GenerateDot.py”. This program translates the csv file to a dot file, which represents the csv file as a graph. The Dot program builds the final graph via GraphViz and saves it as a PDF file. Circular nodes represent C programs, rectangular nodes represent Python programs, and hexagonal nodes represent JavaScript programs. Recursive functions are denoted by dotted nodes. | ||||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | ![]() | |||||||
Figure 4: Example of a multilingual call graph | ||||||||
Line: 49 to 49 | ||||||||
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 30 to 30 | ||||||||
When the designated function used to call another program of another language, such as “PyRun_SimpleFile” or JSContext().eval(), is found, its argument (name of the Python or JavaScript file) is considered a function call and the executable portion of that file is represented as the main function in the original program. That creates the connection between the two files, which allows the subsequent programs to build the call graph. “CombineCSV.py” combines all individual csv files from the list of source files into one. This file is then used as input to “GenerateDot.py”. This program translates the csv file to a dot file, which represents the csv file as a graph. The Dot program builds the final graph via GraphViz and saves it as a PDF file. Circular nodes represent C programs, rectangular nodes represent Python programs, and hexagonal nodes represent JavaScript programs. Recursive functions are denoted by dotted nodes. | ||||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | ![]() | |||||||
Figure 4: Example of a multilingual call graph | ||||||||
Line: 50 to 50 | ||||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
How does it work? | ||||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | ![]() ![]() | |||||||
The process starts with C, Python and JavaScript source code from which separate ASTs (Abstract Syntax Tree) are dumped using Clang-Check (for C files) | ||||||||
Line: 12 to 14 | ||||||||
Figure 1: Portion of a C AST file | ||||||||
Changed: | ||||||||
< < | the AST module and the file ast2json.py (for Python files), | |||||||
> > | the AST module and the file ast2json.py![]() | |||||||
![]() | ||||||||
Changed: | ||||||||
< < | And SpiderMonkey for JavaScript files. | |||||||
> > | And SpiderMonkey![]() | |||||||
![]() | ||||||||
Changed: | ||||||||
< < | The AST files have very different structures for C and Python, but the parsers are designed to handle each kind of AST differently. Those parsers filter the AST files detecting and recording function calls and their arguments. Initially, the program is capable of detecting literals and variables as arguments. Reaching Definition Analysis will be developed in the future in order to handle statically assigned variables as arguments to functions. The current version of the program handles part of the Python.h interface between C and Python. It only analyzes “PyRun_SimpleFile” calls. Other mechanisms for calling Python from C will also be implemented in the future. When a call to “PyRun_SimpleFile” is found, its argument (name of the python file) is considered a function call and the executable portion of that python file is represented as the main function in C. That creates the connection between the C and the Python files, which allows the subsequent programs to build the call graph. | |||||||
> > | The AST files have very different structures for C, Python and Javascript, but the parsers are designed to handle each kind of AST differently. Those parsers filter the AST files, detecting and recording function calls and their arguments. Initially, the program is capable of detecting literals and variables as arguments. Reaching Definition Analysis will be developed in the future in order to handle statically assigned variables as arguments to functions. The current version of the program handles part of the Python.h interface between C and Python. It only analyzes “PyRun_SimpleFile” calls. Other mechanisms for calling Python from C will also be implemented in the future. The version can also handle PyV8's eval function to call a JavaScript program from Python. In the future, the program will be able to handle cases in which a JavaScript program is called from a C program, and both JavaScript and Python functions are called from C programs. | |||||||
Changed: | ||||||||
< < | “CombineCSV.py” combines all individual csv files from the list of source files into one. This file is then used as input to “GenerateDot.py”. This program translates the csv file to a dot file, which represents the csv file as a graph. The Dot program builds the final graph and saves it as a PDF file. Circular nodes represent C functions and Rectangular nodes represent Python functions. | |||||||
> > | When the designated function used to call another program of another language, such as “PyRun_SimpleFile” or JSContext().eval(), is found, its argument (name of the Python or JavaScript file) is considered a function call and the executable portion of that file is represented as the main function in the original program. That creates the connection between the two files, which allows the subsequent programs to build the call graph. “CombineCSV.py” combines all individual csv files from the list of source files into one. This file is then used as input to “GenerateDot.py”. This program translates the csv file to a dot file, which represents the csv file as a graph. The Dot program builds the final graph via GraphViz and saves it as a PDF file. Circular nodes represent C programs, rectangular nodes represent Python programs, and hexagonal nodes represent JavaScript programs. Recursive functions are denoted by dotted nodes. | |||||||
![]() | ||||||||
Line: 48 to 48 | ||||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
How does it work? | ||||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | ![]() | |||||||
Changed: | ||||||||
< < | The process starts with C and Python source code from which separate ASTs (Abstract Syntax Tree) are dumped using Clang-Check (for C files) | |||||||
> > | The process starts with C, Python and JavaScript source code from which separate ASTs (Abstract Syntax Tree) are dumped using Clang-Check (for C files) | |||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | ![]() | |||||||
Figure 1: Portion of a C AST file | ||||||||
Changed: | ||||||||
< < | and the AST module (for Python files). | |||||||
> > | the AST module and the file ast2json.py (for Python files), | |||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | ![]() | |||||||
Changed: | ||||||||
< < | Figure 2: Portion of a Python AST file | |||||||
> > | Figure 2: Portion of a Python AST json file | |||||||
Changed: | ||||||||
< < | The AST files have very different structures for C and Python, but the parsers are designed to handle each kind of AST differently. Those parsers filter the AST files detecting and recording function calls and their arguments. Initially, the program is capable of detecting literals and variables as arguments. Reaching Definition Analysis will be developed in the future in order to handle statically assigned variables as arguments to functions. The current version of the program handles part of the Python.h interface between C and Python. It only analyzes “PyRun_SimpleFile” calls. Other mechanisms for calling Python from C will also be implemented in the future. | |||||||
> > | And SpiderMonkey for JavaScript files. | |||||||
Changed: | ||||||||
< < | When a call to “PyRun_SimpleFile” is found, its argument (name of the python file) is considered a function call and the executable portion of that python file is represented as the main function in C. That creates the connection between the C and the Python files, which allows the subsequent programs to build the call graph. | |||||||
> > | ![]() | |||||||
Changed: | ||||||||
< < | “CombineCSV.py” combines all individual csv files from the list of source files into one. This file is then used as input to “GenerateDot.py”. This program translates the csv file to a dot file, which represents the csv file as a graph. The Dot program builds the final graph and saves it as a PDF file. Circular nodes represent C functions and Rectangular nodes represent Python functions. | |||||||
> > | Figure 3: Portion of a JavaScript AST json file | |||||||
Added: | ||||||||
> > | The AST files have very different structures for C and Python, but the parsers are designed to handle each kind of AST differently. Those parsers filter the AST files detecting and recording function calls and their arguments. Initially, the program is capable of detecting literals and variables as arguments. Reaching Definition Analysis will be developed in the future in order to handle statically assigned variables as arguments to functions. The current version of the program handles part of the Python.h interface between C and Python. It only analyzes “PyRun_SimpleFile” calls. Other mechanisms for calling Python from C will also be implemented in the future. | |||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | When a call to “PyRun_SimpleFile” is found, its argument (name of the python file) is considered a function call and the executable portion of that python file is represented as the main function in C. That creates the connection between the C and the Python files, which allows the subsequent programs to build the call graph. | |||||||
Added: | ||||||||
> > | “CombineCSV.py” combines all individual csv files from the list of source files into one. This file is then used as input to “GenerateDot.py”. This program translates the csv file to a dot file, which represents the csv file as a graph. The Dot program builds the final graph and saves it as a PDF file. Circular nodes represent C functions and Rectangular nodes represent Python functions. | |||||||
Changed: | ||||||||
< < | Figure 3: Example of a multilingual call graph | |||||||
> > | ![]() | |||||||
Added: | ||||||||
> > | Figure 4: Example of a multilingual call graph | |||||||
Permissions | ||||||||
Line: 43 to 45 | ||||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Changed: | ||||||||
< < | Process Description | |||||||
> > | How does it work? | |||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | ![]() | |||||||
The process starts with C and Python source code from which separate ASTs (Abstract Syntax Tree) are dumped using Clang-Check (for C files)
![]() | ||||||||
Changed: | ||||||||
< < | Figure 2: Portion of a C AST file | |||||||
> > | Figure 1: Portion of a C AST file | |||||||
and the AST module (for Python files).
![]() | ||||||||
Changed: | ||||||||
< < | Figure 3: Portion of a Python AST file | |||||||
> > | Figure 2: Portion of a Python AST file | |||||||
The AST files have very different structures for C and Python, but the parsers are designed to handle each kind of AST differently. Those parsers filter the AST files detecting and recording function calls and their arguments. Initially, the program is capable of detecting literals and variables as arguments. Reaching Definition Analysis will be developed in the future in order to handle statically assigned variables as arguments to functions. The current version of the program handles part of the Python.h interface between C and Python. It only analyzes “PyRun_SimpleFile” calls. Other mechanisms for calling Python from C will also be implemented in the future. | ||||||||
Line: 28 to 28 | ||||||||
![]() | ||||||||
Changed: | ||||||||
< < | Figure 4: Example of a multilingual call graph | |||||||
> > | Figure 3: Example of a multilingual call graph | |||||||
Permissions |
Line: 1 to 1 | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Added: | |||||||||||
> > |
Process Description![]() ![]() ![]() ![]() Permissions
|