summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2017-05-02 00:50:10 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-05-10 11:13:32 (GMT)
commitd815dfbea379b427bdad10f6f8cdaf6a3d484306 (patch)
tree3b8402f4d9f6d38cc10a928715a5f0e55b2a714b
parentcbea3d8b6b1964fc3e6b4f6d30123300863d7237 (diff)
downloadpoky-d815dfbea379b427bdad10f6f8cdaf6a3d484306.tar.gz
dev-manual: Cleaned up "Gdbserver" term
This should be "gdbserver" when referred to generically. (From yocto-docs rev: 83b2be50e34b0c07cce1f27b55e595752b80b3ea) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml32
1 files changed, 16 insertions, 16 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 15530b2..d63df4d 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -10665,16 +10665,16 @@
10665 </para> 10665 </para>
10666 10666
10667 <para> 10667 <para>
10668 To help get past the previously mentioned constraints, you can use Gdbserver. 10668 To help get past the previously mentioned constraints, you can use
10669 Gdbserver runs on the remote target and does not load any debugging information 10669 gdbserver, which runs on the remote target and does not load any
10670 from the debugged process. 10670 debugging information from the debugged process.
10671 Instead, a GDB instance processes the debugging information that is run on a 10671 Instead, a GDB instance processes the debugging information that is run on a
10672 remote computer - the host GDB. 10672 remote computer - the host GDB.
10673 The host GDB then sends control commands to Gdbserver to make it stop or start the debugged 10673 The host GDB then sends control commands to gdbserver to make it stop or start the debugged
10674 program, as well as read or write memory regions of that debugged program. 10674 program, as well as read or write memory regions of that debugged program.
10675 All the debugging information loaded and processed as well 10675 All the debugging information loaded and processed as well
10676 as all the heavy debugging is done by the host GDB. 10676 as all the heavy debugging is done by the host GDB.
10677 Offloading these processes gives the Gdbserver running on the target a chance to remain 10677 Offloading these processes gives the gdbserver running on the target a chance to remain
10678 small and fast. 10678 small and fast.
10679 </para> 10679 </para>
10680 10680
@@ -10685,7 +10685,7 @@
10685 with their debugging information and also be sure the target is compiled with no optimizations. 10685 with their debugging information and also be sure the target is compiled with no optimizations.
10686 The host GDB must also have local access to all the libraries used by the 10686 The host GDB must also have local access to all the libraries used by the
10687 debugged program. 10687 debugged program.
10688 Because Gdbserver does not need any local debugging information, the binaries on 10688 Because gdbserver does not need any local debugging information, the binaries on
10689 the remote target can remain stripped. 10689 the remote target can remain stripped.
10690 However, the binaries must also be compiled without optimization 10690 However, the binaries must also be compiled without optimization
10691 so they match the host's binaries. 10691 so they match the host's binaries.
@@ -10728,7 +10728,7 @@
10728 the partial filesystem with the full filesystem. 10728 the partial filesystem with the full filesystem.
10729 </para></listitem> 10729 </para></listitem>
10730 <listitem><para> 10730 <listitem><para>
10731 <emphasis>Configure the system to include Gdbserver in 10731 <emphasis>Configure the system to include gdbserver in
10732 the target filesystem:</emphasis></para> 10732 the target filesystem:</emphasis></para>
10733 10733
10734 <para>Make the following addition in either your 10734 <para>Make the following addition in either your
@@ -10825,18 +10825,18 @@
10825 <listitem><para> 10825 <listitem><para>
10826 <emphasis>Debug a program:</emphasis></para> 10826 <emphasis>Debug a program:</emphasis></para>
10827 10827
10828 <para>Debugging a program involves running Gdbserver 10828 <para>Debugging a program involves running gdbserver
10829 on the target and then running Gdb on the host. 10829 on the target and then running Gdb on the host.
10830 The example in this step debugs 10830 The example in this step debugs
10831 <filename>gzip</filename>: 10831 <filename>gzip</filename>:
10832 <literallayout class='monospaced'> 10832 <literallayout class='monospaced'>
10833 root@qemux86:~# gdbserver localhost:1234 /bin/gzip —help 10833 root@qemux86:~# gdbserver localhost:1234 /bin/gzip —help
10834 </literallayout> 10834 </literallayout>
10835 For additional Gdbserver options, see the 10835 For additional gdbserver options, see the
10836 <ulink url='https://www.gnu.org/software/gdb/documentation/'>Gdb Server Documentation</ulink>. 10836 <ulink url='https://www.gnu.org/software/gdb/documentation/'>GDB Server Documentation</ulink>.
10837 </para> 10837 </para>
10838 10838
10839 <para>After running Gdbserver on the target, you need 10839 <para>After running gdbserver on the target, you need
10840 to run Gdb on the host and configure it and connect to 10840 to run Gdb on the host and configure it and connect to
10841 the target. 10841 the target.
10842 Use these commands: 10842 Use these commands:
@@ -10906,10 +10906,10 @@
10906 </section> 10906 </section>
10907 10907
10908 <section id="platdev-gdb-remotedebug-launch-gdbserver"> 10908 <section id="platdev-gdb-remotedebug-launch-gdbserver">
10909 <title>Launch Gdbserver on the Target</title> 10909 <title>Launch gdbserver on the Target</title>
10910 10910
10911 <para> 10911 <para>
10912 Make sure Gdbserver is installed on the target. 10912 Make sure gdbserver is installed on the target.
10913 If it is not, install the package 10913 If it is not, install the package
10914 <filename>gdbserver</filename>, which needs the 10914 <filename>gdbserver</filename>, which needs the
10915 <filename>libthread-db1</filename> package. 10915 <filename>libthread-db1</filename> package.
@@ -10917,15 +10917,15 @@
10917 10917
10918 <para> 10918 <para>
10919 Here is an example, that when entered from the host, 10919 Here is an example, that when entered from the host,
10920 connects to the target and launches Gdbserver in order to 10920 connects to the target and launches gdbserver in order to
10921 "debug" a binary named <filename>helloworld</filename>: 10921 "debug" a binary named <filename>helloworld</filename>:
10922 <literallayout class='monospaced'> 10922 <literallayout class='monospaced'>
10923 $ gdbserver localhost:2345 /usr/bin/helloworld 10923 $ gdbserver localhost:2345 /usr/bin/helloworld
10924 </literallayout> 10924 </literallayout>
10925 Gdbserver should now be listening on port 2345 for debugging 10925 gdbserver should now be listening on port 2345 for debugging
10926 commands coming from a remote GDB process that is running on 10926 commands coming from a remote GDB process that is running on
10927 the host computer. 10927 the host computer.
10928 Communication between Gdbserver and the host GDB are done 10928 Communication between gdbserver and the host GDB are done
10929 using TCP. 10929 using TCP.
10930 To use other communication protocols, please refer to the 10930 To use other communication protocols, please refer to the
10931 <ulink url='http://www.gnu.org/software/gdb/'>Gdbserver documentation</ulink>. 10931 <ulink url='http://www.gnu.org/software/gdb/'>Gdbserver documentation</ulink>.