From 387f41adcd32dff7b7de7fe34a8637692ee7c7b1 Mon Sep 17 00:00:00 2001
From: Joel Sherrill <joel.sherrill@OARcorp.com>
Date: Wed, 10 Feb 1999 18:33:15 +0000
Subject: Base version.

---
 doc/rtems_gdb/started.t | 57 +++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 57 insertions(+)
 create mode 100644 doc/rtems_gdb/started.t

(limited to 'doc/rtems_gdb/started.t')

diff --git a/doc/rtems_gdb/started.t b/doc/rtems_gdb/started.t
new file mode 100644
index 0000000000..e2b80b6c36
--- /dev/null
+++ b/doc/rtems_gdb/started.t
@@ -0,0 +1,57 @@
+@c
+@c  COPYRIGHT (c) 1988-1998.
+@c  On-Line Applications Research Corporation (OAR).
+@c  All rights reserved.
+@c
+@c  $Id$
+@c
+
+
+@section Getting Started
+
+This section describes the steps which are necessary to set up a
+debugging session with RTEMS/GDB.
+
+
+@subsection 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
+
+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.
+
+This initialization phase can be written in a @code{``.gdbinit''}
+file. Each time, the user will launch GDB, it will execute this initialization
+sequence.
+
+
+@subsection 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:
+
+@example
+(gdb) attach 1
+@end example
+
+When successfully attached, the user can control the execution of
+the target system from the debugger.
+
+
-- 
cgit v1.2.3