Ie10 error. Stack makes script debugging easier

ArticleDirectory

• Dom exception and error. Stack
• Performance Considerations
• Asynchronous exception

The error. Stack support has been added to ie10 to speed up script debugging and correct errors. Especially some errors that are hard to reproduce, such as asynchronous operations. The following content is from the Microsoft IE team, which describes this feature in great detail.

 

Debug an application Program

Structured error handling in Javascript depends onThrowAndTry/catch, The developer will declare an error in it and pass the control flow to a part of the program that handles the error. When an error is thrown, chakra, that is, the JavaScript engine in Internet Explorer, captures the call chain that triggers the error. This process is also called the call stack. If the object to be thrown isError(Or a function, and its prototype chain will causeError), Then chakra will create a stack trace to manually read the call stack list. This list is represented as an attribute, that isErrorObjectStack.StackContains the error message, function name, and source file location information of the function. This information will help developers understand the called functions, and even view the incorrectCodeTo quickly diagnose defects. For example, the information may indicate that a parameter passed to the function is null or invalid.

Let's take a look at a simple script and discuss it in depth. This script is trying to calculate(0, 2)And(12, 10)Distance between two points:

(Function(){

'Use strict';

FunctionSquareroot (n ){

If(N <0)

Throw NewError ('Cannot take square root of negative number .');

ReturnMath. SQRT (N );

}

FunctionSquare (n ){

ReturnN * N;

}

FunctionPointdistance (pt1, pt2 ){

ReturnSquareroot (pt1.x-pt2.x) + (pt1.y-pt2.y ));

}

FunctionSample (){

VaRPt1 = {X: 0, Y: 2 };

VaRPt2 = {X: 12, Y: 10 };

Console. Log ('Distance is :'+ Pointdistance (pt1, pt2 ));

}

Try{

Sample ();

}

Catch(E ){

Console. Log (E. Stack );

}

})();

This script contains a defect that does not adjust the differences between components. Therefore, for some input,PointdistanceThe function returns an error. In other cases, this script causes the error. To understand the meaning of stack tracing, let's check the errors in the F12 developer tool and its script tab:

Stack trace will be dumpedCatchConsole in the clause, because it is located at the top of the stack, it originated fromSquarerootFunction errors become obvious. To debug this problem, developers do not need to view the stack trace in depth; the system has violatedSquarerootAnd you only need to view the upper level of the stack, the reason will become very clear:SquarerootThe subexpression in the call should beSquare.

During debugging,StackAttribute helps identify the code used to set breakpoints. Remember: you can also use other methods to view the call stack. For example, if you set the script debugging program to the "Capture exceptions or interrupt" mode, you can use this debug program to check the call stack. For deployed applications, you can considerTry/catchTo capture failed calls and record them in the server. Then, developers can view the call stack to isolate the problem area.

Dom exception and error. Stack

Previously, I noticed that the object to be thrown must beErrorOr caused by its prototype chainError. This is intended for it; JavaScript supports triggering any object, or even a primitive that serves as an exception. Although the system can capture and check all these objects, their full use does not contain error or diagnostic information. Therefore, onlyStackAttribute.

Even if the object is a DOM exception, they do not containErrorPrototype chain, so they will not containStackAttribute. In some application scenarios, you may want to perform Dom operations and expose JavaScript-compatible errors.Try/catchMerge your dom operation code in the data block andCatchClause raises a newErrorObject:

FunctionCausesdomerror (){

Try{

VaRDIV = Document. createelement ('Div');

Div. appendchild (DIV );

}Catch(E ){

Throw NewError (E. tostring ());

}

}

However, you may consider whether to use this mode. This may be the most suitable mode for utility library development, especially when you consider whether the code intent is to hide Dom operations or simply implement a task. If the objective is to hide the DOM operation, the merge operation is triggeredErrorIt may be the correct method we need to choose.

Performance Considerations

The construction of a stack trace starts when an error object is thrown. To construct a stack trace, You need to view the current execution stack. To prevent performance problems (or even recursive stack traces) during the process of traversing a super-large stack, by default, ie collects only the top 10 stack frames. However, you can set the static attributeError. stacktracelimitSet it to another value. This setting is global and must be changed before an error is thrown. Otherwise, it will be invalid for Stack tracking.

Asynchronous exception

When a stack is asynchronously called back (for exampleTimeout,IntervalOrXMLHttpRequest), The asynchronous callback (rather than the Code created by the asynchronous callback) will be at the bottom of the call stack. This will have some potential impact on code with tracing problems: if you use the same callback function for multiple asynchronous callbacks, it is difficult for you to identify which callback generates an error by checking it separately. Let's make a slight modification to the previous example, and we will avoid direct callsSample (), But put it into the timeout callback:

(Function(){

'Use strict';

FunctionSquareroot (n ){

If(N <0)

Throw NewError ('Cannot take square root of negative number .');

ReturnMath. SQRT (N );

}

FunctionSquare (n ){

ReturnN * N;

}

FunctionPointdistance (pt1, pt2 ){

ReturnSquareroot (pt1.x-pt2.x) + (pt1.y-pt2.y ));

}

FunctionSample (){

VaRPt1 = {X: 0, Y: 2 };

VaRPt2 = {X: 12, Y: 10 };

Console. Log ('Distance is :'+ Pointdistance (pt1, pt2 ));

}

SetTimeout (Function(){

Try{

Sample ();

}

Catch(E ){

Console. Log (E. Stack );

}

},2500 );

})();

Once you execute this code segment, you will find that the stack trace has a slight delay. At this time, you will also find that the bottom of the stack is not a global code,Anonymous Function. In fact, this is not the same anonymous function, but passedSetTimeout. Because you have lost the context related to the suspended callback, you may not be able to determine the content of the called callback. In an application scenario, the system registers a callback to process multiple buttons.ClickEvent, you cannot tell which callback will be referenced by registration. Even so, this restriction is limited, because in most cases, the top of the stack may highlight the problem area.

Demonstration of viewing experience

Watch this demo now to learn how to use ie10 in Windows 8 consumer preview. You canEvalIf an error occurs, you can check the error. If you run the code within ie10, You can hover the error code line over the stack trace, so you can highlight your code line. You can enter the code in the code area or select from several examples in the list. You can also setError. stacktracelimitValue.

For more information, seeError. StackAndStacktracelimit.

Partially reposted ieblog