Rust API for Debugger instances

NEW
Unassigned

Status

()

Core
JavaScript Engine
P2
enhancement
2 years ago
a year ago

People

(Reporter: jimb, Unassigned)

Tracking

(Blocks: 1 bug)

unspecified
Points:
---
Dependency tree / graph
Bug Flags:
qe-verify -

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
So that Servo can use SpiderMonkey's debugging API, SpiderMonkey should provide a Rust API for working with Debugger instances.

Updated

2 years ago
Blocks: 1263289
Severity: normal → enhancement
Whiteboard: [devtools-html]
Can you detail what do you mean by a "Rust API", from what I understand the Debugger API is made to be used from JS, how would it be different?  Is there any reasons to have a different API for Servo than the one we used for Gecko?
I certainly don't intent to ask a Rust API directly in SpiderMonkey, but I would like us to avoid having to host JS code to debug JS code. Given that the Debugger API is written in C++, it makes sense to me that we should be able to use it directly from C++.
(In reply to Nicolas B. Pierron [:nbp] from comment #1)
> Can you detail what do you mean by a "Rust API", from what I understand the
> Debugger API is made to be used from JS, how would it be different?  Is
> there any reasons to have a different API for Servo than the one we used for
> Gecko?

See bug 1263317 -- the summary is that Servo doesn't want to ever support privileged JS, so the existing way we provide an interface to Debugger (via a JS interface in privileged compartments) is not going to fly. Instead, we are adding an alternative interface to the same Debugger infrastructure for Servo's use.
(Reporter)

Comment 4

2 years ago
Yeah, this discussion belongs on bug 1263317, let's continue it there if necessary.

Updated

2 years ago
Flags: qe-verify-
Priority: -- → P2
(Reporter)

Updated

2 years ago
No longer blocks: 1263289

Updated

2 years ago
Blocks: 1263289
Whiteboard: [devtools-html]
You need to log in before you can comment on or make changes to this bug.