Closed
Bug 729833
Opened 13 years ago
Closed 13 years ago
IonMonkey: Provide a js_DumpIonStack function to be able to locate the guilty line of a testcase
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: gkw, Assigned: nbp)
References
Details
Attachments
(1 file)
|
(deleted),
patch
|
dvander
:
review+
|
Details | Diff | Splinter Review |
As per f2f discussion with Nicolas, it seems difficult to find the line number of the line that the testcase is failing at.
Having a js_DumpIonStack function would be nice to print all ion frames of the last activation, including inline frames, providing function location, pc and (hopefully) line numbers.
What do you mean by failing? Like, if we hit an assert and want to dump the state of the world? That seems like a really good idea.
|
Reporter | |
Comment 2•13 years ago
|
||
> What do you mean by failing? Like, if we hit an assert and want to dump the
> state of the world? That seems like a really good idea.
Yes, an assert or probably a crash.
|
Assignee | |
Comment 3•13 years ago
|
||
Assignee: general → nicolas.b.pierron
Status: NEW → ASSIGNED
Attachment #603893 -
Flags: review?(dvander)
Comment on attachment 603893 [details] [diff] [review]
Add js_DumpBacktrace
r=me though it might be easier to just use fprintf instead of sprinter
Attachment #603893 -
Flags: review?(dvander) → review+
|
|
Assignee | |
Comment 5•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•