Follow up to an issue pointed out in the review of D73808. We shouldn't just pass in a nullptr TypeSourceInfo
in case Clang decided to access it.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
We have test coverage for this already, not sure why the sanitizer bot hasn't flagged this already: http://lab.llvm.org:8080/coverage/coverage-reports/coverage/Users/buildslave/jenkins/workspace/coverage/llvm-project/lldb/source/Plugins/TypeSystem/Clang/TypeSystemClang.cpp.html#L1302
Comment Actions
I think assigning a nullptr is fin as the constructor doesn't deference it. But I guess touching the decl in wrong way will cause Clang to touch the TypeSourceInfo?