[llvm-bugs] [Bug 40175] New: ASTMatchers cause crash through an assertion

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=40175

            Bug ID: 40175
           Summary: ASTMatchers cause crash through an assertion
           Product: clang
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: development at jonas-toth.eu
                CC: htmldeveloper at gmail.com, llvm-bugs at lists.llvm.org,
                    neeilans at live.com, richard-llvm at metafoo.co.uk

Hi,

the newly introduced capabilities to limit the traversal-scope for the AST
Matchers triggers crashes for certain traversals. The revision introducing this
behaviour is https://reviews.llvm.org/D54309#1320628.

This bug: https://bugs.llvm.org/show_bug.cgi?id=39949
seems to come from the same underlying issue.

To reproduce the problem locally you can add this test-case
(https://github.com/JonasToth/clang/blob/fix_crash/unittests/Analysis/ExprMutationAnalyzerTest.cpp#L1134)
to your local clang. It was the minimal case I could create to show the
behaviour. It relies on the `ExprMutAnalyzer` to trigger the problem while
doing its analysis.

Removing the assertion (ASTMatchFinder.cpp L.680) "fixed" the problem in the
sense that the analysis succeeded and no other defects were visible. But that
is the case for the (old) full AST-Traversal and might differ in limited scope.

Given the condition manifests in an implemented check already we should work
that out before the 8.0 release, in my opinion.

Best, Jonas

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20181228/f53e3773/attachment.html>