-
Notifications
You must be signed in to change notification settings - Fork 1.7k
devtools console reports incorrect line numbers for errors and prints #5851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Added Triaged label. |
This comment was originally written by [email protected] We need a debugger API method for retrieving current stack trace to fix this. See bug 2573 for details. |
This comment was originally written by [email protected] Added Triaged label. |
This comment was originally written by [email protected] Added this to the Later milestone. |
This comment was originally written by [email protected] Pavel, is there a VM bug we can use to mark this one as blocked on? If not, may I ask you to file one, please? |
This comment was originally written by [email protected] This bug is already marked as blocked on issue #2573. |
This is still a problem but it isn't blocked by 2573. |
Fixed with dartium r1461 Added Fixed label. |
DevTools console has a very handy feature that allows to quickly jump from the message printed to the place from where it originated. However it does not work with Dart code.
For messaged printed with print I see "undefined:1" as a location and for exceptions usually I see "file.dart:1".
Also DevTools source view shows red exception blobs at file.dart:1 position instead of showing them at the place where they actually occurred.
The text was updated successfully, but these errors were encountered: