Coordinating instances of a thread or other service in emulation

• US 9,558,019 B2
• Filed: 03/22/2007
• Issued: 01/31/2017
• Est. Priority Date: 03/22/2007
• Status: Active Grant

• Current Assignee: MEC Management, LLC (Three Affiliated Tribes of the Fort Berthold Reservation, North Dakota)
• Original Assignee: The Invention Science Fund I, L.L.C. (Intellectual Ventures LLC)
• Inventors: Malamud, Mark A., Jung, Edward K. Y., Lord, Robert W., Cohen, Alexander J., Levien, Royce A., Wood, JR., Lowell L., Rinaldo, Jr., John D.
• Primary Examiner(s): DORAIS, CRAIG C
• Application Number:
  US11/728,269
• Publication Number:
  US 20080235711A1
• Time in Patent Office: 3,603 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators

Abstract

A system, method, computer program product, and carrier are described for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface or indicating a virtually instantiated service via a data flow between a user interface and an operating system, the virtually instantiated service including at least a virtual instance; and accessing another instance of the virtually instantiated service at least partly in response to the user interface after indicating the virtually instantiated service via the data flow between the user interface and the operating system or manipulating a second instance of the thread at least partly in response to a second input arriving from the user interface after beginning the emulation of the first instance of the thread.

Claims

1. A method comprising:

obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface, the software flaw indication indicating an incorrect computational result resulting from one or more errors related to usage of one or more instruction sequences within the emulation of the first instance of the thread, the incorrect computational result detected by comparing one or more actual results generated by emulation of the first instance of the thread with one or more known parameters with corresponding one or more theoretical results, including at least;

wherein the software flaw indication indicates a threshold number of errors in one or more categories related at least in part to usage of one or more instruction sequences within the emulation of the first instance of the thread resulting from at least a change in the emulation environment, and

wherein the change in the emulation environment is based at least in part on receiving an external resource authorization specifying a conditional access to a resource; and

invoking circuitry for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication.

2. The method of claim 1 in which the invoking circuitry for manipulating a second instance of the thread at least partly in response to a second input arriving from the user interface after beginning the emulation of the first instance of the thread comprises:

receiving the second input from the user interface after obtaining the software flaw indication resulting from the emulation of the first instance of the thread.

3. The method of claim 1 in which the obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

deciding to obtain a component of the software flaw indication in response to another component of the software flaw indication.

4. The method of claim 1 in which the invoking circuitry for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

receiving the second input after manifesting the software flaw indication at the user interface.

5. The method of claim 1 in which the invoking circuitry for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

receiving the second input from the user interface after concluding the emulation of the first instance of the thread.

6. The method of claim 1 in which the invoking circuitry for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

manipulating a variant of the thread at least partly in response to the second input from the user interface.

7. The method of claim 1, wherein an emulation environment in which the first instance of the thread is executed is configured with the first input from the user interface.

8. The method of claim 7, wherein the emulation environment is configured, based at least in part on the first input from the user interface, to implement fault detection logic.

9. The method of claim 7, wherein the emulation environment is configured, based at least in part on the first input from the user interface, to implement error recovery logic.

10. The method of claim 7, wherein the emulation environment is configured, based at least in part on the first input from the user interface, to adjust event simulation.

11. The method of claim 1, wherein obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

generating an indication of an error from the first instance of the thread being executed by the emulation.

12. The method of claim 1, wherein obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface, wherein the software flaw indication indicates a threshold number of errors in one or more categories related to usage of one or more instruction sequences within the emulation and wherein the method includes:

obtaining the software flaw indication resulting from the emulation of the first instance of the thread at least partly in response to the first input from the user interface, the software flaw indication indicating a threshold number of errors in one or more categories related in part to usage of one or more instruction sequences within the emulation of the first instance of the thread resulting from at least an interaction history, wherein the interaction history being based at least in part on a reputation of an operational history.

13. The method of claim 1, wherein the software flaw indicates the threshold number of errors in one or more categories related to usage of one or more instruction sequences within the emulation of the first instance of the thread in at least one of a divide-by-zero operation, an illegal write or read operation, a timeout, an illegal operation, or a fault event.

14. The method as recited in claim 1, wherein the invoking circuitry for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

invoking circuitry for manipulating a second instance of the thread by at least executing the second instance of the thread natively in a physical environment without emulation.

15. A system comprising:

circuitry for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface, the software flaw indication indicating an incorrect computational result resulting from one or more errors related to usage of one or more instruction sequences within the emulation of the first instance of the thread, the incorrect computational result detected by comparing one or more actual results generated by emulation of the first instance of the thread with one or more known parameters with corresponding one or more theoretical results, including at least;

wherein the circuitry for obtaining a software flaw indication is configured to obtain a software flaw indication that indicates a threshold number of errors in one or more categories related to usage of one or more instruction sequences within the emulation of the first instance of the thread resulting from at least a change in the emulation environment resulting at least in part from the emulation being hosted in another emulation environment; and

circuitry for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication.

16. The system of claim 15 in which the circuitry for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

circuitry for receiving at least one of an error signal or a warning in the software flaw indication.

17. The system of claim 15 in which the circuitry for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

circuitry for executing at least a portion of the second instance of the thread natively.

18. The system of claim 15 in which the circuitry for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

