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
Cannot evaluate private members in other libraries from debugging tools #13811
Comments
Is still an issue? Added this to the M9 milestone. |
I believe this is fixed with the package selector mechanism |
This is still an issue. |
Removed this from the 1.6 milestone. |
Removed Oldschool-Milestone-1.6 label. |
Now that the Dart Dev Compiler and the Dart VM are both running with the CFE we should investigate solving this issue. DDC had a reasonable solution using dloadRepl and replNameLookup helpers to evaluate private members where possible. It would be great to have an option in the CFE to perform resolution of privates in a repl friendly manner permitting privates from all libraries. In the static case the CFE would resolve to the appropriate private and in the dynamic case DDC and the DartVM would need to have a fallback slow path like In practice, very few privates are defined in multiple objects on the same library so most of the time invoking privates just works with this solution. In the rare case it doesn't. users get a reasonable error explaining why it was not permitted. |
This issue recently came up on dart-misc |
Fyi @alan-knight who now owns eval support for the Dart Dev Compiler. |
At a breakpoint in a library method of a type which is subclassed in a separate library, I cannot evaluate private fields.
The text was updated successfully, but these errors were encountered: