ARM64 simulator: Implement single-step profiling
Categories
(Core :: JavaScript Engine: JIT, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox129 | --- | fixed |
People
(Reporter: lth, Assigned: yury)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Reporter | ||
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Comment 1•6 years ago
|
||
For your information, I do not think this is necessary. I have been debugging using the simulator with the following gdb file to be sourced when I start debugging a process with the ARM64 simulator and this works like a charm. The only trick is that to make it work with rr
, you have to use rcc
instead of rc
.
This file adds a breakpoint at the location where the simulator is stepping, and enabling/disabling and displays the ARM64 instruction each time. The value of the registers are made available in the $x__ variables.
If needed we can move this file in the tree for a better debugging experience, but I do not think we need to add some interactive mode as part of the Simulator. From my experience, these interactive mode are worse than any integrated experience within gdb.
Comment 2•6 years ago
|
||
Since we all got ARM64 devices on hand, and the arm64.gdb script from the previous comment gives us enough tooling on top of the simulator, the simulator profiling (tracing) is no longer necessary.
Assignee | ||
Comment 3•6 months ago
|
||
We need this (for wasm stuff). I'll reopen it.
Assignee | ||
Comment 4•6 months ago
|
||
Updated•6 months ago
|
Description
•