summaryrefslogtreecommitdiffstats
path: root/doc/rgdb_specs/conclusion.t
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--doc/rgdb_specs/conclusion.t33
1 files changed, 0 insertions, 33 deletions
diff --git a/doc/rgdb_specs/conclusion.t b/doc/rgdb_specs/conclusion.t
deleted file mode 100644
index abc6137966..0000000000
--- a/doc/rgdb_specs/conclusion.t
+++ /dev/null
@@ -1,33 +0,0 @@
-@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.
-
-@ifclear use-html
-@image{process,6in,,"Remote debugger tasks and handlers"}
-@end ifclear
-
-@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
-