summaryrefslogtreecommitdiffstats
path: root/doc/rgdb_specs/conclusion.t
blob: b2ed9ca34007e491bb282d3fc326276f89a36c8c (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
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
@c
@c  RTEMS Remote Debugger Server Specifications
@c
@c  Written by: Eric Valette <valette@crf.canon.fr>
@c              Emmanuel Raguet <raguet@crf.canon.fr>
@c
@c
@c  $Id$
@c

@chapter Conclusion

In this document we have presented how we envisage to add remote debugging facilities
to RTEMS by implementing a remote debugger daemon for GDB. As any debug implemented
in software, it will have limitation but we are confident that most of them
can be removed by adding separate software components dedicated to debug activity.
We must keep in mind that even with this approach, no software will enable the
debug of code with interrupt entirely masked at processor level and that In
Circuit Emulator (ICE) or use of BDM extension on the target board are the ultimate
way to really debug any portion of an RTOS. BDM support in GDB is still weak
but people are working on it and we may get something better in a near future.

@ifset use-ascii
@example
@group
XXXXX reference it in the previous paragraph
XXXXX insert process.eps
XXXXX Caption remote debugger tasks and handlers
@end group
@end example
@end ifset

@ifset use-tex
@example
@group
@c XXXXX reference it in the previous paragraph
@c XXXXX insert process.eps
@c XXXXX Caption remote debugger tasks and handlers
@end group
@end example
@image{process,6in,}
@end ifset


@ifset use-html
@c <IMG SRC="process.jpg" WIDTH=500 HEIGHT=600 ALT="remote debugger tasks and handlers">
@html
<IMG SRC="process.jpg" ALT="remote debugger tasks and handlers">
@end html
@end ifset