circuitry for presenting a common image graphically distinguishing the first instance of the thread from the second instance of the thread.

19. The system of claim 15 in which the circuitry for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

circuitry for obtaining the software flaw indication at a non-volatile storage element.

20. The system of claim 15 in which the circuitry for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

circuitry for extracting the software flaw indication from a resource containing data resulting from emulating another thread.

21. The system of claim 15 in which the circuitry for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

circuitry for causing the software flaw indication to identify a software module containing the thread.

22. The system of claim 15 in which the circuitry for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

circuitry for manipulating a variant of the thread at least partly in response to the second input from the user interface.

23. A system comprising:

(a) means for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface, the software flaw indication indicating an incorrect computational result resulting from one or more one or more errors related to usage of one or more instruction sequences from the first instance of the thread being executed by the emulation, the incorrect computational result detected by comparing one or more actual results generated by emulation of the first instance of the thread with one or more known parameters with corresponding one or more theoretical results, including at least;

1) means for determining that the software flaw indication indicates a threshold number of errors in one or more categories related to usage of one or more instruction sequences within the emulation of the first instance of the thread, the means for determining configured to determine that prior usage of the emulator has failed to generate greater than a second threshold number of errors in one or more categories; and

(b) means for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication.

24. The system of claim 23 in which the means for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

means for receiving at least one of an error signal or a warning in the software flaw indication.

25. The system of claim 23 in which the means for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

means for creating the first instance of the thread in response to the first input from the user interface.

26. The system of claim 23 in which the means for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

means for configuring an emulation environment in response to the first input from the user interface.

27. The system of claim 23 in which the means for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

means for executing at least a portion of the second instance of the thread natively.

28. The system of claim 23 in which the means for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

means for presenting a common image graphically distinguishing the first instance of the thread from the second instance of the thread.

29. The system of claim 23 in which the means for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

means for receiving the second input from the user interface after obtaining the software flaw indication resulting from the emulation of the first instance of the thread.

30. The system of claim 23 in which the means for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

means for obtaining the software flaw indication at a non-volatile storage element.

31. The system of claim 23 in which the means for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

means for extracting the software flaw indication from a resource containing data resulting from emulating another thread.

32. The system of claim 23 in which the means for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

means for deciding to obtain a component of the software flaw indication in response to another component of the software flaw indication.

33. The system of claim 23 in which the means for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

means for causing the software flaw indication to identify a software module containing the thread.

34. The system of claim 23 in which the means for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

means for receiving the second input after manifesting the software flaw indication at the user interface.

35. The system of claim 23 in which the means for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

means for receiving the second input from the user interface after concluding the emulation of the first instance of the thread.

36. The system of claim 23 in which the means for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

means for manipulating a variant of the thread at least partly in response to the second input from the user interface.

37. The system of claim 23, in which the means for manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread, and b) the software flaw indication comprises:

means for executing at least a portion of the second instance of the thread natively;

means for receiving the second input from the user interface after obtaining the software flaw indication resulting from the emulation of the first instance of the thread, after concluding the emulation of the first instance of the thread, and after manifesting the software flaw indication at the user interface; and

means for presenting a common image graphically distinguishing the first instance of the thread from the second instance of the thread.

38. The system of claim 23, in which the means for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

means for creating the first instance of the thread in response to the first input from the user interface;

means for extracting the software flaw indication from a resource containing data resulting from emulating another thread; and

means for receiving at least one of an error signal or a warning as the software flaw indication at a non-volatile storage element.

39. The system of claim 23, in which the means for obtaining a software flaw indication resulting from an emulation of a first instance of a thread at least partly in response to a first input from a user interface comprises:

means for configuring an emulation environment in response to the first input from the user interface; and

means for deciding to obtain a component of the software flaw indication in response to another component of the software flaw indication.

40. The system of claim 23 in which the software flaw indication indicating one or more errors related to usage of one or more instruction sequences from the first instance of the thread being executed by the emulation results from at least one of:

a divide-by-zero operation, an illegal write or read operation, a timeout, an illegal operation, or a fault event in the one or more instruction sequences of the first instance of the thread being executed by the emulation.

41. A method comprising:

indicating a thread via a data flow from an operating system to a user interface;

obtaining a software flaw indication resulting from an emulation of a first instance of the thread at least partly in response to a first input from the user interface, the software flaw indication indicating an incorrect computational result resulting from one or more errors related to usage of one or more instruction sequences within the emulation of the first instance of the thread, the incorrect computational result detected by comparing one or more actual results generated by emulation of the first instance of the thread with one or more known parameters with corresponding one or more theoretical results;

manipulating a second instance of the thread at least partly in response to a) a second input arriving from the user interface after beginning the emulation of the first instance of the thread and after indicating the thread via the data flow from the operating system to the user interface and b) the software flaw indication; and

signaling a decision whether to transfer data to an emulation of the second instance of the thread from the emulation of the first instance of the thread and whether to host the one or more instruction sequences natively at least partly as a result of an indication in the obtained data of at least one successful result in the emulation of the first instance of the thread while hosting software, wherein the at least one successful result in the emulation of the first instance of the thread while hosting the software includes at least determining that prior emulation of the first instance of the thread while hosting the software has failed to generate greater than a threshold number of errors in one or more categories.