Closed
Bug 1868187
Opened 1 year ago
Closed 1 year ago
Expose native function call arguments to onNativeCall hooks
Categories
(Core :: JavaScript Engine, enhancement, P1)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
122 Branch
Tracking | Status | |
---|---|---|
firefox122 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
For now Debugger.onNativeCall
hook only exposes reason
(call, get or set) and callee
(a Debugger.Object reference of the function being called.
But it would be helpful for the JS Tracer (bug 1803616) to also expose the arguments being passed to that native function call. May be only do that via an additional Debugger flag as that won't be useful for eager evaluation usecase.
Assignee | ||
Updated•1 year ago
|
Component: Debugger → JavaScript Engine
Product: DevTools → Core
Assignee | ||
Comment 1•1 year ago
|
||
Also expose the object onto which the native method is called, if any.
This will allow to describe the class related to the method call.
Expose this additional data only on-demand so that the usage of onNativeCall
related to console eager evaluation, which do not need this data,
can avoid this extra computation.
Updated•1 year ago
|
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Updated•1 year ago
|
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e3db7aa730ed
Expose native call arguments via Debugger.inspectNativeCallArguments and Debugger.onNativeCall. r=arai
Comment 3•1 year ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox122:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•