diff options
| author | Alex Lorenz <arphaman@gmail.com> | 2017-05-04 13:56:51 +0000 |
|---|---|---|
| committer | Alex Lorenz <arphaman@gmail.com> | 2017-05-04 13:56:51 +0000 |
| commit | ce4518f21d55eee34d891db39baaeb471ee79397 (patch) | |
| tree | 2ecb31b59758120d7cf3edf2fff626e304c0a9be /lldb/packages/Python/lldbsuite/test/functionalities/non-overlapping-index-variable-i | |
| parent | 66af84bfc008ca9fce242310724a2e8313386049 (diff) | |
| download | bcm5719-llvm-ce4518f21d55eee34d891db39baaeb471ee79397.tar.gz bcm5719-llvm-ce4518f21d55eee34d891db39baaeb471ee79397.zip | |
DiagnosticsEngine should clear DelayedDiagID before reporting the
delayed diagnostic
This fix avoids an infinite recursion that was uncovered in one of our internal
tests by r301992. The testcase is the most reduced version of that
auto-generated test.
This is an improved version of the reverted commit r302037. The previous fix
actually managed to expose another subtle bug whereby `fatal_too_many_errors`
error was reported twice, with the second report setting the
`FatalErrorOccurred` flag. That prevented the notes that followed the diagnostic
the caused `fatal_too_many_errors` to be emitted. This commit ensures that notes
that follow `fatal_too_many_errors` but that belong to the diagnostic that
caused `fatal_too_many_errors` won't be emitted by setting the
`FatalErrorOccurred` when emitting `fatal_too_many_errors`.
rdar://31962618
llvm-svn: 302151
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities/non-overlapping-index-variable-i')
0 files changed, 0 insertions, 0 deletions
