diff options
| author | Pavel Labath <labath@google.com> | 2018-03-21 11:10:57 +0000 |
|---|---|---|
| committer | Pavel Labath <labath@google.com> | 2018-03-21 11:10:57 +0000 |
| commit | 03a77e9a3909037e88d5479557a61275702b7f7c (patch) | |
| tree | b1d7b907bb18d978327413141d5f2483e04650df /llvm/unittests/BinaryFormat | |
| parent | 369e97511db857e3b2c100eab61af0319eec0179 (diff) | |
| download | bcm5719-llvm-03a77e9a3909037e88d5479557a61275702b7f7c.tar.gz bcm5719-llvm-03a77e9a3909037e88d5479557a61275702b7f7c.zip | |
Fix crash exposed by r328025
The issue was that the ASTDumper was being passed a null pointer
(because we did not create any declaration for the operator==). The
crash was in logging code, so it only manifested it self if you ran the
tests with logging enabled (like our bots do).
Given that this is logging code and the rest of the debugger is fine
with the declaration being null, I just make sure the logging code can
handle it as well. Right now I just do the null check in
ClangExpressionDeclMap, but if the ASTDumper class is meant to be a
debugging/logging aid, then it might be a good idea move the check
inside the class itself.
llvm-svn: 328088
Diffstat (limited to 'llvm/unittests/BinaryFormat')
0 files changed, 0 insertions, 0 deletions
