summaryrefslogtreecommitdiffstats
path: root/doc/rtems_gdb/started.t
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>1999-02-10 18:54:14 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>1999-02-10 18:54:14 +0000
commit7b597b85405cb0740cbe57af7c1ad5f0cb665b18 (patch)
treebe365fce3d93a30944750dc99ad650700f321ad6 /doc/rtems_gdb/started.t
parentBase file. (diff)
downloadrtems-7b597b85405cb0740cbe57af7c1ad5f0cb665b18.tar.bz2
Now generates HTML, PostScript, and info correctly.
Diffstat (limited to 'doc/rtems_gdb/started.t')
-rw-r--r--doc/rtems_gdb/started.t12
1 files changed, 4 insertions, 8 deletions
diff --git a/doc/rtems_gdb/started.t b/doc/rtems_gdb/started.t
index e2b80b6c36..c639001235 100644
--- a/doc/rtems_gdb/started.t
+++ b/doc/rtems_gdb/started.t
@@ -7,32 +7,28 @@
@c
-@section Getting Started
+@chapter Getting Started
This section describes the steps which are necessary to set up a
debugging session with RTEMS/GDB.
-@subsection Compiling The System Components
+@section Compiling The System Components
The components that need to be debugged have to be compiled with the -g option
in order the generated file to contain the required information for the debug
session.
-@subsection Starting a debugging session
+@section Starting a debugging session
After having launched GDB, the user must connect to the RTEMS target with the
following commands:
@example
-
(gdb) setrpcmode sun
-
(gdb) setdaemontype rdbg
-
(gdb) target rtems target-name
-
@end example
Then he can use the file GDB command to specify the binary to be debugged.
@@ -42,7 +38,7 @@ file. Each time, the user will launch GDB, it will execute this initialization
sequence.
-@subsection Attaching To The System
+@section Attaching To The System
The entire target system is viewed as a single multi-threaded process,
the identifier of which is 1. To attach, use: