Overview of JavaScript debugging techniques in Google ie _javascript tips

Today, I found a corner that never noticed before, I believe I can greatly improve my writing JS speed. can quickly detect errors.

For example, today's overtime is an example of debugging a JS error discovery.

　　1, Google Browser reported the wrong

The above is the error of the Google Browser, only to report an error file, I believe that is the place by null called the length property caused. Since this is a system that has been maintained for several years, people are coming and going, and do not know how many have gone through the hand. And the business logic is extremely complex, JS files are thousands of lines. It is obviously impractical to exclude a length by one length.

2014.3.18

Just know today, alas, the original Google browser also has the wrong call stack:

　　2, IE reported in the wrong

Debugging JS in IE is like debugging. NET in VS, there is a call stack, as long as you point a few, you can find out where this line of code is invoked in error:

The above is the entire content of this article, I hope to help you, thank you for the support of cloud habitat community!