From: Daniel Jacobowitz <drow@mvista.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] gdbserver --attach support
Date: Fri, 15 Feb 2002 08:01:00 -0000 [thread overview]
Message-ID: <20020215110124.A21634@nevyn.them.org> (raw)
In-Reply-To: <6137-Fri18Jan2002101403+0200-eliz@is.elta.co.il>
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
next prev parent reply other threads:[~2002-02-15 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 12:25 Daniel Jacobowitz
2002-01-17 12:31 ` Andrew Cagney
2002-01-17 12:46 ` Daniel Jacobowitz
2002-01-18 0:17 ` Eli Zaretskii
2002-02-15 8:01 ` Daniel Jacobowitz [this message]
2002-02-15 10:49 ` Eli Zaretskii
2002-02-15 11:06 ` Daniel Jacobowitz
2002-02-15 8:12 ` Daniel Jacobowitz
2002-02-15 10:51 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020215110124.A21634@nevyn.them.org \
--to=drow@mvista.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox