Revise comments on js::Debug::mark. Also inline Debug::sweepCompartment into Debug::sweepAll.

Add Script.prototype.getAllOffsets and getLineOffsets.

Quick follow-up for thinko in bug 667925: lists can be empty. r=orange.

Bug 667925 - Line number is bogus on JSOP_TRACE opcodes. r=brendan.

Add Script.prototype.getOffsetLine.

Add Frame.prototype.offset.

Test that we get the same Debug.Script instance for different closures made from the same 'function' expression/declaration/statement.

Fix 'if' in DebugObject_trace: the scope of a declaration includes its initializer.

Support disabling debug mode in a compartment with scripts on the stack. Dump the debug-mode JIT code during a later GC.

Change js::Debug::heldScripts to have pointers to debuggee-compartment objects as keys, rather than wrappers.

Change js::Debug::objects to have referents as keys, rather than cross-compartment wrappers of referents. This adds support for cross-compartment WeakMaps and changes js::Debug::objects to be one. It eliminates the vexing JSMSG_DEBUG_STREAMS_CROSSED error messsage. The GC interaction between jsgc and jsdbg is a little more complex now; like the cross-compartment wrapper maps, Debug::objects must be marked (just once) during per-compartment GC. In other ways this is a simplification.

Fix Debug-ctor-03.js (regression: the exception is being thrown in the wrong compartment since rev e05d3da5866a) and make removeDebuggee throw if it would disable debug mode in a compartment with scripts on the stack.

GlobalObject::getOrCreateDebuggers must be called in the global object's compartment, since it may create an object.

Initial support for Debug.Script instances. r=jorendorff, push=jorendorff.

Merge.

Fix MSVC-only errors and a warning.

Automatically turn debug mode on/off when adding/removing debuggees. This allows most of the tests to run without the -d command-line flag. Now a compartment is in debug mode if * JSD1 wants debug mode on, thanks to a JS_SetDebugMode* call; OR * JSD2 wants debug mode on, because a live Debug object has a debuggee global in that compartment. Since this patch only adds the second half of the rule, JSD1 should be unaffected. The new rule has three issues: 1. When removeDebuggee is called, it can cause debug mode to be turned off for a compartment. If any scripts from that compartment are on the stack, and the methodjit is enabled, returning to those stack frames will crash. 2. When a Debug object is GC'd, it can cause debug mode to be turned off for one or more compartments. This causes the same problem with returning to deleted methodjit code, but the fix is different: such Debug objects simply should not be GC'd. 3. Setting .enabled to false still does not turn off debug mode anywhere, so it does not reduce overhead as much as it should. A possible fix for issue #1 would be to make such removeDebuggee calls throw; a different possibility is to turn off debug mode but leave all the scripts alone, accepting the performance loss (as we do for JSD1 in JSCompartment::setDebugModeFromC). The fix to issues #2 and #3 is to tweak the rule--and to tweak the rule for Debug object GC-reachability.

Define new macro, THIS_DEBUGOBJECT_OWNER_REFERENT, which also provides the owning Debug. r=jorendorff, push=jorendorff.

Comment fixes, assertions, and cleanups to Debug GC-related code. r=jorendorff, push=jorendorff.

Use WeakMap for the Debug::objects, the mapping from referents to Debug.Objects. r=jorendorff, push=jorendorff.