aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKonrad Kleine <kkleine@redhat.com>2020-02-20 08:20:41 -0500
committerKonrad Kleine <kkleine@redhat.com>2020-02-20 14:30:12 +0100
commitc7b7f76ae6ae2a5f3d9753b37ef811da15386cd4 (patch)
tree83cfd839f0b22806f1db25b59cc86e4fc0fa1038
parent7b59ff2fa0a56a0158f3f21aaed217118da669a3 (diff)
downloadllvm-c7b7f76ae6ae2a5f3d9753b37ef811da15386cd4.zip
llvm-c7b7f76ae6ae2a5f3d9753b37ef811da15386cd4.tar.gz
llvm-c7b7f76ae6ae2a5f3d9753b37ef811da15386cd4.tar.bz2
[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
-rw-r--r--lldb/docs/lldb-gdb-remote.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/lldb/docs/lldb-gdb-remote.txt b/lldb/docs/lldb-gdb-remote.txt
index 06cd09d..276beed 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