Capturing telemetry data by dynamic language engine

• US 9,069,897 B2
• Filed: 11/23/2011
• Issued: 06/30/2015
• Est. Priority Date: 11/23/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Hamilton, Jennifer A., Seth, Gaurav, Qu, Yong
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): FINKLEY, RESHAUN
• Application Number:
  US13/304,178
• Publication Number:
  US 20130132930A1
• Time in Patent Office: 1,315 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/0778 Dumping, i.e. gathering error/state information after a fault for later diagnosis
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence
• CPC Class Codes: G06F 2209/481 Exception handling
• CPC Class Codes: G06F 9/45529 Embedded in an application, e.g. JavaScript in a Web browser

Abstract

At least one embodiment described herein relates to the selective capturing of script code stacks associated with exceptions thrown by script code. For unhandled exceptions, the script engine 1) captures the script code stack in a host-accessible manner in which a host that hosts the script engine may access the captured script code stack, 2) completes unwinding of the script stack, and 3) reports the captured script code stack to a host that hosts the script engine. For at least one of the handled exceptions thrown by the script code for which the script code itself handles the exception, the script code stack is not captured in the host-accessible manner. Also, the call stack property of an error object is populated at throw time, rather than creation time.

Claims

1. A method, implemented at a computer system that includes one or more processors, for communicating script call stacks associated with unhandled script exceptions across a security barrier between a scripting environment and a host environment at the computer system, the method comprising:

presenting, at the one or more processors, a security barrier between a scripting environment that includes a script engine and a host environment that includes a host component, the host component maintaining execution control at the one or more processors when scripts are not being executed at the script engine, the security barrier being configured to separate the script engine from the host component, the security barrier including an interface for communicating script call stacks between the script engine and the host component;

during execution of script code at the script engine, detecting, by the script engine, that a first exception has been thrown by the script code, the first exception being an unhandled exception because the script code lacks code for handling the first exception, and performing at least the following based the first exception having been thrown by the script code;

the script engine capturing a first script call stack representing at least a portion of a script stack associated with execution of the script code at the script engine when the first exception was thrown, wherein capturing the first script call stack includes capturing the first script call stack in a host-accessible manner in which the first script call stack can be communicated to the host component using an object model of the host component;

the script engine completing unwinding of the script stack after capturing the first script call stack; and

the script engine communicating the first script call stack to the host component over the interface in the security barrier using the object model of the host component; and

during execution of the script code at the script engine, detecting, by the script engine, that a second exception has been thrown by the script code, the second exception being a handled exception because the script code includes code for handling the second exception, and performing at least the following based the second exception having been thrown by the script code;

the script engine capturing a second script call stack representing at least a portion of the script stack associated with execution of the script code at the script engine when the second exception was thrown, wherein capturing the second script call stack includes capturing the script call stack in a script-accessible manner;

the script engine abstaining from capturing any script call stack in the host-accessible manner; and

the script engine communicating the second script call stack to the script code.

2. The method in accordance with claim 1, wherein the host component is an operating system.

3. The method in accordance with claim 1, wherein the host component is a browser.

4. The method in accordance with claim 1, wherein the first script call stack represents a subset of the script stack at the time the first exception was thrown.

5. The computer program product in accordance with claim 1, wherein the first script call stack represents all of the script stack at the time the first exception was thrown.

6. The method in accordance with claim 1, wherein the first script call stack represents a portion of the script stack at the time the first exception was thrown, in which a top portion of the script stack is removed.

7. The method in accordance with claim 6, wherein a bottom portion of the script stack that remains in the first script call stack includes a number of stack frames that is configurable by a user.

8. The method in accordance with claim 6, wherein the top portion includes a recursion portion.

9. The method in accordance with claim 1, wherein the script engine completing unwinding of the script stack after capturing the first script call stack occurs before the script engine communicating the first script code stack to the host component.

10. The method in accordance with claim 1, wherein the host component performs the following for the first exception:

displaying the first script call stack to a user.

11. The method in accordance with claim 1, wherein the host component performs the following for the first exception:

causing the script engine to cease execution of the script code.

12. The method in accordance with claim 1, wherein the first script call stack is a logical script call stack.

13. The method in accordance with claim 1, wherein the first script call stack is a physical script call stack.

