Closed
Bug 967036
Opened 11 years ago
Closed 11 years ago
CurrentScriptFileLineOrigin can return bogus JSScript
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: djvj, Assigned: djvj)
References
Details
Seeing a case in bug 332176 where, for a call to |eval| directly from a browser callback, |CurrentScriptFileLineOrigin| returns a bogus JSScript as being the caller.
|
||
Comment 1•11 years ago
|
||
In bug 332176 attachment 8368755 [details] [diff] [review], the changes to CurrentScriptFileLineOrigin leave *script unset in the case where we create a NonBuiltinScriptFrameIter but it is immediately done. I'm sorry --- that's exactly the kind of thing that should be caught in review...
|
Assignee | |
Comment 2•11 years ago
|
||
Yeah, just ran into this :) I'm closing this bug as a INVALID and just fixing it in the patch.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
|
|
Assignee | |
Updated•11 years ago
|
Assignee: nobody → kvijayan
|
||
Comment 3•11 years ago
|
||
What bug, djvj?
|
|
||
Comment 4•11 years ago
|
||
jorendorff: bug 332176
You need to log in
before you can comment on or make changes to this bug.
Description
•