diff options
| author | Artem Dergachev <artem.dergachev@gmail.com> | 2018-12-04 02:00:29 +0000 |
|---|---|---|
| committer | Artem Dergachev <artem.dergachev@gmail.com> | 2018-12-04 02:00:29 +0000 |
| commit | 60eb8c113b57176d9235db511ba9eadb1be92232 (patch) | |
| tree | ce24267fd1838ca696e7eaeabae36e3d6627e723 /lldb/packages/Python/lldbsuite/test/expression_command/call-function | |
| parent | 5b8d58592583e34ffbe180d36feaf10cef66ead5 (diff) | |
| download | bcm5719-llvm-60eb8c113b57176d9235db511ba9eadb1be92232.tar.gz bcm5719-llvm-60eb8c113b57176d9235db511ba9eadb1be92232.zip | |
[analyzer] MoveChecker: Improve warning and note messages.
The warning piece traditionally describes the bug itself, i.e.
"The bug is a _____", eg. "Attempt to delete released memory",
"Resource leak", "Method call on a moved-from object".
Event pieces produced by the visitor are usually in a present tense, i.e.
"At this moment _____": "Memory is released", "File is closed",
"Object is moved".
Additionally, type information is added into the event pieces for STL objects
(in order to highlight that it is in fact an STL object), and the respective
event piece now mentions that the object is left in an unspecified state
after it was moved, which is a vital piece of information to understand the bug.
Differential Revision: https://reviews.llvm.org/D54560
llvm-svn: 348229
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function')
0 files changed, 0 insertions, 0 deletions
