aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectSource.cpp
diff options
context:
space:
mode:
authorRoy Shi <royitaqi@users.noreply.github.com>2025-09-04 16:35:06 -0700
committerGitHub <noreply@github.com>2025-09-04 16:35:06 -0700
commit10bcf0c0d81c87eab09aeadfe0565ff1aa4a138e (patch)
tree40ed7c774d4260ae648a643253a08f5f11a31818 /lldb/source/Commands/CommandObjectSource.cpp
parent7bee9d958bb8ad6faca598ff30bcb59fe11fa678 (diff)
downloadllvm-10bcf0c0d81c87eab09aeadfe0565ff1aa4a138e.zip
llvm-10bcf0c0d81c87eab09aeadfe0565ff1aa4a138e.tar.gz
llvm-10bcf0c0d81c87eab09aeadfe0565ff1aa4a138e.tar.bz2
[lldb-dap] Destroy debugger when debug session terminates (#156231)
# Patch Currently, in Server Mode (i.e. `--connection`), all debuggers are destroyed when the **lldb-dap process** terminates. This causes logging and release of resources to be delayed. This can also cause congestion if multiple debuggers have the same destroy callbacks, which will fight for the same resources (e.g. web requests) at the same time. Instead, the debuggers can be destroyed as early as when the **debug session** terminates. This way, logging and release of release of resources can happen as soon as possible. Congestion can also be naturally reduced, because it's unlikely that all debug sessions will terminate at the same time. # Tests See PR #156231.
Diffstat (limited to 'lldb/source/Commands/CommandObjectSource.cpp')
0 files changed, 0 insertions, 0 deletions