DYNAMIC DATA FLOW TRACKING METHOD, DYNAMIC DATA FLOW TRACKING PROGRAM, AND DYNAMIC DATA FLOW TRACKING APPARATUS

• US 20120066698A1
• Filed: 05/18/2010
• Published: 03/15/2012
• Est. Priority Date: 05/20/2009
• Status: Abandoned Application

• Current Assignee: Toyota Jidosha Kabushiki Kaisha (Toyota Motor Corporation)
• Original Assignee: NEC Corporation
• Inventors: Yanoo, Kazuo
• Application Number:
  US13/321,753
• Publication Number:
  US 20120066698A1
• Time in Patent Office: Days
• US Class Current: 719/330
• CPC Class Codes: G06F 11/28 by checking the correct order of processing G06F11/08 - G06F11/26 take precedence; monitoring patterns of pulse trains H03K5/19

Abstract

A dynamic data flow tracking apparatus, a dynamic data flow tracking method, and a dynamic data flow tracking program are provided which can raise the dynamic data flow analysis speed for a program linked to plural shared libraries. A specification of data passing between functions included in a shared library is defined in a signature, which is stored in a storage unit (108). At least a part of the propagation of a tag between the functions in a call destination is skipped by referring to the signature stored in the storage unit (108) at the time of giving a call to a function defined in the signature from a program.

Claims

1. A dynamic data flow tracking method of dynamically tracking a data flow by setting a tag for data in a process and causing the tag to propagate with data passing in the process,

wherein a specification of the data passing between functions included in a shared library is defined as a signature, and

at least a part of the propagation of the tag between the functions is skipped by referring to the signature at the time of giving a call to the functions defined in the signature from a program.

2. The dynamic data flow tracking method according to claim 1, wherein the tag propagates in a bundle at the time of giving a call to the function.

3. The dynamic data flow tracking method according to claim 1, wherein it is judged whether an executable code which is a code in execution is included in the shared library, and at least a part of the propagation of the tag is skipped on the basis of the result of the judge.

4. The dynamic data flow tracking method according to claim 3, wherein it is judged whether the executable code is included in the shared library by comparing address information of the executable code with address information of the shared library.

5. The dynamic data flow tracking method according to claim 1, wherein when a call is given to a function defined in the signature from a function not defined in the signature, a return address and values of parameters are stored as history information, and a first state in which at least a part of the propagation of the tag is skipped is entered,

when a call is given to an address of a function not defined in the signature in the first state, the return address is stored as history information and a second state in which the propagation of the tag is not skipped is entered, and

newest history information is removed when a return destination is equal to the return address included in the newest history information at the time of return from the function call, and at least a part of the propagation of the tag is skipped when it is in the first state.

6. The dynamic data flow tracking method according to claim 5, wherein when a call is given to a function defined in the signature from a function not defined in the signature and only when the data which is a propagation source of the tag has a default value, the return address and the values of the parameters are stored as the history information and the first state is entered.

7. The dynamic data flow tracking method according to claim 5, wherein information on whether a callback is given to a function not defined in the signature from a function defined in the signature and data handed over to the function defined in the signature should be should be handed over with the callback is defined in the signature, and

wherein when the tag of data as a propagation source of the tag defined in the signature has a default value or when the tag does not have a default value and data is not handed over with the callback, the return address and the values of the parameters are stored as the history information and the first state is entered.

8. A dynamic data flow tracking program for causing a computer to perform a dynamic data flow tracking operation of dynamically tracking a data flow by setting a tag for data in a process and causing the tag to propagate with data passing in the process, wherein a specification of the data passing between functions included in a shared library is defined in a signature, and

wherein at least a part of the propagation of the tag between the functions is skipped by referring to the signature at the time of giving a call to the functions defined in the signature from a program.

9. The dynamic data flow tracking program according to claim 8, wherein the tag propagates in a bundle at the time of giving a call to the function.

10. The dynamic data flow tracking program according to claim 8, wherein it is judged whether an executable code which is a code in execution is included in the shared library and at least a part of the propagation of the tag is skipped on the basis of the result of the judge.

