Open Bug 1174896 Opened 9 years ago Updated 2 years ago

[jsdbg2] Debugger.Object.prototype.script is null if the object has not been instantiated with the referent function's global Debugger.Object

Categories

(Core :: JavaScript Engine, defect)

41 Branch
defect

Tracking

()

People

(Reporter: fayolle-florent, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0 Build ID: 20150611135623 Steps to reproduce: In bug 1050691, I use this workaround to access the Debugger.Script object: > + let script = dbgGlobal.makeDebuggeeValue(obj.unsafeDereference()).script; where |dbgGlobal| is the thread actor debuggee global and |obj| is the Debugger.Object instance of a function. Just calling obj.script returns null, and according to :fitzgen, that's unexpected. Florent
Component: Untriaged → Developer Tools
Status: UNCONFIRMED → NEW
Component: Developer Tools → JavaScript Engine
Ever confirmed: true
Product: Firefox → Core
Glancing at Debugger::wrapDebuggeeValue, we don't seem to do any kind of unwrapping, which may be the issue here.
Summary: Debugger.Object.prototype.script is null if the object has not been instanciated with the referent function's global Debugger.Object → [jsdbg2] Debugger.Object.prototype.script is null if the object has not been instantiated with the referent function's global Debugger.Object
BTW, if that's a good first bug, I would be glad to work on it. Florent
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.