source: rtems/doc/rtems_gdb/started.t @ 387f41a

4.104.114.84.95
Last change on this file since 387f41a was 387f41a, checked in by Joel Sherrill <joel.sherrill@…>, on 02/10/99 at 18:33:15

Base version.

  • Property mode set to 100644
File size: 1.2 KB
Line 
1@c
2@c  COPYRIGHT (c) 1988-1998.
3@c  On-Line Applications Research Corporation (OAR).
4@c  All rights reserved.
5@c
6@c  $Id$
7@c
8
9
10@section Getting Started
11
12This section describes the steps which are necessary to set up a
13debugging session with RTEMS/GDB.
14
15
16@subsection Compiling The System Components
17
18The components that need to be debugged have to be compiled with the -g option
19in order the generated file to contain the required information for the debug
20session.
21
22
23@subsection Starting a debugging session
24
25After having launched GDB, the user must connect to the RTEMS target with the
26following commands:
27
28@example
29
30(gdb) setrpcmode sun
31
32(gdb) setdaemontype rdbg
33
34(gdb) target rtems target-name
35
36@end example
37
38Then he can use the file GDB command to specify the binary to be debugged.
39
40This initialization phase can be written in a @code{``.gdbinit''}
41file. Each time, the user will launch GDB, it will execute this initialization
42sequence.
43
44
45@subsection Attaching To The System
46
47The entire target system is viewed as a single multi-threaded process,
48the identifier of which is 1. To attach, use:
49
50@example
51(gdb) attach 1
52@end example
53
54When successfully attached, the user can control the execution of
55the target system from the debugger.
56
57
Note: See TracBrowser for help on using the repository browser.