summaryrefslogtreecommitdiffstats
path: root/lldb/docs
diff options
context:
space:
mode:
authorColin Riley <colin@codeplay.com>2013-11-20 12:35:52 +0000
committerColin Riley <colin@codeplay.com>2013-11-20 12:35:52 +0000
commit4442546be9dc78d2f46b0afb62aac03a3b2b40d6 (patch)
treebcd36fa338c0b3f1f0ee97b32e833b03df2f9e5f /lldb/docs
parentc0bfa8c2310fd415886835f130c01a660bca8940 (diff)
downloadbcm5719-llvm-4442546be9dc78d2f46b0afb62aac03a3b2b40d6.tar.gz
bcm5719-llvm-4442546be9dc78d2f46b0afb62aac03a3b2b40d6.zip
Test commit. Capitalize 'os'.
llvm-svn: 195242
Diffstat (limited to 'lldb/docs')
-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 18e23e63c33..9a51383a71a 100644
--- a/lldb/docs/lldb-gdb-remote.txt
+++ b/lldb/docs/lldb-gdb-remote.txt
@@ -10,7 +10,7 @@ Some packets improve performance, others allow for remote process launching
(if you have an OS), and others allow us to dynamically figure out what
registers a thread might have. Again with GDB, both sides pre-agree on how the
registers will look (how many, their register number,name and offsets). We
-prefer to be able to dynamically determine what kind of architecture, os and
+prefer to be able to dynamically determine what kind of architecture, OS and
vendor we are debugging, as well as how things are laid out when it comes to
the thread register contexts. Below are the details on the new packets we have
added above and beyond the standard GDB remote protocol packets.
OpenPOWER on IntegriCloud