IE 8 debugger doesn't stop on TypeError

Question

I'm trying to get an angular.js/jQuery app running in IE8. I mostly have things working, but it spews a lot of console errors:

TypeError: 'undefined' is null or not an object

These errors in the developer tools don't have a source location (file & line) associated with them, and the debugger doesn't break on errors when these are being thrown, even if "Break on Error" is enabled.

Other than disabling portions of my code to search for the cause, is there any way to figure out where this is coming from? I'm getting dozens of them in every Angular digest cycle, so it's not as straightforward as figuring out what page actions cause them.

It's not obvious what, if anything, they're breaking on the page, but I haven't yet had the ability to test the whole thing, so it's hard to conclude they're benign; even if they are, I'd prefer to get rid of them; they're noisy and I'm concerned that they may be visible to the user under some IE error-handling configurations.

Answer 1

Though I've never used it, I've heard that DebugBar is an improvement over the standard IE8 developer tools.

Also, as JJZabkar mentioned in the question comments, Angular versions below 1.3 require certain shims to be in place to work with IE8 or below.

Another thing to be aware of, which is also described at that link he provided (https://docs.angularjs.org/guide/ie), is IE8's lack of support for custom element tags, which will foil any use of element-based directives (possibly causing errors) if you do not take certain measures.