David Spickett dfbe3a79e2 [lldb] Check that qLaunchGDBServer packet does not return an error ... While looking at https://github.com/llvm/llvm-project/issues/61955 I noticed that when we send qLaunchGDBServer we check that we got a response but not what kind of response it was. I think this was why the bug reporter saw: (lldb) run error: invalid host:port specification: '[192.168.64.2]' The missing port is because we went down a path we only should have chosen if the operation succeeded. Since we didn't check, we went ahead with an empty port number. To test this I've done the following: * Make a temporary copy of lldb-server. * Run that as a platform. * Remove the copy. * Attempt to create and run a target. This fails because the running lldb-server will try to invoke itself and it no longer exists. Reviewed By: jasonmolenda Differential Revision: https://reviews.llvm.org/D153513		2023-06-30 09:12:30 +00:00
..
API	[lldb] Check that qLaunchGDBServer packet does not return an error	2023-06-30 09:12:30 +00:00
Shell	[lldb] Make the test for D153043 linux-only	2023-06-20 07:57:47 +02:00
Unit	[NFC][Py Reformat] Reformat python files in lldb	2023-05-25 12:54:09 -07:00
CMakeLists.txt	[lldb] Remove reproducer test suite (NFC)	2023-05-26 09:33:40 -07:00
lit.cfg.py	[NFC][Py Reformat] Reformat python files in lldb	2023-05-25 12:54:09 -07:00
lit.site.cfg.py.in	Use lit_config.substitute instead of foo % lit_config.params everywhere	2022-03-16 09:57:41 +01:00