diff options
| author | Miro Bucko <mbucko@meta.com> | 2024-04-25 12:20:43 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-04-25 09:20:43 -0700 |
| commit | ef2ca97f48f1aee1483f0c29de5ba52979bec454 (patch) | |
| tree | fa40715e92dcecd1e8596ecc209eb33633c36dff /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp | |
| parent | f4e3daa562ce077c729634bd3ae8757aae8d46ef (diff) | |
| download | llvm-ef2ca97f48f1aee1483f0c29de5ba52979bec454.zip llvm-ef2ca97f48f1aee1483f0c29de5ba52979bec454.tar.gz llvm-ef2ca97f48f1aee1483f0c29de5ba52979bec454.tar.bz2 | |
[lldb-dap] Report exit status message in lldb-dap, same as lldb cli (#89405)
Summary:
When the target inferior process that is being debugged exits in lldb
command line, it emits following message:
`Process 4049526 exited with status = -1 (0xffffffff) debugserver died
with signal SIGTERM`
lldb-dap on the other hand does not emit a similar message. This PR adds
the same status message to lldb-dap.
Test Plan:
In VSCode debug any target and hit stop mode, kill lldb-server and
observe an exit status message similar to the following: Process 2167677
exited with status = -1 (0xffffffff) debugserver died with signal
SIGTERM
Reviewers:
@jeffreytan81,@clayborg,@kusmour,
Subscribers:
Tasks:
lldb-dap
Tags:
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp')
0 files changed, 0 insertions, 0 deletions