A while back, we decided that only actual global objects, or safely-unwrappable wrappers around such, or Debugger.Object instances referring to either of the above, should be permitted as ways to identify debuggees to addDebuggee, removeDebuggee, and hasDebuggee, to provide a more capability-like security model for the debugger. When we implemented this, we forgot to change the Debugger constructor, which adds its arguments as debuggees.

Comment on attachment 698950 [details] [diff] [review] Make Debugger constructor accept only the same kinds of debuggee designators as addDebuggee and friends. Review of attachment 698950 [details] [diff] [review]: ----------------------------------------------------------------- Looks good.

Try: https://tbpl.mozilla.org/?tree=Try&rev=9634a00a79c8

jimb: did you forget to land this r+'d patch from January 2013? Is it still relevant?

Yes, I forgot to land it. Thanks very much!

A fresh try push, seeing as this is six months old: https://tbpl.mozilla.org/?tree=Try&rev=e55e14dae2cd