diff options
| author | Artem Dergachev <artem.dergachev@gmail.com> | 2018-02-27 22:05:55 +0000 |
|---|---|---|
| committer | Artem Dergachev <artem.dergachev@gmail.com> | 2018-02-27 22:05:55 +0000 |
| commit | f119bf99e59f22c1ec7bb51478d671ce4bcc8f7e (patch) | |
| tree | 476fdb8117e34127ce77eedfe5b96e2cb7f16f02 /lldb/packages/Python/lldbsuite/test/python_api/frame/main.c | |
| parent | 8edd70b7c6cff63c9c8081b172115403ee189a3b (diff) | |
| download | bcm5719-llvm-f119bf99e59f22c1ec7bb51478d671ce4bcc8f7e.tar.gz bcm5719-llvm-f119bf99e59f22c1ec7bb51478d671ce4bcc8f7e.zip | |
[analyzer] UndefinedAssignmentChecker: Better warning message in implicit ctors.
When a class forgets to initialize a field in the constructor, and then gets
copied around, a warning is emitted that the value assigned to a specific field
is undefined.
When the copy/move constructor is implicit (not written out in the code) but not
trivial (is not a trivial memory copy, eg. because members have an explicit copy
constructor), the body of such constructor is auto-generated in the AST.
In this case the checker's warning message is squeezed at the top of
the class declaration, and it gets hard to guess which field is at fault.
Fix the warning message to include the name of the field.
Differential Revision: https://reviews.llvm.org/D43798
llvm-svn: 326258
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/frame/main.c')
0 files changed, 0 insertions, 0 deletions
