gdb/gdbserver/

[deliverable/binutils-gdb.git] / gdb / gdbserver / README

diff --git a/gdb/gdbserver/README b/gdb/gdbserver/README
index 71887cae2901a8b672b52954cc096ac9f88c19dc..9394198c0e844a9dec929bccd3abdacc137ad108 100644 (file)
--- a/gdb/gdbserver/README
+++ b/gdb/gdbserver/README
@@ -9,6 +9,8 @@ host.  GDB and GDBserver communicate using the standard remote serial protocol
 implemented in remote.c, and various *-stub.c files.  They communicate via
 either a serial line or a TCP connection.
 
+For more information about GDBserver, see the GDB manual.
+
 Usage (server (target) side):
 
 First, you need to have a copy of the program you want to debug put onto
@@ -47,7 +49,7 @@ print an error message and exit.
 On some targets, gdbserver can also attach to running programs.  This is
 accomplished via the --attach argument.  The syntax is:
 
-       target> gdbserver COMM --attach PID
+       target> gdbserver --attach COMM PID
 
 PID is the process ID of a currently running process.  It isn't necessary
 to point gdbserver at a binary for the running process.
@@ -77,14 +79,25 @@ command, otherwise you may get an error that looks something like
 
 Building gdbserver:
 
-The supported targets as of February 2002 are:
-       arm-*-linux-gnu
-       i386-*-linux-gnu
-       ia64-*-linux-gnu
-       m68k-*-linux-gnu
-       mips-*-linux-gnu
-       powerpc-*-linux-gnu
-       sh-*-linux-gnu
+The supported targets as of November 2006 are:
+       arm-*-linux*
+       crisv32-*-linux*
+       cris-*-linux*
+       i[34567]86-*-cygwin*
+       i[34567]86-*-linux*
+       i[34567]86-*-mingw*
+       ia64-*-linux*
+       m32r*-*-linux*
+       m68*-*-linux*
+       m68*-*-uclinux*
+       mips*64*-*-linux*
+       mips*-*-linux*
+       powerpc[64]-*-linux*
+       s390[x]-*-linux*
+       sh-*-linux*
+       spu*-*-*
+       x86_64-*-linux*
+       xscale*-*-linux*
 
 Configuring gdbserver you should specify the same machine for host and
 target (which are the machine that gdbserver is going to run on.  This