source: rtems/doc/rtems_gdb/started.t @ 26f9f12

4.104.114.84.95
Last change on this file since 26f9f12 was 6449498, checked in by Joel Sherrill <joel.sherrill@…>, on Jan 17, 2002 at 9:47:47 PM

2001-01-17 Joel Sherrill <joel@…>

  • SUPPORT, LICENSE: New files.
  • Numerous files touched as part of merging the 4.5 branch onto the mainline development trunk and ensuring that the script that cuts snapshots and releases works on the documentation.
  • Property mode set to 100644
File size: 1.2 KB
Line 
1@c
2@c  COPYRIGHT (c) 1988-2002.
3@c  On-Line Applications Research Corporation (OAR).
4@c  All rights reserved.
5@c
6@c  $Id$
7@c
8
9
10@chapter Getting Started
11
12This section describes the steps which are necessary to set up a
13debugging session with RTEMS/GDB.
14
15
16@section 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@section 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(gdb) setrpcmode sun
30(gdb) setdaemontype rdbg
31(gdb) target rtems target-name
32@end example
33
34Then he can use the file GDB command to specify the binary to be debugged.
35
36This initialization phase can be written in a @code{``.gdbinit''}
37file. Each time, the user will launch GDB, it will execute this initialization
38sequence.
39
40
41@section Attaching To The System
42
43The entire target system is viewed as a single multi-threaded process,
44the identifier of which is 1. To attach, use:
45
46@example
47(gdb) attach 1
48@end example
49
50When successfully attached, the user can control the execution of
51the target system from the debugger.
52
53
Note: See TracBrowser for help on using the repository browser.