summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/options/foo.cpp
diff options
context:
space:
mode:
authorAdam Balogh <adam.balogh@ericsson.com>2018-12-04 10:22:28 +0000
committerAdam Balogh <adam.balogh@ericsson.com>2018-12-04 10:22:28 +0000
commit42d241fc0b25d71c4c048019a25e286b8bd4bb6f (patch)
tree0a1a0e0f8c4155aa10036b61d17c588d7146e450 /lldb/packages/Python/lldbsuite/test/expression_command/options/foo.cpp
parent026cc2ff9552fa372bd5a38397fd0866d69fd96d (diff)
downloadbcm5719-llvm-42d241fc0b25d71c4c048019a25e286b8bd4bb6f.tar.gz
bcm5719-llvm-42d241fc0b25d71c4c048019a25e286b8bd4bb6f.zip
[Analyzer] Iterator Checkers - Use the region of the topmost base class for iterators stored in a region
If an iterator is represented by a derived C++ class but its comparison operator is for its base the iterator checkers cannot recognize the iterators compared. This results in false positives in very straightforward cases (range error when dereferencing an iterator after disclosing that it is equal to the past-the-end iterator). To overcome this problem we always use the region of the topmost base class for iterators stored in a region. A new method called getMostDerivedObjectRegion() was added to the MemRegion class to get this region. Differential Revision: https://reviews.llvm.org/D54466 llvm-svn: 348244
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/options/foo.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud