diff options
| author | John Harrison <harjohn@google.com> | 2025-10-21 15:21:27 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-21 15:21:27 -0700 |
| commit | e29d4ebb89705162b588caf69b45581f1da3a45c (patch) | |
| tree | 7fb801ce707e944cd01899b88b59a102036c4a68 /llvm/lib/Transforms/Utils/BasicBlockUtils.cpp | |
| parent | c89eb13e6e2b839ca4e6851849224a41d35f8637 (diff) | |
| download | llvm-e29d4ebb89705162b588caf69b45581f1da3a45c.zip llvm-e29d4ebb89705162b588caf69b45581f1da3a45c.tar.gz llvm-e29d4ebb89705162b588caf69b45581f1da3a45c.tar.bz2 | |
[lldb-dap] Correct lldb-dap `seq` handling. (#164306)
We've been treating the `seq` attribute incorrectly in lldb-dap.
Previously, we always had `seq=0` for events and responses. We only
filled in the `seq` field on reverse requests.
However, looking at the spec and other DAP implementations, we are
supposed to fill in the `seq` field for each request we send to the DAP
client.
I've updated our usage to fill in `seq` in `DAP::Send` so that all
events/requests/responses have a properly filled `seq` value.
Diffstat (limited to 'llvm/lib/Transforms/Utils/BasicBlockUtils.cpp')
0 files changed, 0 insertions, 0 deletions