diff options
| author | Craig Topper <craig.topper@gmail.com> | 2015-11-26 05:51:54 +0000 |
|---|---|---|
| committer | Craig Topper <craig.topper@gmail.com> | 2015-11-26 05:51:54 +0000 |
| commit | 5e35e669a58fad4f39ecea7289f5271fe89dafb9 (patch) | |
| tree | 436a44fb8ba74c27b481db8c80f37cd3183dd8c0 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp | |
| parent | a52e2b22e68e427972f72188073b1c74a4758ebd (diff) | |
| download | bcm5719-llvm-5e35e669a58fad4f39ecea7289f5271fe89dafb9.tar.gz bcm5719-llvm-5e35e669a58fad4f39ecea7289f5271fe89dafb9.zip | |
[Diagnostics] Call setMapping on the correct diagnostic states in a few places. GetCurDiagState() was being used when it shouldn't be.
I spotted this by inspection in the for loop that wasn't using its iterator and was just acting on the current state repeatedly.
This appears to have been introduced as a copy and paste bug in r140763 over 4 years ago.
I have no idea how to test this. I just went back to the original commit and tried to use the variables it was using before that.
llvm-svn: 254134
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp')
0 files changed, 0 insertions, 0 deletions
