e05d3da5866a594138b9678d12bc122a81551946: GlobalObject::getOrCreateDebuggers must be called in the global object's compartment, since it may create an object.
Jason Orendorff <jorendorff@mozilla.com> - Mon, 20 Jun 2011 14:06:42 -0500 - rev 75648
GlobalObject::getOrCreateDebuggers must be called in the global object's compartment, since it may create an object.
ac45a3dbfe3304dca3b9c9b0de4464f1e102a0b3: Initial support for Debug.Script instances. r=jorendorff, push=jorendorff.
Jason Orendorff <jorendorff@mozilla.com> - Fri, 17 Jun 2011 16:28:32 -0500 - rev 75647
Initial support for Debug.Script instances. r=jorendorff, push=jorendorff.
6885f4c66607709010eae5d47f39b6b22ee3f707: Merge.
Jason Orendorff <jorendorff@mozilla.com> - Fri, 17 Jun 2011 11:12:33 -0500 - rev 75646
Merge.
feb8c7a919b366b7d8c5390007cddf9c828a81d0: Fix MSVC-only errors and a warning.
Jason Orendorff <jorendorff@mozilla.com> - Thu, 16 Jun 2011 10:25:10 -0500 - rev 75645
Fix MSVC-only errors and a warning.
a95ab01cda09f6a4f344ed1898e4ff1bfd65a6d5: Automatically turn debug mode on/off when adding/removing debuggees.
Jason Orendorff <jorendorff@mozilla.com> - Thu, 02 Jun 2011 21:58:46 -0500 - rev 75644
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.
700d8a05c7de53fbeb84e2b3b4ac4cb8ae7e82e4: Define new macro, THIS_DEBUGOBJECT_OWNER_REFERENT, which also provides the owning Debug. r=jorendorff, push=jorendorff.
Jim Blandy <jimb@mozilla.com> - Wed, 15 Jun 2011 18:02:02 -0500 - rev 75643
Define new macro, THIS_DEBUGOBJECT_OWNER_REFERENT, which also provides the owning Debug. r=jorendorff, push=jorendorff.
8164f83c3cf8d429424c36298d11b324333996b9: Comment fixes, assertions, and cleanups to Debug GC-related code. r=jorendorff, push=jorendorff.
Jim Blandy <jimb@mozilla.com> - Wed, 15 Jun 2011 18:00:06 -0500 - rev 75642
Comment fixes, assertions, and cleanups to Debug GC-related code. r=jorendorff, push=jorendorff.
8247161274fbcb5d827c3e32ab6637a306520087: Use WeakMap for the Debug::objects, the mapping from referents to Debug.Objects. r=jorendorff, push=jorendorff.
Jim Blandy <jimb@mozilla.com> - Wed, 15 Jun 2011 17:53:26 -0500 - rev 75641
Use WeakMap for the Debug::objects, the mapping from referents to Debug.Objects. r=jorendorff, push=jorendorff.
b5d3c424d66d01df04121bd502cdfe5efb685428: Merge from TM. Huge merge. Stack changes from bug 656462.
Jason Orendorff <jorendorff@mozilla.com> - Wed, 15 Jun 2011 16:14:09 -0500 - rev 75640
Merge from TM. Huge merge. Stack changes from bug 656462.
ed51e6c81d01ff76f0aa7ec6e0046b2bc1c2d0c1: Cross stack segment boundaries when looking for the youngest frame. Correctly check that live stack frames are on the stack.
Jim Blandy <jimb@mozilla.com> - Wed, 08 Jun 2011 07:25:22 -0700 - rev 75639
Cross stack segment boundaries when looking for the youngest frame. Correctly check that live stack frames are on the stack.
210f10efc3e47992e5e87010c1b948c9e3b14110: Verify that accessing frame properties throws once the frame is dead.
Jim Blandy <jimb@mozilla.com> - Tue, 07 Jun 2011 12:15:26 -0700 - rev 75638
Verify that accessing frame properties throws once the frame is dead.
8b978fbe8b9c3013e51e4a46b8cd7389550fccc9: Merge from TM.
Jim Blandy <jimb@mozilla.com> - Tue, 07 Jun 2011 12:12:28 -0700 - rev 75637
Merge from TM.
903f84bae52857b06082a6001f734c0b61243b6a: Backed out changeset d02083014f57; build problems in nsXPConnect.cpp
Jim Blandy <jimb@mozilla.com> - Mon, 06 Jun 2011 09:01:47 -0700 - rev 75636
Backed out changeset d02083014f57; build problems in nsXPConnect.cpp
215d305502a77fcb2bd9772d692745bea7eeb71c: Backed out changeset 720b3fe3c84e; build problems in nsXPConnect.cpp.
Jim Blandy <jimb@mozilla.com> - Mon, 06 Jun 2011 08:57:34 -0700 - rev 75635
Backed out changeset 720b3fe3c84e; build problems in nsXPConnect.cpp.
720b3fe3c84efd6336c37451d7cc8e357a5931db: Fix getYoungestFrame to get the newest frame even if it is in another cx.
Jason Orendorff <jorendorff@mozilla.com> - Thu, 02 Jun 2011 22:21:13 -0500 - rev 75634
Fix getYoungestFrame to get the newest frame even if it is in another cx.
d02083014f57890a0e9977094ff51625e9ead9a6: Automatically turn debug mode on/off when adding/removing debuggees.
Jason Orendorff <jorendorff@mozilla.com> - Thu, 02 Jun 2011 21:58:46 -0500 - rev 75633
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. The fix to issues #2 and #3 is to tweak the rule--and to tweak the rule for Debug object GC-reachability.
9ac0d2ba9ac020baddf21845a5af6cc7d7c802cc: Fix bug in Debug::hasAnyLiveHooks.
Jason Orendorff <jorendorff@mozilla.com> - Thu, 02 Jun 2011 21:32:22 -0500 - rev 75632
Fix bug in Debug::hasAnyLiveHooks.
e05e71b1bda14bda7ba0cc026fe811cac595dd42: Add jit-test tag to the new test in the previous check-in.
Jason Orendorff <jorendorff@mozilla.com> - Thu, 02 Jun 2011 20:44:03 -0500 - rev 75631
Add jit-test tag to the new test in the previous check-in.
f5018c7fabf7114839195041a12dff380651b1e7: Add passing test.
Jason Orendorff <jorendorff@mozilla.com> - Thu, 02 Jun 2011 20:41:16 -0500 - rev 75630
Add passing test.
f95a35c5010cb770791369c2a61714441f66e72a: JS_SetDebugModeForCompartment: Instead of asserting that enabling debug mode is safe, check and throw if it is not. The change to AllFramesIter in Stack.cpp is by luke, r=me.
Jason Orendorff <jorendorff@mozilla.com> - Thu, 26 May 2011 14:54:47 -0500 - rev 75629
JS_SetDebugModeForCompartment: Instead of asserting that enabling debug mode is safe, check and throw if it is not. The change to AllFramesIter in Stack.cpp is by luke, r=me.
(0) -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip