From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add new cmd line parameter "--pid" for attach.
Date: Sat, 05 Jan 2002 13:12:00 -0000 [thread overview]
Message-ID: <3C376B1E.66517F6E@redhat.com> (raw)
In-Reply-To: <6436-Sat05Jan2002105609+0200-eliz@is.elta.co.il>
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]
Eli Zaretskii wrote:
>
> > Date: Fri, 4 Jan 2002 19:21:06 -0800
> > From: Michael Snyder <msnyder@cygnus.com>
> >
> > --command=FILE Execute GDB commands from FILE.\n\
> > --core=COREFILE Analyze the core dump COREFILE.\n\
> > + --pid=PID Attach to running process PID.\n\
> > ", stream);
>
> The new command-line option should be described in gdb.texinfo as
> well.
Sure. How's this?
[-- Attachment #2: pid.patch --]
[-- Type: text/plain, Size: 1033 bytes --]
2002-01-05 Michael Snyder <msnyder@redhat.com>
* gdb.texinfo (--pid): Document new command line option (attach).
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.62
diff -p -r1.62 gdb.texinfo
*** gdb.texinfo 2001/12/30 03:52:20 1.62
--- gdb.texinfo 2002/01/05 21:10:15
*************** Connect to process ID @var{number}, as w
*** 851,856 ****
--- 851,867 ----
(unless there is a file in core-dump format named @var{number}, in which
case @samp{-c} specifies that file as a core dump to read).
+ @item -pid @ver{number}
+ @itemx -p @var{number}
+ @cindex @code{--pid}
+ @cindex @code{-p}
+ Use @var{number} as a process ID to attach to.
+
+ @item -p @var{number}
+ Connect to process ID @var{number}, as with the @code{attach} command.
+ If there is no such process, @value{GDBN} will attempt to open a core
+ file named @var{number}.
+
@item -command @var{file}
@itemx -x @var{file}
@cindex @code{--command}
next prev parent reply other threads:[~2002-01-05 21:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 19:25 Michael Snyder
2002-01-05 0:59 ` Eli Zaretskii
2002-01-05 13:12 ` Michael Snyder [this message]
2002-01-06 0:04 ` Eli Zaretskii
2002-01-06 21:26 ` Michael Snyder
2002-01-07 1:20 ` Eli Zaretskii
2002-01-07 11:07 ` Michael Snyder
2002-01-07 12:28 ` Eli Zaretskii
2002-01-07 13:39 ` Michael Snyder
2002-01-07 16:14 ` Michael Snyder
2002-01-08 0:53 ` Eli Zaretskii
2002-01-08 15:15 ` Michael Snyder
2002-01-07 18:55 ` Elena Zannoni
2002-01-08 15:15 ` Michael Snyder
2002-01-08 16:59 ` Andrew Cagney
2002-01-10 13:09 ` Elena Zannoni
2002-01-10 16:20 ` Andrew Cagney
2002-01-10 16:46 ` Elena Zannoni
2002-01-11 2:19 ` Richard Earnshaw
2002-01-10 17:06 ` Michael Snyder
2002-01-10 17:28 ` Andrew Cagney
2002-01-10 17:56 ` Frank Ch. Eigler
2002-01-11 12:26 ` Michael Snyder
2002-01-10 23:53 ` Eli Zaretskii
2002-01-10 13:13 ` Elena Zannoni
2002-01-10 14:49 ` Michael Snyder
2002-01-10 15:02 ` Michael Snyder
2002-01-10 23:23 ` Eli Zaretskii
2002-01-11 12:24 ` Michael Snyder
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=3C376B1E.66517F6E@redhat.com \
--to=msnyder@redhat.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