Closed
Bug 1904992
Opened 1 year ago
Closed 1 year ago
Handle JSOp::AddDisposable in the stack dump in disassemble
Categories
(Core :: JavaScript Engine, task, P3)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
129 Branch
| Tracking | Status | |
|---|---|---|
| firefox129 | --- | fixed |
People
(Reporter: arai, Assigned: debadree333)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
The following code dumps the disassemble, with stack state
dis();
{
using x = {};
}
There, AddDisposable converts the OBJ value pushed by NewObject to <unknown>.
00015: 2 TryUsing #
00016: 3 NewObject {} # OBJ
00021: 3 AddDisposable # <unknown>
00022: 3 InitAliasedLexical "x" (hops = 0, slot = 3) # <unknown>
00027: 3 Pop #
it's because AddDisposable pops 1 value and pushes 1 value, as defined below,
* Stack: v => v
*/ \
IF_EXPLICIT_RESOURCE_MANAGEMENT(MACRO(AddDisposable, add_disposable, NULL, 1, 1, 1, JOF_BYTE)) \
but it's not handled by stack dump, which results in using "<unknown>".
switch (op) {
case JSOp::Arguments:
return write("arguments");
...
default:
break;
}
return write("<unknown>");
| Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Assignee: nobody → debadree333
Status: NEW → ASSIGNED
Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/e377861c75fb
Handle JSOp::AddDisposable in the stack dump in disassemble. r=arai
Comment 3•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox129:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 129 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•