projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 5614438) | patch
[lldb/gdb-server] Better reporting of launch errors
authorPavel Labath <pavel@labath.sk>
Tue, 27 Sep 2022 18:04:10 +0000 (20:04 +0200)
committerPavel Labath <pavel@labath.sk>
Thu, 6 Oct 2022 15:18:51 +0000 (17:18 +0200)
commit8d1de7b34af46a089eb5433c700419ad9b2923ee
tree4ba7c2f22668cfa698f48fc3a7602b06652dbf0ftree | snapshot
parent561443818a15e7b368ddbb58207a14c60ba55c58commit | diff
[lldb/gdb-server] Better reporting of launch errors

Use our "rich error" facility to propagate error reported by the stub to
the user. lldb-server reports rich launch errors as of D133352.

To make this easier to implement, and reduce code duplication, I have
moved the vRun/A/qLaunchSuccess handling into a single
GDBRemoteCommunicationClient function.

Differential Revision: https://reviews.llvm.org/D134754
lldb/source/Plugins/Platform/gdb-server/PlatformRemoteGDBServer.cpp diff | blob | history
lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp diff | blob | history
lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.h diff | blob | history
lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp diff | blob | history
lldb/test/API/functionalities/gdb_remote_client/TestGDBRemoteClient.py diff | blob | history
Domain: System / Toolchain;