summaryrefslogtreecommitdiffstats
path: root/doc/rtems_gdb/swarch.t
blob: 34b69253e7641895523ee300134d6de4561b3c75 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
@c
@c  COPYRIGHT (c) 1988-1999.
@c  On-Line Applications Research Corporation (OAR).
@c  All rights reserved.
@c
@c  $Id$
@c


@chapter Software Architecture

RTEMS/GDB host-target debugger is architectured around:

@itemize @bullet
@item One debugger, running on the host.
@item One debug server, running on the target.
@end itemize

The host debugger communicates with the debug server using Sun RPC
over UDP/IP (Ethernet).

When opening a debugging session, the user takes the control over
the entire target system. The target system is viewed as a single multi-threaded
process.

The debugger can observe the state of the system objects, without
stopping the entire system. However, breakpoints and stepping affect (stop)
the entire system.

For a given target, only one single system debugging session is possible
at a time.