From 387f41adcd32dff7b7de7fe34a8637692ee7c7b1 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Wed, 10 Feb 1999 18:33:15 +0000 Subject: Base version. --- doc/rtems_gdb/trouble.t | 48 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) create mode 100644 doc/rtems_gdb/trouble.t (limited to 'doc/rtems_gdb/trouble.t') diff --git a/doc/rtems_gdb/trouble.t b/doc/rtems_gdb/trouble.t new file mode 100644 index 0000000000..28999aac67 --- /dev/null +++ b/doc/rtems_gdb/trouble.t @@ -0,0 +1,48 @@ +@c +@c COPYRIGHT (c) 1988-1998. +@c On-Line Applications Research Corporation (OAR). +@c All rights reserved. +@c +@c $Id$ +@c + + +@section Troubleshooting + +This section describes symptoms in some situations where the debugger does not +work correctly, and it gives guidelines for resolving the problems encountered. + + +@subsection Target machine name unknown on the host + +RTEMS/GDB fails to connect to target machine named my_target: + +@example +(gdb) target rtems my_target + +Attaching remote machine across net... Invalid hostname. Couldn't find remote +host address. +@end example + +@i{==> Ask your system administrator to add an entry with the +Internet number of machine my_target in the file /etc/hosts on your host machine. } + + +@subsection{Debug server not present + +The target rtems command fails: + +@example + +(gdb) target rtems my\_target + +Attaching remote machine across net... RPC timed out. Couldn't connect +to remote target + +@end example + + +@i{==> Verify that the target system is properly configured, +and is running the debugging daemon and communication stack.} + + -- cgit v1.2.3