Closed Bug 1868187 Opened 10 months ago Closed 10 months ago

Expose native function call arguments to onNativeCall hooks

Categories

(Core :: JavaScript Engine, enhancement, P1)

enhancement

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.

Component: Debugger → JavaScript Engine
Product: DevTools → Core

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.

Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Blocks: js-debugger
Severity: -- → N/A
Priority: -- → P1
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
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: