diff options
| author | Walter Erquinigo <wallace@fb.com> | 2021-07-12 11:46:36 -0700 |
|---|---|---|
| committer | Walter Erquinigo <wallace@fb.com> | 2021-07-12 13:22:25 -0700 |
| commit | 8ea1a630d66f4d70a7177c6eb522a3efff21b1be (patch) | |
| tree | 1e5193180fb5a707aa2162c54989a45a75174170 /lldb/unittests/Process/gdb-remote/GDBRemoteCommunicationClientTest.cpp | |
| parent | 7ed3e87825b48747bc5e4fb6daa1f08b543c4ec9 (diff) | |
| download | llvm-8ea1a630d66f4d70a7177c6eb522a3efff21b1be.zip llvm-8ea1a630d66f4d70a7177c6eb522a3efff21b1be.tar.gz llvm-8ea1a630d66f4d70a7177c6eb522a3efff21b1be.tar.bz2 | |
[vscode] fix ubsan problem in the progress event reporter
The error
UndefinedBehaviorSanitizer: undefined-behavior /Users/buildslave/jenkins/workspace/lldb-cmake-sanitized/llvm-project/lldb/tools/lldb-vscode/ProgressEvent.cpp:89:64 in
was found in https://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-sanitized/1910/consoleFull#-15641370498254eaf0-7326-4999-85b0-388101f2d404
It turns out that we were not setting m_event_type when initializatin
and update case. The fix is very simple.
Differential Revision: https://reviews.llvm.org/D105832
Diffstat (limited to 'lldb/unittests/Process/gdb-remote/GDBRemoteCommunicationClientTest.cpp')
0 files changed, 0 insertions, 0 deletions