14. A computer program product comprising one or more hardware storage devices having stored thereon computer-executable instructions that, when executed by one or more processors of a computer system, cause the computer system to communicate script call stacks associated with unhandled script exceptions across a security barrier between a scripting environment and a host environment at the computer system, including at least the following:

presenting, at the one or more processors, a security barrier between a scripting environment that includes a script engine and a host environment that includes a host component, the host component maintaining execution control at the one or more processors when scripts are not being executed at the script engine, the security barrier being configured to separate the script engine from the host component, the security barrier including an interface for communicating script call stacks between the script engine and the host component;

during execution of script code at the script engine, detecting, by the script engine, that a first exception has been thrown by the script code, the first exception being an unhandled exception because the script code lacks code for handling the first exception, and performing at least the following based the first exception having been thrown by the script code;

the script engine capturing a first script call stack representing at least a portion of a script stack associated with execution of the script code at the script engine when the first exception was thrown, wherein capturing the first script call stack includes capturing the first script call stack in a host-accessible manner in which the first script call stack can be communicated to the host component using an object model of the host component;

the script engine completing unwinding of the script stack after capturing the first script call stack; and

the script engine communicating the first script call stack to the host component over the interface in the security barrier using the object model of the host component; and

during execution of the script code at the script engine, detecting, by the script engine, that a second exception has been thrown by the script code, the second exception being a handled exception because the script code includes code for handling the second exception, and performing at least the following based the second exception having been thrown by the script code;

the script engine capturing a second script call stack representing at least a portion of the script stack associated with execution of the script code at the script engine when the second exception was thrown, wherein capturing the second script call stack includes capturing the script call stack in a script-accessible manner;

the script engine abstaining from capturing any script call stack in the host-accessible manner; and

the script engine communicating the second script call stack to the script code.

15. The computer program product in accordance with claim 14, wherein the script engine completing unwinding of the script stack after capturing the first script call stack occurs before the script engine communicating the first script code stack to the host component.

16. The computer program product in accordance with claim 14, wherein the host component performs the following for the first exception:

displaying the first script call stack to a user.

17. A computer system, comprising:

one or more processors; and

one or more hardware storage devices having stored thereon computer-executable instructions that, when executed by the one or more processors, cause the computer system to communicate script call stacks associated with unhandled script exceptions across a security barrier between a scripting environment and a host environment at the computer system, including at least the following;

presenting, at the one or more processors, a security barrier between a scripting environment that includes a script engine and a host environment that includes a host component, the host component maintaining execution control at the one or more processors when scripts are not being executed at the script engine, the security barrier being configured to separate the script engine from the host component, the security barrier including an interface for communicating script call stacks between the script engine and the host component;

during execution of script code at the script engine, detecting, by the script engine, that a first exception has been thrown by the script code, the first exception being an unhandled exception because the script code lacks code for handling the first exception, and performing at least the following based the first exception having been thrown by the script code;

the script engine capturing a first script call stack representing at least a portion of a script stack associated with execution of the script code at the script engine when the first exception was thrown, wherein capturing the first script call stack includes capturing the first script call stack in a host-accessible manner in which the first script call stack can be communicated to the host component using an object model of the host component;

the script engine completing unwinding of the script stack after capturing the first script call stack; and

the script engine communicating the first script call stack to the host component over the interface in the security barrier using the object model of the host component; and

during execution of the script code at the script engine, detecting, by the script engine, that a second exception has been thrown by the script code, the second exception being a handled exception because the script code includes code for handling the second exception, and performing at least the following based the second exception having been thrown by the script code;

the script engine capturing a second script call stack representing at least a portion of the script stack associated with execution of the script code at the script engine when the second exception was thrown, wherein capturing the second script call stack includes capturing the script call stack in a script-accessible manner;

the script engine abstaining from capturing any script call stack in the host-accessible manner; and

the script engine communicating the second script call stack to the script code.

18. The computer system in accordance with claim 17, wherein the script engine completing unwinding of the script stack after capturing the first script call stack occurs before the script engine communicating the first script code stack to the host component.

19. The computer system in accordance with claim 17, wherein the host component performs the following for the first exception:

displaying the first script call stack to a user.

20. The computer system in accordance with claim 17, wherein the host component performs the following for the first exception:

causing the script engine to cease execution of the script code.