| Issue |
63466
|
| Summary |
Failure to launch lldb-server gdbserver is not explained by lldb
|
| Labels |
lldb
|
| Assignees |
|
| Reporter |
DavidSpickett
|
As seen in the test for https://reviews.llvm.org/D153513, when lldb-sever platform tries to launch lldb-server gdbserver and fails, the error is not explained to the user in lldb. Originally it wouldn't even report the packet error but with that patch it will but with no extra context.
We should have some mechanism to report that we didn't find lldb-server or that it had moved or permissions had changed etc.
In this case I triggered it by moving lldb-server after I had started the platform.
```
(lldb) run
lldb < 43> send packet: $qLaunchGDBServer;host:<host>;#f0
lldb < 7> read packet: $E09#ae
error: unable to launch a GDB server on '<host>'
```
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
