Re: [RFA] gdbserver --attach support

Daniel Jacobowitz
2002-02-15T16:01:43Z

On Fri, Jan 18, 2002 at 10:14:03AM +0200, Eli Zaretskii wrote:
> > Date: Thu, 17 Jan 2002 15:25:04 -0500
> > From: Daniel Jacobowitz <drow@mvista.com>
> >
> > Someone else did this some time ago, but got lost in the paper trail, I
> > think. This adds '--attach <pid>' as an alternative for 'prog [args...]'.
>
> How about documenting this in gdb.texinfo?

Well, that took me much too long. Eli, how's this? I haven't written
texinfo before, but I think I did OK.

--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer

2002-02-15 Daniel Jacobowitz <drow@mvista.com>

* gdb.texinfo: Document gdbserver ``--attach'' command.

Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.89
diff -u -r1.89 gdb.texinfo
--- gdb.texinfo 2002/02/08 00:39:45 1.89
+++ gdb.texinfo 2002/02/15 15:59:44
@@ -9956,7 +9956,7 @@
system does all the symbol handling.

To use the server, you must tell it how to communicate with @value{GDBN};
-the name of your program; and the arguments for your program. The
+the name of your program; and the arguments for your program. The usual
syntax is:

@smallexample
@@ -9992,6 +9992,16 @@
conflicts with another service, @code{gdbserver} prints an error message
and exits.} You must use the same port number with the host @value{GDBN}
@code{target remote} command.
+
+On some targets, @code{gdbserver} can also attach to running programs.
+This is accomplished via the @code{--attach} argument. The syntax is:
+
+@smallexample
+target> gdbserver @var{comm} --attach @var{PID}
+@end smallexample
+
+@var{PID} is the process ID of a currently running process. It isn't necessary
+to point @code{gdbserver} at a binary for the running process.

@item On the @value{GDBN} host machine,
you need an unstripped copy of your program, since @value{GDBN} needs