Author: Konrad Kleine Date: 2020-02-20T14:30:12+01:00 New Revision: c7b7f76ae6ae2a5f3d9753b37ef811da15386cd4
URL: https://github.com/llvm/llvm-project/commit/c7b7f76ae6ae2a5f3d9753b37ef811da15386cd4 DIFF: https://github.com/llvm/llvm-project/commit/c7b7f76ae6ae2a5f3d9753b37ef811da15386cd4.diff LOG: [lldb]: fix typo in lldb-gdb-remote.txt Summary: The logic of the sentence made more sense when "with" is replaced with "without". Reviewers: labath Subscribers: lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D74895 Added: Modified: lldb/docs/lldb-gdb-remote.txt Removed: ################################################################################ diff --git a/lldb/docs/lldb-gdb-remote.txt b/lldb/docs/lldb-gdb-remote.txt index 06cd09d77c41..276beedd047c 100644 --- a/lldb/docs/lldb-gdb-remote.txt +++ b/lldb/docs/lldb-gdb-remote.txt @@ -3,7 +3,7 @@ remote debugging. Why? Normally you need to start the correct GDB and the correct GDB server when debugging. If you have mismatch, then things go wrong very quickly. LLDB makes extensive use of the GDB remote protocol and we wanted to make sure that the experience was a bit more dynamic where we can -discover information about a remote target with having to know anything up +discover information about a remote target without having to know anything up front. We also ran into performance issues with the existing GDB remote protocol that can be overcome when using a reliable communications layer. Some packets improve performance, others allow for remote process launching _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits