dart2js should format V8 stack traces like the VM #12575
Labels
closed-obsolete
Closed as the reported issue is no longer relevant
P2
A bug or feature request we're likely to work on
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
web-dart2js
Comments
|
Unfortunately, Error.prepareStackTrace is not supported anymore :-( The V8 team has removed a lot of Error properties that dart2js used to take advantage of. I do think we should try to format stack traces, but I really don't think the VM's format is that readable. |
|
Worth noting that issue #13095 is now tracking potential improvements to the VM's stack trace format. |
|
I'm looking into removing the string representation of the exception. |
|
Added Started label. |
|
Added this to the M7 milestone. |
|
Removed this from the M7 milestone. |
|
Removed this from the Later milestone. |
|
Removed Oldschool-Milestone-Later label. |
kevmoo
added
P2
sigmundch
added
the
closed-obsolete
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
V8 provides an API for controlling the formatting of stack traces (see https://code.google.com/p/v8/wiki/JavaScriptStackTraceApi). dart2js should take advantage of this capability and make stack traces look like they do on the Dart VM.
This is especially important for V8 because the stack traces are otherwise very difficult to parse, since they include the string representation of the Exception itself. This means that the trace can include arbitrary text before the actual trace begins, making it impossible to parse accurately in some cases.
The text was updated successfully, but these errors were encountered: