CODEWITHSUNDEEP
javascriptdebugging
Osan
Osan

Reputation: 187

Javascript not reporting errors

So, I'm writing an application that has ~5k lines of javascript... and it's stopped reporting errors. No firebug, IE triangle thing, nothing. It just won't work if there's an error. Anyone seen anything like this before? Debugging is somewhat... frustrating...

My best guess is too many layers of abstraction? But there aren't really that many.

Upvotes: 2

Views: 399

Answers (2)

c69
c69

Reputation: 21527

99% your script is not executing at all. You need manual trace, either with breakpoints, console.logs or alerts.

1% is that you have error handlers, who silence them. Look for suspicious try { .. } catch () {} and window.onerror.

Upvotes: 2

Simon Sarris
Simon Sarris

Reputation: 63872

Something else is wrong. It's not simply the size of your javascript. I'm running 70,000 lines of JavaScript in Chrome's debugger and FireFox 6's firebug and there are no debugging problems.

Look elsewhere. Is something not getting loaded? Do you need to clear cache and refresh? Try another browser (like Chrome) and see the results.

If it stopped reporting errors, its more likely those errors do not exist in your current revision, or that a block of code that you think is executing is actually never run. Set a breakpoint.

Upvotes: 3

Related Questions