summaryrefslogtreecommitdiffstats
path: root/doc/rtems_gdb/swarch.t
diff options
context:
space:
mode:
Diffstat (limited to 'doc/rtems_gdb/swarch.t')
-rw-r--r--doc/rtems_gdb/swarch.t32
1 files changed, 32 insertions, 0 deletions
diff --git a/doc/rtems_gdb/swarch.t b/doc/rtems_gdb/swarch.t
new file mode 100644
index 0000000000..8e7eaf9840
--- /dev/null
+++ b/doc/rtems_gdb/swarch.t
@@ -0,0 +1,32 @@
+@c
+@c COPYRIGHT (c) 1988-2002.
+@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.
+