-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Analyzer null pointer crash when combining --strong and --warnings #26466
Comments
I think there are two problems here. The first problem is that we're throwing an exception while trying to resolve html_dartium.dart: Mismatch in DeclarationResolver while resolving .../dart-sdk/lib/html/dartium/html_dartium.dart #0 RecursiveAstVisitor&ExistingElementResolver._mismatch (package:analyzer/src/generated/resolver.dart:3457:5) This looks like it could be caused by a difference between the summaries and the file we're trying to resolve. The file defined a top-level variable named @scheglov Could you look into the first problem? The second problem is that dependencies can cross partition boundaries, but we didn't take that possibility into account. I'll look at how to fix that problem. |
This would correspond to the code in build_sdk_summaries.dart, which creates strong mode summaries. R=brianwilkerson@google.com, paulberry@google.com BUG= #26466 Review URL: https://codereview.chromium.org/1988853002 .
Additional fix https://codereview.chromium.org/2003863002 |
Eventually we might want to go over all of the code and sprinkle it with checks like with to avoid re-resolving what we already know, and to avoid updating parts of element model which cannot be updated because the element model is resynthesized from a summary. R=brianwilkerson@google.com BUG= #26466 Review URL: https://codereview.chromium.org/2003863002 .
This should solve the underlying problem: https://codereview.chromium.org/2008133002/ |
Analyzing a trivial file that just imports
dart:html
with current dev release (1.17-dev.3.0) or bleeding edge analyzer passing flags--strong --warnings
, produces the following crash:Code is:
The text was updated successfully, but these errors were encountered: