4.104.114.84.95
Rev | Line | |
---|
[387f41a] | 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 | @chapter Software Architecture |
---|
| 11 | |
---|
| 12 | RTEMS/GDB host-target debugger is architectured around: |
---|
| 13 | |
---|
| 14 | @itemize @bullet |
---|
| 15 | @item One debugger, running on the host. |
---|
| 16 | @item One debug server, running on the target. |
---|
| 17 | @end itemize |
---|
| 18 | |
---|
| 19 | The host debugger communicates with the debug server using Sun RPC |
---|
| 20 | over UDP/IP (Ethernet). |
---|
| 21 | |
---|
| 22 | When opening a debugging session, the user takes the control over |
---|
| 23 | the entire target system. The target system is viewed as a single multi-threaded |
---|
| 24 | process. |
---|
| 25 | |
---|
| 26 | The debugger can observe the state of the system objects, without |
---|
| 27 | stopping the entire system. However, breakpoints and stepping affect (stop) |
---|
| 28 | the entire system. |
---|
| 29 | |
---|
| 30 | For a given target, only one single system debugging session is possible |
---|
| 31 | at a time. |
---|
| 32 | |
---|
Note: See
TracBrowser
for help on using the repository browser.