sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual: Did a re-org on the subsections of remote DBG section. 

Fixes YOCTO #3540

Realized that a better organization of the sub-sections could
be applied.  Pulled the last two sections up a level.

(From yocto-docs rev: d196db9bf1f88aa0677453396abdd61bf5d724dd)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-04-10 10:10:23 -07:00 committed by Richard Purdie
parent a4223949ad
commit 823ab7fc9e
1 changed files with 27 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -4016,41 +4016,41 @@
and the GDB prompt appears.
</para>
</section>
</section>
<section id='platdev-gdb-connect-to-the-remote-gdb-server'>
<title>Connect to the Remote GDB Server</title>
<section id='platdev-gdb-connect-to-the-remote-gdb-server'>
<title>Connect to the Remote GDB Server</title>
<para>
From the target, you need to connect to the remote GDB
server that is running on the host.
You need to specify the remote host and port.
Here is the command continuing with the example:
<literallayout class='monospaced'>
<para>
From the target, you need to connect to the remote GDB
server that is running on the host.
You need to specify the remote host and port.
Here is the command continuing with the example:
<literallayout class='monospaced'>
target remote 192.168.7.2:2345
</literallayout>
</para>
</section>
</literallayout>
</para>
</section>
<section id="platdev-gdb-remotedebug-launch-gdb-using">
<title>Use the Debugger</title>
<section id="platdev-gdb-remotedebug-launch-gdb-using">
<title>Use the Debugger</title>
<para>
You can now proceed with debugging as normal - as if you were debugging
on the local machine.
For example, to instruct GDB to break in the "main" function and then
continue with execution of the inferior binary use the following commands
from within GDB:
<literallayout class='monospaced'>
<para>
You can now proceed with debugging as normal - as if you were debugging
on the local machine.
For example, to instruct GDB to break in the "main" function and then
continue with execution of the inferior binary use the following commands
from within GDB:
<literallayout class='monospaced'>
(gdb) break main
(gdb) continue
</literallayout>
</para>
</literallayout>
</para>
<para>
For more information about using GDB, see the project's online documentation at
<ulink url="http://sourceware.org/gdb/download/onlinedocs/"/>.
</para>
</section>
<para>
For more information about using GDB, see the project's online documentation at
<ulink url="http://sourceware.org/gdb/download/onlinedocs/"/>.
</para>
</section>
</section>