# IT:AD:JScript:Debugging # * [[../|(UP)]] {{indexmenu>.#2|nsort tsort}} ## Tools ## * Chrome: * Great [summary](http://code.google.com/chrome/devtools/docs/scripts-breakpoints.html) * FireBug: * Read this [tutorial](http://michaelsync.net/2007/09/30/firebug-tutorial-script-tab-javascript-debugging) * F12: * [http://msdn.microsoft.com/en-us/library/gg589507(v=vs.85).aspx](http://msdn.microsoft.com/en-us/library/gg589507(v=vs.85).aspx) ## console ## * Use `console.log(msg)`, console.debug, console.info, console.warn, console.error, console.clear to send message to the debugger window. * Works in all browser now (older IE's didn't support it). * *"+1. And for the benefit of anyone arriving at this question now, it's worth pointing out that since the question was answered, all browsers have now implemented the console object, so console.log() etc should work in all browsers, including IE. However, in all cases, you need to have the debugger window open at the time, otherwise calls to console will generate errors. – Spudley Feb 10 '11 at 14:59"* ([Src](http://stackoverflow.com/a/164408)) #### Scenario #### Need to walk up the stack to find out variables #### Solution #### From the immediate console, use something like `arguments.callee.caller` to walk up the stack.