11. The dynamic data flow tracking program according to claim 10, wherein it is judged whether the executable code is included in the shared library by comparing address information of the executable code with address information of the shared library.

12. The dynamic data flow tracking program according to claim 8, wherein when a call is given to a function defined in the signature from a function not defined in the signature, a return address and values of parameters are stored as history information and a first state in which at least a part of the propagation of the tag is skipped is entered,

wherein when a call is given to an address of a function not defined in the signature in the first state, the return address is stored as history information and a second state in which the propagation of the tag is not skipped is entered, and

wherein newest history information is removed when a return destination is equal to the return address included in the newest history information at the time of return from the function call and at least a part of the propagation of the tag is skipped in the first state.

13. The dynamic data flow tracking program according to claim 12, wherein when a call is given to a function defined in the signature from a function not defined in the signature and only when the data which is a propagation source of the tag has a default value, the return address and the values of the parameters are stored as the history information and the first state is entered.

14. The dynamic data flow tracking program according to claim 12, wherein information on whether a callback is given to a function not defined in the signature from a function defined in the signature and data handed over to the function defined in the signature should be should be handed over with the callback is defined in the signature, and

wherein when the tag of data as a propagation source of the tag defined in the signature has a default value or when the tag does not have a default value and data is not handed over with the callback, the return address and the values of the parameters are stored as the history information and the first state is entered.

15. A dynamic data flow tracking apparatus that dynamically tracks a data flow by setting a tag for data in a process and causing the tag to propagate with data passing in the process, comprising:

a storage unit for storing a signature in which a specification of the data passing between functions included in a shared library is defined; and

a dynamic data flow analysis process adding unit for adding a tag propagation process of skipping at least a part of the propagation of the tag between the functions by referring to the signature at the time of giving a call to the functions defined in the signature from a program.

16. The dynamic data flow tracking apparatus according to claim 15, wherein the dynamic data flow analysis process adding unit adds the tag propagation process of causing the tag to propagate in a bundle at the time of giving a call to before or after the function.

17. The dynamic data flow tracking apparatus according to claim 15, wherein the dynamic data flow analysis process adding unit judges whether an executable code which is a code in execution is included in the shared library and skips at least a part of the propagation of the tag on the basis of the result of the judge.

18. The dynamic data flow tracking apparatus according to claim 17, wherein the dynamic data flow analysis process adding unit judges whether the executable code is included in the shared library by comparing address information of the executable code with address information of the shared library.

19. The dynamic data flow tracking apparatus according to claim 15, wherein the dynamic data flow analysis process adding unit calls a process of storing a return address and values of parameters as history information and entering a first state in which at least a part of the propagation of the tag is skipped when a call is given to a function defined in the signature from a function not defined in the signature and storing the return address as history information and entering a second state in which the propagation of the tag is not skipped when a call is given to an address of a function not defined in the signature in the first state, and adds the called process to the program, and

wherein the dynamic data flow analysis process adding unit calls a process of removing newest history information when a return destination is equal to the return address included in the newest history information at the time of return from the function call and skipping at least a part of the propagation of the tag with reference to the signature in the first state and adds the called process to the program.

20. The dynamic data flow tracking apparatus according to claim 19, wherein the dynamic data flow analysis process adding unit adds a process of storing the return address and the values of the parameters as the history information and entering the first state when a call is given to a function defined in the signature from a function not defined in the signature and only when the data which is a propagation source of the tag has a default value to the program as the call source,.

21. The dynamic data flow tracking apparatus according to claim 19, wherein the signature information includes information on whether a callback is given to a function not defined in the signature from a function defined in the signature and data handed over to the function defined in the signature should be should be handed over with the callback, and

wherein the dynamic data flow analysis process adding unit adds a process of storing the return address and the values of the parameters as the history information and entering the first state when the tag of data as a propagation source of the tag defined in the signature has a default value or when the tag does not have a default value and data is not handed over with the callback to the program as the call source.